This is an analogy familiar to software programmers. Code that refers to data that does not exist produces software crashes. The whole science of software engineering has spent a lot of effort on creative solutions to prevent such code from being written.
Humans also experience 'crashes' when executing their strategy. A couple of examples: (i) A process requires an input, but there is no clarity or agreement on who will provide that output. (ii) A process generates an output, but there is no clarity or agreement on who will consume that output.
Humans can tolerate ambiguity better than machines, they do this by asking questions and collaborating. When they can't or won't, dysfunctional behavior is generated.
When creating a plan make sure everything is connected to everything else. After the plan is created, it has to be tracked. A good plan that connects all the dots will make tracking status easier. The final challenge is to present the plan. Too much detail may result in the important items not getting the desired attention. Different stakeholders have different needs, so the presentation has to be targeted to their needs. Communication becomes easier when the dots can be connected in a meaningful and relevant way.
Everything is connected to everything else. Find the connection to create, track and communicate your plans to execute strategy.
No comments:
Post a Comment