Strategy Is What You Stop Doing

Sep 10, 2026 | Blog, Deep Essays

The strategy offsite was excellent. Sharp slides. Clear pillars. A narrative the board could love. People left energized. Someone said, “This is the most focused I have felt in years.”

Monday’s standup still has fourteen P0s. The backlog still contains last year’s initiatives with new labels. The calendar still hosts standing meetings for work the deck implied was over. A manager asks which project to stop. The room goes quiet. Nobody wants to pay the social cost of disappointing a sponsor. By Friday, the strategy has been “communicated.” The work has not been subtracted.

If that gap feels familiar, you do not primarily have a messaging problem. You have an execution-as-subtraction problem. Strategy decks fail to change weekly work when leaders treat strategy as inspiration rather than committed refusal.

This essay is for managers through VPs drowning in priorities: leaders who can recite the strategy and still run calendars that look like last year. Especially directors and VPs who need portfolio focus, and managers translating company strategy into team stop-doing lists. It is about how to execute strategy as a leader by stopping work on purpose. Not another OKR primer with invented success rates.

Reframe: strategy execution is subtraction under constraint

Strategy language loves addition: new bets, new motions, new capabilities. Operations reality is constrained: same people, same hours, same cognitive load. If the strategy cannot name what becomes less important, it is a wish list.

Strategy execution is subtraction under constraint. If nothing stopped, strategy was messaging.

“Strategy is what you stop doing” is an operating rule, not a slogan. It means:

Every focus bet implies a kill, pause, or deliberate neglect elsewhere
Leaders pay social cost publicly when they stop work that still has fans
Calendars and backlogs are the proof artifacts, not the slide footer
Capacity math is mandatory: who does this instead of what?

Focus as strategy for managers begins when a team can show a stop-doing list that matches the company’s stated bets. From strategy deck to weekly execution is a translation problem. Translation without subtraction is theater.

This pairs with the Director / VP hub portfolio map (own / influence / ignore). If everything is “own,” you own overload. It also pairs with Stop Doing IC Work Detox for new managers whose personal backlog is the first subtraction target.

Named framework: FOCUS → FINISH → FREEZE → FORGET

Use FOCUS → FINISH → FREEZE → FORGET to turn strategy into a kill list and a protected focus set. Pair every step with capacity math.

FOCUS

What are the few bets that will get disproportionate attention this quarter?

Focus is not a brainstorm. It is a short list with owners, success definitions, and explicit non-goals. If your focus list needs a scroll bar, it is not focus.

Focus questions:

What would make this quarter matter if only three things moved?
Which bets are company-critical vs. locally interesting?
What customer or financial constraint makes these bets non-optional?
Who owns each bet end-to-end (one Accountable human)?

Use Who Owns This: RACI Lite when bets span functions. Dual-owned strategy bets become dual-orphaned strategy bets.

FINISH

What in-flight work must be completed because stopping midstream creates more damage than finishing?

Finish criteria prevent eternal nearly-done projects from blocking subtraction. Define done. Time-box the finish. Assign an owner. Resist expanding finish into a new initiative.

Finish questions:

What is the minimum shippable end state?
What is the date after which we will not keep polishing?
What dependencies would make a pause unethical or unsafe (security, customer commitments already made)?

Finish is not a loophole to keep everything. It is a narrow gate.

FREEZE

What pauses with an owner, a revisit date, and a written reason?

Freeze is honest pause. It is not “hope later.” Zombie projects love fake freezes with no date and no owner.

Freeze packet (sample practice):

Why paused
What would unpause it
Owner of the frozen work
Revisit date
Communication sent to stakeholders

If you cannot name the revisit date, you are not freezing. You are forgetting without courage, or keeping a political option alive in the shadows.

FORGET (kill)

What ends, with explicit communication and dignity for the people who shipped it?

Killing work is strategy. Communicate:

What stops
Why (link to focus bets / constraints)
What happens to customers/users impacted
How the team’s effort is honored
What people work on instead

Saying no to execute strategy requires this last mile. Without it, stealth work returns at night.

Capacity math binds all four: for each FOCUS item, name what FREEZE/FORGET frees. If the math does not close, your focus list is still a wish list.

