Posts Tagged ‘ process ’

Appropriation & Adaptation

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 “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?”



The Myth of Best Practices

I’m a process geek. You might safely assume, then, that I would be a fan of “best practices.” You would be very wrong. Best practices generally aren’t. Unlike the promised intent, there is usually more than one best way to proceed in a given situation. We ignore that at our peril.



I Am A Process Geek

A personal confession: my professional career has been dedicated to process. While I appreciate the value of process, I am also challenged by how it is often implemented. It’s easy to ask for everything. It’s a lot harder to focus on what is essential and valuable.



Dreams & Reality

“Why are we doing that?” It sounds like a simple question. It often has a very complex answer. Getting to the essence of why is important for project success, but how we usually think about projects often gets in the way. Reframing the questions to get the answers that we need.



Process Can’t Compensate For Culture

Process is appealing. It provides structure and guidance and rules and boundaries. The challenge is that organizations are messy and complex. Projects are difficult. They require work and adaptation. You can’t just take process from one place, apply it to another, and expect it to work properly. You need to do something else.



Best Practices Usually Aren’t

There are few terms that have the same unbridled acceptance in business as “best practices.” Except that, for many organizations, best practices fail to deliver on the theoretical promise implied by the term. Best implies one superior way of working, where in reality there are many practices dependent upon many different things.



12