If you disappeared for ninety days — no calls, no email, no decisions, no rescue — what in your business actually stops?
Not what gets messy. Not what slows down. What stops cold, because you were not there to hold it up.
Most founders cannot answer that in under a minute. The effort it takes to produce the list is the measurement. So here is a way to run the question properly, because it is not rhetorical. It is a test, and like any test it has a sequence.
The 90-Day Absence Test
The 90-Day Absence Test is a dependency audit you can run on your own business in an afternoon. Four moves, and they only work in order:
- The Dare — answer the absence question honestly, with no rescue clause.
- The Stop List — separate what stops from what merely slows.
- The Dependency Sort — classify each stop-point by what it actually depends on.
- The Conversion — rebuild each stop-point as architecture instead of memory.
Most people skip move two. They jump from the dare straight to a to-do list of things to document, and they never learn which of those things are load-bearing. That is why the exercise so often produces a folder of notes nobody reads and nothing changes.
Move One: Take the Dare Honestly
Three rules make this move useful.
Ninety days means ninety. Not "I would check in on Fridays." Not "well, I would still take the important calls." The rescue clause invalidates the test. You are measuring what the organization can carry without you, not what it can carry if you stay lightly involved.
Write, do not think. Set a timer for ten minutes and produce answers without editing. The first few will be polite and flattering. The real list surfaces underneath them, usually somewhere around minute six.
Answer in the present tense. Not "I would like to think the team could handle it." What actually happens. You already know. The point of writing it down is to stop negotiating with what you know.
Move Two: Build the Stop List
A stop-point has three properties: no owner, no substitute, and no written standard. If any one of those three exists, you have a slow — tolerable, expensive, survivable. If none of them exist, you have a stop.
Write each one as a complete sentence, in this shape:
If I am gone, ______ does not happen, and there is no one who can ______.
Two families usually appear. Decision stops — nothing gets approved, priced, hired, killed, or committed. Knowledge stops — nobody knows why the process runs this way, what the client actually agreed to, or where the real constraint lives. The first family is about authority. The second is about memory. They need different repairs, which is why mixing them together in one list wastes your afternoon.
Move Three: The Dependency Sort
Go down the stop list and tag each item with the thing it actually leans on. Four types cover nearly everything:
- Memory dependency — it lives in your head.
- Judgment dependency — it lives in your instincts.
- Relationship dependency — it lives in your personal relationships.
- Permission dependency — it lives in your signature.
The tag tells you the repair. Memory becomes documentation. Judgment becomes a framework — written decision criteria anyone can apply. Relationship becomes breadth: more people holding the connection, not one person holding it all. Permission becomes delegation with a defined boundary, so the answer is not always you.
Move Four: The Conversion
For each stop-point you have tagged, build three things: a written standard, a named owner, and a place where the work is visible. Without all three, you have documentation. With all three, you have architecture.
Then define two boundaries for the owner. The decision criteria — what makes a good call here, written down in plain language. And the authority limit — what this person can decide without you, and the point at which it comes back. Ambiguity at that edge is what pulls founders back into every decision they were trying to leave behind.
Picture a founder who has answered the dare and found that pricing exceptions are a stop. Today, every discount call lands on her desk because she is the only person who knows which clients are worth bending for. The conversion is not a policy memo. The conversion is a written standard for exceptions, a named owner on the commercial side, an authority limit expressed in a range rather than a feeling, and a pipeline where every exception is recorded so the pattern becomes visible. She is no longer the exception engine. She is the person who designed it.
The Mistake That Kills the Exercise
Listing tasks instead of stops. Tasks are infinite; stops are a short list. If your list has forty items, you answered the wrong question.
There is a second, quieter mistake: building architecture nobody lives in. A document that is never opened during real work is not a system, it is an artifact. A standard that exists beside the work instead of inside it changes nothing. The test of a conversion is not whether it is written down — it is whether the work now happens inside it when you are not in the room.
The Advanced Version: Shrink the Interval
Once you have your list, do not go straight to ninety days. Go to fourteen. Announce it clearly, route the stop-points you converted to their owners, and count what comes back to you. Then run it at thirty. Then ninety.
A shrinking stop list across those intervals is what business sovereignty actually looks like in practice — not a founder who works less by accident, but an organization that holds its own shape when the founder steps out of frame.
Where the Executive Architecture Review Fits
The Executive Architecture Review takes this exercise and runs it as structured discovery rather than a solo afternoon. It is built to surface dependency patterns, blind spots, and the specific stop-points that keep pulling you back — and then to help you convert them into working architecture instead of a longer list.
EXIUSS Intelligence offers a 14-day free trial of that guided experience, including 95+ Founder Frameworks turned into actionable structure, a personalized EXIUSS Protocol that reveals your organizational dependencies, and a working Workspace where you build funnels, load your CRM and pipeline, and stand the first initiatives up. Everything you build in the trial carries over when you upgrade. To be transparent about the line: real-time voice conversation with the system is unlocked on the paid tier, not inside the trial.
Start here: trial.codebreakers.pro
The dare comes first, though. Answer it honestly — the real list, present tense, no rescue clause. Then book the Executive Architecture Review and bring that list with you. It is the most useful document you will hand anyone this year, because it is the only one that tells the truth about what your business still cannot do without you.