The Diagnostic
The organization knows something is off but needs to understand it clearly enough to act. The Diagnostic is how that understanding gets built — in plain language, with a sequenced roadmap, and with enough honesty that the executive team can read it and know exactly what to do next.
Two variants — determined in conversation, not in advance
One named operational problem, diagnosed in depth. Why the data isn't driving decisions. Where the operating rhythm is producing drag instead of motion. Whether the organization is actually equipped to absorb the technology investment it's considering. Why a stalled initiative has stalled, and what it would take to unstick it.
A cross-functional assessment of the operational picture as a whole. Stakeholder conversations at every level — not just leadership. Review of the systems and artifacts that reveal how the organization actually runs. Honest synthesis of what is working, what is not, and what is being avoided.
Most organizations do not need the Full Diagnostic. The ones who do, need it badly.
What this looks like in practice
Regardless of variant, every Diagnostic delivers a written diagnosis in plain language that the executive team can read, understand, and act on. It includes a sequenced roadmap identifying the three to five highest-impact moves — in the order they should happen and with an honest assessment of what each will cost to execute.
Quick wins are identified and delivered during the engagement itself, so the investment returns value before the final deliverable lands. If deeper work is warranted, the Diagnostic includes a specific, scoped proposal for execution.
Why this engagement exists
Most consulting engagements fail because the scope was wrong from day one. The Diagnostic is how that mistake gets avoided. It is also how both parties earn the right to work together at deeper levels — the organization sees the quality of the thinking, and the work is scoped against what was actually found, not what was assumed.