Nobody’s calendar has a meeting titled “our processes are failing.” Instead, process problems show up in disguise \u2014 as tired people, missed dates, and stories everyone tells with a shrug. After 20+ years of walking into organizations, we can usually tell within a day. These are the six signs we look for.<\/p>\n
The strongest performers spend their days rescuing orders, expediting exceptions, and patching the same failures they patched last quarter \u2014 and they’re praised for it. Firefighting feels productive; it’s actually expensive maintenance of the status quo. When heroism is the operating model, the process is the problem. (We wrote a whole post on this: fighting fires isn’t a strategy<\/em>.)<\/p>\n A predictable, recurring event that still requires late nights is the clearest possible signal of process debt: too many manual steps, too much rework, reconciliation that exists because upstream data can’t be trusted. Predictable work should be boring.<\/p>\n When this sentence ends conversations instead of starting them, your processes have stopped being decisions and become folklore. Nobody remembers why the report is produced, why the approval loop has five stops, why the form is filled out twice \u2014 and nobody feels licensed to ask.<\/p>\n Somewhere in your operation there is a person who can’t take a real vacation because a critical process lives entirely in their head. That’s not dedication \u2014 it’s key-person risk, and it’s one bad flu season away from being an emergency. (We once found hundreds of millions of dollars<\/a> flowing through exactly this arrangement.)<\/p>\n Not the official system \u2014 the spreadsheet next to it, maintained by hand, fed by emails, re-typed from data that already existed electronically. The workbook is the workaround that became the process. It works right up until it catastrophically doesn’t.<\/p>\n If your most reliable quality check is a complaint, your cost of poor quality is far larger than you think \u2014 most leaders are off by 5\u201310\u00d7 \u2014 because every escaped error carries rework, concessions, and quietly eroded trust.<\/p>\n Three or more of these?<\/strong> That’s not a staffing problem, a talent problem, or a culture problem. It’s a process problem \u2014 and process problems are the most fixable problems in business.<\/p><\/blockquote>\n Resist the urge to launch a dozen fixes. The disciplined path: pick the symptom with the clearest cost, measure it honestly, run one focused improvement project to completion \u2014 including the controls that make it stick \u2014 and use that win to fund the next. This is precisely what the Lean Six Sigma method<\/a> was built for.<\/p>\n Start by putting a number on it: the free Cost of Poor Quality Calculator<\/a> takes two minutes and usually changes the conversation from “should we act?” to “how fast can we start?”<\/p>\n Try internal first if you have trained practitioners and leadership air-cover. Bring in outside help when the problems cross departmental boundaries (internal teams get stuck at political seams), when you need a trusted independent baseline, or when you’re building an improvement capability for the first time and want it done right once. See our guide to hiring a Lean Six Sigma consultant for the five filters to apply.<\/p>\n In our experience, overwhelmingly yes. When the same symptom appears across different people \u2014 every month-end is heroic, every cross-team handoff drops \u2014 the common factor is the process. Replacing people into a broken process reliably produces the same results with new names.<\/p>\n Suspicion isn’t a diagnosis. The free Windy Hill Toolkit turns these signs into numbers \u2014 cost of poor quality, bottleneck location, readiness gaps \u2014 in minutes, with no login.<\/p>\n Explore the Free Toolkit →<\/a><\/p>\n Prefer a conversation? Let’s talk<\/a> — 610-316-4056.<\/p>\n<\/div>\n2. Month-end takes a heroic push. Every month.<\/h2>\n
3. “That’s just how we’ve always done it.”<\/h2>\n
4. One person is the only one who knows how<\/h2>\n
5. The real process lives in a spreadsheet<\/h2>\n
6. Errors get caught by customers, not controls<\/h2>\n
What to do next<\/h2>\n
Frequently asked questions<\/h2>\n
When should we hire a process improvement consultant instead of fixing it ourselves?<\/h3>\n
Are these signs really process problems and not people problems?<\/h3>\n
Put numbers on the symptoms<\/h2>\n