Eliminate 90% of Decision Interruptions and Reclaim 8 Hours a Week: Decision Protocol for $70K–$100K Operators
For $90K–$150K/month founders with 3–8 person teams, this 2-hour decision protocol cuts 35–45 daily interruptions to 3–5 edge cases and frees 11–18 hours weekly.
The Executive Summary
Founders at $100K–$120K/month quietly lose 11–18 hours weekly to “quick questions,” turning into full-time decision bottlenecks instead of installing a 2-hour protocol that cuts 90% of interruptions.
Who this is for: Founders and operators at $90K–$150K/month with 3–8 person teams who feel permanently interrupted and suspect they’ve become the default decision-maker for everything.
The decision problem: The decision bottleneck trap where 35–45 “check with me” questions a day convert into 11–18 lost hours weekly and stall growth while the team’s judgment never develops.
What you’ll learn: The 2-Hour Decision Protocol with the Category Identification Hour, Rule Creation Hour, six decision categories that cover 85–95% of daily questions, and three authority levels your team can follow without you.
What changes if you apply it: You move from 40 ad-hoc questions a day to 3–5 true edge cases, free 9–16 hours weekly for strategy, and unlock stuck revenue bands like $94K–$118K or $112K–$124K+.
Time to implement: Block 2 hours once to build the protocol and a 30-minute team meeting to roll it out, then see 70–90% fewer questions within 30 days and a durable 11+ hours weekly of reclaimed founder time.
Written by Nour Boustani for $90K–$150K/month founders who want their teams to make 90% of decisions independently so they can get out of Slack and back into strategy.
Freeing 11–18 hours weekly at $90K–$150K/month comes from documented decision rules, not hope; upgrade to premium to get the full protocol, templates, and deployment toolkit.
› Library Navigation: Quick Navigation · Deep Dives
The $286K Decision Bottleneck Trap at $90K–$150K/Month
Aaron, Agency Owner, is stable at $112K/month with a 4-person team, but his day runs on “Got a minute?” pings instead of the growth work he plans.
He reviews every decision, answers every edge case, and the team won’t move without him.
He’s involved in everything, which quietly makes him essential to the business.
Aaron’s Business Current state:
Revenue steady (not growing)
Team capable (good hires)
Systems documented (clear processes)
Problem: The Team asks 35–45 questions daily, requiring Aaron’s decision
Typical day:
8 am: Start strategic work (growth planning)
8:17 am: “Should I approve this client request?” (3 minutes)
8:24 am: Back to strategic work
8:41 am: “Client wants meeting Friday, do I book it?” (2 minutes)
8:47 am: Back to strategic work
9:02 am: “This invoice looks wrong, what should I do?” (5 minutes)
9:11 am: Back to strategic work
9:28 am: “Client’s unhappy with timeline, how do I respond?” (8 minutes)
Decision interruption load:
Pattern: 35–45 interruptions daily.
Time per interruption: 3–5 minutes, including context switching.
Total time lost: 2–3.5 hours daily, 11–18 hours weekly on decision-making for the team.
Time impact:
Strategic work planned: 20 hours weekly
Strategic work actual: 2–7 hours weekly (the rest interrupted)
Decision interruptions: 11–18 hours weekly
Net capacity for growth: 2–7 hours weekly (90% reduction)
Revenue impact:
Can’t execute growth initiatives (no time)
Can’t develop new services (interrupted)
Can’t build partnerships (constant reactive mode)
Revenue stuck at $112K monthly for 11 months
Opportunity cost:
Growth initiatives blocked: $15K–$25K monthly potential (based on past successful launches)
Annual stuck revenue: $180K–$300K unrealized
Team impact:
Team can’t make decisions independently (waiting on Aaron)
Team velocity is slow, blocked on decisions 3–7 times daily
Team learning stunted (not practicing judgment)
Team morale: Frustrated by how dependent they feel on Aaron for every decision.
Aaron’s state:
Working 58 hours weekly
Decision fatigue by 2 pm daily
Strategic work fragmented (can’t think deeply)
Considering reducing team size (ironically, to reduce interruptions)
Total cost of being a decision bottleneck:
Time cost: 11–18 hours weekly, 30% of working hours.
Revenue cost: $180K–$300K annually in blocked growth
Team cost: Velocity reduction, morale issues, dependency
Founder cost: Burnout, fragmented focus, strategic paralysis
The trap, he thinks:
“I’m the only one who can make these decisions correctly.”
The cost: the team never learns, the founder stays essential forever, and the growth ceiling is at $112K.
[Decision Bottleneck Cost Snapshot]
[Daily Questions] --> 35–45
|
v
[Time Lost] --> 11–18 hrs/week
|
v
[Blocked Initiatives] --> Growth projects paused
|
v
[Outcome] --> Revenue stuck at $112K/monthThe $286K decision bottleneck trap is the backdrop; the next move is seeing how the same pattern repeats across $80K–$150K/month stages before you install the fix.
Decision Bottleneck Pattern Across $80K–$150K/Month Stages
Now that you’ve seen how decision bottleneck costs 11–18 hours weekly plus $180K–$300K annually, here’s where this mistake shows up at every stage.
At every revenue stage, founders become bottlenecks because they keep decision authority instead of delegating clear judgment frameworks.
At $80K–$100K: First hires ask constant questions, founder answers everything (8–12 hours weekly).
At $100K–$120K: Team of 3–5 asks 30–50 questions daily, founder essential for all decisions (11–18 hours weekly).
At $120K–$150K: Team of 6–8 waiting on decisions, velocity drops 40–60%, growth stalls.
At $150K+: Founder is a full-time decision-maker, zero time for strategy, revenue plateaus.
The pattern: keeping decision authority instead of delegating judgment frameworks.
The cost: $200K–$500K annually in opportunity cost, as the founder becomes a full-time reactive decision-maker rather than a strategic leader.
Most founders answer every question, which quietly teaches dependency.
The 2-Hour Decision Protocol establishes rules so the team makes 90% of its decisions independently, using the founder’s judgment criteria.
Systematic, not ad-hoc.
Revenue Stage Breakdown:
At $80K–$100K/month: First 1–2 team members
What it looks like: “Should I do X or Y?” asked 15–25 times daily
Where it shows: Every task requires confirmation, the founder answering questions 6–10 hours weekly
Typical mistake: Answering every question instead of creating decision rules
Cost without protocol: $100K–$150K annually in founder time opportunity cost
At $100K–$120K/month: Team of 3–5 people
What it looks like: “Check with me” interruptions 35–45 times daily
Where it shows: Founder’s calendar fragmented, strategic work impossible, constant reactive mode
Typical mistake: “Faster to just answer than explain the framework.”
Cost without protocol: $180K–$300K annually in blocked growth initiatives
At $120K–$150K/month: Team of 6–8 people
What it looks like: Decisions queued, team velocity drops, initiatives stall waiting for approval
Where it shows: Founder spending 25–35 hours weekly just making decisions for the team
Typical mistake: Keeping all decision authority “to maintain quality.”
Cost without protocol: $300K–$500K annually in growth ceiling
At $150K+/month: Team of 8–12+ people
What it looks like: Founder is a full-time decision bottleneck, and revenue plateaued
Where it shows: Can’t scale further without founder cloning themselves
Typical mistake: Hiring “decision-makers” instead of creating decision frameworks
Cost without protocol: Business unsellable (too founder-dependent)
Why the 2-Hour Decision Protocol Cuts 70–90% of Daily Questions
A 2-hour decision protocol build forces simplicity; long, drawn-out protocols get too complex to follow, and a fixed 2-hour window keeps you focused on only the essential rules.
The protocol builds decision trees for six common categories:
Client requests (scope, timeline, pricing)
Quality issues (errors, complaints, revisions)
Resource allocation (time, money, tools)
Communication (tone, timing, escalation)
Process exceptions (edge cases, special situations)
Team coordination (who does what, priorities)
These 6 categories cover 85–95% of daily decisions. When you build rules for these categories, the team decides independently most of the time, and only 5–15% of true exceptions still escalate while overall question volume drops by about 90%.
Judgment transfer:
Team learns the founder’s decision criteria and how decisions are actually made.
Team applies those criteria independently in day-to-day situations.
Team gets feedback on edge cases where the rules are not yet clear.
Team improves judgment over time as those edge cases are reviewed together.
Tight feedback cycle turns daily decisions into rapid learning for the team.
The 2-Hour Decision Protocol has been run across 50+ teams at $90K–$180K; in each case, a 2-hour build cut 85–92% of decision interruptions within 30 days. Founder time freed: 9–16 hours weekly, and revenue growth resumed in 80% of cases within 90 days.
Case — Marcus, Consultant, $94K/month with 3-person team.
Before protocol, the team asked 28 questions per day on average. Marcus spent 14 hours weekly answering them, and his strategic work was blocked.
Built the decision protocol in 2 hours on Saturday morning, created rules for 6 categories, and shared it with the team on Monday.
Weekly question trend after protocol:
Week 1: Questions dropped to 18 per day (36% reduction), with the team actively referring to the protocol.
Week 2: Questions dropped to 9 per day (68% reduction), and the team was making most decisions independently.
Week 4: Questions dropped to 3–4 per day (86% reduction), and only true edge cases were escalating.
Impact after protocol:
Time saved: 11 hours weekly.
Time used for: New service development.
Revenue change: $94K → $107K in 3 months.
Protocol ROI: 2 hours created $13K monthly, or $156K annually.
Priya, Agency Owner, $118K/month with 5-person team.
Before protocol: The team asked 41 questions daily, Priya spent 17 hours weekly deciding, and revenue had been stuck for 9 months.
Built protocol: 2 hours on Sunday afternoon, then a 30-minute Monday morning meeting to train the team and implement it.
Weekly question trend after protocol:
Week 1: Questions dropped to 26 daily (37% reduction).
Week 3: Questions at 12 daily (71% reduction).
Week 6: Questions at 4–5 daily (88% reduction). Sustained.
Impact after protocol:
Time saved: 14 hours weekly.
Used for: Partnership development, service expansion.
Revenue $118K → $131K in 4 months. Growth unblocked.
You’ve probably stayed essential for the same reasons.
The pattern across all cases: a decision protocol eliminates dependency.
Ad-hoc answering means the team never learns and you stay the permanent bottleneck.
Decision rules mean the team learns your judgment and the business operates independently.
The difference isn’t complexity; it’s the 2-hour forcing function, the clear categories, and the escalation clarity.
Systematic.
The 2-Hour Decision Protocol is where the story switches from diagnosing the decision bottleneck trap to explicitly engineering how decisions leave your plate in two focused hours.
2-Hour Decision Protocol for Systematic Decision Authority Transfer
Most founders think decision protocols take weeks to build. That’s wrong. Complexity kills adoption.
The 2-Hour Decision Protocol is a time-boxed procedure that identifies 6 decision categories in Hour 1, creates if/then rules for each in Hour 2, and deploys to the team immediately on Day 1.
Not theory. A tested procedure.
You execute two hours in sequence:
Hour 1 identifies categories where the team asks questions.
Hour 2 builds decision trees with clear rules.
That’s it.
The 2 phases:
Phase 1: Category Identification (Hour 1) — Map where questions come from
Phase 2: Rule Creation (Hour 2) — Build if/then decision trees per category
Why This Sequence
You can’t build rules until you know what you’re building them for.
Why sequence matters: You can’t create rules (Hour 2) until you’ve mapped question categories (Hour 1).
Order of operations: Hour 1 (Category ID) must be completed before Hour 2 (Rule Creation).
Core constraint: You can’t build decision trees without knowing decision types.
Result when done in order: When you execute both hours in sequence, decision authority transfers to the team, the team operates independently using the founder’s judgment criteria, and the founder is freed for strategy.
Back to Aaron: stuck at $112K/month, with 35–45 daily interruptions.
Starting situation:
Revenue: $112K/month stable, not growing
Problem: The Team asks 35–45 questions daily, and Aaron is essential for all decisions
Time cost: 11–18 hours weekly answering questions
Decision: Build decision protocol Saturday morning
Phase 1: Category Identification (Hour 1, 9 am–10 am)
Goal: Map all questions from the team into decision categories
Method: Review the past week of team questions (Slack history, email, in-person)
Aaron’s Week of Questions (sample 10 of 40+ total)
Monday:
“Client wants to add another page to website, should I approve?” — Client request
“Meeting invite for Friday 3pm, book it?” — Scheduling
“Client says logo looks wrong, do I redo?” — Quality issue
“Designer wants to buy new software $29/month, approve?” — Resource allocation
“Client email sounds frustrated, how should I respond?” — Communication tone
“Two projects due same day, which priority?” — Resource allocation
Tuesday:
“Client asking for discount, what do I say?” — Pricing
“Deliverable has typo client might not notice, fix or send?” — Quality standard
“Client wants call today, do I move other meeting?” — Scheduling priority
“Team member sick, do I tell client about delay?” — Communication transparency
(Continues through Friday... 40+ questions reviewed)
Step 1: Group questions into categories
Aaron’s categories emerged:
Category 1: Client Scope Requests (11 questions)
Adding features
Timeline changes
Deliverable modifications
Category 2: Quality Decisions (8 questions)
Errors/typos
Client complaints
Revision requests
Category 3: Resource Allocation (9 questions)
Tool purchases
Time prioritization
Budget decisions
Category 4: Scheduling (7 questions)
Meeting booking
Priority conflicts
Client urgency
Category 5: Communication (6 questions)
Response tone
What to tell clients
Escalation timing
Category 6: Pricing/Money (4 questions)
Discount requests
Upsell opportunities
Payment issues
Remaining: Uncategorized (5 questions)
True edge cases, one-off situations
Coverage: 35 of 40 questions (88%) fit six categories
Phase 1 complete: 6 decision categories identified, 88% coverage
When Every Question Routes To You
Once you see how 11–18 hours weekly disappear into the decision bottleneck trap, treating this as optional doesn’t make sense; upgrade to premium and build the protocol.
Phase 2: Rule Creation (Hour 2, 10 am–11 am)
Goal: Build if/then decision trees for each category
Method: For each category, create 3–5 rules covering common scenarios
Rule Template:
If [condition], then [action] — Authority: Team decides / Team notifies / Escalate to founder
Aaron’s Decision Rules by Category:
Category 1: Client Scope Requests
1. Rule 1A: If request within original scope → Approve immediately, execute.
Authority: Team decides independently
2. Rule 1B: If request adds <2 hours work → Approve, note on invoice for final billing discussion.
Authority: Team decides, notifies Aaron in weekly update
3. Rule 1C: If the request adds 2–5 hours of work → Send the client a formal scope change with cost/timeline impact, await client approval.
Authority: Team decides to send the scope change, notifies Aaron the same day
4. Rule 1D: If the request adds 5+ hours of work → Escalate to Aaron before responding to the client.
Authority: Founder decides
5. Rule 1E: If unclear whether in scope or not → Refer to original contract, if still unclear, escalate.
Authority: Team decides if clear, escalates if ambiguous
Category 2: Quality Decisions
1. Rule 2A: If deliverable doesn’t meet pre-delivery checklist → Fix before sending to client, no exceptions.
Authority: Team decides independently (quality standard)
2. Rule 2B: If client requests minor revision (<1 hour) → Implement immediately if within three total revisions.
Authority: Team decides independently
3. Rule 2C: If client requests major revision (1–3 hours) → Implement if within scope and <3 total revisions, notify Aaron.
Authority: Team decides, notifies same day
4. Rule 2D: If client requests revision #4+ → Escalate to Aaron before responding.
Authority: Founder decides (may indicate deeper issue)
5. Rule 2E: If the client complains about quality → Acknowledge immediately, investigate, propose a solution, notify Aaron within 2 hours.
Authority: Team responds professionally, founder reviews the resolution
Category 3: Resource Allocation
1. Rule 3A: If tool/software under $50/month and approved category → Purchase, submit receipt.
Authority: Team decides independently
Approved categories: Design software, project management, productivity independently
2. Rule 3B: If tool/software $50–$200/month → Propose with business case, await Aaron’s approval.
Authority: Founder approves
3. Rule 3C: If tool/software $200+/month → Full proposal with ROI analysis required.
Authority: Founder approves after evaluation
4. Rule 3D: If two projects need same resource (time conflict) → Prioritize by client tier (A > B > C), then by deadline.
Authority: Team decides using tier system
Rule 3E: If resource needed but not budgeted → Escalate with business case.
Authority: Founder decides
Category 4: Scheduling
1. Rule 4A: If meeting request within business hours → Book if Aaron’s calendar shows available.
Authority: Team decides independently
2. Rule 4B: If an urgent client request conflicts with an existing meeting → Prioritize client meeting, reschedule internal meeting.
Authority: Team decides independently
3. Rule 4C: If two client meetings conflict → Prioritize by client tier (A > B > C)
Authority: Team decides, notifies both clients professionally
4. Rule 4D: If the client wants a meeting outside business hours → Offer alternative times in business hours first, escalate if the client insists.
Authority: Team offers alternatives, founder decides on exceptions
5. Rule 4E: If meeting request with <4 hours notice → Check Aaron calendar, if available book it, if not propose next available.
Authority: Team decides based on availability
Category 5: Communication
1. Rule 5A: If client question answered in documentation/past emails → Send reference + brief friendly explanation.
Authority: Team decides independently
2. Rule 5B: If client seems frustrated (but not hostile) → Respond with empathy, propose solution, notify Aaron within 4 hours.
Authority: Team responds, notifies founder
3. Rule 5C: If client uses hostile/angry tone → Acknowledge professionally, de-escalate, notify Aaron within 1 hour, pause work.
Authority: Team responds calmly, founder handles resolution
4. Rule 5D: If needed to deliver bad news (delay, issue) → Be transparent, explain the situation, propose a solution, notify Aaron before sending.
Authority: Team drafts, founder reviews before sending
5. Rule 5E: If the client asks for Aaron specifically → Ask if the team member can help, if the client insists, loop Aaron in.
Authority: The Team tries to help first, escalates if needed
Category 6: Pricing/Money
1. Rule 6A: If client asks for discount → Politely decline, explain value, escalate if client pushes.
Authority: Team declines first, founder decides on exceptions
2. Rule 6B: If payment is overdue 7+ days → Send a friendly reminder, if no response in 3 days, escalate.
Authority: Team sends a reminder, founder handles non-payment
3. Rule 6C: If opportunity for upsell (additional service) → Mention organically if relevant, don’t hard-sell, notify Aaron.
Authority: Team plants seed, founder closes upsell
4. Rule 6D: If the invoice has an error → If under $100, fix immediately; if over $100, notify Aaron first.
Authority: Team fixes small errors, founder approves large corrections
5. Rule 6E: If client asks for payment plan → Escalate to Aaron with client details.
Authority: Founder decides payment terms
Phase 2 complete: 30 decision rules created across six categories (5 rules each).
Total protocol time: 2 hours (1 hour category ID + 1 hour rule creation)
Output: Decision Protocol Document (shared with team)
Deployment: Monday morning team meeting (30 minutes)
Aaron presented the protocol to the team:
Explained purpose (1): Faster decisions, team empowerment
Walked through protocol (3): 6 categories and example rules
Feedback and edge cases (5):
Answered questions about edge cases
Set expectation to follow rules and escalate only when needed
Established a weekly review of edge cases to improve the protocol
Week 1 Results:
Questions asked Monday–Friday:
Monday: 31 questions (down from 35–45 baseline)
Tuesday: 26 questions
Wednesday: 19 questions (team getting comfortable)
Thursday: 16 questions
Friday: 13 questions
Week 1 average: 21 questions daily (40% reduction from baseline 35–45)
Aaron’s time: 7 hours weekly answering questions (down from 11–18 hours).
Week 2–4 Results:
Questions continued dropping as the team internalized the protocol:
Week 2 average: 12 questions daily (66% reduction)
Week 3 average: 7 questions daily (80% reduction)
Week 4 average: 4 questions daily (89% reduction)
Post-protocol steady state:
Sustained questions: 3–5 per day from Week 4 onward.
Aaron’s time on decisions: 1.5–2 hours weekly (down from 11–18 hours).
Time freed: 11 hours weekly (65% reduction in decision-making time).
Time allocation shift
Before protocol:
Strategic work: 7 hours weekly (fragmented)
Decision-making: 14 hours weekly
Client work: 15 hours weekly
Operations: 12 hours weekly
Total: 48 hours weekly
After protocol (Week 4+):
Strategic work: 18 hours weekly (uninterrupted blocks)
Decision-making: 2 hours weekly
Client work: 15 hours weekly
Operations: 8 hours weekly
Total: 43 hours weekly (5 fewer hours, more strategic output)
Revenue impact (Month 2–4)
Strategic time used for:
New service development (8 hours weekly for 6 weeks)
Partnership outreach (4 hours weekly for 8 weeks)
Team training on advanced skills (3 hours weekly, ongoing)
Results:
Month 2: $112K (protocol implemented, strategic work started)
Month 3: $118K (new service launched, 2 upsells)
Month 4: $124K (partnership closed, new client tier)
Month 5: $127K (momentum sustained)
Annual impact:
Revenue baseline: $112K → $124K.
Monthly change: +$12K
Annual change: +$144K
ROI summary:
Time invested: 2 hours protocol creation.
Revenue impact: $144K additional annual revenue.
Return: 72× revenue per hour invested.
Phase 1: Category Identification Hour for Team Decision Questions
Timeline: 60 minutes
Purpose: Map team questions into decision categories
Tools needed: Last week’s Slack/email history, notepad or spreadsheet
Output: 5–7 decision categories covering 80%+ of questions
Step 1: Collect 30–50 Team Questions from the Last 5 Days
Pull the last 5 business days of team questions
Where to look:
Slack direct messages
Email to you from the team
In-person questions (if you track them)
Meeting notes where decisions were requested
Minimum target: 30–50 questions reviewed
Copy questions into the list:
[Question 1]
(Continue through 30–50 questions)
Aaron’s collection (40 questions from Mon–Fri):
Client wants to add a page, approve?
Meeting Friday, 3 pm, book?
Client says logo wrong, redo?
Designer wants software $29/mo, approve?
Client email frustrated, how to respond?
(Continues to #40...)
Step 2: Group Recurring Questions into 5–7 Decision Categories
Group similar questions: read through all questions, notice patterns, and create groups.
Common patterns:
Client asking for changes (scope)
Team asking about quality/errors
The team is asking about spending money
Team asking about scheduling
Team asking how to communicate
Team asking about priorities
Don’t overthink. If 3+ similar questions, it’s a category.
Aaron’s grouping:
Group A: Client Scope Changes (11 questions)
Add feature
Change timeline
Modify deliverable
Group B: Quality/Errors (8 questions)
Fix before sending?
Client complaint
Revision requests
Group C: Money/Resources (9 questions)
Buy software?
Approve expense?
Budget decisions
Group D: Scheduling (7 questions)
Book this meeting?
Which priority?
Client’s urgent request
Group E: Communication (6 questions)
How to respond?
What tone?
When escalate?
Group F: Pricing (4 questions)
Discount request
Payment issue
Upsell opportunity
Uncategorized: 5 questions (true one-offs)
6 categories cover 35 of 40 questions, 88% coverage.
Step 3: Validate Decision Categories Cover 80%+ of Team Questions
Refine category names and definitions. For each category, write:
Category Name: _
Definition: This category covers decisions about...
Refine category names and definitions. For each category, write:
Category Name: _
Definition: This category covers decisions about...
Example questions:
_
(Add more questions as needed)
Frequency: Approximately _ questions per week
Aaron’s validated categories:
Category 1: Client Scope Requests
Definition: When clients ask for changes/additions to the original agreement
Examples:
“Can you add X?”
“Change deadline to Y?”
“Include Z too?”
Frequency: ~11 per week
Category 2: Quality Decisions
Definition:
Issues with deliverable quality
Errors
Client complaints
Examples:
“This has typo, fix?”
“Client unhappy with design.”
“Redo this?”
Frequency: ~8 per week
Category 3: Resource Allocation
Definition:
Spending money,
Prioritizing time
Using resources
Examples:
“Buy this tool?”
“Which project first?”
“Approve expense?”
Frequency: ~9 per week
Category 4: Scheduling
Definition:
Calendar decisions
Meeting priorities
Time conflicts
Examples:
“Book this?”
“Move that?”
“Client urgent call?”
Frequency: ~7 per week
Category 5: Communication
Definition:
How/when to communicate with clients
Tone
Escalation
Examples:
“How respond?”
“What to say?”
“Tell client about delay?”
Frequency: ~6 per week
Category 6: Pricing/Money
Definition:
Discounts
Payment terms
Invoicing
Upsells
Examples:
“Give discount?”
“Payment late, what do?”
“Offer upsell?”
Frequency: ~4 per week
Hour 1 complete: 6 categories identified, 88% question coverage
Phase 2: Rule Creation Hour for If/Then Decision Rules
Timeline: 60 minutes
Purpose: Build if/then decision trees for each category
Output: 3–5 rules per category with clear authority levels
Rule Creation Template for Decision Authority Levels
For each category, create 3–5 rules:
Category Name: _
Rule [X]:
If [condition], then [action]
↓
Authority level:
☐ Team decides independently
☐ Team decides + notifies founder
☐ Escalate to founder
↓
Rationale: _
(Repeat 3–5 times per category)
Step 1: Build Rules for the Highest-Frequency Decision Category
Pick the category with the most questions. Build 5 rules.
Aaron started with Category 1: Client Scope Requests (11 questions/week)
Rule structure:
Small changes (easy, yes)
Medium changes (judgment needed)
Large changes (escalate)
Unclear situations (how to handle)
Emergency requests (time-sensitive)
Aaron’s Category 1 Rules (completed in 15 min):
Rule 1A: If clearly within original scope → Approve immediately
→ Authority: Team decides independently
→ Rationale: No cost/timeline impact, straightforward
Rule 1B: If adds <2 hours work → Approve, note for invoice discussion
→ Authority: Team decides + notifies weekly update
→ Rationale: Minor impact, manageable
Rule 1C: If adds 2–5 hours work → Send scope change to client, get approval
→ Authority: Team decides + notifies same day
→ Rationale: Client needs to approve, moderate impact
Rule 1D: If adds 5+ hours work → Escalate before responding
→ Authority: Founder decides
→ Rationale: Major impact needs founder evaluation
Rule 1E: If unclear whether in scope → Check contract, if still unclear, escalate
→ Authority: Team tries first, escalates if needed
→ Rationale: Teach contract interpretation
Category 1 complete: 5 rules, 15 minutes
Step 2: Build 3–5 Rules for Each Remaining Decision Category
Template approach
Every category needs:
Rule A: Simple/clear situation (team decides)
Rule B: Standard situation (team decides + notifies)
Rule C: Complex situation (team decides with parameters)
Rule D: High-stakes situation (escalate)
Rule E: Edge case handling (how to determine)
Aaron’s remaining categories (9 min each)
Category 2: Quality Decisions (9 min)
Rule 2A: If fails checklist → Fix before sending (team decides)
Rule 2B: If minor revision <1hr → Implement if <3 total (team decides)
Rule 2C: If major revision 1–3hr → Implement if in scope (team decides + notifies)
Rule 2D: If revision #4+ → Escalate (founder decides)
Rule 2E: If quality complaint → Acknowledge, fix, notify within 2hr (team responds + notifies)
Category 3: Resource Allocation (9 min)
Rule 3A: If <$50/mo approved category → Purchase (team decides)
Rule 3B: If $50–$200/mo → Propose with case (founder approves)
Rule 3C: If $200+/mo → Full ROI proposal (founder approves)
Rule 3D: If time conflict → Prioritize by tier, then deadline (team decides)
Rule 3E: If unbudgeted → Escalate with case (founder decides)
Category 4: Scheduling (9 min)
Rule 4A: If business hours → Book if available (team decides)
Rule 4B: If urgent conflicts internal → Prioritize client (team decides)
Rule 4C: If two clients conflict → Prioritize by tier (team decides)
Rule 4D: If outside hours → Offer alternatives first (team tries, founder decides exception)
Rule 4E: If <4hr notice → Check availability, book or propose next (team decides)
Category 5: Communication (9 min)
Rule 5A: If answered in docs → Send reference + explanation (team decides)
Rule 5B: If frustrated client → Empathize, solve, notify 4hr (team responds + notifies)
Rule 5C: If hostile client → De-escalate, notify 1hr, pause (team responds + founder resolves)
Rule 5D: If bad news → Transparent, solution, review before send (team drafts + founder reviews)
Rule 5E: If asks for Aaron → Team tries help first, escalate if insists (team tries + escalates)
Category 6: Pricing/Money (9 min)
Rule 6A: If discount request → Decline politely, escalate if pushes (team declines + founder decides exception)
Rule 6B: If payment 7+ days late → Reminder, 3 days escalate (team reminds + founder handles)
Rule 6C: If upsell opportunity → Mention if relevant, notify (team plants + founder closes)
Rule 6D: If invoice error <$100 → Fix immediately, if >$100 notify first (team fixes small + founder approves large)
Rule 6E: If payment plan request → Escalate with details (founder decides)
Hour 2 complete: 30 rules across 6 categories (5 rules each)
Total protocol time: 2 hours
You’ve seen how the protocol works when it’s built and deployed cleanly. Now you need to see what quietly breaks it before you run it in your own business.
Three Hidden Failure Modes That Break Decision Protocols
The 2-Hour Decision Protocol works when kept simple. Here’s what breaks it.
Problem 1: Overcomplicated Decision Rules with 10+ Conditions Per Category
You try to solve the decision bottleneck by making the protocol bigger, not simpler.
What it is: building decision trees with 15–20 rules per category, trying to cover every scenario.
Why it happens: fear of missing edge cases and perfectionism.
What it costs: the team can’t remember the rules, doesn’t use the protocol, and keeps asking the same questions; the protocol is abandoned within 2 weeks and you’re back to the bottleneck.
The fix: maximum five rules per category; if you need more, your categories are too broad, so split them into two categories.
Problem 2: Vague Decision Authority Levels That Say “Use Your Judgment”
What it is: rules that say “decide what’s best” without clear criteria.
Why it happens: the founder is uncomfortable with clear, binary decision authority.
What it costs: the team still asks questions because “judgment” is undefined; the protocol doesn’t reduce questions, and time is wasted creating it.
The fix: use three clear levels only—“Team decides independently,” “Team decides + notifies founder,” or “Escalate to founder.” No ambiguity.
Problem 3: Building a Decision Protocol Without Training the Team
What it is: Creating a protocol, sending it to the team via email, and assuming they’ll follow it.
Why it happens: “It’s self-explanatory.”
What it costs: The team doesn’t read it, doesn’t remember it, and keeps asking questions; the protocol goes unused and has zero impact.
The fix: Run a 30-minute team meeting to walk through the protocol, answer questions, role-play scenarios, get buy-in, and then deploy.
Avoid these three:
Keep rules simple (5 max per category).
Make authority crystal clear (3 levels).
Train the team actively (30-minute meeting).Protocol works.
Full Time and Revenue Math on the 2-Hour Decision Protocol
Typical decision bottleneck:
Questions daily: 35–45
Time per question: 3–5 minutes (including context switch)
Weekly time: 11–18 hours
Strategic work: Fragmented, interrupted, minimal
Revenue: Stuck (no growth capacity)
After 2-Hour Protocol (Week 4+ sustained)
Questions daily: 3–5 (90% reduction)
Time per question: Same (3–5 min)
Weekly time: 1.5–2 hours (89% reduction)
Time freed: 11 hours weekly minimum
Strategic work: 11 uninterrupted hours weekly
Revenue: Growth resumed (capacity unlocked)
Net impact:
Time investment: 2 hours protocol + 30 min team training
Time returned: 11 hours weekly→ 572 hours annually
ROI per hour: 572 ÷ 2.5 = 229× return on time invested
Revenue impact: Strategic capacity restored to $100K–$300K annually (typical growth when the bottleneck is removed).
Aaron’s numbers
Before protocol:
Questions: 40 daily average
Time: 14 hours weekly
Strategic work: 7 hours weekly (fragmented)
Revenue: $112K monthly (stuck 11 months)
After protocol (Week 4):
Questions: 4 daily average (90% reduction)
Time: 2 hours weekly
Strategic work: 18 hours weekly (uninterrupted)
Time freed: 12 hours weekly
Used freed time for:
New service development: Launched Month 3 → +$6K monthly
Partnership development: Closed Month 4 → +$8K monthly
Team skill building: Improved delivery efficiency → +$3K monthly margin
Revenue trajectory:
Month 1: $112K (protocol built)
Month 2: $112K (strategic work started)
Month 3: $118K (new service launched)
Month 4: $124K (partnership closed)
Month 5–6: $127K (sustained)
Annual impact: +$15K monthly average → +$180K annually
Return: 2 hours created $180K annually → $90K per hour invested
What Changes in Your Business When You Install the 2-Hour Decision Protocol
What Changes:
Day 1 (protocol deployment)
Team trained on six categories, 30 rules
Questions continue (team learning)
The founder is still answering most (transition period)
Week 1:
Questions drop 30–40% (team trying protocol)
Founder time: 7–10 hours weekly (improvement starting)
Team confidence: Building (seeing it work)
Week 2–4:
Questions drop 70–90% (protocol internalized)
Founder time: 1.5–3 hours weekly (sustainable state)
Strategic work: Uninterrupted blocks possible
Team velocity: Faster (not waiting on decisions)
Month 2–3:
Freed time applied to growth initiatives
Revenue momentum returns
Team judgment improving (learning from edge cases)
Month 4+:
Protocol: Refined based on edge cases.
Team decisions: Better than the founder in some areas (closer to details).
Founder role: Strategic only, team handles tactical.
Revenue: Growing (bottleneck removed).
What doesn’t change:
Quality standards (protocol enforces them)
Founder involvement (still reviewing, just less frequent)
Team accountability (actually increases with clear authority)
What improves:
Team autonomy (90% independent decisions)
Founder focus (11+ hours weekly for strategy)
Team learning (practicing judgment builds skill)
Revenue growth (strategic capacity restored)
Founder energy (decision fatigue eliminated)
When Two Hours Decide $286K
If you won’t spend 2 hours installing the 2-Hour Decision Protocol, you’re quietly accepting the $180K–$300K annual tax of doing everyone’s thinking; block the time and run it.
Run the 2-Hour Decision Protocol Field Test Checklist
Next time you’re fielding 25+ “quick questions” a day, run this before you accept another quarter of being the decision bottleneck.
☐ Logged 5 days of “check with me” questions, counted daily volume, and wrote weekly decision hours using the 11–18 hour bottleneck math.
☐ Clustered 30–50 questions into 5–7 decision categories and confirmed they cover at least 80% of your team’s question load.
☐ Wrote 3–5 if/then rules plus authority levels for each category so the team knows when to decide, notify, or escalate.
☐ Ran a 30-minute protocol rollout meeting and logged question volume in Weeks 1 and 4 to see if you hit the 70–90% drop.
☐ Logged weekly hours reclaimed and the revenue or projects you moved into that 9–16 hour block so you can see your own $180K–$300K upside.
Two focused hours here are what stop the $180K–$300K decision bottleneck tax from chaining your $90K–$150K/month capacity to Slack instead of strategy.
Where to Go From Here: Install the 2-Hour Decision Protocol and Stop Donating Strategic Time
If you’re in the $90K–$150K/month band and still trapped in the decision bottleneck pattern, you’re donating 11–18 hours a week you never get back.
From here, run the sequence once:
Map recent “check with me” decisions into the 6 core categories so the 2-Hour Decision Protocol targets the real interruption pattern instead of random noise.
Build rules and authority levels for each category so 35–45 daily questions collapse into a handful of true edge cases instead of hitting you by default.
Roll the protocol in one team session so your next 4 weeks run on documented judgment instead of ad-hoc approvals, and you see the reclaimed time in your calendar.
This protocol becomes the permanent line between a business that needs you in every decision and one where The 2-Hour Decision Protocol prevents that drag from coming back.
FAQ: 2-Hour Decision Protocol System
Q: How does the 2-Hour Decision Protocol eliminate 90% of “check with me” interruptions?
A: In 2 hours you map six decision categories and create 30 if/then rules with clear authority levels, so the team handles 85–95% of daily decisions and only 3–5 true edge cases reach you each day.
Q: How much does the decision bottleneck trap cost a $100K–$120K/month founder each year?
A: Answering 35–45 questions daily consumes 11–18 hours weekly, blocks growth initiatives, and quietly costs $180K–$300K in unrealized upside while keeping you stuck as the essential decision-maker at around $112K/month.
Q: Why does the decision bottleneck trap keep turning founders into full-time reactive decision-makers?
A: Founders answer every question instead of building decision rules, so at $80K–$150K/month teams ask 15–50 questions daily, judgment never develops, and the business loses $100K–$500K annually in opportunity as revenue plateaus.
Q: How do I use the 2-Hour Decision Protocol with its Category Identification Hour and Rule Creation Hour before my next quarter?
A: In Hour 1 you review 30–50 questions from the last 5 days and group them into 5–7 categories; in Hour 2 you create 3–5 if/then rules and authority levels per category, then run a 30-minute team meeting to walk through the protocol so questions drop 70–90% within 30 days.
Q: What happens if I keep answering 35–45 “quick questions” a day instead of installing this protocol?
A: You keep losing 11–18 hours weekly, your strategic work shrinks to 2–7 hours, and revenue stays stuck between $94K and $124K while $180K–$300K in growth potential and 572+ hours of annual strategic capacity remain locked.
Q: How does Marcus’s example show the ROI of building a decision protocol in just 2 hours?
A: Marcus cut daily questions from 28 to 3–4 in 4 weeks, freed 11 hours weekly, and turned those hours into a new service that took him from $94K to $107K/month in 3 months—an annualized $156K return from a one-time 2-hour build.
Q: How does Priya’s team at $118K/month change once the 2-Hour Decision Protocol is live?
A: Her team’s questions fell from 41 to 4–5 per day over 6 weeks, she recovered 14 hours weekly for partnerships and service expansion, and revenue grew from $118K to $131K in 4 months after being stuck for 9 months.
Q: What are the six decision categories that cover 85–95% of daily team questions?
A: The protocol organizes questions into client requests, quality issues, resource allocation, communication, process exceptions, and team coordination (including scheduling and pricing/money), so nearly all decisions route through predefined rules instead of landing directly on you.
Q: How do the three authority levels stop vague “use your judgment” instructions from backfiring?
A: Every rule specifies whether the team decides independently, decides and notifies you, or escalates, which removes ambiguity, prevents default escalation, and ensures only 5–15% of truly high-stakes decisions reach you.
Q: How much time and revenue does a working decision protocol unlock over 12 months?
A: A typical founder invests 2 hours to build the protocol and 30 minutes to train the team, then gains at least 11 uninterrupted hours weekly—about 572 hours annually—that can be converted into $100K–$300K in additional revenue once the decision bottleneck is removed.
⚑ Found a Mistake or Broken Flow?
Use this form to flag issues in articles (math, logic, clarity) or problems with the site (broken links, downloads, access). This helps me keep everything accurate and usable. Report a problem →
› More to Explore: Quick Navigation · Deep Dives
➜ Help Another Founder, Earn a Free Month
If this system helps you recover 11–18 hours weekly and $180K–$300K in blocked growth from decision bottlenecks, share it with one founder who needs that relief, not as a pitch but as relief.
When you refer 2 people using your personal link, you’ll automatically get 1 free month of premium as a thank-you.
Get your personal referral link and see your progress here: Referrals
Get the 2-Hour Decision Protocol Implementation Toolkit
You’ve read the system. Now implement it.
Premium gives you:
Battle-tested PDF toolkit with every template, diagnostic, and formula pre-filled—zero setup, immediate use
Audio version so you can implement while listening
Unrestricted access to the complete library—every system, every update
What this prevents: Staying the permanent decision bottleneck and losing 11–18 hours weekly plus $180K–$300K in blocked growth.
What this costs: $12/month. You get the implementation toolkit for this decision bottleneck system, not just the article.
Download everything today. Implement this week. Cancel anytime, keep the downloads.
Already upgraded? Scroll down to download the PDF and listen to the audio.
