Crafting And Executing Strategy Thompson

A Framework That Actually Holds Up When Things Go Wrong

I spent the better part of three years learning strategy the hard way — watching carefully crafted plans fall apart because someone in the middle forgot to execute, or the execution outpaced the strategy entirely. Most frameworks you find in textbooks look clean on paper and fall apart the moment you try to use them. The approach from Thompson, Gamble, and Strickland is different because it forces you to tie every strategic move to measurable outcomes before you commit resources. At its center, the method breaks down into five interrelated questions you need to answer in sequence. First, where are we now? This means assessing the current strategic position — market share, competitive advantages, internal capabilities, and the external environment. Second, where do we want to go? This is the vision and goal-setting phase, and I have seen too many companies skip straight to action without clearly defining what success looks like. Third, how do we get there? This is strategy formulation — choosing the competitive approach, deciding which markets to compete in, and structuring the organization to support that choice. Fourth, executing the strategy. This is where most organizations fail, and fifth, monitoring and evaluating. You need feedback loops that actually force course corrections rather than just quarterly reviews that get ignored. The key insight that separates this from generic strategic planning advice is the emphasis on the connection between each step. You cannot formulate a solid strategy if your diagnostic of the current situation is sloppy. You cannot execute well if your goals are vague. And you cannot evaluate effectively if you did not define clear metrics at the beginning. I learned this after wasting about four months on a market entry plan that looked good on slide decks but had no operational roadmap attached to it. The team knew where we wanted to go, but nobody could tell me what the first three concrete steps were or who owned each one.

How the Process Actually Works in Practice

Start with the external and internal analysis. This is not just collecting data for the sake of data collection. You need to identify which external factors actually matter to your strategic position and which internal capabilities are genuinely competitive advantages versus table stakes. Use tools like Porter's Five Forces, PESTEL analysis, and value chain analysis, but do not treat them as checklists. Pick the ones that actually illuminate your situation and discard the rest. I once watched a senior strategist spend two weeks building a fifty-slide PESTEL deck that nobody referenced again after the initial presentation. The information was accurate but completely disconnected from the strategic decisions that needed to be made. Then move to goal setting. Write down specific, measurable objectives for each time horizon — short-term, mid-term, and long-term. Vague goals like "improve market position" or "become more innovative" are useless because they give you nothing to measure and therefore nothing to manage. I prefer writing goals in a format that specifies the metric, the target value, and the timeline. "Increase market share in the segment from eight percent to twelve percent within eighteen months by capturing two competitor accounts" gives you a concrete target and a measurable path to track progress. Strategy formulation comes next. This is where you make the hard choices about competitive approach. Will you compete on cost leadership, differentiation, or focus? These are not mutually exclusive in all cases, but pretending you can be everything to everyone is a reliable path to mediocrity. I worked on a project where a mid-sized manufacturer tried to simultaneously pursue low cost and premium differentiation across the same product line. The result was a confused brand identity, operational complexity that drove up costs, and a loss of market position to competitors who had chosen a clearer direction. The Thompson framework makes this trade-off explicit rather than letting it develop implicitly through conflicting initiatives.

The Execution Problem Most People Underestimate

Execution is where strategies die. Not because the strategy was bad but because the organization failed to translate strategic intent into daily operations. This requires several things happening at once. You need the right organizational structure, compatible processes and systems, the right culture, and people with the right skills in the right positions. If any of these are misaligned, execution will be slower, more expensive, or outright unsuccessful. One practical technique I found useful was mapping every strategic objective to specific operational metrics at the team level. Instead of saying "improve customer satisfaction" as a company-wide goal, break it down into what each department needs to measure and improve. Sales tracks response time. Product tracks defect rates. Support tracks resolution time. Each of these feeds into the aggregate customer satisfaction metric, and each has a clear owner. This creates accountability at every level rather than leaving execution as an abstract responsibility of middle management. Another critical factor is resource allocation. Strategy execution requires money, people, and time. Too often I see organizations announce a new strategic direction without shifting resources to match it. They expect teams to do new things with the same tools, budgets, and headcount they had before. This almost never works. If you are pursuing a differentiation strategy, you may need to invest more in R&D and quality control. If you are pursuing cost leadership, you need to restructure for efficiency, which often means different people and different processes. Aligning the budget with the strategy is not optional — it is the primary signal that tells the organization which priorities are real versus which are aspirational.

