This article is part of the How Do YOU CM2? blog series in collaboration with the Institute for Process Excellence (IpX). Although I receive compensation for writing this series, I stand behind its content. I will continue to create and publish high-quality articles that I can fully endorse. Enjoy this new series, and please share your thoughts!
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:
- Legacy habits will resist. People like being the keeper of knowledge. However, these experts are crucial in translating their tribal knowledge into models and sharing it with everyone.
- Model-based governance exposes gaps. What was once hidden in coffee corner conversations now demands formal resolution.
But the payoff? 🚀
- Faster impact analysis and planning of changes. Get more done with the same amount of time and resources.
- End-to-End traceability baked-in, that allows you to innovate and be more agile.
- The ability to scale your organization’s knowledge, not just its headcount and without depending on who’s retiring next year.
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.
Copyrights by the Institute for Process Excellence.