THE NO GAPS METHOD
A gap doesn't close by itself.
A fit call, then five steps to a finished guide. Then we keep going until every piece is in place.
.png)
● Fit Call
Twenty minutes, and you'll know.
We'll ask what you're building or what you're leaving, how you got to this size, and which job would hurt most if the person doing it left tomorrow. If it's not a fit, you'll know in twenty minutes. If it is, you'll know exactly what happens next.
01
Scope
We decide what gets written down, in what order, and who's driving it.
The question that settles almost every scoping argument is whose job is this? If one person would be handed all of it, it's one guide. If you'd hand pieces to different people, it's one guide per person's piece.
“A guide gives a job edges. A job without edges can't be handed to anyone — which is why hiring someone to take it off your plate never quite worked.”
02
Capture
Nothing has to be cleaned up first. Cleaning it up is the job.
Send us whatever you've got, in whatever shape it's in. Recordings, four contradictory old versions, a voice memo, an email thread, the checklist taped inside a cabinet door. Your team contributes in whatever way is easiest for them. No prep. No format.
And we watch the work, not just listen to it. Your best people do things they don't even realize they're doing.
Draft
03
Four people do it four different ways. You get one version, and it's the right one.
The reconciling is the hard part. Several people contribute, and one person you name at scoping decides whose version is authoritative when they conflict. Everyone's input still shapes the guide. One person signs it.
Approve
04
Nothing reaches your team until someone inside your company has put their name on it.
Three people say yes, always, however many contributed. The person who does the work confirms it's what actually happens. The person who owns the process confirms it's what should happen. And someone who can commit the company says this is how we do it now.
The chain is three people long no matter how many contributed, which is what keeps sign-off from being where this stalls.
05
Launch
The team gets it, uses it, and knows why.
Into the system you already use, with the rollout kit. Approved and in use are different things, and a document can sit in the first for months. Getting from one to the other is the launch.
How long it takes
Fit Call
20 minutes
Scope
Week one
Capture
At your team's pace
A finished guide
30 days from capture complete
After that
Ongoing, for as long as it's useful
About three guides a month, and roughly two hours a week of your team's time.
Ask whoever would have to write it how long it would take. Then ask when they’d start.
This is a project you hand off,
not one you run.
The owner
Two conversations. The fit call, and signing off on what matters.
Your Champion
Names who's involved, keeps it moving, and is the person we talk to.
The people who do the work
Show us how they actually do it. That's the whole ask.
Us
Everything else.
The last time this didn't get done, it was on somebody's desk who already had a job.