SD / 06.2026 FACTS · NBS · NELNET

Strategic Integration

A framework. A foundation. A case for the role.

Stephen M. Doherty · Prepared for Mary Boisen
01The cycle, compressedi 02The call center is the research instrumentii 03The 90-day planiii 04What earns the first 90 daysiv 05What the diagnostic surfacesv 06What the foundation looks likevi 07What this isvii
§ 01 The cycle, compressed

The cycle, compressed.

An operational hunch travels a long path through standard channels. That path is built for products that ship to customers. It is not built for the tools operations needs by Friday.

STANDARD PATH FOR AN OPERATIONAL IMPROVEMENT multiple teams · multiple gates · iteration restarts the cycle OPERATIONS PRODUCT ENGINEERING notice friction draft request test review prioritize roadmap plan build QA handoff → handoff → ← handoff weeks-to-months · 3+ teams · prioritization gates at every transition · iteration sends you back to product COMPRESSED PATH · DIAGNOSTIC + BUILD IN ONE HEAD single team · zero handoffs · graduates as a working tool TRANSFORMATION Build D 0–3 Test D 4–7 Iterate D 7–14 Validate D 14–21 Graduate D 21+ ~3 weeks to validated pilot · iterations: hours-to-days · graduates to engineering pre-validated

Every operational improvement that has been wanted has been gated by the standard cycle. When the diagnostic and the build live in the same head, the gating changes. First iteration: days. Next iteration: hours. The platform that emerges learns from itself. Improvement compounds.

§ 02 The research instrument

The call center is the research instrument.

It is currently read as a cost center. It is, in fact, the highest-fidelity continuous research instrument in the organization. Every call that reaches an agent represents a failure somewhere upstream.

Where the function is today
Reactive call rate

Every contact begins after a family or school has already hit a wall. Goes down only by reducing access. Or when families give up.

Reactive · does not compound.
→
Where the function is going
Proactive resolution rate

Needs met before they become a call. Calls that do happen are resolved through integrated handling, not manual assembly. The customer is anticipated, not deflected.

Proactive · compounds.

Three categories. Three proactive paths.

The proportions among these three determine where the highest-leverage interventions live. Each category has a distinct path from reactive to proactive. The diagnostic's first deliverable is naming the actual ratio at FACTS.

34%

Informational

Family or school needed to know something they could not find.

Proactive path Self-service surfaces that anticipate the question.
41%

Procedural

They needed to do something they could not do themselves.

Proactive path Workflow automation that completes the action without an agent.
25%

Structural

Something broke upstream and they are calling to recover.

Proactive path Upstream engineering that prevents the breakage.

Mock distribution drawn against representative operational data. The actual ratios are the diagnostic's first deliverable.

From human translators to cognitive bridge

The integration gap, and the bridge that closes it.

Today · the gap

A K-12 school's business office calls the Client Center because a family has hit a system limit they can't navigate alone. The school has already performed one translation, turning what the family said into a question that fits the data model. Inside the call, an agent performs the second: manual lookup, re-entry, cross-reference across CRM, Plan Management, Aid, and Enrollment. Two layers of human middleware. The cost hides inside Average Handle Time as though it were a service cost. It is a design cost.

Tomorrow · the closer

AI bridges the way families talk ("my daughter is starting in the fall and I don't know what's next") to the way data models are organized. Schools have been the human translators. AI becomes the new one — routing, pre-filling, escalating only when judgment is genuinely required. Work pre-AI software literally could not do.

The bridge agent today AI tomorrow CRM family record Plan Mgmt payment schedule Aid Records award status Enrollment school + grade manual lookup · re-entry · cross-reference
§ 03 The 90-day plan

The 90-day plan.

Listening, mapping, and shipping happen concurrently. The diagnostic itself produces an artifact. Day 90 ends not with a plan but with one seam visibly closed.

30 days
DIAGNOSTIC

