A week without the founder is a useful operating test, provided it is planned and does not leave customers or staff unsupported. The purpose is to identify dependence on a person, not to prove that leadership is unnecessary.
Prepare the boundaries
List decisions expected during the week. Assign routine decisions to named roles with limits. Specify which issues justify contacting the founder, such as a serious incident or a commitment outside authority. Give the team an alternative escalation contact where appropriate.
Confirm access to calendars, customer records, payment information and supplier contacts. Test those permissions before the week starts. A handover document is not sufficient if the receiving person cannot open the relevant system.
Run a supervised rehearsal
Start with a day or a limited workflow. Let the delegated team act while the founder observes only agreed escalations. Record requests for missing information and decisions that were delayed.
For the full week, maintain an exception log rather than interrupting for every routine question. Keep service standards and customer commitments visible. Avoid removing support from work that requires specialist judgement.
Afterwards, review outcomes with the team: what worked, what required improvisation and what should change? Update authority, documentation and cover arrangements. Repeat the test when a material role or process changes.
The strongest result is not zero messages. It is a week of sound decisions, maintained service and a small, understandable set of legitimate escalations.