{"id":493,"date":"2026-03-23T17:43:09","date_gmt":"2026-03-23T17:43:09","guid":{"rendered":"https:\/\/shermanperryman.com\/blog\/your-biggest-blocker-isnt-scope-its-a-burned-out-counterpart\/"},"modified":"2026-03-23T17:43:09","modified_gmt":"2026-03-23T17:43:09","slug":"your-biggest-blocker-isnt-scope-its-a-burned-out-counterpart","status":"publish","type":"post","link":"https:\/\/shermanperryman.com\/blog\/your-biggest-blocker-isnt-scope-its-a-burned-out-counterpart\/","title":{"rendered":"Your biggest blocker isn\u2019t scope\u2014it\u2019s a burned-out counterpart"},"content":{"rendered":"
\n
Federal Delivery<\/div>\n

Your biggest blocker isn\u2019t scope\u2014it\u2019s a burned-out counterpart<\/h1>\n

Scope creep isn\u2019t killing your timeline. A tired reviewer with 200 emails is.<\/p>\n

\n

Only 7% of federal workers report high motivation.<\/p>\n

That translates into slower reviews, thin meeting attendance, and rising error rates.<\/p>\n

Pushing harder won\u2019t beat systemic drag. Designing for it will.<\/p>\n<\/section>\n

\n Delivery that ignores counterpart capacity is self-sabotage. Respect the load. Win the timeline.\n <\/div>\n
\n

The environment is the constraint<\/h2>\n

Motivation is underwater. Workloads are up. Approvals sit in inbox purgatory.<\/p>\n

When capacity drops, context decays. You get rework and d\u00e9j\u00e0 vu decisions.<\/p>\n

Every resubmission resets the clock. Your Gantt doesn\u2019t care. The org chart does.<\/p>\n

Stop designing for a perfect reviewer. They don\u2019t exist right now.<\/p>\n

Design for a smart, overloaded civil servant who can give you 12 focused minutes a week.<\/p>\n

Make those 12 minutes count.<\/p>\n<\/section>\n

\n

Optimize for low cognitive load<\/h2>\n

Replace long decks with one-page decision briefs.<\/p>\n

Two to three vetted options. Explicit risks. A recommended path. A clear ask.<\/p>\n

No Easter eggs. No scavenger hunts in the appendix.<\/p>\n

Use a repeatable frame:<\/p>\n

Purpose:<\/strong> One sentence on what needs a decision and why it matters now.<\/p>\n

Options (2\u20133):<\/strong> Trade-offs in one line each. No \u201cOption 4: magic.\u201d<\/p>\n

Risks:<\/strong> Top three with mitigations you control. Don\u2019t list the whole universe.<\/p>\n

Recommendation:<\/strong> Bold. Own it. One line.<\/p>\n

Decision Window:<\/strong> Deadline tied to a program outcome, not a date.<\/p>\n

Signatures:<\/strong> Pre-staged. E-sign ready. No printer required.<\/p>\n

Standardize artifacts across the team.<\/p>\n

Same filenames. Same sections. Same highlights. Zero time wasted on format debates.<\/p>\n

Create a \u201cgolden path\u201d template for every recurring deliverable.<\/p>\n

Inputs, outputs, acceptance criteria. Fill-in-the-blanks. No blank-page fear.<\/p>\n

Anchor deadlines to outcomes you can\u2019t miss.<\/p>\n

\u201cApprove by 4\/12 to obligate FY funds without reprogramming.\u201d<\/p>\n

Outcome beats calendar in a low-morale shop.<\/p>\n

Pre-stage approvals.<\/p>\n

Book five-minute \u201cclick to sign\u201d holds on calendars two weeks out.<\/p>\n

Missed? Auto-bump 24 hours with a summary email. Zero politicking.<\/p>\n<\/section>\n

\n

Governance that accelerates decisions<\/h2>\n

Meetings aren\u2019t the problem. Bad meetings are.<\/p>\n

Short. Predictable. Outcome-focused. That\u2019s your edge.<\/p>\n

Run a low-friction cadence:<\/p>\n

1) Weekly 20-minute Decision Gate.<\/strong> Three decisions max. All pre-reads due 48 hours prior.<\/p>\n

2) 15-minute RAID Triage midweek.<\/strong> Risks, Assumptions, Issues, Dependencies. Nothing else.<\/p>\n

3) Asynchronous status.<\/strong> 5 bullets or a 90-second Loom. No slide circus.<\/p>\n

4) Monthly 30-minute Retrospective.<\/strong> One keep. One stop. One start. Ship the changes.<\/p>\n

Adopt a two-touch rule.<\/p>\n

If a topic needs a third meeting, convert it to a decision brief or kill it.<\/p>\n