The tactical ritual lives in Strategy → Kill List (30 min). This essay is the operating philosophy around that play.

Translating company strategy into team stop/start/continue

Managers should not wait for perfect cascading OKRs. They should translate.

A simple workshop (60-90 minutes) with the team or leadership peers:

Restate company focus bets in plain language (no jargon cosplay)
List current team work (real backlog and calendar commitments)
Tag each item: fuels a focus bet / finishes a must-ship / candidate freeze / candidate kill
Run capacity math: hours/people available vs. tagged focus+finish
Draft FREEZE and FORGET lists with owners and dates
Write the communication before leaving the room

Avoid theater: do not relabel everything as strategic. Do not create fourteen “key results” that recreate the old backlog. Strategic priorities kill list thinking is subtraction first.

For managers still learning to stop personal heroics, combine with Delegation Without Dumping. Subtraction that dumps chaos on the team is not strategy. It is abdication.

Worked example: director portfolio kill list (sample)

Labeled sample. Fictional director, Maya, owns a portfolio with two product bets, one sales motion support initiative, and one internal tooling project. Same people staff all four.

Starting state (Monday after offsite)

Bet A: redesign onboarding for mid-market (company focus)
Bet B: expand analytics dashboards (company focus, quieter)
Sales motion: custom demo environment for a segment push
Internal tooling: rewrite an admin console “while we are in there”
Plus: fourteen P0 bugs/requests with sponsors

Calendar proof: Maya’s leads each have three standing meetings for different initiatives. Nobody has a protected focus block for Bet A.

FOCUS

Maya picks Bet A as primary and Bet B as secondary for the quarter. Sales motion becomes a scoped supporting thread with a thin definition of done. Admin console rewrite is not focus.

FINISH

Two in-flight dashboard releases for Bet B get finish criteria and a two-week ship window. A half-done demo environment for sales gets a minimum viable finish, not a platform fantasy.

FREEZE

Admin console rewrite freezes with owner Raj, revisit date in 90 days, unpause condition: Bet A onboarding metrics stable and staffing headroom. Maya sends a written freeze note to stakeholders who wanted “while we are in there.”

FORGET

Three local P0 pet projects without customer evidence are killed. Maya meets the sponsors. She does not hide behind a PMO email. She pays the social cost. She offers a path to revive only through a dated proposal tied to focus bets.

Capacity math

Freezing the rewrite and killing pets frees two engineers and one PM slice for Bet A. Sales demo finish uses a time-boxed SE rotation instead of a standing team. Calendar change: kill two standing meetings; create twice-weekly Bet A working sessions; protect focus blocks on lead calendars.

Cross-functional consequences

Sales wanted unlimited demo customization (How Sales Works literacy helps explain motion tradeoffs). Maya partners with the sales leader using options, not a wall: scoped finish now, larger platform later if metrics justify. Finance partner sees staffing implications via a simple capacity narrative (Finance for Non-Finance Managers, Forecast / Money Pre-Read habits for resource asks).

This is how to execute strategy as a manager of managers: portfolio subtraction with calendar consequences. Without calendar consequences, the kill list is literature.

Killing work that still has fans, sponsors, or sunk cost

Sunk cost will argue fluently. Fans will argue emotionally. Sponsors will argue politically.

Leaders need a script that is firm and respectful:

Acknowledge the value delivered so far
Restate the constraint and the focus bets
Offer freeze vs kill with clear criteria
Name what the people move to (do not leave identity void)
Document the decision where the organization can see it

If stealth work continues after a kill, treat it as an operating breach, not a quirky passion project. Stealth work destroys trust in strategy. Use leadership meeting time to surface stealth early (Leadership Team Meeting Design).

Communicating stops without demoralizing teams:

Separate “the work ends” from “you failed”
Celebrate learning and shipped increments
Move people onto visible focus work quickly
Avoid mocking the discontinued project in public

People grieve projects. Allow a short, adult goodbye. Then run the new system.

Portfolio leaders vs. team managers

Directors/VPs allocate attention across bets, interfaces, and ignore lists. Their artifact is a portfolio map plus a kill/freeze register. Their failure mode is attending everything.

