Part two — a briefing for the steering committee

The Crossing

Part one named the cost of standing still. This is the plan for moving — the platform, the operating model, and the people: built by a few who earned it, inherited by everyone willing, with the lights on the whole way.

Companion to The Quiet Cost of Standing Still Built to be questioned About a nine-minute read
The plan
01How we will behave

Six commitments, before any architecture.


Transformations fail on behavior before they fail on technology. So the plan starts with the rules we will hold ourselves to — the answers, in advance, to the ways this usually goes wrong.

Commitment 01

The lights stay on

Claims pay, filings file, care goes out. The old model retires only after the new one has earned each job. Nothing is switched off on faith.

Commitment 02

Proof every ninety days

No eighteen-month promises. Every quarter ships something a member, a clinician, or this committee can see. What can't prove itself gets rescoped or stopped.

Commitment 03

Buy the commodity, build the difference

Modern data platforms are excellent and boring; we buy one. Our energy goes to what no vendor sells: our members, our contracts, our clinical relationships.

Commitment 04

Follow-through is a system, not a virtue

Intake with real answers — yes by when, no because, or here's the self-serve path. Commitments get names and dates, and the scoreboard remembers.

Commitment 05

People decisions early, once, with respect

One honest window, three fair paths, no rolling purge and no quiet drift. Accountability, not payback — the boundary from part one stands.

Commitment 06

Members feel every milestone

Each phase must move something that touches care: a signal sooner, a gap closed in-window, an answer in time to matter. Otherwise it isn't progress; it's plumbing.

02The path

Four proofs, not one leap.


The mirror image of the decay timeline in part one. Same horizons, opposite direction — and every phase ends with something real, shipped and visible, before the next begins.

First 90 days

The honest map.

  • The whole estate named and owned: every report, pipeline, and shadow system, in daylight.
  • The skills and willingness conversations happen here — once, fairly, for everyone.
  • The build team forms — earned over years, criteria in the open — and one door stays open for anyone we've underrated.
  • Platform and partner chosen; the accountable leader named; the first zombie reports retired.
Months 3–9

Foundation & first proof.

  • The modern platform stands up with governance built in, not bolted on.
  • Claims, enrollment, and provider domains land first — the spine of everything else.
  • The first care signal reaches care management; the first manual reports retire into self-service.
  • Every learner works with an agentic assistant from day one; the bar is judgment, not typing.
Months 9–18

Migrate the middle.

  • The reporting estate moves methodically; unclaimed reports die of natural causes, celebrated.
  • Regulatory filings rebuilt on governed pipelines — parallel validation before any cutover.
  • Shadow spreadsheets are offered a paved road home. Amnesty, not blame.
  • The second wave inherits instrumented domains — and each takes one end to end, architects reviewing, not doing.
Months 18–24+

The compounding turns.

  • Predictive runs in production: rising risk, in-window gap closure, readmission outreach.
  • Data products have owners, roadmaps, and users who would protest their loss.
  • The function is measured in decision speed and member outcomes — not report counts.
  • The architects who built it stand as principals — elevated, paid, and staying with what they made.
the crossover — the new model carries more than the old RUN THE OLD safely, to the end BUILD THE NEW proof by proof First 90 days Months 3–9 Months 9–18 Months 18–24+

Honesty about money, up front: running two models costs more before it costs less. The dual-run is the price of never missing a filing and never gambling members' data on a big-bang cutover. We will bring this committee the real number, not a flattering one.

03Who builds it

Earned, not appointed.


The platform is built by a small team whose judgment was proven the slow way — years of it, in the open. This is not a favor granted in a meeting; it is a lagging indicator of a decade of willingness to learn. The price of admission has been posted the whole time.

The criteria are published, not whispered: demonstrated curiosity, judgment under pressure, and the respect of the people who watched them work. And because any leader's sight has blind spots — org layers, distance, quiet competence that never felt safe to show itself — one more door stands open: anyone who believes they've been underrated can raise a hand and take the same judgment exam as everyone else. If no one walks through it, it cost nothing. If two people do, we just found two people a recruiter would have charged us for.

And the second wave does not inherit homework. They inherit an instrumented system — one that explains itself, whose build history and runbooks are the curriculum. Inheritance is not the ceiling, either: every learner takes a domain of their own, end to end, with the architects reviewing rather than doing. Building is the prize, and everyone willing gets a turn at it.

If you had been learning all along, we already know your name.
04The new bar

Think in pipelines. The assistant does the typing.


Everyone who touches the platform works with an agentic assistant — not as a perk, as the job. That changes what we ask of a twenty-year veteran: not to become a software engineer at fifty-two, but to do what they are already better at than anyone in the building — knowing what a claims table must mean, what “correct” looks like, and what should never ship.

The assistant collapses the part they would have hated — syntax, boilerplate, the nuts and bolts — and elevates the part they were hired for: judgment. The bar differs by role, but the direction is the same for everyone. Reason about what the pipeline should do. Let the machine handle how.

The exam is judgment, not typing: we hand you a plausible-looking pipeline with a subtle flaw, and ask whether you catch it. Assistants make output cheap long before they make judgment cheap — and plausible-but-wrong is the one thing a filing cannot survive.

This is also what finally makes the willingness question fair. With the mechanical wall gone, the bar is reachable by anyone who wants it — so whoever doesn't clear it is answering the willingness question, not the capacity question.

05How it runs, day to day

