A founder of an 18-person consultancy on a beach in Greece, day four of a two-week holiday. He has fielded six work calls already. The operations director has flagged a customer escalation. The finance director has flagged a vendor query. His deputy has flagged a hiring decision. None of these is genuinely beyond the team. All have come to him by default.
He has spent three years saying the business runs without him when he is away. He knows on day four that the business does not. He has not yet worked out why.
Why does the holiday test fail even when the team is competent?
The team is competent. The team is also reading the structural signals. If the founder has not been explicit about who owns what decision, the team’s safe move is to ask. If the founder has previously reversed decisions the team made independently, the team’s rational response is to escalate rather than risk another reversal.
If the role architecture has not been redesigned, the team has the same job description they had before the founder took the holiday and no formal authority to absorb the decisions that emerge in the founder’s absence. The holiday test fails on the architecture, not on the people. Most founders mistake the failure for a team capability problem and respond by trying to coach the team into more confident behaviour. The intervention is at the wrong layer. The team will not absorb operational authority until the role design, accountability chart, and decision matrix have been redrawn to give them somewhere clear to absorb it into.
The two-week founder time audit
Live in the calendar for two typical weeks. Either the founder or an assistant records every fifteen-minute block in a spreadsheet. Each block is categorised: strategic thinking, customer-facing (sales, relationship management, problem resolution), financial review, hiring and people management, operational decisions (approvals, problem-solving, process improvements), administrative work, meetings with vendors or partners, external relations.
Once this data is collected for two typical weeks, patterns emerge. A common finding is that the founder spends 40 to 50 percent of their time on operational decisions (client escalations, hire-or-fire calls, vendor selections, approval of exceptions to process), 15 to 20 percent on customer-facing work, 10 to 15 percent on financial review, and very little on strategic thinking. The audit is the surprise. Most founders thought they were spending their time on strategy.
What must stay with the founder, what can move?
The categories that must stay with the founder are typically narrow. Strategy: where is the firm going, what should we stop doing, how do we differentiate. Major external relationships: key customer relationships at the principal level, investor or funder relationships, industry leadership. Hiring or termination of senior leadership roles. Everything else is potentially moveable, even when it does not feel that way to the founder who has been doing it for years.
The audit makes this concrete. For each category in the time tracker, the founder marks: must stay, can move with effort, can move now. The “can move now“ column is usually larger than the founder expected. The “can move with effort“ column requires the role redesign and the documented procedures (the SOPs) to be in place before the move is feasible. The “must stay“ column is what fills the post-bottleneck calendar.
The accountability chart, distinct from the org chart
The org chart shows reporting relationships and titles. The accountability chart shows the functions that must exist and the roles that own each function. In the accountability chart, sales sits as a function rather than a person. Underneath it sits the role of Sales Lead or VP Sales, and underneath that the individual account managers.
If the business needs customer onboarding designed and run but no role owns it, onboarding either does not happen or happens ad hoc and inconsistently. The accountability chart makes explicit which functions exist and who owns each one. As the firm scales, this chart gradually expands: operations becomes operations, finance, and human resources as distinct functions; sales becomes sales development, account management, and customer success. The org chart drifts to follow. Founders who design the org chart first and then try to retrofit accountabilities tend to leave functions unowned. Founders who design the accountability chart first find the org chart writes itself.
The leadership team redesign
The leadership team in a firm moving past founder dependency consists of the Integrator (operational leader), the Visionary (founder), and the functional heads, typically finance, operations or delivery, sales or business development, and people. These are the seven to ten senior roles that should meet weekly in the L10. Individual contributors and first-line managers do not attend the leadership L10; they attend their own functional team meetings or department huddles.
This distinction matters. If the L10 includes front-line staff, it becomes inefficient and loses its executive decision function. If the L10 is only leadership (seven to ten people, all with P&L or functional accountability), it can move quickly and make strategic decisions. The leadership team redesign sometimes requires hiring into roles that do not yet exist (a finance lead in a firm that has been running on a part-time bookkeeper, or a people lead in a firm that has had no dedicated HR function).
The holiday test as operational diagnostic
Two weeks. No calls. No texts. No emails read. No deferred decisions. The team handles client escalations, hiring decisions, vendor queries, financial approvals, all inside the normal cadence. If the test passes, the role redesign has worked. If it fails on day three with a customer escalation that “only the founder can handle,“ the boundary condition for that decision was not properly defined, or the role holder was not properly resourced, or both.
The pre-holiday calibration matters. Before the test, walk the leadership team through the categories of decision that may arise. Confirm who owns each. Confirm the boundary conditions: what triggers a genuine emergency contact, and what does not. The holiday test runs as a planned drill the team has prepared for, not as a surprise. The team has the matrix, the accountability chart, and the operating cadence in place. They are running the system the founder built.
What the post-holiday review looks like
On return, the founder reviews what was decided, what was deferred, what was held. Deferred items are usually the diagnostic. Whatever the team waited for is the gap in the role redesign. The fix is to refine the boundary conditions and the authority matrix, not to take fewer holidays. The fix is also rarely to retrain the team; the team responded to the architecture they had, and the architecture is what needs redrawing.
Founders who run the holiday test annually find their architecture tightens with each cycle. The first test surfaces the largest gaps. The second test surfaces the medium gaps. By the third test, the firm runs well in the founder’s absence and the architecture genuinely holds. Without an annual test, the architecture drifts and the dependency rebuilds quietly.
What to do this quarter
Run the time audit for the next two weeks. Mark each fifteen-minute block by category. At the end of the second week, run the must-stay versus can-move filter. The output is the spec for the role redesign and the accountability chart.
Then plan the holiday for ten to twelve weeks out. That gives time to install the matrix, the SOPs, and the cadence before the test. Tell the team the holiday is happening and that there will be no contact. The pre-holiday calibration sessions become the forcing function for the architecture work that needs to land before you go.
If you would like a second pair of eyes on whether the architecture is ready for the test, book a conversation.
