While models can be awesomely useful, they are ultimately just constructs that were created because they were relevant to someone at some point. What’s more important is understanding where our models come from in the first place: how they are created, how they evolve and what they connect back to. We forget their underpinnings at our peril. But unfortunately we do that a little too often.
This Is All Make-Believe
We fall in love with our models, our processes and our standards. They’re helpful when they help us to make sense of the world, but they can also get in the way. What we sometimes forget is that they were all invented to provide a perspective on a problem. That means we can change them, adapt them, evolve them and dispense with them when they stop providing value.
Culture Matters
Culture matters. That might seem obvious to say, but we tend to ignore that when it comes to process design and organizational change. We can see that when implementing process, what works depends upon context. But the challenge is reading context accurately, and making appropriate choices that work. We need to lead with culture and follow with practice, not the other way around.
Successfully Navigating Process
Getting process right is hard. While we might know what not to do, identify what to do is challenging and difficult. In a world where we accept that the right answer to process is “it depends,” we need to get clear and specific about how we can figure out what it depends on. Identify the questions to ask and the approach to take is challenging. Following it is even harder. Doing both is essential.
Embracing The Maturity Monster
Maturity models as a concept have become incredibly popular. We use them as cover to justify any number of improvement efforts. But how we use them is often misguided, dangerous and downright wrong. Maturity as a concept can be useful, but we need to understand what it means and how it should be applied.
Embracing “It Depends”
Process needs to work. To work, it needs to be relevant. That means that what we implement needs to be contextually appropriate, relevant and accepted. Cookie-cutter solutions don’t work here. What works depends. But the real question is, “what does it depend on?”