Gatekeepers are humans. Protect their time.<\/p>\n

Bundle asks. Avoid 11th-hour surprises. Show the diff, not the whole doc.<\/p>\n

Use a crisp RAID log that reads like a tape.<\/p>\n

ID, owner, impact, due date, temperature.<\/p>\n

No long narratives. Make it skimmable on a phone in a taxi between buildings.<\/p>\n

Escalation shouldn\u2019t feel like betrayal.<\/p>\n

Define it upfront: X days without movement triggers Y path.<\/p>\n

Escalate the block, not the person.<\/p>\n<\/section>\n

\n

Contract levers when approvals lag<\/h2>\n

You can\u2019t manage what the contract contradicts.<\/p>\n

Wire relief into the structure.<\/p>\n

Align milestones to dependencies you don\u2019t control.<\/p>\n

\u201cMilestone 3 due 10 business days after COR feedback on Deliverable 2.\u201d<\/p>\n

Not \u201cdue 5\/15 regardless of review.\u201d<\/p>\n

Define stoppage and relief explicitly.<\/p>\n

Clock stops after X days without government feedback. Schedule shifts are automatic, not negotiated each time.<\/p>\n

Include partial acceptance to avoid holding the whole release hostage.<\/p>\n

Put a deemed-acceptance clause on low-risk artifacts.<\/p>\n

\u201cIf no comments in 7 business days, deliverable is accepted for invoicing.\u201d<\/p>\n

Risk stays managed. Cash flow stays alive.<\/p>\n

Use NTE buckets for rework caused by late changes.<\/p>\n

Track causality in change logs. Convert overruns to equitable adjustments with receipts.<\/p>\n

Define alternates for approvals.<\/p>\n

Primary COR, alternate COR, and program chief as tiebreaker.<\/p>\n

Silence shouldn\u2019t be a blocker state.<\/p>\n

Codify the RACI in the SOW or attachment.<\/p>\n

Roles, authorities, and what \u201capproval\u201d means.<\/p>\n

Authority clarity cuts cycles more than talent does.<\/p>\n

Phase funding with option CLINs tied to decision gates.<\/p>\n

Unlock next work when defined outcomes clear, not when a date flips.<\/p>\n

Budget reality meets delivery flow.<\/p>\n<\/section>\n

\n

Operating patterns that travel<\/h2>\n

Make the right thing the easy thing.<\/p>\n

Standardize, templatize, and pre-wire.<\/p>\n

Run a \u201cfriction kill list.\u201d<\/p>\n

Every week, remove one recurring speed bump.<\/p>\n

File path confusion? Fix naming. Meeting drift? Freeze agendas. Late redlines? Pre-bundle changes.<\/p>\n

Build a decision brief library.<\/p>\n

Examples, not theory. Redacted real wins.<\/p>\n

New staff plug into muscle memory on day one.<\/p>\n

Set up a signature station.<\/p>\n

Approved signer list, backup list, contact methods, and business hours.<\/p>\n

Clarity removes heroics.<\/p>\n

Establish a \u201c24\u201348\u201372\u201d SLA rhythm.<\/p>\n

24 hours: acknowledge. 48 hours: directional feedback. 72 hours: decision or escalation path engaged.<\/p>\n

Everyone knows the next move. Nobody guesses.<\/p>\n

Meeting rules of engagement are simple.<\/p>\n

Pre-reads 48 hours in advance. No pre-read, no decision.<\/p>\n

Start with the decision, not the deck. End with owners and dates.<\/p>\n

Use async to respect attention.<\/p>\n

Short clips. Timestamped notes. Threaded questions.<\/p>\n

Reserve live time for choices and edge cases.<\/p>\n<\/section>\n

\n \u201cSpeed is a byproduct of clarity. Clarity is a byproduct of design.\u201d\n <\/div>\n
\n

Adapt to bandwidth without slipping scope<\/h2>\n

Protect scope by simplifying paths, not by shrinking ambition.<\/p>\n

Do the drafting. Offer options. Carry the admin load.<\/p>\n

Three moves that keep scope intact:<\/p>\n

1) Collapse decisions.<\/strong> Bundle related approvals to reduce context switching.<\/p>\n

2) Pre-approve edges.<\/strong> Get thresholds and guardrails signed once, apply many times.<\/p>\n

3) Stage deliverables.<\/strong> Ship thin slices for early acceptance. Stack them into the whole.<\/p>\n

When you remove friction from the path, scope stops feeling heavy.<\/p>\n

The work doesn\u2019t change. The experience does.<\/p>\n<\/section>\n

\n

Black Fortitude doctrine<\/h2>\n

Principles we run in every low-morale environment.<\/p>\n