Diagnose · Standard entry engagement
What is preventing this transformation from becoming an executable operating change?
The standard entry engagement maps the current operating model, friction, controls, dependencies, and transformation risks, then gives leadership a prioritized intervention and next-stage roadmap.
2–3 weeks
Starting at $10K
Principal-led with explicit scope boundaries
The buyer and the moment
Who this is for.
For a COO, Chief Transformation Officer, CIO, or healthcare operations executive facing administrative burden, provider friction, a stalled modernization effort, or an automation decision built on an unstable workflow.
- Administrative cost or provider burden is rising without a shared explanation.
- Workstreams report progress while enterprise outcomes remain unchanged.
- A transformation has missed milestones or lost executive confidence.
- AI, automation, or a platform investment is proposed before the operating model is explicit.
- A new executive needs an independent read before inheriting the current plan.
Outputs
What the engagement produces.
- Current-state operating model
- Workflow and administrative-friction map
- Control and decision-rights analysis
- Transformation dependency model
- Risk and readiness findings
- Economic and value hypothesis
- Prioritized interventions and next-stage roadmap
- Executive readout
Stage 1
Frame and read
Bound the executive question, review existing artifacts, and identify evidence gaps.
Stage 2
Trace and test
Interview the people closest to the work and trace friction, controls, decisions, and dependencies.
Stage 3
Diagnose and sequence
Synthesize findings, prioritize interventions, and give leadership an explicit next-stage decision.
What the starting price assumes. The starting price assumes one coherent problem, existing documentation, bounded stakeholder access, and a decision-oriented executive readout.
Boundaries
What this engagement is not.
Stated before contracting so access, accountability, and expansion decisions are explicit.
- The scope is one transformation, workflow family, or coherent operating problem.
- The diagnostic establishes a defensible baseline; it does not guarantee savings or outcomes before evidence exists.
- Implementation, detailed solution design, and vendor procurement are separate decisions.
- TKO may recommend internal execution, an existing partner, a different specialist, or no further investment.
Expansion path: Validated problems can move into future-state design or into execution accountability. Expansion is evidence-based, not automatic.
Capabilities
What this engagement draws on.
Is this the former Program Recovery Review?+
Program recovery is now one use case within the broader Transformation Diagnostic. The engagement also applies before a program fails, when burden, controls, workflow, or investment choices are still being framed.
Do you need production data?+
Not always. Existing artifacts and interviews can establish the first model. Any sensitive-data requirement is separately scoped with explicit handling controls.
Other entry points
Use the smallest engagement that can answer the question.
Principal-led healthcare advisory
Start with the transformation question.
A focused working conversation about what is changing, what is stuck, and which decision leadership needs to make before more money or momentum is lost.