September 23, 2025
Community Voice
When organizations talk about going model-based, most think about tools, data structures, and integration.
But here’s another real roadblock: tribal knowledge.
For decades, many companies have relied on tribal knowledge, the one engineer who knows why a certain design decision was made, the veteran program manager who “just remembers” why a requirement was skipped, the unwritten rules everyone follows but nobody documents.
👉 In a model-based governance environment, there is no place for tribal knowledge.
Why? Because models don’t guess. Models don’t “just know.” Models need precision, traceability, clarity, and a single source of truth. In other words models need to be clear, concise, and valid!
Here’s where the CM2 standard becomes the bridge:
1️⃣ Define before you design. Governance first, modeling second. A model built on unclear rules is just a prettier version of chaos.
2️⃣ Kill the “expert memory” culture. Replace it with accessible, documented decision logic that anyone can trace and trust.
3️⃣ Shift mindset, not just software. Transitioning to model-based governance is not about digital tools replacing documents, it’s about replacing assumptions with accountability.
And here’s the uncomfortable truth:
But the payoff? 🚀
The organizations that succeed don’t just “install” a new tool; they lead a cultural transformation. They make it safe for people to let go of tribal knowledge, and they prove that documented, model-based governance is not bureaucracy, it’s freedom. Freedom from firefighting, rework, and guessing.
Transitioning from a document-based to model-based isn’t a technology challenge; it’s a leadership challenge.
So I’ll leave you with this:
💡 When your organization says it’s going “model-based,” are you tackling tribal knowledge head-on or just deploying a new tool?
Check out the other How Do YOU CM2? posts.
Use code Martijn10 for 10% off training—and don’t forget to tell them Martijn sent you 😉.
Copyrights by the Institute for Process Excellence
This article was originally published on ipxhq.com & mdux.net.
Known by his blog moniker MDUX—Martijn is a leading voice in enterprise configuration management and product lifecycle strategy. With over two decades of experience, he blends technical depth with practical insight, championing CM2 principles to drive operational excellence across industries. Through his blog MDUX:The Future of CM, his newsletter, and contributions to platforms like IpX, Martijn has cultivated a vibrant community of professionals by demystifying complex topics like baselines, scalability, and traceability. His writing is known for its clarity, relevance, and ability to spark meaningful dialogue around the evolving role of configuration management in Industry 4.0.