Strategy is the captain's slow-cadence job.

The trap most operators fall into

Daily cadence is addictive. Every PR shipped, every customer answered, every campaign launched — the dopamine of motion. You get good at the daily and your business feels like it's compounding.

Then you look up after a quarter and the metric you actually care about hasn't moved. Or worse, the business has compounded in a direction you didn't choose. The daily was honest. The strategy was missing.

This is the trap of optimization without direction. You can't out-execute a wrong target. The captain's job is to pick the target — and that's a different rhythm than shipping.

What strategy actually is

Strategy is the captain's slow-cadence job. It's where you decide what your business is for — and what it's not for — at a rhythm that gives reality time to talk back.

Most teaching on strategy stops at the first half: "set objectives, define key results." OKR theatre. The half it skips is the one that matters: the cadence at which you check whether the objectives still make sense.

If you set quarterly objectives and don't revisit them at quarter-end, you didn't do strategy. You did a kickoff. Strategy is the loop, not the spreadsheet.

The two halves: framework + ritual

What separates strategy that works from strategy that's just documentation:

1. The framework — your strategy file

   Active objectives, quarterly rocks, annual themes, monthly review. Lives in your Command Kit at strategy/. This is what you write down.

2. The ritual — the Strategic cadence

   The recurring meeting (with yourself or your team) where you compare the strategy file against real-world data. Lives at quarterly and yearly cadence. This is what you do.

One without the other doesn't work. A strategy file you never revisit becomes shelf-ware. A quarterly review with no underlying file becomes vibes. Couple them and the strategy gets sharper every cycle.

The framework — what to write down

Four artifacts in strategy/ in your Command Kit:

• Annual theme — one frame for the year. Not a goal — a direction. The single sentence that holds the year. Example: "the year of paying customers" or "the year we kill our worst venture." If it doesn't make you smile or wince, it's not specific enough.
• Quarterly rocks — three big projects scoped to ship within the quarter. If you can't ship it in 13 weeks, it's not a rock — it's a theme. Each rock has milestones and a "what I need to NOT do" line.
• Active objectives — the three things you're optimizing for right now, with key results. No more than three. Every yes is a no to something else.
• Monthly review — five questions you sit with monthly to check whether direction still holds. Not a status update — a recalibration.

The ritual — what to actually do

The framework is dead text without the rhythms that animate it. From the MaxShip Master Cadence:

• Monthly — open strategy/monthly-review.md, answer the five questions honestly, edit objectives.md if direction needs to shift
• Quarterly — last quarter's rocks vs results. Did the metrics move? Set next quarter's three rocks. The kill-list. Compensation + role conversations with team.
• Yearly — the 10-hour retrospective: wins, losses, learning points, key partners, finance, what's working and what's not. Output: a finalized report formatted for AI consumption.

Each ritual updates the framework. Each updated framework feeds the next ritual. That's the loop.

The compounding move

The yearly retrospective produces a finalized report. Drop that report in ~/command/strategy/. Next year, every Claude conversation has it as context. Your AI strategic-planning copilot gets one year sharper.

This is the meta-loop most strategy teaching misses. The artifact of this year's strategy becomes next year's input. The captain stops re-explaining their business to a fresh AI in January. Their strategic context grows.

This year's retrospective is next year's command.

What MaxShip does differently

The competitive landscape on this is loud and shallow:

• OKR consultants teach you to set objectives. They don't teach the rhythm to validate them.
• Productivity apps give you a place to write objectives. They don't give you a methodology for using them.
• Strategy frameworks (Lean, Hoshin Kanri, Wardley Maps) give you mental tools for picking direction. They don't say how often to check.

The MaxShip pattern: strategic planning is a Mental Framework paired explicitly with a Cadence. The framework lives in your Command Kit. The ritual lives in your calendar at quarterly + yearly. They're inseparable. One without the other is the failure mode.

How to start (if you're not running this)

1. Clone the Command Kit if you haven't. Open the strategy/ folder.
2. Fill in annual-themes.md for the current year. One sentence. Don't be precious about it — you'll edit it.
3. Fill in quarterly-rocks.md for the current quarter. Three rocks max.
4. Schedule the Strategic cadence: book a recurring 30-minute monthly slot for monthly-review.md, a recurring half-day quarterly for the rocks retrospective, a full day at year-end.
5. Tell your AI where the strategy file is. Every meaningful conversation about a project starts with: "look at strategy/objectives.md first."

Run for one quarter. Skip the tools and frameworks debate. Just answer the questions and check whether reality matches the file. The methodology gets sharper through use, not theory.