How to Improve Quality Without Bureaucracy

The quest for quality often leads software organizations down a paradoxical path: adding more manual checks and approvals that actually make quality worse, not better. Release processes that require manual QA signoff, security review, or executive approval might feel safer, but they create long, unpredictable feedback cycles that hide problems and increase risk. Consider what happens when teams batch up multiple changes for a big release requiring manual review. Engineers context-switch to new tasks while waiting for approval. When issues are found, the original context is lost and debugging becomes complex. Meanwhile, more code is being built on potentially problematic foundations. The cycle repeats, creating a growing backlog of changes waiting for review. This pattern appears in many forms. Manual QA phases that take days or weeks. Change review boards that meet monthly. Pre-release checklists that grow ever longer. While each addition to the process aims to improve quality, the cumulative effect is often the opposite: larger, riskier deployments that are harder to troubleshoot when things go wrong. The most effective teams recognize that rapid, automated feedback is far more valuable than manual process gates. They invest in automated testing, continuous integration, and tooling that catches issues early. They deploy small changes frequently rather than batching them up. When manual reviews are needed, they happen continuously rather than becoming bottlenecks. So, remember: - Large batches of changes increase risk, not safety - Manual approvals create queues that hide problems - Long feedback cycles make debugging more difficult - Automated checks scale better than manual processes - Frequent small deployments tend to be lower risk than infrequent large ones The path to better quality is enabling faster feedback through automation and smaller batch sizes—it's not adding more manual processes. Truly embracing quality at scale requires letting go of the illusion of control that manual processes provide.

When Mary Barra took over GM's HR department, she found a 10-page dress code policy. She replaced all 10 pages with just two words: "Dress appropriately." The HR team panicked. A senior director sent an angry email demanding more detailed rules. But Barra held firm. When the director called to complain that his team wore jeans to government meetings, she didn't cave. Instead, she told him: "Have a conversation with your team." Two weeks later, he called back excited. His team had solved it themselves...they'd keep dress pants in their lockers for important meetings. Here's what happened across GM: 1. Managers started making decisions instead of following rulebooks 2. Employee engagement improved as people felt trusted 3. Bureaucracy dropped as leaders focused on outcomes, not compliance Barra realized: "If they can't handle 'dress appropriately,' what other judgment decisions are they not making?" She built a culture where thinking mattered more than rule-following. Most companies write longer policies to avoid problems. Mary wrote shorter ones to create leaders.

It's time to change How we Improve Quality... In today's fast-evolving economic landscape, we find ourselves at a moment where doing “more with less” is no longer a buzzword, but a necessity across all industries and especially in healthcare. Today, many health systems dedicate 1-2% of their operating revenue to quality improvement & safety activities. When I was CEO of the IHI, I would regularly hear from quality leaders about impending cuts to their divisions. And yet, the CEOs of those same systems would tell me that they knew they couldn't compromise on quality & safety. So how to square the math? Today, sadly much of our quality investment is tied up in manual processes—data collection, spreadsheet wrangling, and retrospective reporting that rarely drives real-time action or measurable impact. It’s time for a shift. I believe quality professionals should not be buried in administrative tasks, but instead leading the really hard change management necessary to transform clinical care. By automating the manual abstraction and leaning into expert-led transformation, we can finally focus on what matters most: making care systems more optimal for patients and providers alike. Here’s how we envision that transformation: 🔄 Optimization: Let’s use our most valuable resource—people—more efficiently. When automation takes care of repetitive tasks, quality experts can focus on strategy, problem-solving, and driving cultural change. 🎯 Prioritization: Real-time data and AI-powered insights allow us to see what truly matters. Instead of spreading efforts thin, we can zero in on the improvements that will yield the greatest impact for patients and teams alike. 🔁 Complete + Continuous: Sampling is no longer enough. Modern systems enable comprehensive monitoring across entire populations—always on, always learning. That means no more waiting weeks or months to identify a problem that needed action yesterday. Finally, finally (!), the technologies we are introducing in healthcare are good enough to do the heavy lifting, liberating our quality teams to do the valuable change management work that only they can do best. #HealthcareTransformation #QualityImprovement #DigitalHealth #Automation #PatientSafety #HealthTech #ContinuousImprovement #Leadership

