20 Years of TRACtion: What We've Learned About Making Continuous Improvement Work

November 19, 2026

Two decades of working with continuous improvement leaders have reinforced some important lessons about choosing the right projects, managing improvement work, and sustaining results.

Bill Hathaway Founder and CEO

Bill Hathaway Founder and CEO

In 2006, Lean Six Sigma programs were expanding rapidly. Organizations were training Green Belts and Black Belts, launching improvement projects, and investing significant resources in operational excellence. There was plenty of activity, but senior leaders were beginning to ask a reasonable question: What are we getting for all this investment?

Answering that question was often burdensome. The evidence was scattered across spreadsheets, presentations, emails, and individual project files. Gathering an accurate picture of progress could become a project of its own. MoreSteam introduced TRACtion in 2006 to help close that gap.

Two decades later, TRACtion has evolved alongside the organizations that use it. To mark the anniversary, we spoke with MoreSteam CEO Bill Hathaway and Director of Software Development and TRACtion Product Manager Keegan Donnelly about what they've observed while working with continuous improvement leaders. Their experiences reinforce several lessons about what separates programs that produce lasting improvements from those that generate plenty of activity but struggle to demonstrate their value.

1. Choose projects that matter to the business

Over the years, Bill has seen organizations invest considerable time and effort in projects that sound useful but have little connection to the priorities of the business. The teams may have been plenty capable and the problems legitimate, but without a compelling business reason to pursue the work, projects struggled to compete with everyday operational demands.

This is where strategy deployment becomes important. Improvement resources are limited, and organizations need a disciplined way to identify the performance gaps that matter most, what benefits a project might deliver, and decide whether the organization is prepared to support the work. Projects that address a significant customer problem, remove a production constraint, or improve critical business processes are much more likely to attract the support needed to succeed.

Of course, that doesn't mean all improvement opportunities should originate with leadership. Keegan emphasizes the importance of capturing ideas from the people closest to the processes themselves. Those employees recognize problems and opportunities that aren't visible at higher levels of the organization, because in some cases, processes appear to function well, but only because people are expending considerable effort to workaround the existing problems.

You won’t see any improvement in your financial situation if teams elect to do projects to rearrange the break room.

— Bill Hathaway
MoreSteam

Those employees often recognize problems that aren't visible at higher levels of the organization. Sometimes processes appear to function well only because employees have become accustomed to working around problems, putting in extra effort just to keep things running.

Organizations need ways to surface those problems, evaluate their potential impact, and decide which deserve attention. But not every opportunity warrants a formal improvement project. As Bill puts it, "You won’t see any improvement in your financial situation if teams elect to do projects to rearrange the break room."

Good project selection requires connecting opportunities from across the organization to its strategic priorities. It's not about collecting the most ideas or choosing the biggest projected savings. It's about directing limited improvement capacity toward work that matters to the business and the people responsible for getting it done.

2. Consistency is key

One of the advantages of having 20 years of project data is the opportunity to learn what separates projects that get completed from those that don't. By examining TRACtion's project metadata in aggregate, MoreSteam identified that consistent progress is strongly associated with whether a project gets finished.

Projects that receive updates at least once a week are much more likely to reach completion. But even a relatively short lapse in activity matters. When a project goes two weeks without an update, its likelihood of ever being completed drops considerably.

It's a useful finding, and perhaps not surprising given what we know about how improvement work competes with day-to-day responsibilities. Most people working on improvement projects have other jobs to do, and urgent demands have a way of crowding out work that doesn't require immediate attention. A week without progress can easily become two, and before long, a project that once seemed important has vanished from the day’s to-do list.

We recognize that an update in TRACtion isn’t itself meaningful. Instead, the frequency of updates is likely a proxy for something more important, like whether the project remains a priority, whether the team has established a regular cadence of work, and whether leaders are paying attention. Still, this finding suggests that consistency matters, and it takes surprisingly little time for a project to lose momentum. Two weeks can pass in the blink of an eye in most organizations, and yet that may be all it takes for a project to be at risk of never getting finished. So, establish expectations for regular progress, recognize when projects are losing momentum, and intervene early. As we often say, the “M” in DMAIC should not stand for “months”.

Image of a group of people adding reminders to a caledar

3. Remember that improvement is a crime scene investigation, not a checklist

Managing a process improvement project is fundamentally different from managing a conventional implementation project, like a capital improvement project. With an implementation, you generally know what needs to be done and can plan the steps to get there. With process improvement, you know there's a problem, but you don't necessarily know what's causing it or how to solve it.

"Most improvement projects are investigations. They're detective work," Bill explains. He compares the process to arriving at a crime scene. You know a crime has been committed, but you don't know who committed it. You begin asking questions: Who was there? Who had a motive? Who had the opportunity? In process improvement, the criminal is the process input responsible for the undesirable outcome, and the investigation is about finding the evidence that identifies it.

