PHASE 07
PHASED, SEQUENCED,
NOT A BIG BANG.
The plan below is deliberately slow at the start and deliberately narrow throughout. Both of those are the point. Every version of this that tries to do everything at once fails in the same way.
Why big-bang fails
The appealing version is a transformation. Map everything, choose a platform, migrate, train, launch. Three months and the business is different.
It fails for reasons that are structural rather than about execution quality.
Nothing improves for months, so the project is running on faith while the actual business keeps making demands. When something does break, and something will, you changed twelve things simultaneously and cannot tell which one caused it. Your team absorbs an enormous amount of change at once, which means they absorb very little of it. And the decisions made in month one, before you learned anything, are baked into everything built afterward.
Phased work has the opposite properties. Something improves early, each change is isolated enough to diagnose, the team adapts in increments, and later decisions benefit from what the earlier ones taught you.
The phases
- Audit. One to two weeks. What systems exist, who does what, where the obvious pain is, what the team says is broken. No solutions yet. This phase is only about seeing the current state clearly.
- Map. Two weeks. Follow one lead and one job end to end, with the people who do the work. Every real step, including the undocumented ones. Mark every place the work waits.
- Fix the highest-leverage handoff. Two to four weeks. One handoff. Define done, name the owner, make the handoff an event. Usually no software at all.
- Automate one thing. Four to eight weeks. One process, usually lead follow-up. Built narrow, run on a subset, widened with a named owner watching.
- Measure. Two to four weeks of running before you compare to the baseline you captured in the audit. Honest comparison, cost included.
- Repeat. Back to the map with what you now know. The second cycle is faster because the team has done it and the decisions are easier.
Three to five months for the first full cycle in a typical small business, alongside the actual work. Anyone promising materially faster is either not doing the mapping or not doing the measuring.
This is one piece of a bigger picture; Ben Lovro's main site has the rest.
Phase three is where people quit
Worth flagging specifically, because the handoff phase is the one that gets skipped and it is the one that carries most of the value.
It is unsatisfying. There is nothing to buy, nothing to demo, and the deliverable is a page describing what done means at one stage and whose name is on it. It does not feel like progress in the way a new platform does.
It is also, reliably, the cheapest improvement available. Defining done and naming an owner at a single broken handoff costs a conversation and produces measurable change in how fast work moves. No subscription, no migration, no training.
Do this phase before you automate anything. A clean handoff is what makes the automation in phase four simple, because there is now something specific to automate.
Keeping the team with you
Operations projects fail on people more often than on technology, and the failure is usually set up in the first week.
- Say why, before you start. Not efficiency. Something they recognize: you will stop chasing people for information, and you will stop being blamed for things that were never yours.
- Involve the people who do the work. They know where it breaks. A process designed without them will be worked around, correctly, because it will be wrong.
- Be straight about roles. If nobody is being replaced, say so plainly. If something is genuinely changing, say that instead. People fill silence with the worst available explanation.
- Ship something that helps them early. The first improvement should remove work somebody finds tedious. That buys the patience for the rest.
- Let them tell you it is wrong. They will be right more often than the design. A team that reports problems is the early warning system.
What to do in the first two weeks
If you take nothing else from this site, take this. None of it requires a purchase.
- List every system your business runs on. Including the spreadsheets and the text threads. Most owners are surprised by the length.
- Ask three people what the most annoying part of their week is. Write down the answers verbatim. Do not defend anything.
- Follow one lead end to end. Every step, every wait, every undocumented workaround.
- Count one thing. Leads never contacted a second time, or median hours to first response. That is your baseline.
- Write one sentence: the single place the most work is waiting is _____, because _____.
That sentence is the start of the whole project, and you can have it by the end of next week.
Frequently asked
Questions people actually ask
How long does the whole thing take?
Three to five months for a first full cycle in a typical small business, running alongside normal work. Then it repeats, faster each time, because the team has done it before and the map already exists.
Can I skip the audit and mapping?
You can, and it is the most reliable way to waste the rest. Every implementation failure I have seen traces back to automating something nobody had written down first.
What if I do not have time for this?
Then start with the two-week list at the end of this page, which is a few hours total. The honest tension is real: this work competes with revenue-producing work, which is exactly why it stays permanently at the bottom of the list and why nothing changes.
Should I hire a consultant?
Possibly for the build phase, where experience saves a month of learning tools you will never use again. The mapping cannot be fully outsourced, because the undocumented steps live in your team's heads and they will only surface them to someone they trust.
What if the first automation fails?
Expected often enough to plan for. That is why it runs narrow on a subset first, with an owner and an off switch. A failure caught on one lead source in week one is a lesson. The same failure across the whole pipeline is an incident.
Do I need to do the phases in order?
The first four, yes. The order exists because each phase produces the input the next one requires. Automating before defining done is the specific inversion that causes most of the failures on the next page.
Make your next move
A year from now, what will you be glad you started today?
You don't need another promise that everything will be easy. You need something useful to learn — and a next step you're willing to take.