Document core business processes to pinpoint inefficiencies and enable smooth delegation, using an executive-ready, structured overview.
Walk me through how your business actually operates day to day. This overview is about capturing the reality, not the ideal version.
A founder of a SaaS company is about to hire their 6th employee and realizes every process lives in their head. Onboarding new people requires weeks of shadowing. When they're unavailable, things stall. The business works because they personally know how everything connects - and they're starting to sense how fragile that is.
Frame this as a documentation exercise, not a process design exercise. 'We're not redesigning anything today - we're mapping what already exists, as it actually works right now. Pick the product or service that generates the most revenue.' The resistance to process documentation usually comes from founders who associate it with bureaucracy. Naming it as a visibility exercise rather than a control exercise reduces that resistance.
'What could go wrong?' sections left blank or filled with genuinely unlikely catastrophes while obvious single points of failure go unnamed. The founder often can't see their own indispensability - they know the process works, so the risk feels theoretical. Watch also for time estimates given in ranges ('a few days to a week') that would make adding up total cycle time impossible. Push for specific numbers.
Start with the 'Who is responsible?' column across all six steps. Ask: 'How many of these have your name in them?' Then: 'If you were unavailable for three weeks, which steps would stall?' The answers to those two questions usually land with more impact than any single process detail. Then move to the 'What could go wrong?' fields - read each one and ask whether it has happened before.
A founder who cannot complete this worksheet in 30 minutes because they genuinely cannot describe how each stage works - the confusion is real, not avoidance - may be running on improvisation more than they realize. Severity: low to moderate. Complete the worksheet together in session as an interview rather than assigning it as independent work.
A COO at a professional services firm has personally managed the sales and order processing function for four years. A new hire is being brought in to take it over. The COO can't fully articulate the process because it has evolved organically. The handoff is in 60 days.
Frame the exercise as the source document for the handoff, not a coaching artifact. 'The output of this worksheet is what you give the new person in week one. It needs to be specific enough that they could execute without you in the room.' That reframe makes the exercise immediately practical. The COO will be more precise when writing for a real reader than for a coaching session.
Steps where the 'Who is responsible?' field has the COO's name and no one else's - those are the handoff risks. Watch also for steps where the description is accurate in principle but missing the informal knowledge that makes it work: vendor names, contact preferences, unwritten rules about how clients are handled. The undocumented knowledge is the most valuable thing to surface.
Ask the COO to read the completed worksheet as if they were the new hire encountering it for the first time. 'Where would you get stuck? What question would you have?' That perspective-taking exercise usually identifies three to five missing pieces. Then ask: 'Which step here is most likely to go wrong in the first 90 days if you're not available to field questions?'
A leader who genuinely struggles to describe their own process - not from avoidance, but because the process has no real structure and has always run on improvisation and relationship - may be setting up the new hire for failure even with a completed handoff document. Severity: low. Surface this observation: 'This may not be a documentation problem - it might be that the process needs to be designed before it can be handed off.'
A founder of a marketing agency is in early conversations with an acquirer. The due diligence request will include a process overview for all major service lines. The founder has never had to produce this. The business works well but has never been formally documented. The timeline is 45 days.
Frame this as the document the acquirer is asking for, not a coaching exercise. That context makes the specificity requirement concrete - an acquirer will ask follow-up questions, and vague answers reduce valuation. 'What is the service line that generates the most margin?' Start there. Resist the temptation to document everything at once.
Documentation that describes how the process is supposed to work rather than how it actually works. In acquisition contexts, founders often unconsciously produce idealized process descriptions. The 'What could go wrong?' field is the best test - if it says 'nothing significant' for any step, the founder is editing for the acquirer rather than documenting reality. Watch also for steps where one person's name appears in four or more rows.
Start with the 'What could go wrong?' column across all six steps. Ask: 'If you were the acquirer reading this - would you believe these answers?' Then: 'Which of these risks has actually happened in the last 12 months?' That surfaces the gap between the documented version and the operational reality. Then ask: 'After looking at this, what are the two or three things you would fix before you'd be comfortable showing this to someone who's going to own it?'
A founder who responds to this exercise with significant anxiety - not about the work, but about what will be revealed - may be carrying undisclosed business problems that the acquisition process will surface regardless. Severity: moderate. Separate the coaching conversation from the acquisition conversation: 'What's the thing you're most worried will come up in due diligence that isn't on this worksheet?'
A client wants to take ownership of their own development rather than waiting for a manager to drive it
ExecutiveA client has marketing activity but no visibility into where prospects are dropping off before becoming clients
CareerA client plans one year at a time and never builds toward a long-term direction
