No surprises
What actually happens
The most common quiet question about consulting is what am I actually buying. Here is the whole shape of it, from first email to the part where you no longer need me.
Before we start
The discovery call
Thirty minutes. You describe what is happening, what you have tried, and what a good outcome looks like. I ask questions and tell you honestly whether I am the right fit. If I am not, I say so and point you somewhere better.
What you bring
- Thirty minutes and candor
- No preparation
What you get
- A straight read on fit
- A written recap if it helps you brief others
Within a week
The proposal
A short document: scope, approach, timeline, deliverables, and investment. Fixed and written down, so there is no meter running and no surprise line item later.
What you bring
- A decision, taken at your own pace
What you get
- A proposal you can forward to finance without translating it
Weeks one and two
Discovery
Interviews with the people closest to the work, a read of what already exists, and a map of how the work actually flows. This is where the real problem usually turns out to be somewhere nobody was looking.
What you bring
- Access to a handful of people, an hour each
- Existing docs, however messy
What you get
- Interviews run and synthesized
- A current-state map and an honest read
Weeks three to eight
Design and build
We design the fix together, in the open. You see drafts early and often, because a system designed without the people inside it is a system that gets quietly ignored.
What you bring
- Working sessions and reactions to drafts
What you get
- The design, the artifacts, the working systems
- Weekly written updates in your workspace
The last stretch
Adoption
Communications, enablement, and reinforcement so the change survives launch day. This is the part most engagements skip, and it is the reason most changes fade.
What you bring
- Sponsorship, visibly
What you get
- Enablement materials and the rollout plan
- Support through the first weeks of real use
At the end
Handover
You keep everything: playbooks, systems, decision logs, institutional memory. The goal was never to make you need me next quarter. If you want ongoing thought partnership, the retainer exists for that, but it is a choice, not a dependency.
What you bring
- An honest debrief, including what did not work
What you get
- Everything handed over, documented and usable
Questions this does not answer are answered on the FAQ page, honestly. Read the FAQ.
Where organizations stand
The Operational Backbone Ladder
Five levels, from work that runs on heroics to work that runs without you. Most organizations sit between two rungs, and the goal is never level five everywhere: it is level three or four where it matters most.
Heroics
Score 0 to 14The work gets done because specific people refuse to let it fail.
Knowledge lives in heads, decisions wait for one or two people, and quality tracks who happened to be available. It works until someone leaves or burns out.
The next move: Stabilize first: name decision owners and capture the three processes that would hurt most to lose.
Written down
Score 15 to 23The important things exist somewhere, but finding them takes asking.
Documentation exists in pockets and is often stale. Processes are described but not enforced, so people follow them when convenient.
The next move: Give the documentation one home, one owner, and a review cadence, then wire it into how work actually starts.
Governed
Score 24 to 30Work has a path, and decisions have homes.
Intake is predictable, stages are visible, and decision rights are agreed. Most friction now comes from the seams between teams rather than inside them.
The next move: Work the seams: handoffs, shared definitions, and the operating rhythm that keeps cross-team work moving.
Compounding
Score 31 to 36Each project leaves the next one easier.
Reusable assets accumulate, institutional memory survives turnover, and change tends to hold past launch. Improvement is a habit, not a project.
The next move: Automate the remaining friction and turn what works into assets other teams can pick up unchanged.
Runs without you
Score 37 to 40The system carries the work, and leaders spend their attention on what is next.
New people are productive quickly, quality does not depend on who is on shift, and leadership time goes to strategy rather than unblocking.
The next move: Protect it: rhythms decay quietly. Review the backbone annually and keep the knowledge base honest.
This ladder is a shared vocabulary, not a scorecard. Its value is letting a whole leadership team point at the same rung and agree what the next one requires.