You can't know in advance where the evidence will lead or which analytical tools you'll need. That's why Bill argues that improvement projects shouldn't be managed as a predetermined sequence of activities. Leading with a checklist of tools can send teams through the motions without ever identifying the real cause of the problem.

This thinking influenced TRACtion's original design. Rather than guiding practitioners through "this tool, then this tool, then this tool," Bill envisioned a question-driven approach: "this question, then this question, then this question." The evidence determines which tools are appropriate and where the investigation goes next. It was a subtle but consequential distinction, and one that reflected MoreSteam's broader approach to teaching continuous improvement.

Twenty years later, Bill still considers that question-driven philosophy one of the things MoreSteam got right from the start.

4. Don't overengineer the improvement process

Continuous improvement practitioners spend a great deal of time trying to eliminate non-value-added work from business processes. Ironically, we also have a tendency to introduce those same inefficiencies into the systems we use to manage improvement work.

An image of three people adjusting gears and adding more gears to a process

Keegan has observed this tendency when helping organizations configure TRACtion. It's tempting to require extensive documentation, multiple approval levels, and detailed reporting for every project. Each additional requirement may seem reasonable on its own, but collectively they can create a substantial administrative burden. As Keegan observes, "When they get to the core of what's really important to be tracked, that's when they have the highest adoption from people internally."

Bill describes the design challenge as "allowing complexity but not requiring it." Some projects justify formal tollgate reviews, detailed financial validation, and extensive documentation. Others are relatively straightforward improvements that can be managed effectively with an A3 or a simple record of the problem, the action taken, and the results. Applying the same level of administrative rigor to both may simply discourage people from participating.That balance between structure and flexibility has shaped TRACtion's development from the beginning. When TRACtion launched, competing project tracking software often required significant investments in custom programming, sometimes reaching five or six figures, just to accommodate an organization's workflows or specific reporting requirements. With TRACtion, customers could configure their own project roadmaps, permissions, notifications, approvals, and reports in an hour-long phone call with MoreSteam. Organizations could establish the oversight they needed without paying for extensive custom development or adopting processes that didn't fit the way they worked.

As TRACtion evolved to support idea collection, different improvement methodologies, and more sophisticated benefit tracking, that flexibility became even more important. Organizations could add capabilities as their programs matured without requiring every project or practitioner to take on the same level of complexity.

5. Visibility matters, but so does the cost of creating it

One of the most persistent challenges in improvement management is balancing the needs of program leaders with those of project teams. Program leaders need timely, reliable information about which projects are progressing, where teams need support, and what benefits the organization can expect. Project teams, meanwhile, want to spend their time improving processes, not repeatedly documenting work they've already done.

The tension is understandable. Information is essential to managing an improvement program, but collecting it creates work of its own. When reporting becomes disconnected from the actual problem-solving process, it can begin to feel like an administrative burden rather than a useful part of the work.

Two people sitting side by side at computers fist bumping. The EngineRoom logo is on one computer screen and the TRACtion logo is on the other.

This realization helped shape the integration between TRACtion and EngineRoom, MoreSteam's data analysis software, and continues to influence the development of both products. Instead of treating analysis and project documentation as separate activities, the aim is to connect them more directly.

Bill describes the ideal simply: "You do the work one time, one place." The ambition is to reduce duplicate documentation, make project information easier to access, and allow reporting to emerge more naturally from the work itself.

After twenty years, one of the most important lessons in designing improvement software is also one of the simplest: the system should make it easier to solve problems, not create another problem to manage.

6. Prove the value of the improvement system, and keep proving it

There's an inherent timing challenge in continuous improvement. The investment in people, training, and projects often happens well before the benefits are realized. Those benefits may accumulate over months or years, and some are difficult to quantify. When budgets tighten or leadership changes, that imbalance can make improvement programs vulnerable.

Bill has observed that organizations with durable Operational Excellence systems make a deliberate effort to communicate project successes, demonstrate operational improvements, and explain how those improvements support broader organizational objectives. They don't assume good work will speak for itself or that senior leaders will automatically recognize its value simply because projects are being completed.

But credibility matters as much as visibility. Suppose an improvement project eliminates several hours of administrative work each week. That's a worthwhile accomplishment, and the recovered capacity may allow employees to take on more valuable activities. It doesn't necessarily mean the organization has reduced its expenses by the equivalent labor cost, however. There's an important distinction between actual cost savings, cost avoidance, increased capacity, and other operational benefits. Treating them as interchangeable can undermine confidence in the value of the improvement.

