Many people assume that a strategy is a big-picture overall direction, divorced from any specific action. But defining strategy as broad concepts, thereby leaving out action, creates a wide chasm between “strategy” and “implementation.” If you accept this chasm, most strategy work becomes wheel spinning.

A good strategy includes a set of coherent actions. They are not “implementation” details; they are the punch in the strategy. A strategy that fails to define a variety of plausible and feasible immediate actions is missing a critical component.

Many people call the guiding policy “the strategy” and stop there. This is a mistake. Strategy is about action, about doing something. The kernel of a strategy must contain action. It does not need to point to all the actions that will be taken as events unfold, but there must be enough clarity about action to bring concepts down to earth. To have punch, actions should coordinate and build upon one another, focusing organizational energy.

The idea that coordination, by itself, can be a source of advantage is a very deep principle. It is often underappreciated because people tend to think of coordination in terms of continuing mutual adjustments among agents. Strategic coordination, or coherence, is not ad hoc mutual adjustment. It is coherence imposed on a system by policy and design. More specifically, design is the engineering of fit among parts, specifying how actions and resources will be combined.

People normally think of strategy in terms of action—a strategy is what an organization does. But strategy also embodies an approach to overcoming some difficulty. Identifying the difficulties and obstacles will give you a much clearer picture of the pattern of existing and possible strategies.