Biweekly Momentum Driver
Review shipped work, missed commitments, and the next two-week promise
- Difficulty
- Easy
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 94%
The Biweekly Momentum Driver is a compact delivery review built around three questions: what shipped during the last two weeks, what was promised but not shipped, and what will ship during the next two weeks. The comparison between commitments and actual delivery makes momentum observable and exposes execution gaps before they become chronic. Misses are accompanied by reasons rather than hidden inside general status language. The review ends with a fresh, explicit shipment commitment for the following cycle. Using a fixed template makes successive updates comparable, while a context-rich AI assistant can assemble evidence from project documents and transcripts to reduce reporting overhead and identify inconsistencies.
Origin
Extracted from Marketing Against the Grain as a templatized project update the host runs every two weeks.
Core principles
- 01Judge momentum by shipped outcomes
- 02Compare delivery against explicit commitments
- 03Explain misses instead of hiding them
- 04Make the next delivery promise visible
How to run it
- 1
Collect shipped outcomes
List the concrete work completed and delivered during the previous two weeks. Focus on usable outputs rather than activity or effort.
Pro tip Link each shipment to the project outcome it supports.
Watch out Do not count meetings, drafts, or work in progress as shipped unless they were the promised deliverable.
- 2
Compare with commitments
Retrieve the promises made in the previous update and compare each one with actual delivery.
Pro tip Use the same template every cycle so promises cannot disappear between reports.
Watch out Avoid rewriting old commitments after seeing the results.
- 3
Explain misses
Identify commitments that were not met and document the reasons, including blockers, scope changes, or faulty assumptions.
Pro tip Separate controllable execution failures from legitimate strategic changes.
Watch out An explanation should not become an excuse that removes accountability.
- 4
Set the next shipment promise
Specify the concrete outputs that will be delivered during the next two weeks. Ensure each commitment has an owner and a clear definition of done.
Pro tip Prefer a small number of outcome-linked promises over a long activity list.
Watch out Overcommitting makes the review less credible and obscures priorities.
- 5
Publish the update
Share the completed review with stakeholders and use it to resolve dependencies or adjust priorities.
Pro tip Keep the format stable so readers can scan changes quickly.
Watch out Do not publish sensitive explanations beyond the audience that needs them.
In the wild
A growth team reports that it shipped a new onboarding checklist and two lifecycle emails. It had also promised an analytics dashboard, but the event schema was incomplete. The review records that miss, assigns the schema fix, and commits to shipping the dashboard and one activation experiment during the next two weeks.
→ Stakeholders receive an honest view of delivery, the missed dependency is addressed, and the next commitments are explicit.
Common mistakes
Reporting activity instead of shipments
Hours worked, meetings attended, and tasks started do not demonstrate that the project produced a usable outcome.
Omitting missed promises
A highlight-only update prevents the team from learning why planned work failed to ship.
Making ambiguous commitments
Promises such as “make progress on onboarding” cannot be objectively evaluated in the next review.
Is it for you?
Best for
It is best for teams delivering concrete outputs in short cycles across complex projects.
Not ideal for
It is not ideal for work whose meaningful outputs cannot be evaluated on a two-week cadence.
From the transcript
“The bi weekly momentum driver is basically a way that we show what we ship every two weeks.”
“What did we ship the this two weeks? Was there anything we said we. We going to do that we didn't do, and what are…”
From the episode
This AI Workflow Made Me 10X More Productive