Bill emphasizes the importance of involving finance in validating financial results, particularly for projects claiming substantial savings. Keegan sees the same issue when organizations configure TRACtion and decide which financial and nonfinancial benefits to track. The information needs to be meaningful to leadership while remaining practical for project teams to collect consistently.

A credible accounting of improvement's contribution, supported by operational evidence and communicated regularly, gives leaders a much stronger basis for continuing to invest in the work.

7. Make it easier for people to share what they've learned

Keegan Donnelly Director of Product Development and TRACtion Product Manager

Keegan Donnelly Director of Software Development & TRACtion Product Manager

A repository of completed improvement projects provides a wealth of organizational knowledge that can help other teams solve similar problems. Keegan emphasizes the importance of preserving project records so organizations can celebrate successes and share best practices. That doesn't mean documenting every detail. Capturing the problem, what the team learned, the solution implemented, and the results provides a useful starting point.

Over time, these records become an increasingly valuable resource, but only if people can find and use the information. Before beginning a new investigation, teams should be able to see whether someone elsewhere in the organization has encountered a similar problem, what they tried, and what they learned. Sometimes the best next step isn't another investigation, but applying a solution that's already been proven.

This is an area where artificial intelligence presents some interesting possibilities. Imagine being able to search hundreds of completed projects and quickly discover that another facility has already solved a similar problem. AI could help teams find relevant examples, understand which approaches worked and which didn't, and identify recurring problems or successful practices across facilities that might otherwise go unnoticed.

8. Software can support an improvement culture, but it can't create one

It's tempting to believe that implementing a project management system will bring greater discipline and accountability to an improvement program. And it can certainly help. But a system won't compensate for managers who aren't actively engaged in the work.

Keegan sees this difference in the organizations he works with. Some have leaders who regularly review projects, ask questions, help teams work through obstacles, and make decisions about priorities and resources. Others put a system in place and expect people to keep their projects moving and their records current without much management involvement. It's not surprising that the first group tends to have more success.

Bill has seen the same pattern over two decades of working with operational excellence leaders. People have competing responsibilities and priorities are constantly shifting. Someone has to make decisions and hold people accountable for getting the work done. As Bill puts it plainly, "The software is never a substitute for leadership."

The purpose of a system like TRACtion is to help managers do those things more effectively. It makes the work visible, provides a common framework for managing projects, and helps leaders see where their attention is needed. But it doesn't decide which problems are worth solving or ensure that people have the time and resources to solve them. That's still the job of management, and no amount of technology is going to change it.

A group of people traversing to the top of a mountain. They are all holding hands, pulling each other up the mountain with the leader planting a flag at the peak.

Twenty years later, the fundamentals still apply

TRACtion has changed considerably since its launch in 2006. What began as a way to manage and report on Lean Six Sigma projects has evolved to support different improvement methodologies, flexible workflows, idea prioritization, financial and operational reporting, and connections to the analytical tools practitioners use. Much of that evolution has been shaped by customers. As Keegan explains, organizations share common improvement goals, but they often have different ways of organizing the work, measuring success, and supporting their teams. Listening to those differences has helped MoreSteam make TRACtion more flexible and better suited to the realities of continuous improvement.

Looking ahead, both Bill and Keegan see opportunities to make better use of accumulated project knowledge, reduce administrative work, and connect improvement activity more directly to organizational strategy. AI will undoubtedly play a role, and we'll continue exploring ways to help practitioners and leaders make better decisions. But twenty years of experience also remind us that new technology doesn't eliminate the need for a strong management system.

Choose problems that matter. Give people enough structure to work effectively without burying them in bureaucracy. Apply the scientific method when investigation is needed, and avoid reinventing solutions when the answers are already known. Keep projects moving, communicate their value credibly, and make what you've learned available to others.

Most importantly, recognize that sustained improvement requires sustained leadership attention. That was true when TRACtion launched twenty years ago, and there's little reason to believe it will be any less important twenty years from now.

Lindsay Van Dyne

Vice President of Marketing • MoreSteam

Lindsay Van Dyne is responsible for developing and executing MoreSteam’s marketing strategy. She brings a deep understanding of Lean Six Sigma, having served as MoreSteam’s eLearning Product Manager for the company’s comprehensive suite of Yellow, Green, and Black Belt courses. Over the years, she has attended dozens of industry conferences, webinars, and workshops, gaining firsthand insight into the evolving needs of continuous improvement professionals.

Her marketing experience includes technical aspects of search engine optimization (SEO), digital content strategy, lead generation, website development, event management, and partner relationships. Lindsay holds a B.S. in Chemical Engineering from the University of Notre Dame and a B.S. in Computational Physics and Mathematics from Bethel College.

Lindsay Van Dyne Full Bio

Use Technology to Empower Your Continuous Improvement Program