Is quality management the most thankless job in the organization? In many companies, QM teams want to be the Hermione Granger of the workplace—knowledgeable, prepared, and doing the right thing—but end up perceived as Argus Filch, the grumpy caretaker enforcing rules nobody asked for.This week's guest, Regina Haar, works at Q.Wiki (Modell Aachen), where she helps quality managers move from being considered annoying compliance police to becoming genuine enablers. She joins Roland to unpack why this role is so often stuck—and what it takes to change it from the inside out.In this episode we are talking about:The Harry Potter metaphor that lands every time: quality managers see themselves as Hermione (smart, principled, always prepared), but the organization experiences them as Filch—chasing people down, enforcing rules, and getting little recognition for it.The root cause of the image problem: when certification becomes the why of quality management, employees have no intrinsic motivation—usage spikes before audits and collapses after. Event-driven, not value-driven.Two formative lessons from Regina's career: a missing colleague's undocumented knowledge cratered a major production, and a well-meaning onboarding plan failed because it lacked a coherent big picture. Both point to the same conclusion—context and structure matter as much as content.The “Scribbler” trap: a LinkedIn poll found that 45% of respondents said only the quality or process management team designs processes—making QM the bottleneck and ensuring the business never emotionally owns what gets documented.The first lever for change is decentralized creation: replace “I write your processes” with “I coach you to write them.” Build a platform where content originates with the people doing the work.Intrinsic motivation requires three things—autonomy, self-efficacy, and social integration. Centralized modeling teams undermine all three and kill the very engagement QM is trying to build.The Marauder's Map metaphor: a management system should work like Fred and George Weasley's map—showing you where you are, where others are, and which hidden paths exist. Two clicks to the answer beats perfectly formatted documentation.Embedding process guidance into runtime systems—through a Chrome extension, a CRM integration, or a contextual sidebar—moves the mountain to the user instead of making users climb to the mountain.Combining knowledge management and process management is an underutilized power move: processes give structure, and knowledge gives detail. Together they raise relevance and adoption—but they typically live in separate tools and separate teams.Quality departments chronically underinvest in internal marketing. Projects die not because the work was bad, but because the wins were never communicated. The shift needed—from cost center to value creator—was told loudly, repeatedly, and in the language of business outcomes.You can find Regina on LinkedIn here: https://www.linkedin.com/in/regina-haar/.Please reach out to us by either sending an email to ⁠[email protected]⁠ or signing up for our newsletter and reading articles about process and architecture on our Substack… Go and subscribe at ⁠whatsyourbaseline.substack.com⁠.And if you like to support “the little podcast that could,” become a Patron at ⁠https://www.patreon.com/c/whatsyourbaseline⁠. We appreciate you!

Ask this episode

“What did the council decide on item 42?” — answered with the speaker and the moment.

Transcript

Related