The 90-Day Protocol
One Pillar. One Rule. Ninety Days.
You have a number now. The number is not the work. It is the map. That is where the Story Tax is collected. Not in the diagnostic. In the moment your old story asks to be performed again. This protocol exists for that moment. It is not a leadership-development program. It is not a personality overhaul. It is a cost-reduction strategy.
This page summarizes the protocol. The full text, with the baseline steps, the five core rules, and the tracking tables, is Appendix B of The Story Tax (pp. 155 to 173).
One Pillar
Your score will surface a dominant pillar: the single behavioral pattern accounting for the largest share of your drag. One of the five is running at a cost the others are not.
Do not try to address all five simultaneously. The 90-Day Protocol in Appendix B is built around your dominant pillar only. Do not turn one diagnosis into five simultaneous projects. You will not know which rule worked, which one failed, or which story found a new route around both.
From The Story Tax, Chapter 6 (p. 57) and Appendix B (p. 157).
One Rule
The 90-Day Protocol turns your dominant STIx pillar into one visible operating rule. The rule replaces a recurring behavioral pattern with a structural constraint your team can see, use, and eventually trust.
Binary: It either held or it did not. Observable: A calendar, decision log, message thread, or project record can show what happened. Narrow: It targets one recurring behavior, not your entire leadership style. Protected: Legitimate exceptions are defined before the first hard moment arrives. Repeatable: You can run it without motivation, interpretation, or a committee meeting.
If the rule requires a paragraph to explain, it is not a rule. It is an intention.
Use the rule that matches your dominant pillar. Do not improve the language before you run it.
The Presence Rule
Decision Identity
The Authority Rule
Delegation Integrity
The Output Rule
Meeting Theater
The Timing Rule
After-Hours Processing
The Close-Date Rule
Speed Signature
The full text of each rule is in The Story Tax, Appendix B (pp. 162 to 164).
Ninety Days
Do not begin on Monday morning because you feel inspired by your score. That is how a behavioral experiment becomes a mood. Before Day 1, build the baseline: select one primary pillar, name the behavior precisely, select one operating measure and one quality guardrail, choose one witness, define exceptions before you need them, and record the baseline.
Hold the Rule
Days 1 to 21The first twenty-one days are not about improvement. They are about contact. You are going to encounter the behavior more often than you expect. That is not failure. It is the first useful data the protocol gives you.
Compliance Check, Not a Re-Score
Day 21At Day 21, check compliance and the operating measure. Do not demand a miracle and do not claim a full Tier 4 score change yet.
Rule-hold rate = eligible instances in which the rule held ÷ total eligible instances.
Find the Defense
Days 22 to 60By now, the story has noticed the rule. It will not announce itself as resistance. It will sound like experience: “This one is different.” Your job is to test whether the stated exception meets the exception criteria you wrote before Day 1.
Review the Mechanism, Not Your Mood
Day 45Review the log with your witness. Ask whether failures clustered around a specific audience, decision type, or identity threat; whether the team used the authority or space created; whether the operating measure moved; and whether the quality guardrail held.
Do not replace the rule because you are tired of it. Fatigue is not disconfirmation.
Measure, Adjust, Stabilize
Days 61 to 90The final thirty days answer a simpler question: Did the new behavior become part of the operating system, or did it remain a private act of willpower? Install one structural support. The support is not bureaucracy. It is the part of the organization that remembers the rule when you are busy being yourself.
Full Re-Run
Day 90Run the full diagnostic again. Compare like with like. Do not compare a raw analog score with a digital score.
A flat result is not failure. It is a finding.
A protocol that cannot stop for evidence is not a protocol. It is another story. If the protocol contributes to a material customer impact, legal or compliance risk, safety concern, decision-boundary breach, or repeated quality-guardrail failure, pause the rule. Document the event. Review the operating design with the relevant decision owner.
The protocol ends. The work does not.
From The Story Tax, Appendix B (pp. 157 to 173).
Protocol Questions
What is the 90-Day Protocol?
The 90-Day Protocol turns your dominant STIx pillar into one visible operating rule. The rule replaces a recurring behavioral pattern with a structural constraint your team can see, use, and eventually trust.
What happens at Day 21?
At Day 21, check compliance and the operating measure. Do not demand a miracle and do not claim a full Tier 4 score change yet. Return to your behavior log and calculate your rule-hold rate: eligible instances in which the rule held, divided by total eligible instances.
How is progress measured?
Do not interpret a lower score by itself as proof of improvement. The score is the mirror. The operating evidence is the face. Compare baseline behavior frequency, rule-hold rate, documented exceptions, operating measure, quality guardrail, and relevant pillar evidence.
What happens at Day 90?
Run the full diagnostic again. Compare like with like. A flat result is not failure. It is a finding.
From The Story Tax, Chapter 6 (p. 57) and Appendix B (pp. 156 to 173).
Keep Going
BookFunnel will ask for your email address to deliver the sample and to send you occasional emails about the book. You may opt out of any email at any time. Privacy Policy