Operator readiness is often discussed as a personality judgment. Someone is “ready” because they are experienced, trusted, or confident in meetings. Those qualities matter, but they do not answer the operational question: when a familiar situation appears without the founder, can this person identify the decision, use the available context, act within a boundary, and leave a clear record?
A readiness test should make that question easier to see. It should not be a surprise exam, a performance of loyalty, or a way to find fault with someone who was never given enough authority.
Test a situation, not a job title
Start with one recurring handoff. It might be a delivery exception, a client request, a resourcing choice, or an internal escalation. Pick a situation that matters but is safe enough to discuss openly. Do not begin with the most confidential or politically loaded decision in the agency.
Write the scenario in plain language. Include the information an operator would actually receive, but do not add a hidden clue that the founder normally keeps in their head. The test is supposed to show whether the operating context is usable, not whether the operator can guess what the founder wants.
For a Singapore-based agency working with clients in different markets, be explicit about the setting. State the relevant time zone, the expected response window if one exists, and who is available during that window. Avoid turning those details into a promise to every client; they are simply part of the scenario being tested.
The four signals to observe
Watch for four things during the drill.
Recognition: Does the operator identify that the scenario fits the handoff? If not, the trigger may be hidden in the founder’s language or not defined at all.
Reasoning: Can the operator explain which facts matter and which are noise? A useful handoff gives them context without requiring a full oral history.
Authority: Does the operator know what they can decide, what they can communicate, and when to escalate? Hesitation is not always a capability issue. It may reveal that the boundary has never been made explicit.
Record: Can the operator say where they would capture the decision, the next action, and any unresolved question? A decision that lives only in a private conversation is hard to hand off again.
These signals give the founder something better than a vague impression. They show which part of the operating system needs work.
Run the drill in three passes
The first pass should be quiet. Give the operator the scenario and the available context. Ask them to talk through what they would do, without interrupting to correct them. Take notes on the questions they ask and the assumptions they make.
The second pass introduces one realistic wrinkle. A client changes the priority. A team member becomes unavailable. A deadline is at risk. The wrinkle should reflect the agency’s work, not a theatrical trick. Ask the operator what changed, whether the original decision still stands, and what they would communicate.
The third pass closes the loop. Ask them to draft the short message or ledger entry they would leave behind. The writing does not need to sound like the founder. It needs to make the decision and next step legible to the next person.
If this is a first drill, 30 minutes is enough to learn a lot. Protect the time from turning into a general strategy discussion. The point is to test the handoff, not solve the entire agency in one conversation.
Score the handoff, not the person
Use a simple scale for each signal: clear, partly clear, or blocked. Then describe the evidence. “Partly clear: identified the trigger but asked who could approve the scope change” is more useful than “not ready.”
Some common results:
- Recognition is blocked: the handoff needs a clearer trigger and examples.
- Reasoning is blocked: the context is incomplete, contradictory, or too dependent on founder history.
- Authority is blocked: the agency has not decided the boundary. No amount of confidence training can fix an absent decision rule.
- Record is blocked: the agency needs a named place and a minimum record format.
Treat the result as a design input. The operator may also tell you that a scenario should not be delegated yet. That is valuable. Readiness includes the ability to identify a genuine boundary, not a requirement to accept every responsibility immediately.
The agency handoff plan guide explains how to turn each finding into a usable trigger, decision, boundary, and record. The founder dependency guide can help you choose the first dependency if the agency has too many possible tests.
Give feedback that preserves trust
Start with what the operator could see and act on. Then name the ambiguity in the system. “You had the project context, but the plan did not say whether this type of change needed approval” is a better conversation than “you should have known.”
Invite the operator to challenge the handoff. Ask what felt risky, what information arrived too late, and where they would want a backup. Their answers are not resistance to delegation. They are evidence about whether the operating design matches the work.
If the operator made a reasonable decision that differs from the founder’s preferred answer, examine the boundary before correcting the person. A handoff cannot be successful if the hidden standard is “make the choice I would have made.” It needs an explicit decision rule or a clear statement that the operator owns the judgment.
Repeat with variation
One successful drill proves only that one scenario was workable on that day. Repeat with a second situation that uses a different kind of judgment. For example, pair a delivery decision with an internal resourcing decision. Compare what transfers and what remains founder-specific.
Do not run a test every week for its own sake. Run one after a material change, after an absence, or when the same question keeps returning. Record the changes in the operating ledger so the agency can see why the handoff evolved.
Readiness is a relationship with the system
An operator is not a replacement founder. The aim is not to reproduce every instinct, preference, or relationship. The aim is to create enough shared context and authority for defined work to move, with an honest route for the work that should still come back.
That is why the test belongs alongside a planned absence conversation. The planned founder absence guide helps set the period and boundaries for the test. If the deeper objective is future transfer of ownership, the ownership transition preparation guide explains why repeated, observable operating decisions matter beyond a single week away.
The most useful result of a readiness test is not a pass. It is a precise sentence about what the operator can own now, what needs clearer context, and what the founder still needs to decide before the next handoff.