Short answer: A 3-A project launch checklist is a list of 24 deliverables, four per week, that takes one improvement project from problem to finished standard work in six weeks. Weeks 1 and 2 are Apprehend (define the problem and reach 70 percent confidence). Weeks 3 and 4 are Analyze (eliminate waste before designing fixes). Weeks 5 and 6 are Activate (implement, standardize, close). Run six projects at once, staggered by phase, and you finish 52 projects a year instead of three or four.
Most leadership teams know the feeling: more work, less profit. Improvement projects pile up, each one runs for months, and the business barely moves. The 3-A Method from Stagnation Assassin fixes the cadence problem, not the effort problem. This checklist is the operating version of that method. Miss a deliverable and you miss the timeline.
Why Does a 3-A Project Take Exactly Six Weeks?
A 3-A project takes six weeks because teams hold urgency for roughly 30 to 40 days before competing priorities intrude. Six weeks forces decisions while leaving enough time for careful implementation. Traditional DMAIC programs typically run four to six months, which is long enough for enthusiasm to fade and projects to slide into maintenance mode.
Related reading: Lead Time Compression: 12 Speed Tactics
Related reading: How Can You Achieve 10-50% Capacity Gains in Just 14 Days?
The math matters more than the motivation. In Stagnation Assassin, Todd Hagopian compares the two approaches directly: traditional programs complete three to four projects a year at about 40 percent improvement each, while the 3-A pipeline completes 52 projects at 5 to 10 percent each. Fifty-two smaller wins touch every corner of the organization and build capability that keeps compounding.
"A single 3-A project delivers modest improvement. Fifty-two projects running systematically deliver transformation."
Todd Hagopian, Stagnation Assassin, Chapter 7
Apprehend Phase Checklist: Weeks 1 and 2
Apprehend means reaching 70 percent confidence for intelligent action, not gathering every possible fact. The phase ends with a go or no-go decision. If the problem turns out to be five problems, stop and redefine it before you spend another hour.
Week 1 Deliverables
- One-page charter (Day 1). Problem statement, scope, one success metric, the five or six team members and an executive sponsor. If it takes more than a day, the team is overthinking.
- A bounded problem definition. Not "quality issues in production." Write something specific, measurable and solvable in six weeks. The book's example from a retail equipment manufacturer (REM): reduce inspection time from 23 minutes to under 10 by eliminating redundant checks.
- Minimum viable data plan (Day 2). List the few metrics that matter, give each one a single owner and set a Day 5 deadline. Data collection follows the 70% Rule: directional confidence, not statistical perfection.
- Current-state process walk (Days 4 and 5). Walk the real process and draw what you see, not what the manual says. Note wait times and rework.
Week 2 Deliverables
- Stakeholder and constraint map. Name only the people whose input or approval you actually need. The REM improvement project needed seven stakeholders, not a 30-person steering committee. Map constraints across four categories: technical, operational, management and strategic. Separate genuine constraints from assumed barriers.
- Root cause session. Two hours maximum, using 5 Whys or a fishbone diagram, with frontline workers in the room.
- Baseline metrics. Document current performance for the success metric and mark "we start here." No baseline means no way to prove improvement.
- Apprehend gate review (Day 12). Fifteen minutes with the sponsor. Clear problem, measured baseline and an engaged team means go.
Analyze Phase Checklist: Weeks 3 and 4
Analyze inserts elimination before solution design. The best question in continuous improvement is "What breaks if we skip this step?" Most methodologies jump from the problem straight to a new design. 3-A removes waste first, which often solves most of the problem before anyone designs anything.
Week 3 Deliverables
- Step-by-step elimination review. Ask the "What breaks?" question of every step, checkpoint and document. In the book, a Refrigeration division specification project found 17 documents. Eight were legacy cruft nobody read and were eliminated on Day 11 with no objections.
- Consolidation of what survives. The remaining nine documents became one master specification on Day 12. The problem was 73 percent solved before any improvement was designed.
- Solution list and impact and effort ranking. Generate options for what remains, rate each for impact and effort, and circle high impact, low effort.
- Simple cost and benefit case. Implementation cost, annual benefit and payback for the top options. Conservative estimates that prove true earn finance's trust.
Week 4 Deliverables
- Standardization plan. After elimination, standardize the remaining activities so they run the same way every time.
- Integration check. How does the change affect upstream and downstream processes? A local improvement that breaks something elsewhere is worse than no improvement.
- Implementation plan with single owners. Every action gets one owner and one date. "Improve the process" fails. "Install visual controls by a named date" works.
- Analyze gate review. Unnecessary steps eliminated, remaining activities standardized, integration plan and implementation plan approved with no ambiguity.
"Simplification beats optimization."
Todd Hagopian, Stagnation Assassin, Chapter 7
The REM inspection example shows why. Optimizing all 17 checkpoints by 10 percent each would have cut inspection from 23 minutes to 21. Eliminating the 11 checkpoints that had not caught a defect in years cut it to 9 minutes, and quality improved because inspectors could focus.
Activate Phase Checklist: Weeks 5 and 6
Activate is about speed, because the longer the gap between decision and implementation, the higher the risk of regression. Implement the easy components immediately while the complex pieces are prepared, then roll out with communication, hands-on training and on-site support.
Week 5 Deliverables
- Quick-win implementation. At REM, the 11 redundant inspection points were eliminated on Day 21, the checklist was updated and inspectors were trained in four hours. Inspection time dropped from 23 to 14 minutes that same day.
- Controlled pilot of the complex pieces. Run them in one area first and fix what the pilot exposes.
- Daily blocker removal. Bring blockers to the morning War Room and decide on the spot under the 48-Hour Decision Guarantee.
- Visual tracking. Put the result on the physical project board where everyone can see it.
Week 6 Deliverables
- Standard work documentation. Standardization is implementation, not a later step. Work instructions, training material and troubleshooting guides are written while the change goes live.
- Training cascade. Hands-on practice, not slides, with experts available during the first days.
- Metrics into daily operations. Update standard work within 48 hours and add the metric to visual boards. Improvements not embedded within 60 days face a high probability of regression.
- Closure and celebration. Before and after metrics, public recognition that ties the result to strategy, and lessons captured for the next team.
How Should You Staff a 3-A Team?
Staff each 3-A team with five or six people: a process owner, fresh eyes, an adjacent process representative and technical expertise when needed. The book's rule is at least 50 percent frontline participation, because people closest to the work see what management misses.
- One project per person at a time. Each employee joins one project, then rotates out.
- Rotate into leadership. After four rotations, employees can lead projects.
- Alignment, not unanimity. Consensus-seeking kills the six-week clock. Every decision gets one owner.
How Do You Stagger Six Projects at Once?
Run six projects simultaneously, two in each phase, so two finish and two launch every two weeks. Projects 1 and 2 are in Apprehend, 3 and 4 in Analyze, and 5 and 6 in Activate. The result is a steady rhythm rather than heroic sprints. Smaller organizations can scale the number down. Todd Hagopian doubled the enterprise value of a twelve-person manufacturing company he bought using this system alongside the others in the book.
Two pieces of infrastructure keep the pipeline alive:
- Morning War Rooms. Fifteen minutes daily. Projects report blockers and decisions are made immediately.
- The 48-Hour Decision Guarantee. Small-dollar decisions within 48 hours, medium within five days, high-dollar escalated within ten. In the Refrigeration division, average decision time dropped from 18 days to 1.4 days and projects stuck waiting fell from 40 percent to 5 percent.
How Do You Measure a 3-A Pipeline?
Track three pipeline health metrics: completion rate, implementation success rate and participation rate. The book's targets are 85 percent of projects completed within six weeks, 90 percent of improvements still functioning at 90 days, and 25 percent of the organization on active projects, raised over time toward full participation.
Decision speed sits underneath all three. In the Refrigeration division's first quarter, with the 48-hour guarantee enforced, project completion ran at 88 percent. When decisions slipped to weekly reviews the next quarter, completion collapsed to 31 percent. Durability is the final test: an REM audit at 18 months found 94 percent of improvements still functioning.
For the full method behind this checklist, read 52 Projects in 52 Weeks: The 3-A Method, compare it with legacy programs in 3-A Methodology vs Six Sigma, and pair it with the 48-Hour Decision Guarantee Protocol.
Frequently Asked Questions
What are the three phases of the 3-A Method?
The three phases are Apprehend (Weeks 1 and 2, define the problem to 70 percent confidence), Analyze (Weeks 3 and 4, eliminate waste and standardize) and Activate (Weeks 5 and 6, implement, train and lock in standard work).
What if a project needs more than six weeks?
Break it into linked six-week projects. In Stagnation Assassin, a lead time that was cut in half came from four rounds of six sequential 3-A improvements, 24 modest projects, rather than one large initiative.
How many 3-A projects should run at once?
The standard pipeline runs six projects at once, two in each phase, which yields about 52 completed projects a year. Smaller organizations can run fewer, as long as each person holds one project at a time.
How is 3-A different from Six Sigma DMAIC?
DMAIC typically runs four to six months per project and optimizes existing steps. 3-A runs six weeks and eliminates unnecessary steps before optimizing anything, so it completes far more projects per year.
Sources
- Todd Hagopian, Stagnation Assassin: The Anti-Consultant Manifesto, Chapter 7 (the 3-A Method, the 52-Project Pipeline and the Seven Laws Governing 3-A Success).
Put This to Work With Your Team
Stagnation Assassins exists to turn these frameworks into results inside real organizations. If your leadership team is putting in more work for less profit, pick one of two next steps. Book Todd Hagopian to speak at your leadership offsite or conference, or read the books and run the playbook yourself.