Managers execute one team’s slice: backlog tags, meeting subtraction, 1:1 alignment to focus, refusal of random inbound. Their failure mode is absorbing every executive whim as a new P0.

Both need the same framework at different altitudes. Both need capacity math. Both need to stop treating “strategic” work as evening homework. If strategy only happens after 6 p.m., you do not have a strategy operation. You have a fatigue plan.

Cross-functional portfolio subtraction needs interface owners (How Departments Work Together). Killing a project in one team can strand a partner team. Announce freezes across seams.

Meeting and artifact design that keeps strategy in daylight

Artifacts that help:

One-page focus list with non-goals
Kill/freeze register with owners and dates
Portfolio map: own / influence / ignore
Weekly capacity snapshot (simple, not a new PMO bureaucracy)
Decision log for stops

Meetings that help:

Weekly kill-list hygiene (30 minutes)
Monthly portfolio refresh for directors
LT decisions on contested kills

Meetings that hurt:

Strategy “updates” with no subtraction decisions
Status on frozen work as if it were alive
Recurring steering for initiatives that should be dead

Failure modes: priority inflation and zombie projects

Prioritize everything

If everything is P0, nothing is. Repair: hard cap on active focus bets per team.

Zombie projects

No owner, no date, occasional thrash. Repair: freeze packet or kill. No third state called “simmer.”

Strategy as communication only

Deck shipped, backlog unchanged. Repair: require calendar and backlog diffs within one week of strategy communication.

No capacity math

New bet layered onto full plan. Repair: no new focus without named freeze/kill.

Stealth work after a kill

Passion returns underground. Repair: visible breach response; move energy to focus work; address incentives.

Freeze as hope

“Paused” forever. Repair: revisit dates; missed revisit becomes kill or explicit re-funding.

PMO decks own strategy, managers’ calendars do not

Central slides look clean while teams thrash. Repair: judge strategy by team artifacts and calendars, not only portfolio software.

Confusing delegation with dump

Stopping IC work by throwing undifferentiated tasks at reports. Repair: Delegation Without Dumping plus clear outcomes.

Monday operating cadence: keep strategy visible in backlog and calendar

Weekly: Strategy → Kill List ritual (30 minutes)

Use the play. Review:

Focus bets still true?
Finish items on track to done-or-kill?
Freezes approaching revisit?
Any stealth or zombie signals?
Calendar proof: what meeting or block changed?

Weekly: protected focus blocks

Leaders inspect whether focus work has daytime space. If not, subtract a meeting before adding pep talks.

Weekly manager 1:1 prompt

In Weekly 1:1 Operating Cadence: “What did we stop or refuse this week that protected focus?”

Monthly: portfolio map refresh (directors/VPs)

Own / influence / ignore. Move items deliberately. Publish changes.

Monthly: cross-functional freeze/kill sync

Tell partner teams what stopped so they do not plan on ghosts.

Quarterly: strategy proof review

Compare deck language to backlog reality. No invented ROI claims required. Proof is subtraction and progress on focus bets.

Resource and money awareness without fake ROI stats

Stopping work has cost and frees cost. Finance partners can help you see tradeoffs without turning strategy into a spreadsheet religion. Use plain capacity and spend narratives. Do not invent strategy ROI percentages. Do show what you will not staff.

If a focus bet needs funding, bring a pre-read that states what will be frozen or killed to make room. That is adult strategy execution.

Soft landing plans for discontinued work

A kill without a soft landing creates customer pain and internal cynicism. Before you announce FORGET, write:

Customer impact: who notices, what message they get, what alternative exists
Data and systems: what is archived, what remains readable, who owns remnants
People: where each contributor lands next week (focus bet, finish crew, or explicit bench plan)
Partners: which other teams had dependencies, and how you prevent stranded work
Metrics: which dashboards will look “worse” because a vanity stream ended, and how leadership will interpret that honestly

This is not change-management theater. It is operational manners. Teams forgive hard tradeoffs. They do not forgive careless endings that make them look incompetent in public.

Handling executive drive-bys and new “tiny” asks

