5 Steps to Shift from Reactive to Proactive Quality Management
You don’t build proactive quality management with one big fix. You do it by shifting small habits, priorities, and conversations.
I recently spoke with Atty Chakraborty, a Quality Systems Engineer at Analog Devices. She was also named Quality Magazine’s 2025 Rookie of the Year.
She shared how she moved her team from reacting to potential problems as they came up to planning ahead and preventing them through a robust quality management system (QMS).
This shift did not happen through a single mandate, but through six months of getting people on board and talking openly about the goals.
She managed this without overwhelming her team or burning bridges. She taught her team to work through problems instead of handing them answers. That switch made continuous improvements stick.
Here are the effective steps from our conversation that any quality leader can implement to start making this change.
Step 1: Diagnose the Reactive Firefighting Trap
When asked to describe how she helped move from a reactive to proactive state, Atty Chakraborty said, “If I were to summarize it in one sentence, it would be teaching someone to fish rather than getting the fish for them.”
Before any change was possible, Atty Chakraborty had to recognize the patterns of reactive work. Her early days were defined by ad hoc requests and constant interruptions. She described it as a “reactive fire mode where things pop up and they have to be handled immediately.”
This state is familiar with manufacturing quality. It means your team spends its days responding to failures and audits, not preventing them. You facilitate solutions for others instead of building their capability to solve problems themselves.
Several signs indicate you are in this trap. One is resource fluidity. “If you look at the typical Six Sigma process, you would think that it’s easy to get resources and that they would commit before starting the project,” Atty noted. “However, in reality, there is a high chance that it will change. People will get moved into more urgent things.”
Another sign is a focus on compliance over usability. Atty observed processes that “were meeting our compliance needs, but not the best to work with.” When a process is only judged on whether it passes an audit, rather than how it helps engineers do their jobs better, it remains a source of recurring friction. This cycle keeps the quality team in a perpetual firefighting role.
Step 2: Map the Mess with a Quality Management System
“Just like any other quantity process, it’s very important to know what the problem statement is.”
Here, Atty Chakraborty gave an example of how, in one situation, she went beyond listening casually to complaints to circulating a spreadsheet across the business unit. This invited structured input on pain points about a process that met compliance but frustrated users—the exercise built clarity, prioritized issues, and, most importantly, made stakeholders feel heard.
To map out a quality plan, Atty’s suggestion is to start by defining a clear problem statement based on user feedback, rather than siloed assumptions.
Once the problem is defined, solutions can emerge through brainstorming. “There can be different ways to do this: Some people prefer to just have a blank sheet of paper and go in and discuss with the team. Some people would like to propose certain solutions like a draft, and then discuss them with stakeholders as they go on,” Atty said.
The method depends on organizational culture and the urgency of frustrations with existing processes. This structured feedback loop shifts quality efforts from reactive fixes to proactive improvements.
Step 3: Prioritize Ruthlessly Using the Eisenhower Matrix
Without a way to sort them, a long list of quality issues can freeze progress. Atty Chakraborty introduced the Eisenhower Matrix to her workflow as a proactive approach to quality management.
This tool categorizes tasks by urgency and importance. She sorted items into what must be done now, what could be scheduled later, and what was simply nice to have.
Laying it out visually helped leaders see what mattered most. Atty presented the categorized matrix to management and stakeholders and asked if they agreed with her assessments. This created a shared understanding of where to focus efforts first.
Tying quality work to business priorities helped justify where resources should go. Atty found that breaking down actions by priority and linking them to specific stakeholder roles strengthened her case.
She said, “If you can break down the actions in your quality plan by priority and identify what role each person has in executing that high-priority task, then it’s much easier to convince management why they should be on your plan instead of doing something else.” It showed how the quality plan pushed company goals forward.
Sorting tasks clearly made it easier for others to trust the plan. With a shared framework, decisions felt less personal and more grounded.
Step 4: Over-Communicate Progress, On Purpose
It’s easy to lose people’s attention. Atty Chakraborty addressed this by scheduling monthly update calls without exception.
These meetings weren’t reserved for major milestones. They happened consistently, even when progress was incremental. That steady cadence helped keep the work in focus.
Staying in touch regularly changes how people see the project. Atty observed that a project’s success is not just about meeting deliverables. It’s also about how engaged people feel with what’s happening.
“A lot of the things of a successful project is actually the impression of it,” she said. Regular updates build a perception of steady momentum, which in turn builds confidence in the initiative.
Just showing up builds trust. Atty found that the only way to maintain engagement was to show steady progress. “You just need to keep them informed and in the loop as you go ahead,” she explained, “so that they don’t feel that the project is stagnating.” Being present shows you’re dependable and open to input, which helps weather delays.
Step 5: Elevate the Standard Through Culture, Not Compliance
The final shift makes quality part of how the team works—not just something checked at the end. Atty Chakraborty saw this happen through the CAPA process.
It switched from fixing errors to making the product better. She described guiding engineers to “think about uncharted territory, which they’ve not thought about before.”
This turned CAPAs into a chance to build stronger systems. Instead of focusing solely on containment and correction, the investigation spurred preventive thinking.
“When a defect arises, you can think about the other places where it has arisen,” Atty explained. This encourages engineers to proactively identify potential failure points and strengthen the design.
Raising the bar on quality checks helped change the mindset. Atty gave an example of instituting a “95% defect-free” requirement. That target made people ask why they were aiming higher—and how to meet it.
They stopped asking, “is this just enough to get us out into the market?” to “is this something that is going to make us stand out?” That’s how quality becomes part of the design, not an afterthought.
Driving Better Results with Smarter Workflow Updates
These steps aren’t just tactics to try. They reflect a deeper shift in how teams think about quality. Moving from firefighting to planning depends on that mindset switch.
Atty didn’t wait for a mandate to begin this transformation. She earned trust by staying organized, communicating clearly, and reading the room. Her proactive approach showed that real change happens when processes work for both the people using them and the goals they serve.
For more on how Atty handles the nuances of CAPA culture, stakeholder dynamics, and long-term quality planning, listen to the full episode of the podcast.
