6-Week vs 6-Month Projects: Which Approach Wins?

In this article

Which Wins: 6-Week or 6-Month Projects?

For most operational improvement, six-week projects win. They finish before urgency fades, start paying back within the same year and give you many more learning cycles. Six-month projects make sense only when the work genuinely cannot be split, such as major capital installs or regulated changes.

Six-month projects sound more serious. They come with bigger charters, steering committees and comprehensive scope. That is exactly the problem. Big scope invites delay, delay invites scope creep, and by the time the project lands, the problem it was built to solve has changed.

Watch the companion video on 3-A Continuous Improvement.

Watch on YouTube

How Do Learning Cycles Compare?

Short projects multiply learning. A team running six-week cycles completes several improvement loops in the time a six-month team completes one, and every loop teaches the next. Speed of learning, not size of project, decides who pulls ahead, and the gap widens every quarter you stay slow.

Stagnation Assassin puts the decision version of this plainly: if your competitor takes ninety days per decision and you take ten days, they complete four learning cycles a year while you complete thirty-six. After one year that advantage in organizational learning becomes insurmountable.

The same logic applies to improvement projects. Traditional approaches complete three to four projects a year at around 40 percent improvement each. The 3-A pipeline completes fifty-two projects at 5 to 10 percent each, and those improvements touch every corner of the organization. The pipeline itself is covered in the 3-A Method for continuous improvement.

What Does a Six-Month Project Really Cost?

A long project costs you the months of benefit you never collect. Improvements that sit waiting for Phase 2 earn nothing, and many never ship. A small fix implemented in six weeks pays every week for the rest of the year, while a year-long project puts nothing in the bank this year.

The Refrigeration division learned this on a new product launch that took eighteen months from concept to first shipment. During development the team identified twelve process improvements that would have added 280 basis points of margin and cut manufacturing costs by 23 percent. None were implemented. The excuse was “we’ll address those in Phase 2.” Phase 2 never happened.

Organizations don’t fail to identify improvements; they fail to implement them.

Long timelines also feed the perfection trap. We once spent six weeks analyzing whether to use stainless or aluminum for a $3.47 bracket. A competent engineer could have decided in thirty minutes with 70 percent confidence.

Free from Todd

Symptoms tell you something’s wrong. The cause is usually deeper. My free Stagnation Genome worksheet walks you through five genes and 25 indicators, so you can see what’s actually driving your team.

Get the free Genome worksheet

How Do You Make a Six-Week Project Work?

Use the 3-A Method: two weeks to Apprehend the problem at 70 percent confidence, two weeks to Analyze by eliminating waste before optimizing, and two weeks to Activate with fast implementation and standardization. The scope must be specific, measurable, bounded and solvable in six weeks.

“Quality issues in production” is not a six-week problem. “Station 3 produces units requiring rework 23 percent of the time” is. At REM we scoped a project to cut inspection time from twenty-three minutes to under ten. Eleven of seventeen inspection points had never caught a defect in five years. We eliminated them, and inspection time dropped to nine minutes while quality improved because inspectors could focus.

Perfect improvements that never get implemented create zero value. Good improvements implemented rapidly compound into transformation.

Why exactly six weeks? The book’s answer: teams hold urgency for about thirty to forty days, after which competing priorities intrude and projects drift into maintenance mode. Six weeks forces decisions while leaving time for thoughtful implementation.

The 3-A Method: Six Weeks, Three PhasesThe 3-A Method: Six Weeks, Three PhasesWeeks 1-2: ApprehendDefine the problem at 70 percent confidenceWeeks 3-4: AnalyzeEliminate waste before optimizingWeeks 5-6: ActivateImplement fast and standardize

When Should You Choose a Six-Month Project?

Choose a longer timeline only when the work cannot be broken into independent, valuable pieces: a facility build, a major equipment install, a system cutover or a change that regulators must approve. Even then, run six-week improvement cycles inside the long project so value and learning arrive along the way. For what extreme execution speed looks like on a genuine long project, see how the Empire State Building went up in 410 days.

The test is simple. Ask what the first six weeks would deliver on their own. If the honest answer is “nothing usable,” you may have a genuine long project. If the answer is “a working piece,” cut the scope and ship the piece. For planning cadence rather than project length, see 6-week sprints vs 90-day planning.

How Do You Switch an Organization to Six-Week Projects?

Start with three projects, not fifty-two. Pick problems that are specific and bounded, staff each with five or six people including a process owner and fresh eyes, and commit to a forty-eight-hour decision guarantee so projects never stall waiting on approvals.

Then stagger them. With six projects active, two are in each phase, and every two weeks two finish and two begin. It becomes a steady rhythm rather than heroic sprints, and improvement turns into how the organization works instead of a special initiative.

Frequently Asked Questions

Are six-week projects better than six-month projects?

For most operational improvement, yes. They finish before urgency fades, pay back within the year and produce far more learning cycles. Use longer timelines only for work that cannot be split.

Can complex problems be solved in six weeks?

Many can once they are broken into specific, bounded problems. If a problem is really five problems, split it and run them as separate six-week projects.

What is the 3-A Method?

A six-week improvement method in three two-week phases: Apprehend (define the problem at 70 percent confidence), Analyze (eliminate before optimizing) and Activate (implement and standardize).

Why six weeks and not eight or twelve?

Teams maintain urgency for about thirty to forty days. Six weeks forces decisions while leaving enough time to implement properly.

How many six-week projects should run at once?

The 3-A pipeline runs six at a time, staggered so two projects sit in each phase and two finish every two weeks.

If your improvements are waiting for Phase 2, they are not improvements yet. I help leadership teams compress improvement into six-week cycles that pay back this year. Book me to speak to your team, or get the full method in Stagnation Assassin.

Free from Todd

If this was useful, read Chapter 1 of Stagnation Assassin free. You’ll get the five stagnation genes, the Ten Warning Signs assessment and the 90-Day Question.

Read Chapter 1 free

About the Author

Todd Hagopian is a business transformation author and VP of Product Strategy and Marketing. Known as The Stagnation Assassin, he has led turnarounds across his corporate career, including roles at Berkshire Hathaway, Illinois Tool Works and Whirlpool, and his transformation work has created $3B+ shareholder value across five turnarounds. He is the author of Stagnation Assassin. Invite him to your event through his speaking page or connect on LinkedIn. His newest book is 10-Minute Transformation (February 23, 2027).

Want the short version you can use this week? Pick your problem and get the matching free minibook.

Find my free minibook

The full diagnostic and 90-day playbook: 10-Minute Transformation, February 23, 2027.

Preorder 10-Minute Transformation

Not what you needed? Find Your Solution →