The fastest way to kill energy in a company is to let process replace thinking. Process should exist to sharpen judgment not to dull it or to shield people from reality. When teams start worshiping the checklist, when people follow the script just to “get through the meeting,” you know the game is over. You can see it in the eyes of the team: a quiet resignation, a learned helplessness. You hear, “That’s just how we do things here,” and you know nobody’s expecting anything to change. Thoughtless process is a way to outsource discomfort. You can hide behind it. You can point to it when someone asks why a customer is angry or why a project is stuck. Bureaucracy thrives on this. On the false comfort of repeatable steps, on the myth that consistency is the same thing as progress. But the truth is, every great company is built on tension. Between speed and quality, between what worked yesterday and what’s required tomorrow. Process that survives this tension is earned. Everything else is just set dressing. If your team is spending more time filling out forms than fixing what’s broken, you’re not scaling excellence, you’re scaling mediocrity. The highest-leverage moves always happen outside the manual, at the edges where someone is willing to ask, “Why do we even do it this way?” The people who ask this are worth everything. You don’t fix a broken culture with more process. You fix it by making sure the process never becomes an excuse to stop thinking. The second it does, it’s time to burn it down and start again.

If quality only lives in the QA department, you already have a problem. A real quality culture is built when systems, leadership, and behaviour are aligned. Here is what consistently shows up in organizations that get it right: • Leaders set direction and actively support quality, not just approve it • Leadership commitment is visible through decisions, priorities, and actions • Employees are engaged, empowered, and trusted to improve their own work • Recognition reinforces the right behaviours, not just results • Processes are improved continuously, not only after failures • Standard operating procedures create stability, and learning drives maturity • Data is used to understand reality, not defend opinions • Customer needs guide decisions, not assumptions • Feedback loops stay open across teams and levels • Communication builds transparency, trust, and collaboration Quality culture is not owned by QA. It is shaped daily by leadership behaviour and employee involvement. If you want better quality results, start by strengthening the culture that produces them. Which element do you see most often missing in real workplaces? #QualityGurus

Quality takes time. Not because it’s complex, but because it’s cultural. And culture doesn’t change on command. It’s easy to think a new system, dashboard or QMS rollout will fix the gaps. But without clear direction from leadership, even the best tools won’t do much. Teams end up filling in the blanks themselves. And that’s where inconsistency starts. Deming wrote that quality is decided in the boardroom. That holds up. Direction must come from the top. Not as mandates, but as a clear, shared method everyone understands. What’s often overlooked is that quality is also a social dynamic. It’s built on conversations, habits, trust, and collaboration. When things get busy, those interactions are the first to go. Feedback loops get dropped to ‘save time’, but that silence comes at a cost. Without regular exchange between people, technical quality suffers, even in a fully compliant system. The system might still run, but you’ll notice more errors, more rework, more small decisions that don’t fit together well. Tracking defects gets a lot of attention in some teams. But that’s usually a sign that the process isn’t doing its job. A well-functioning system prevents most defects from happening in the first place. And the time spent counting issues? Often better spent strengthening process stability. There’s also the perception challenge: if quality feels like a policing role, resistance is inevitable. People push back against being audited or checked without context. That’s natural. What works better is when quality is positioned as support, something that helps teams do their job well, not something that checks their work after the fact. This shift takes time. It’s not a change in procedure, it’s a change in posture. And especially in regulated environments, it comes down to how much trust people have to make decisions. Documentation and improvement methods matter, but autonomy is what unlocks real change. It rarely happens through a single initiative. Culture builds through moments, small efforts that add up. Involving people early, designing for clarity, allowing space for reflection, these are what create sustainable systems. One thing I’ve learned: you can have the best process on paper, but if people don’t feel part of it, it won’t work in practice.  → What’s helped you build a quality culture that lasts? Feel free to share what’s worked; always open to learning from other approaches.  

