Clockwork Strategy Execution
This past summer, I started working with a client where the project sponsorship for Balanced Scorecards/Strategy Execution resides within the strategic planning function. In this instance, we started our initial discussions around how to provide a better strategic planning automation system.
I’ve been down this path before, and I’ve built and seen just how work-flow intensive and complicated the automation of the planning process can be. Furthermore, I’m convinced that the automation of the planning cycle is somewhat of a low value-add. Planning is about communication, discussion, analysis, disagreement, and hard choices. Applying a coat of technological asphalt over the process isn’t necessarily a good thing.
So, the conversation morphed into one that crossed their functional boundary into that of strategy execution –- which meant we were really talking about the emerging idea of an Office of Strategy Execution. This label hasn’t been openly applied at this client as of yet, but the planning folks are already way down the path of thinking about how to ensure execution occurs (which is clearly beyond their existing functional definition, but the realization of the gap makes it now impossible to ignore). The key is that planners want to see and ensure the results of their plans.
The realization and point I want to make in this posting is that organizations work in clockwork cycles. Appreciating the nuances of these cycles and their inter-related timing is crucial to better strategy execution, wherever it gets its start.

Recent Comments