What to do with a Sprint after you receive it.
The brief landed in your inbox. Now what happens in the next 30 days determines whether it shipped or rotted.
Two founders, two inboxes.
Two founders received nearly identical Sprint briefs from me last spring. Same depth. Same recommendation shape. Different verticals, same level of clarity in the deliverable.
One shipped six of eight recommended moves in the next 30 days. Her topline lifted 27% by the end of Q2.
The other forwarded the brief to her team Slack with a "thoughts??" and let it sit. Zero moves shipped. Same brief. Different inbox behavior.
The 30 days that matter.
Five things to do in the first 7 days after delivery:
Briefs that rot weren't bad briefs. They lacked an owner and a Monday.
The 30-day execution playbook.
Day 1: read the brief cold. No team. No notes. Just read. Note your gut reaction to the top-ranked move.
Day 2: pick one operator (you or a teammate) who will own execution. Single accountable name. No committees.
Day 3: write the one-page action sheet pulling from the brief. 5-10 moves max. Each one ranked by evidence weight from the brief.
Day 4-5: walk the action sheet through your team. Get owner names and deadlines on every row.
Day 7: ship the top-ranked move. The first move sets the tempo for the next 30.
Day 14: half-cycle check. What shipped? What slipped? What evidence has changed?
Day 30: full review. Compare actual results to the brief's predicted outcome. Capture the diff for the next Sprint.
When to delay execution.
Two cases. One: the brief surfaces a decision you genuinely need to sleep on (rare but real). Two: an external event (M&A talks, leadership change) makes the timing wrong. Both: signal the delay back to whoever produced the brief so the next Sprint targets the new state.
Back to the two inboxes.
The founder who shipped six of eight moves did the boring steps. Day 1 read. Day 2 owner. Day 3 sheet. Day 7 first move. The brief didn't ship the work. The execution layer did.
The other founder eventually re-engaged eight weeks later. We re-ran the Sprint because the category had moved in the intervening time. Same brief shape. Different recommendations. The cost of not running the execution layer was a second Sprint.
[TODO B · Mechanism/why]
[TODO: Explain WHY the thing in A happens. Cite mechanism, data, evidence.]
[Short italic pull-quote that crystalizes the mechanism]
[TODO C · Application/the move]
[TODO: What to do with the insight. Concrete steps.]
- [Step 1] description
- [Step 2] description
- [Step 3] description
[TODO: When NOT to do this / counter-case]
[TODO: One paragraph showing edge case or when the move is wrong.]
[TODO A' · Callback to scene]
[TODO: Return to the opening scene with new meaning. 2-3 sentences. Don't over-resolve.]
What do I do with a strategy brief after receiving it?
Day 1: read it cold. Day 2: pick one operator to own execution. Day 3: write a one-page action sheet from the brief. Day 7: ship the top-ranked move. Day 30: review actual vs predicted. Briefs don't ship work; execution layers do.
Who should own execution of a strategy brief?
One named operator. Single accountable person, not a committee. Could be you, your COO, your head of marketing, or a senior IC. The role matters less than the singularity of accountability.
How fast should I act on a Sprint brief?
First move shipped within 7 days of delivery. The first move sets the tempo for the next 30. Founders who delay the first move past 14 days ship fewer than half the recommended moves.
What if I don't agree with the brief's top-ranked move?
Worth a conversation with whoever produced the brief. Sometimes the evidence is missing context only you have. Sometimes you're reacting emotionally. The 14-day refund window exists for exactly this case.
How do I measure whether a Sprint worked?
Compare actual results to the brief's predicted outcome at Day 30. If results match prediction, the Sprint hit. If results miss prediction, capture the diff so the next Sprint targets the new state. Both outcomes are useful.
Last updated May 31, 2026. Field notes by Alex Lamb, LoopWorker.