Monitoring and the Danger of Silent Drift

The final component, monitoring and evaluation, is where many strategies quietly fail. Organizations set up dashboards and review meetings, but the feedback never leads to action. I encountered this specifically when working with a company that had excellent strategic metrics tracking but no clear trigger points for intervention. Their market share was declining steadily over six months, but because the monthly reports showed incremental changes rather than sudden crashes, nobody felt urgency to respond. By the time the board decided something had to change, they had lost a significant portion of their customer base. The workaround I implemented was establishing explicit trigger thresholds. Instead of reviewing trends passively, we defined specific points at which action was mandatory. If market share dropped below ten percent, a formal strategic review was triggered within one week. If customer acquisition cost rose above a certain threshold, the marketing budget allocation was automatically reassessed. This removed the ambiguity and the tendency to hope conditions would improve on their own. The human tendency is to delay difficult decisions when numbers are moving gradually rather than crashing. Thresholds force the decision earlier when corrective action is still effective.

Where the Thompson Framework Falls Short

No strategic framework is universal. The Crafting And Executing Strategy Thompson approach assumes a relatively stable environment where you can analyze, plan, and then execute with reasonable confidence. In highly volatile markets — think emerging technology sectors or industries disrupted by regulatory changes — the linear sequential nature of the framework can become a liability. Waiting to complete a full strategic analysis before acting can mean missing the window entirely. In those contexts, I recommend supplementing the framework with rapid experimentation cycles and iterative strategy development. Test assumptions quickly, gather real market feedback, and adjust rather than committing to a long-term plan based on predictions. Another limitation is the framework's heavy reliance on analytical rigor. Organizations with weak data infrastructure or poor information systems will struggle to implement it properly. The quality of your strategy is only as good as the quality of your analysis, and if you cannot reliably measure your market position, customer behavior, or competitive dynamics, you are making strategic decisions in the dark. In these situations, investing in basic market intelligence capabilities should precede attempts at sophisticated strategic planning. The framework also tends to underestimate the role of organizational politics and informal power structures. Strategy execution requires coordination across departments, and departmental interests do not always align with strategic objectives. I have seen perfectly sound strategies blocked by middle managers who perceived a threat to their budget or influence. No amount of analytical rigor addresses this directly. You need change management, stakeholder alignment, and sometimes political navigation skills that the framework does not explicitly cover.

Practical Steps to Get Started

If you are applying this approach for the first time, start small. Do not attempt a comprehensive strategic planning exercise across the entire organization. Pick one business unit or product line and run through the full five-step process. Document each step, identify where friction occurs, and refine your approach before scaling. This typically takes four to six weeks for a focused initiative and gives you a realistic template for broader application. Ensure you have senior leadership commitment from the beginning. Strategy is not a planning department exercise. It requires visible sponsorship from top management, especially during the execution phase when tough resource allocation decisions need to be made. Without leadership backing, strategic initiatives tend to lose priority when operational pressures mount, which is most of the time. Build the monitoring system early rather than retroactively. Define your key performance indicators during the goal-setting phase, set up the tracking infrastructure, and establish review rhythms before you begin execution. This is easier when you design it upfront than when you realize six months into implementation that you have no way to measure whether your strategy is working. A well-designed monitoring system with clear triggers can catch problems two or three months earlier than conventional quarterly reviews, which is often the difference between a manageable correction and a strategic failure.

The framework from Thompson and colleagues is not a magic solution. It is a structured way of thinking that forces discipline at each stage of the strategic process. The organizations that benefit most are the ones that apply it rigorously rather than treating it as a paperwork exercise. The gap between strategy and execution is where most competitive advantage is lost, and this framework is designed specifically to close that gap by making every step consequential and connected to the next.