Lanes Momentum Framework
Purpose
Convert a messy set of ideas, tasks, and fire drills into a small operating board that makes the next three weeks visible. The framework is for commanders: the person who chooses the outcome, assigns one accountable owner, gives the team enough context to act, and spends attention on judgment rather than serial execution.
Inputs
- Organization or team name.
- Desired outcome or quarter.
- Candidate work and known constraints.
- People who can own meaningful outcomes.
- Evidence sources and current dashboards.
Processing
- Brain-dump candidate work without pretending the first list is the plan.
- Group work into meaningful outcomes; keep tasks inside cards, not as lanes.
- Choose the top three or four active lanes.
- Assign exactly one accountable owner per lane.
- Plan Week 1 in detail; keep Weeks 2–3 lighter and hold the rest in Beyond.
- Link each lane to a mission brief with context, definition of done, source, and review gate.
- Run the daily lane walk: refine, unblock, narrow, defer, stop, or recommit.
- Move completed cards to the done shelf and use the evidence to reset priorities.
Board rules
- White = not started; yellow = in work; red = blocked; green = done and moved to the shelf.
- A lane is a meaningful project/outcome, not a diary, task dump, or artifact wall.
- One owner per lane. Supporters may contribute; they do not dilute accountability.
- The commander should not own every lane. Preserve energy for prioritization, context, and the final 10%.
- Do not fill the distant horizon with false precision.
- Daily alignment beats a weekly meeting that discovers drift too late.
Outputs
- A completed board using
templates/lanes-board-template.md.
- One mission brief per active lane using
templates/mission-brief-template.md.
- A daily lane-walk decision log.
- A done shelf with evidence links.
Review gate
Do not mark a card green until the definition of done is evidenced. Treat external writes, publishing, billing, permissions, and client-facing actions as separate approvals in the linked mission brief.
Examples
Example 1 — agency fulfillment
Input: SEO delivery, web implementation, AI experiments, sales, and reporting are all competing for attention.
Expected output: Fulfillment becomes the first lane; service implementation cards are assigned to one owner; AI experiments move to Beyond until the delivery bottleneck is reduced.
Why correct: The board reflects the constraint and protects the highest-leverage outcome.
Example 2 — overloaded commander
Input: The founder is listed as owner of every lane.
Expected output: Keep the founder as commander; assign each meaningful lane to the strongest available candidate and use a brief plus daily walk to coach them.
Why correct: Ownership creates a testable opportunity for the team to rise without making the commander the serial bottleneck.
Example 3 — blocked external action
Input: A dry run recommends publishing a press release, but no review has occurred.
Expected output: Mark the card review-gated; save the draft and evidence; do not publish.
Why correct: Analysis and external execution are distinct stages.
Evidence source
Distilled from the AMM mastermind session transcript, especially segments 244–406, 407–561, and 667–775. The session’s reusable governing document is docs/operating-model/lanes-momentum-framework.md.
1---2name: lanes-momentum-framework3description: Turn an agency objective into a small, owned, reviewable lane board with a three-week horizon and daily momentum checks.4trigger_intents: ["build our lanes", "prioritize agency work", "become the commander", "run a lane walk", "create an impact board"]5allowed_tools: [Read, Write, Edit]6input_schema:7 required: [organization, objective, candidate_work]8 optional: [team, horizon, evidence_sources]9output_schema:10 status: "DRAFTED|READY|REVIEW|DONE|BLOCKED"11 artifacts: []12 next_action: ""13metadata:14 source: https://skillmd.com/skills/search-atlas-group/lanes-momentum-framework15 type: framework16 scope: project17 mode: route18---1920# Lanes Momentum Framework2122## Purpose2324Convert a messy set of ideas, tasks, and fire drills into a small operating board that makes the next three weeks visible. The framework is for commanders: the person who chooses the outcome, assigns one accountable owner, gives the team enough context to act, and spends attention on judgment rather than serial execution.2526## Inputs2728- Organization or team name.29- Desired outcome or quarter.30- Candidate work and known constraints.31- People who can own meaningful outcomes.32- Evidence sources and current dashboards.3334## Processing35361. Brain-dump candidate work without pretending the first list is the plan.372. Group work into meaningful outcomes; keep tasks inside cards, not as lanes.383. Choose the top three or four active lanes.394. Assign exactly one accountable owner per lane.405. Plan Week 1 in detail; keep Weeks 2–3 lighter and hold the rest in Beyond.416. Link each lane to a mission brief with context, definition of done, source, and review gate.427. Run the daily lane walk: refine, unblock, narrow, defer, stop, or recommit.438. Move completed cards to the done shelf and use the evidence to reset priorities.4445## Board rules4647- White = not started; yellow = in work; red = blocked; green = done and moved to the shelf.48- A lane is a meaningful project/outcome, not a diary, task dump, or artifact wall.49- One owner per lane. Supporters may contribute; they do not dilute accountability.50- The commander should not own every lane. Preserve energy for prioritization, context, and the final 10%.51- Do not fill the distant horizon with false precision.52- Daily alignment beats a weekly meeting that discovers drift too late.5354## Outputs5556- A completed board using `templates/lanes-board-template.md`.57- One mission brief per active lane using `templates/mission-brief-template.md`.58- A daily lane-walk decision log.59- A done shelf with evidence links.6061## Review gate6263Do not mark a card green until the definition of done is evidenced. Treat external writes, publishing, billing, permissions, and client-facing actions as separate approvals in the linked mission brief.6465## Examples6667### Example 1 — agency fulfillment6869**Input:** SEO delivery, web implementation, AI experiments, sales, and reporting are all competing for attention. 70**Expected output:** Fulfillment becomes the first lane; service implementation cards are assigned to one owner; AI experiments move to Beyond until the delivery bottleneck is reduced. 71**Why correct:** The board reflects the constraint and protects the highest-leverage outcome.7273### Example 2 — overloaded commander7475**Input:** The founder is listed as owner of every lane. 76**Expected output:** Keep the founder as commander; assign each meaningful lane to the strongest available candidate and use a brief plus daily walk to coach them. 77**Why correct:** Ownership creates a testable opportunity for the team to rise without making the commander the serial bottleneck.7879### Example 3 — blocked external action8081**Input:** A dry run recommends publishing a press release, but no review has occurred. 82**Expected output:** Mark the card review-gated; save the draft and evidence; do not publish. 83**Why correct:** Analysis and external execution are distinct stages.8485## Evidence source8687Distilled from the AMM mastermind session transcript, especially segments 244–406, 407–561, and 667–775. The session’s reusable governing document is `docs/operating-model/lanes-momentum-framework.md`.