Season 2 - Episode 3: Your Team Isn’t Slow: Your Decisions Are

If execution feels slower than it should in your company, this episode is for you. In founder- and CEO-led startups, the most expensive operational bottleneck is often not productivity—it’s Decision Cycle Time : how long it takes to make a decision and actually keep it decided.

When decisions keep bouncing back to the top, teams escalate more, meetings multiply, and execution slows down across the business. In this episode of HR Decoded, Annekah Hall breaks down why this happens, how to spot it early, and how to install a practical decision system in 30–90 days—without adding unnecessary bureaucracy.

What we cover Why “slow execution” is often a decision design problem, not a talent problem The 3 concrete symptoms of decision drag: Decisions stretching from hours to days/weeks Meetings ending without owners and dates Founder context-switching becoming the operating model What Decision Cycle Time actually measures (and why “re-deciding” is expensive) The 3 root-cause gaps: Decision rights Decision protocols Spend/commitment thresholds A practical 5-step mechanism to reduce escalations and speed execution: Identify decision categories clogging your week Assign decision rights with clear DRIs and guardrails Install spend and commitment approval protocols Build a decision log to prevent re-deciding Run weekly cadence to move stuck decisions Real-world before/after example of removing a CEO approval bottleneck in ~90 days Common objections and direct rebuttals A 30-day quick-start sprint to implement immediately Key takeaway Your team cannot execute faster than your company can decide. If decision rights are unclear, everything routes upward.

If approval rules are inconsistent, people escalate for safety. If decisions aren’t documented, you relitigate and lose momentum.

Timestamps 00:00 Intro + challenge to founders and leaders 01:30 Why execution feels slow in founder-led startups 05:30 3 symptoms of decision drag 11:00 Defining Decision Cycle Time 15:00 Root cause: design flaw, not character flaw 20:00 The 5-step mechanism to fix it 33:00 Real-world before/after case example 38:00 Objections + rebuttals 42:30 30-day quick-start sprint 44:30 Final takeaway + CTA Links 🌐 Website: 📅 Book a free 15-minute Bottleneck Triage: If this episode helped, follow the show and share it with a founder, operator, or people leader navigating execution bottlenecks.