Stop inspecting quality in. Start building it in. Or better yet, design it in. Most plants are stuck at Level 1. And they wonder why quality never improves. LEVEL 1: INSPECT IT OUT End-of-line inspection. QC sorting good from bad. Rework areas packed with parts. Here’s the problem. You already spent time and money making those defects. You’re just catching them later. It’s the most expensive way to run. LEVEL 2: BUILD IT IN Inline quality checks at every station. Operators own their work. Instant feedback when something’s off. Better. You catch problems at the source. But you still depend on people to spot mistakes. LEVEL 3: DESIGN IT IN Poka-yoke tools that make errors impossible. Parts that only fit one way. Processes that won’t let mistakes happen. Best. The system prevents defects before they exist. No inspection needed. Here’s the truth. Most plants keep hiring inspectors and wonder why quality stays flat. Because you’re still making defects, just finding them later. Good plants move to Level 2. They stop issues early. Great plants aim for Level 3. They eliminate the chance of mistakes altogether. Level 1 finds waste. Level 2 reduces waste. Level 3 eliminates waste. Where’s your plant today? Drop your level below: 1, 2, or 3. P.S. If your quality plan is “add more inspectors,” you’re at Level 1. And that’s the priciest way to run. Move upstream.

Quality is not a department. It never was. When quality becomes the responsibility of a single function — inspectors checking parts, a quality team managing complaints — it becomes a bottleneck, a cost center, and eventually a scapegoat. The most operationally excellent manufacturers I've worked with share a different belief: quality is a virtue embedded in every role, at every level, in every shift. The machinist who catches a dimensional drift before it becomes a nonconformance. The assembler who flags an ambiguous work instruction before it causes a defect. The supervisor who builds time into the day for proper setup rather than rushing to output. The engineer who designs the process so the right outcome is the easiest outcome. These aren't quality department actions. They're the behaviors of a culture that owns quality. Building that culture requires more than a quality policy. It requires clear standards, proper training, visual management, leadership modeling, and systems that make the right behavior easy and the wrong behavior obvious. Quality is a competitive advantage — but only when it's a shared value, not a delegated function. What does quality ownership look like on your floor? #QualityManagement #ManufacturingLeadership #OperationalExcellence #ContinuousImprovement #Culture

I showed up to a plant where “quality” lived in binders, blame, and late-night paperwork. Operators rolled their eyes. Leaders shrugged. Audits felt like punishment. So I didn’t argue about culture. I rebuilt what they actually used. What I did (short and stubborn): 𝗥𝗲𝗺𝗼𝘃𝗲𝗱 𝗻𝗼𝗶𝘀𝗲.  Trimmed overlapping procedures and replaced bloated forms with one-page flows. 𝗘𝗺𝗯𝗲𝗱𝗱𝗲𝗱 𝗰𝗵𝗲𝗰𝗸𝘀. Compliance became part of the work, not an extra chore stuck on the end. 𝗠𝗮𝗱𝗲 𝗮𝘂𝗱𝗶𝘁𝘀 𝘂𝘀𝗲𝗳𝘂𝗹. Audits shifted from fault-finding to coaching. Providing actionable feedback focused on what they wanted to do. 𝗦𝗵𝗶𝗳𝘁𝗲𝗱 𝗱𝗲𝗰𝗶𝘀𝗶𝗼𝗻𝘀 𝘁𝗼 𝘁𝗵𝗲 𝗳𝗹𝗼𝗼𝗿. Gave people the authority and guidance to fix simple problems where they happened. What changed: - People stopped dreading audits and started asking for them. - Frontline teams owned the process because it helped them get their work done. - The endless firefighting softened—repeat problems stopped repeating. You don’t win hearts by lecturing. You win them by making the right thing the easiest thing to do. Quick challenge: pick one process your team complains about. Remove one step this week. See how people respond. If you want practical, no-fluff ways to turn systems like this into something your team will actually use, subscribe to my newsletter. I share real fixes that stop the firefight and start the improvements. Link in the comments 👇

Many organizations add more programs to improve productivity, but the result is often more complexity and little progress. In this Next Big Idea Club article, Don Kieffer and I share five principles from There’s Got to Be a Better Way that simplify work and improve results. 🔹 Begin with a small change and allow the improvement to spread 🔹 Decide carefully when to huddle and when to hand off 🔹 Replace rigid targets with clear intent, visible plans, and real-time feedback 🔹 Limit the amount of work in progress so tasks move forward more smoothly 🔹 Use simple visual tools that make the work obvious These practices are simple, but they are powerful when applied consistently. Read the full article: https://lnkd.in/eNZDBZyP MIT Sloan Executive Education Massachusetts Institute of Technology MIT Sloan School of Management Mark Schwiebert