What Does Installing Systems Ask of the Owner?
Mainly your judgment: the calls only an owner can make, one person you trust to lead the rollout, and the truth when the map is wrong. The heaviest weeks come first, while the map is being built, and your share shrinks once the lead is running the meetings.
Phones face-down on the conference table. The owner of a roughly $2M firm had mapped well for two weeks, then vanished into backlog and left the shared folder looking abandoned. He had promised nine screen recordings of paths only he still ran. He sent two. The lead had stopped nudging because every reminder felt like nagging the boss.
We canceled the homework list and sat for one 90-minute co-working block instead. He clicked. We captured the missing paths live. The map finished that same afternoon. The install did not need more assignments. It needed a smaller surface area for the work and a named person in the room.
Owners ask what working with a systems install looks like when what they mean is: will this take over my life, and will you somehow teach my team to be me. Short answers. It will not take over your life if you protect a few hours a week. Nobody can teach your team to be you. The job is to stop needing them to be you.
You supply decisions, a named team lead, and honesty about what breaks. The installer supplies maps, scorecards, and cadence. That split is the whole expectation. It is not a replay of a sales call, and it is not a promise that your brain becomes a training course.
What do you actually hand over?
In practice, each of the three means something specific:
- Decisions mean you answer the fork when two options are both plausible.
- A named lead means one human who can own outcomes while you are in a meeting, not a rotating cast of whoever is free.
- Honesty means you say when the map is wrong, when a recording never got made, and when you reclaimed a seat after a messy week.
Owners who skip honesty get a pretty map of a business that does not exist. I would rather hear "we never follow that handoff" in week two than discover it in week eleven during a you-away test.
Maps are how work moves, cut one way so gaps show. Scorecards are the few numbers that tell you a seat is winning or drifting. Cadence is the meeting and review rhythm that keeps both from becoming wallpaper. Good installs transfer ownership of Common work and Judgment rules. They leave Custom craft alone. Your voice on the weird proposal stays yours. The invoice that should leave in 48 hours does not.
If you are still choosing between hiring that work out and running it yourself, done for you vs doing it yourself compares what each route asks of you.
How is the work split across the install?
Weeks 1 to 3 are map. One categorization only: by role, or by function, or by department. You show up, name Custom versus Common, and stop rewriting the map for taste. The lead brings the real path, including ugly shortcuts. The output is a map the team recognizes, not a fantasy org chart.
Weeks 4 to 7 document from recordings. Screen captures of how work happens today beat blank templates. You record the paths only you still run, or you sit in a co-working block so capture actually happens. Expect fewer videos than you promised yourself. Owners regularly commit to a dozen and deliver under three. That is useful data, not a moral failure. Reset. Capture live. Move.
Weeks 8 to 10 install cadence and metrics. A short operating meeting, light reviews, and a small set of check-engine lights with red, yellow, and green. You attend the first few, then stop chairing them. The lead runs the meeting without you as the default audience. Protect the numbers from becoming a status dump.
Weeks 11 to 12 are the you-away test. A forced stretch where the business runs on the map, the scorecards, and the lead. You stay reachable for true emergencies and stay out of permission theater. The lead logs every ping that still needed you. That log is the next punch list, not proof the install failed.
Hours are not flat across the twelve weeks. Early weeks lean on your calendar for decisions and capture. Later weeks lean on the lead. Front-load silence and you starve the map. Never hand the chair of the operating meeting to someone else and you starve the test.
How many hours a week getting out takes covers the hours themselves, including where to find them in a full calendar.
Where do installs usually stall?
A second firm finished the map and hung twenty metrics on a wall. Nobody looked. We cut to five check-engine lights with clear red and yellow lines:
- response time
- quote aging
- invoice days
- exception count
- owner pings per day
The wall got quieter. The meeting got useful. Two of the five still drifted for a month because the lead was afraid yellow would look like failure. We had to say out loud that yellow is a light, not a character review. Even then, exception count stayed fuzzy. They could count the pile. They could not yet agree what belonged in it. Partial progress. Better than wallpaper.
A third pattern: the owner who "supports" the lead by answering every Slack in the lead's channel. The lead never got to be the lead. For two weeks we ran a simple rule. Questions that belong to the lead's seat go to the lead first. The owner sees a Friday digest, not a live feed. Pings to the owner dropped. Mistakes rose for about ten days, then fell. That bump is the price of a real seat. If you flatten the bump by reclaiming every call, you paid for an install and bought a slower version of yourself.
Skip a full install when you want a result with zero involvement, when you will not name a decision-maker, when you are in a live cash crisis or the week after a key person quits, or when you are still rewriting every customer-facing sentence for preference. Stabilize first. Be honest and stay in operator mode if you must. Under about five staff you can still map and set a light cadence, but be careful promising yourself a full step-out on a twelve-week clock. Capacity has to exist for ownership to land.
Owners who want someone to absorb every judgment call while they stay in the weeds will hate this model. The point of the install is fewer judgment calls on your phone, which means you have to stop answering the ones that now have a rule. What that feels like shows up in the Friday digest: three items still need you and twelve do not, and you leave the twelve alone on purpose.
What does an install never ask of you?
It does not ask you to become a full-time project manager of your own escape. If your calendar cannot spare the decision windows, you are not in an install. You are in a wish.
Documenting every preference is also off the table. Preference is Custom. Standards are Common. Mixing them creates a novel nobody opens after day thirty.
Nor does it ask you to disappear in week two. Early weeks need you more, not less. Skipping to "I'm offline, figure it out" before the map exists traumatizes a lead and "proves" systems do not work here.
The stalled owner from week five still owes two of the original nine recordings. We stopped chasing the full list. The live paths we pulled in the co-working block cover the revenue and risk work. The two unfinished clips sit on his desktop with names that no longer match the map. He opens them sometimes and closes them.
The lead runs the operating meeting without him most weeks. The Friday digest still has two or three items that need his decision. Last Friday one of those items was a preference he almost answered live in Slack, then pasted into the digest instead and waited. That is not a cloned brain. That is a partial handoff that held overnight.
Frequently asked questions
What if the lead leaves partway through the install?
Name a replacement within a week, even an imperfect one, and walk them through the map and the ping log before you pick up where you stopped. The maps and recordings belong to the business, so they survive the change. Expect your calendar to carry more again for a few weeks while the new lead learns the seats.
What should I do before an install starts?
Name the lead and tell the team before the first mapping session. Then list the work only you still handle, starting with any that a quote or an invoice waits on, and note who touches each item today. That list becomes the first draft of the map, so the early weeks start from facts the lead can check.
Is now the right time for an install?
If you want help scoping what those twelve weeks would ask of your firm, start here: systemstoscalegroup.com/getstarted