Listen and map.

  1. W1

    Land. Survey deployed day one. Seat-time scheduled. Transcript and ticket pulls initiated.

  2. W2

    Five streams running in parallel. Seat-time alongside agents. Working sessions with Mary on cross-divisional context.

  3. W3

    Pattern emergence. Cluster the survey, score the transcripts, map the ticket graveyard.

  4. W4

    Diagnostic locked in operators' own language. Candidate seams ranked on pain × structural leverage.

Artifact delivered

Documented diagnostic in operators' own language. Ranked candidate seams, scored on pain × structural leverage.

60 days
SELECTION

Choose and commit.

  1. W5

    Seam selected. Written rationale: why this one, why not the others, what its closure unlocks.

  2. W6

    Sandbox build begins. Outcomes pre-declared in writing: what success looks like by day 90.

  3. W7

    First working slice in the sandbox. Reviewed with Mary and the affected MD against operator feedback.

  4. W8

    Integration in active build, declared outcomes locked. Pilot operators identified and briefed.

Artifact delivered

Written rationale: why this seam, how its closure enables the next. An integration in active build with pre-declared outcomes.

90 days
PROOF

Ship and measure.

  1. W9

    Pilot deployed to a controlled subset of the client service team. Day-one usage instrumented.

  2. W10

    Live measurement against the Day 60 declaration. Operator feedback drives same-week iteration.

  3. W11

    Stabilization. Adoption pattern visible. The integration works inside the actual workflow, not the planned one.

  4. W12

    Quantified impact and roadmap for the next two seams. A working integration handed over — not a slide, not a plan.

Artifact delivered

A working integration deployed to real operators — not a slide, not a plan. Quantified impact. Roadmap for what closes next.

§ 04 What earns the first 90 days

What earns the first 90 days.

Five streams converge into a ranked list of candidate seams. Five scoring dimensions decide which one closes first. Structural leverage lives at the intersection, not in any single dimension.

↓ ↓ ↓ ↓ ↓
Ranked candidate seams
↓

Five scoring dimensions.

Applied jointly to every candidate. The first project must score highest on the intersection — its success or failure determines organizational belief in the model.

01
Pain Severity

Breadth of impact across the operations team.

02
Signal Clarity

How well the root cause is understood — visible enough to diagnose and solve in 90 days.

03
Scope Containment

Buildable and validatable in the sandbox without multi-department coordination.

04
Demonstrability

Anyone in the building can immediately understand the before and the after.

05
Compounding Potential

Solving it creates reusable infrastructure that accelerates the next solution.

§ 05 What the diagnostic surfaces

What the diagnostic surfaces.

The five streams produce signal. Connected, they answer the questions below. The call center stops being a cost center. It is a research instrument.

Diagnostic Query Surface Illustrative — representative mock data

Each query has a name now because someone is paying attention. The dataset that enables it has existed for years. What was missing was the instrument that could read it.

§ 06 What the foundation looks like

What the foundation looks like.

What follows is a nervous system. I believe it will, in time, be the foundation strategic integration is built upon. The architecture isn't drawn in full yet — but it can be recognized. The first 90 days tie the pieces together.

A school administrator emails about a mid-year transfer. An orchestrator agent reads it, identifies the account, fetches context, and posts unresolved questions to a dispatcher. Domain agents investigate. The synthesis is drafted in the Account Manager's voice. The AM reviews, edits, and sends. Every edit is captured as the system's continuous learning signal.

Ready

Press Replay to watch the inquiry land, decompose, and return as a reviewable draft.

#inquiries Inbound client inquiries
§ 07 What this is

What this is.

The diagnosis is mine. The architecture is mine. The build is mine. The measurement instrument is mine. Diagnostic judgment and technical execution living in the same head: that combination is the function. Everything else is staffing detail.

The function this document describes — diagnostic judgment, architectural design, technical execution, and operational measurement, living in one person — is strategic integration. The title is the name for the work.

By day 90, the work is in your hand.
Not described, but deployed.