Visually map reporting lines and department roles to clarify accountability during growth or reorgs, using an executive-ready org chart format.
Draw your business structure as it exists today, not as you wish it were. What becomes visible when you see the full picture on one page?
A CEO of a 25-person technology company is onboarding a CFO and a VP of Marketing in the same quarter. Neither hire has a clear reporting line below them - their direct reports haven't been formally defined. The CEO has been managing everything informally and is realizing that two new executives coming in without structural clarity will create competing claims on team members.
Frame this as a pre-hire clarity exercise, not a redesign project. 'Before these two people start, let's draw what the structure is - as it actually exists today, not the aspirational version. Then we'll see where the conflicts are before they become interpersonal.' Some CEOs resist this because drawing the real structure exposes how much they've been holding informally. Name that: 'This is going to look messier than you want it to. That's the point.'
The 'Reports To' field used to list multiple managers for a single role - indicating dual-reporting situations that haven't been resolved. Watch also for Level 3 or 4 rows where the Name field is blank but no one has marked the row as 'vacancy' - those are the roles that exist only in someone's informal understanding. Single-point-of-failure identifications that are absent even when the same name appears in five rows.
Start with the Structural Observations section, specifically 'Single points of failure.' Ask: 'If you lost the top person in any row where only one name appears and no backup exists - who's first on that list to keep you up at night?' Then move to the informal reporting lines: 'Which of these relationships would survive a reorg and which would break if the person they're built around left?' That question distinguishes structural from relational accountability.
A CEO who fills in Level 1 and Level 2 completely but cannot populate Level 3 and 4 - not because of time, but because they genuinely don't know what roles exist below their direct reports - has a visibility problem that predates this exercise. Severity: moderate. Explore what the CEO knows and doesn't know about their own organization, and what that says about span of control.
A VP of Engineering at a Series A startup has a team of 18 that started as 5. The org chart from 18 months ago has never been formally updated. Reporting lines have shifted, informal leads have emerged, and two engineers effectively manage others without any official acknowledgment. The team is starting to show tension around authority and decision rights.
Frame this as a gap-mapping exercise, not a performance review of the current structure. 'We're going to draw what actually exists today - not what the HRIS says, not what was true six months ago. When we're done, we'll compare it to what the structure probably needs to look like to function well at this size.' The gap between current and needed is the action plan.
Informal leads who appear in Level 4 rows as individual contributors but whose names also show up in the 'Reports To' column for multiple colleagues. That pattern signals a structural vacuum the team has filled with informal hierarchy. Watch also for the 'Reporting lines that are informal or ambiguous' section to go unfilled - leaders often resist naming informal dynamics in writing even when they're visible in the room.
Start with the informal-leads situation. 'Look at the names that appear as both contributors and as the 'Reports To' for others. What would need to change to make those relationships official?' Then: 'What has kept those roles informal this long?' The answer to the second question usually involves either compensation constraints, performance uncertainty about the informal lead, or the leader's reluctance to formalize something they'd have to manage.
A team structure where the informal hierarchy is significantly different from the formal one - especially where an informal lead has more actual authority than a formal manager - may have a leadership credibility issue the worksheet alone won't resolve. Severity: moderate. The structural fix needs to follow, not precede, a direct conversation about authority and accountability.
A co-founder of a 30-person firm is in early M&A conversations. The acquiring organization has asked for an org chart. The founders have been running with a flat, informal structure that works because they're present every day. Writing it down for an external audience is revealing how much of it depends on personality and presence rather than documented roles.
Be explicit about the audience. 'The acquirer is going to look at this and ask: does this structure work without the founders? We need to draw it as it actually runs, and then we're going to look at what changes if you're not in the picture.' That framing makes the exercise immediately relevant to the transaction, which motivates precision.
Level 1 rows where both founders appear and have no functional differentiation - no clarity on which decisions belong to which founder. Acquirers read that as a governance risk. Watch also for single points of failure in operational roles that are held by long-tenure employees whose institutional knowledge isn't documented. Those are the highest-risk rows from an acquirer's perspective.
Ask the founders to identify every row where the answer to 'What happens to this role if the founders exit in 12 months?' is 'we don't know.' Those rows are the integration risk register. Then: 'If you weren't building this chart for an acquirer but for yourselves - which three things would you change first?' That question separates the structural presentation from the structural reality.
Founders who discover in this exercise that their entire organization runs on their personal relationships and there are no functioning structural mechanisms underneath should be prepared for the possibility that the acquisition timeline needs to extend. Severity: moderate. Name the observation without judgment: 'What we're seeing here is that the structure is founder-dependent. That's fixable, but it takes 6-12 months to change structurally, not cosmetically.'
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