Strategy dies by a thousand small yeses. An executive asks for a quick analysis, a pilot, a custom report. Each sounds cheap. Together they recreate the fourteen-P0 standup.

Install a intake rule for your portfolio:

All new asks go to a weekly triage against FOCUS
“Tiny” asks still require: owner, hours estimate, what slips
If the ask is truly mandatory from above, escalate the tradeoff: “Yes, if we freeze X”
Never accept a mandatory add with silent overtime as the hidden plan

Managers need permission from their directors to use that script. Directors need to back them when the script is used well. Otherwise subtraction is only allowed in offsites.

Strategy, incentives, and sales motions

If sales comp and marketing campaigns still pay on motions you froze, the organization will keep doing the frozen work. Align incentives and campaign calendars with FREEZE/FORGET lists, or admit the freeze was fictional.

Example: you freeze a custom-heavy segment play, but SDRs still get credited for that segment’s activity the old way. Expect stealth customization. Bring sales leadership into the kill-list conversation early. Use options and dated transitions, not surprise cutoffs the week of quarter end.

When not to kill

Subtraction is not nihilism. Do not kill:

Safety, security, or compliance obligations to make a slide look focused
Finish items that would strand customers mid-migration without a plan
Foundational maintenance that keeps the focus bets alive (keep it sized, do not romanticize it as strategy)

Name maintenance as maintenance. Give it a budgeted slice. Hidden maintenance becomes the silent killer of focus when it is ignored until outage.

A 60-minute leadership team agenda for subtraction

Minute 0-10: Restate focus bets and constraints (pre-read required).

Minute 10-25: Review kill/freeze register exceptions only.

Minute 25-40: Decide contested stops; write owners and dates live.

Minute 40-50: Capacity math check: does the plan close?

Minute 50-60: Communication plan and calendar proof assignments.

If your LT cannot spend an hour on stops, it will spend months on thrash. Design the meeting on purpose with Leadership Team Meeting Design.

Manager translation sheet (copy/paste sample)

Team: ____  Quarter: ____
Company focus bets (plain language):
1.
2.

Our FOCUS (max 2-3):
-

FINISH (must ship, dated):
-

FREEZE (owner + revisit date):
-

FORGET / kill (communication date):
-

Capacity math:
People/hours available: ____
Allocated to FOCUS+FINISH: ____
Gap closed by FREEZE/FORGET: ____

Calendar proof this week:
Meeting removed: ____
Focus block added: ____

Use the sheet in staff meeting. If managers cannot fill it, the cascade failed upstream.

Putting it to work this week

List your team’s real active work (backlog + standing meetings).
Tag FOCUS / FINISH / FREEZE / FORGET.
Close capacity math or cut the focus list until it closes.
Run a 30-minute kill-list meeting and send freeze/kill communications.
Change one calendar artifact as proof (delete a meeting, protect a focus block).

If you lead directors, ask each for a one-page portfolio map and kill register before the next LT. If they cannot name stops, they have not started executing.

Personal subtraction for the leader

Portfolio kill lists fail when the leader’s own calendar remains a museum of old commitments. Before you ask teams to stop, audit your week:

Which meetings exist only because a killed project once needed them?
Which “quick syncs” recreate influence over work you should ignore?
Which reviews reward status on frozen streams?
Which personal projects are you keeping as identity souvenirs?

Model FOCUS → FINISH → FREEZE → FORGET on your own time. Teams watch. If you cannot stop, your strategy story becomes another poster. New managers should start with Stop Doing IC Work Detox so personal heroics do not sabotage team focus.

One sentence test

If a stranger read your backlog and calendar, would they infer the same strategy your deck claims? If not, subtraction is unfinished.

Closing

How leaders stop doing work is the hidden half of strategy. The visible half is the deck. The hidden half is the social cost of disappointing a sponsor, disappointing a team that loved a project, and disappointing your own appetite for optionality.

A strategy that cannot name what it makes less important is a wish list. Execution begins when a leader pays the social cost of stopping. Run FOCUS → FINISH → FREEZE → FORGET until Monday’s standup no longer looks like last year’s museum of P0s.