From toll booth to platform.


The platform is the floor. The operating model — how work enters, who owns what, and what the business can count on — is the transformation.

Pillar one

The platform

One governed source of truth, self-service by default. The common question answers itself; the catalog says what every number means; lineage is a property of the system, not a memory.

Pillar two

The products

Data treated as product — claims, quality, risk, member 360 — each with a named owner, a service level, and a roadmap the business can see and argue with.

Pillar three

The partnership

Analysts embedded where decisions happen — clinical, network, service — carrying questions in and signals out. The center becomes a platform team, not a toll booth.

The intake covenant, effective day one: every request gets one of three answers — yes, by this date; no, and here is why; or here is the self-serve path. The fourth answer, silence, is retired permanently.

The people plan — plainly

Three paths. One honest window.

Within the first ninety days, every person on the team hears the same thing, in the same words: here is the new bar, here is the investment available to reach it, and here is the timeline. One conversation, early — not a rumor that hangs over the building for two years.

A spine of experienced modern engineers joins early — not to replace the team, but to set the bar and carry the pairing. The veterans de-risk the migration: nobody reads a claims quirk like the person who has lived with it for a decade.

Grow — for the willing

Funded reskilling, protected learning time, pairing with the new spine. Willingness first, skill second — skill can be taught to anyone who wants it. This path is open to everyone, and we mean it.

Redeploy — for the knowing

Decades of domain knowledge — claims quirks, provider data, filing seasons — is an asset the enterprise needs. Some colleagues will carry it into operations, compliance, and product roles where it counts more than code ever would.

Depart — with dignity

For those who choose not to cross, and for roles that end: honesty early, generous transitions, real outplacement. Decided once, handled with respect — not a rolling purge, and not a slow drift.

Paid to commit. Paid to stay.

The money says what the words say. Build-team rewards are granted up front, at approval — an incentive to commit to the process, not a counteroffer when a recruiter calls. A second reward vests at completion, against a definition of “complete” written down on day one, not argued about in month twenty. And the architects who build it are elevated to principal on a real senior-technical track — paid, respected, and staying embedded with what they built. Reward arrives before recruitment, by design.

One conversation, early. One window, fair. One standard for everyone: are you willing to learn the way the work is done now?

And the guardrail from part one stands: accountability, not payback. No scores get settled under the banner of modernization.

Specific counts, package sizes, and the written definition of “complete” are decisions for this committee with HR and counsel. This page commits us to the how — so those decisions get made once, honestly, and with respect.

06What could go wrong

The risks, named before they find us.


Every transformation this size dies in one of a handful of familiar ways. Naming them now — with the answer built into the plan — is cheaper than meeting them by surprise.

The old model fights backUrgent work quietly devours the people building the future.
Separate run from buildDistinct teams, protected funding. The build team is never the flex capacity.
The big-bang temptationOne giant cutover, promised for month eighteen, believed by no one.
Ninety-day proofsValue shipped every quarter, kill criteria set today — before anyone is attached.
The platform-first delusionBuying tools and calling it transformation.
The operating model is the transformationProduct teams, service levels, self-service. The platform is just the floor.
The quiet vetoResistance that doesn't argue — it waits initiatives out.
Decisions made once, in public, with datesThe willingness window closes. Commitments carry names and quarters.
A missed filingRegulatory continuity gambled on a migration schedule.
Parallel validation before every cutoverOld and new run side by side until the new has earned the filing. The lights never go off.
Plausible-looking wrongAssistants make output cheap; a broken pipeline can look finished.
Judgment is the gateNothing reaches a filing without a person who has proven they can catch a subtle flaw.
The favored-few storyThe build team reads as patronage, and the second wave checks out.
Criteria in the open, one findable doorSelection earned over years and published — and anyone underrated can raise a hand and take the same exam.
07How we'll know

A scoreboard, not a story.


Progress reports are where transformations go to hide. So we will not write many. Each quarter, this committee sees the same short scoreboard — baselines measured honestly in the first ninety days, before anyone is graded against them.

Question → answer time

From weeks toward days — and toward minutes for the routine. The single number that says whether the loop is breaking.

Hand-built recurring reports

Counted, then retired month by month. Every retirement is a person's time returned.

Care signals in-window

Rising-risk flags and care gaps reaching clinical teams while action is still possible — reported jointly with care management.

Self-service share

The portion of routine questions answered without a ticket. The toll booth's traffic, redirected.

Filings on governed pipelines

Regulatory reporting moved off manual paths — each one validated in parallel before it counts.

Shadow systems brought home

Spreadsheet economies adopted onto the platform. Rising at first — that's honesty — then falling toward zero.

08The ask

What we're asking this committee to approve.


Four decisions. Made together, made once — each one designed so that follow-through no longer depends on goodwill.

1

A mandate and a name

One accountable leader with real decision rights over platform, priorities, and people — answering to this committee on the scoreboard.

2

Honest funding for the dual-run

It costs more before it costs less. We ask for the real number, openly — not a flattering one that fails in month seven.

3

The people covenant

Investment for the willing, dignity for the departing — and build-team rewards pre-authorized today: paid to commit up front, paid to stay at completion, against a definition of “done” written on day one.

4

The quarterly scoreboard

Same measures every quarter, kill criteria set now. If a proof fails twice, we change course in daylight — that is the deal.

We said the kind time is now.
This is what now looks like.

Approved today · Visible in ninety days