A process can look successful from the outside
Customers receive the work, invoices go out and the dashboard looks acceptable. Behind the scenes, one person corrects incomplete scopes, reconciles conflicting instructions and remembers every unusual promise. The apparent process depends on knowledge that has never been made visible.
The risk becomes obvious when that person is away or demand increases. Do not wait for a failure to discover which parts of the operation exist only in someone's head.
Ask what the workaround is protecting
Observe a recurring task with the person who performs it. Ask what they check, what they correct and what would happen if they followed the documented process literally. Their workaround may be sensible given the system they have inherited.
Do not remove it until the underlying need is understood. A shortcut that appears inefficient may be preventing a serious error. The objective is to make the protection reliable and shared, not to eliminate judgement indiscriminately.
Worked example (illustrative): the hidden intake check
An experienced project administrator checks every new job for a missing site-access requirement. The formal intake form does not ask for it. They call customers privately, resolve the gap and the team rarely notices.
The business adds the requirement to the intake process and defines when a job is ready to schedule. It trains the team and keeps an exception route for unusual cases. During the trial, the administrator reviews a sample rather than silently fixing every case.
The test tracks missing inputs, unnecessary calls and scheduling errors. A new form field is not success by itself. It must provide usable information without creating unreasonable effort for customers.
Unlock the rest of this lesson
You're halfway through. Enter your email to read the full lesson, use the exercises and quizzes, and unlock the rest of The Business of Growth library.
Already signed up through The Business of Growth? Use the existing signup to return and unlock this browser. No payment required.
Use a failure log with operational definitions
Record the event, stage, missing input, correction and consequence. A structured check sheet can help collect repeated observations consistently. Avoid vague categories such as "careless staff" that describe blame rather than a condition you can change.
Look for the earliest point where prevention is practical. A better handover may be more effective than a final inspection. But do not assume all defects can be prevented cheaply. Compare consequence, frequency and the cost of a control.
Make the standard usable
A standard should explain the required outcome, essential checks and exception route. Include a good example and a borderline case. Ask someone less experienced to use it and identify where they still have to guess.
Keep the standard current. If the real work changes and the document does not, people will build new unofficial processes. Give someone ownership of updating the standard and communicating the change.
Preserve expertise rather than extracting it once
Experienced staff should help design and review the process, not be treated as a source of instructions to copy and then ignore. Their judgement remains valuable for exceptions, coaching and improvement.
The useful growth outcome is that routine work becomes dependable without constant rescue. That releases expert attention for the cases where it genuinely matters and reduces the risk that expansion exposes a hidden single-person dependency.
Your next action
Observe one task that an experienced colleague often rescues. Record the checks they perform and the defect each prevents. Design one earlier prevention step, test it with a less experienced user and preserve an exception route. Review errors and customer effort before removing the old workaround.
Your notes stay on this page unless you choose device saving, download them or submit them to Greg below.
Keep names, private customer details and confidential information out of your notes. Device saving is optional. Only the separate Send my lesson work button below sends anything to Greg. There is no account or cross-device sync.
Two questions before you move on
These checks support learning. They do not assess business health, award a qualification or send a result to Greg.
Ask Greg
Ask a question about this lesson or a challenge in your own business. I read submissions and may reply or cover common questions in future lessons. I cannot promise an individual reply to every question.
Lesson: When your best people hide a broken process. Please do not include confidential client, financial, health or staff information.
Work out where your business is getting stuck
The free Growth Diagnostic asks ten questions across acquisition, conversion, relationships, delivery and commercial control. It gives you an area to investigate and three things you can do next.
One complete sample lesson in each stream is fully open. Read halfway into every other lesson, then enter your email to unlock the remaining content, exercises and quizzes across the library. Ongoing marketing emails are optional.