Key Takeaways
Make execution part of strategy design, not a handoff after planning.
The plan is only a start. When Lawrence Hrebiniak asked AT&T executive Randy Tobias what most worried him about a new competitive strategy, Tobias named implementation, not planning. The division had to overcome inherited habits, rewards based on seniority, functional silos, and resistance to change. The episode frames the book's central claim: execution is not clerical follow-through but a long, connected management process involving more people and uncertainty than strategy formulation does.
Evidence from managers. Hrebiniak's combined surveys and executive-program research gathered responses from 443 managers involved in strategy execution. They identified poor change management, unclear accountability, weak information sharing, and conflicts with organizational power as recurring obstacles. A sound plan can still fail when the wider company cannot support it.
What's important here is the shift from judging leaders by the elegance of their plans to judging whether the organization can carry them out. This resembles systems engineering: a design is not successful until the parts work together under real operating conditions. The book also usefully resists blaming frontline employees for plans that leadership never equipped them to deliver. One caution is that manager surveys reveal perceived obstacles, not definitive causal rankings. Their value is diagnostic: they show where leaders should investigate before assuming a strategy failed because people lacked effort.
Reject vague plans: strategy must dictate capabilities, measures, and business roles.
Strategy creates requirements. A business cannot execute an unclear direction, and it cannot deliver a strategy without the capabilities that strategy demands. A low-cost position may require technology, standardized work, high volume, and cost-focused incentives. Differentiation may instead depend on product development, customer understanding, marketing, and quality. Hrebiniak's study with Charles Snow of 88 companies across four industries found stronger performance when organizational capabilities matched chosen strategies.
Align the levels. Corporate leaders must clarify what each business contributes, what resources it receives, and how its performance will be judged. A strategy review can bring corporate and business leaders together to examine market conditions, agree on roles and measures, and revise assumptions. Nucor's technology investments and performance-oriented practices supported its low-cost strategy, unlike Bethlehem Steel's slower adaptation.
This is a practical version of fit: strategy is credible only when resources, skills, and incentives make it achievable. The idea connects to capability-based theories of competition, which treat accumulated skills and routines as sources of advantage, not merely supporting details. It also exposes a common measurement trap: a corporate target can look objective while being inappropriate for a business facing different market conditions. The book's insistence on negotiated, strategy-specific measures is persuasive, though metrics should remain revisable when markets change rather than hardening into targets that reward yesterday's priorities.
Choose structure by the work: centralize scale, decentralize customer judgment.
Structure has a price. Functional structures group similar expertise and can increase efficiency through repetition, scale, and shared resources. Divisions organized around products, customers, or regions can respond more directly to local needs, but may duplicate staff and systems. Hrebiniak calls these patterns process specialization and purpose specialization. Neither is universally superior; their value depends on what the strategy requires.
Balance the two. Carrefour's centralized product decisions left local stores less able to match customer preferences, while rival Leclerc gave store managers more room to adapt. J&J's decentralized businesses encouraged initiative, but large hospital buyers wanted coordinated sales across its many units. The company had to add coordination without destroying local autonomy. Growth, market differences, technologies, and customer needs all affect where authority belongs.
The useful question is not whether centralization is good, but which decisions benefit from consistency and which need local knowledge. This echoes the principle of subsidiarity in political theory: decisions should sit at the lowest level capable of handling them, unless broader coordination adds value. The structure also shapes what information travels and who gains influence, so an organization chart is never just a diagram. A limitation is that decentralization can be mistaken for responsiveness even when local teams lack skills, data, or authority. Autonomy works only when those conditions are designed alongside it.
Match coordination to interdependence, then name one accountable owner.
Different work needs different links. Pooled interdependence describes units that operate mostly independently, such as separate sales territories. Shared procedures and occasional escalation may suffice. Sequential interdependence describes work passed from one unit to another, as in a supply chain; planning, schedules, quality, and handoffs matter. Reciprocal interdependence means people must repeatedly adjust to one another, as in new product development, where marketing, engineering, production, and customers all shape the result.
Make collaboration concrete. GE's Work-Out sessions brought people from relevant functions together to define problems, agree on actions, assign responsibilities, and follow up. Responsibility plotting and role negotiation can expose disagreements over who is responsible, accountable, consulted, or informed. In one company's stalled product pipeline, clarifying roles helped restore development work.
This framework improves on the vague instruction to collaborate by asking what kind of dependence the task actually creates. It links organizational design to the coordination research of James Thompson, while the accountability tool makes invisible assumptions discussable. The distinction also helps avoid opposite errors: leaving highly interdependent teams to fend for themselves, or burdening independent groups with needless committees. Still, assigning one accountable owner should not erase shared expertise or give a single person unrealistic control over outcomes. Clear ownership works best when decision rights, resources, and escalation paths are explicit too.
Reward the behavior strategy needs, and use feedback to revise execution.
Rewards steer effort. Most managers already want to perform; incentives guide that motivation and can also extinguish it. Measures should connect strategic aims to attainable, meaningful operating objectives. At Ford, Hrebiniak was judged on a strict pass-or-fail sales target. That encouraged him to set easy targets rather than risk missing an all-or-nothing threshold. Measures that reward only individual results can also undermine cooperation when the task depends on teams.
Controls complete the loop. Compare results with agreed objectives, investigate significant gaps, identify causes, make changes, and follow up. In a strategy review, the discussion should examine facts and assumptions, not become a ritual of blame. J.P. Morgan received warnings about risky trading practices before major losses surfaced, but did not act effectively on them. Feedback matters only when the right people can use it.
The section joins motivation with organizational learning: incentives influence what people do, while controls reveal whether those actions produce the desired results. This is close to feedback control in engineering, where a system needs usable signals and a capacity to adjust. The Ford example also shows how a seemingly precise target can provoke gaming when it ignores degrees of performance. Yet measurement is not neutral. Poorly chosen indicators can crowd out unmeasured goals, and excessive monitoring can discourage experimentation. A strong review therefore asks not only whether a metric moved, but whether it still represents the strategy's real purpose.
Break large changes into steps unless the clock truly forces simultaneity.
Size and time interact. When a major problem allows time, sequential change breaks the work into smaller steps, giving managers opportunities to test assumptions, learn, and adjust. The approach can be slow, and external events may disrupt it, but cause and effect remain easier to examine. Complex change occurs when a large problem must be addressed quickly through many simultaneous actions. That raises coordination demands and makes it harder to identify what caused success or failure.
Speed can multiply risk. United and Continental combined reservation systems, websites, and frequent-flyer programs in a rapid transition that produced service problems and confused employees. A deliberate sequence might have reduced the number of moving parts at once. If simultaneous change is unavoidable, Hrebiniak argues that leaders must set priorities and reduce other performance demands so teams can focus.
The argument is not that slow change is always wise, but that speed has an information cost. When many interventions happen at once, managers lose the ability to learn which action mattered, a problem familiar in both organizational research and clinical evaluation. Sequential change preserves clearer tests, though it can also give competitors time to respond or let internal momentum fade. The practical choice is therefore contextual: urgency, reversibility, and the cost of delay should determine pace. Leaders should treat a fast rollout as a high-risk operating condition, not as proof of decisiveness.
Change culture through daily behavior, not motivational speeches about values.
Culture lives in routines. Shared norms influence decisions, risk-taking, cooperation, and how people treat mistakes. But culture also changes when behavior changes. Rather than asking people to adopt new values by declaration, leaders can alter hiring, incentives, controls, responsibilities, and organizational structure so that different behavior becomes possible and worthwhile.
Make the case and communicate it. Hrebiniak recommends explaining why change is necessary, sharing the evidence, involving affected people, and addressing resistance honestly. Preserve useful parts of the old culture where possible. Team-building events alone rarely undo everyday rewards and reporting relationships. J&J's Credo illustrates how a shared statement can matter when it is used to guide actual decisions, not merely displayed. Cultural change takes time; excessive speed can increase uncertainty and obscure what is working.
This behavioral approach gives leaders levers they can actually pull. It also fits social learning: people infer what an organization values from repeated consequences, especially what leaders reward and tolerate. The advice to preserve useful cultural elements is important because change is not a blank-slate exercise. However, behavior-first change can become coercive if leaders redesign incentives without listening to employees or acknowledging losses. Communication and participation are not public-relations accessories; they help reveal local knowledge and make change legitimate. Culture shifts most credibly when leaders' own conduct matches the new expectations.
Build influence by solving scarce problems and proving measurable value.
Power follows dependence. An individual or unit gains influence when others need resources, expertise, or information that cannot easily be obtained elsewhere. Strategy and structure create these dependencies, while resource allocations can strengthen them. To understand an organization's power map, identify who controls essential inputs, who reduces uncertainty, and whether alternative sources exist.
Make the case in results. A vice president of human resources initially struggled to secure funding for executive education by describing broad benefits such as loyalty and better-trained managers. She reframed the proposal around high turnover, estimated its costs, and connected training to reducing those costs. The revised plan was approved. Forming coalitions with influential colleagues can also help, but durable influence comes from contributions others can see. Power has a downside: established leaders may protect their position after the strategy that made them powerful has stopped working.
This account makes organizational politics more analyzable without pretending it disappears. Mapping dependencies can explain why a formally sound proposal stalls, and the revised HR case shows how a social benefit can become more persuasive when connected to observable organizational costs. This resembles resource-dependence theory, where control over scarce inputs shapes influence. There is a productive tension: measurable value can help good ideas win, but easy-to-measure value may crowd out important work whose effects are diffuse or delayed. Leaders should translate benefits into evidence without claiming that every human outcome can be reduced to a financial figure.
Use execution discipline to tame mergers, global expansion, and complex projects.
Applications share a logic. Mergers require strategic justification, careful financial and cultural due diligence, deliberate integration, and agreed measures of success. The book cites research reviews in which roughly 70 percent of deals missed expectations, while warning that rapid integration can add risk. Global strategies likewise require different designs: basic exporting, locally adapted operations, or coordinated sharing of capabilities across countries. The last form depends on integration, global managers, and often matrix structures or alliances.
Adapt the method to the setting. Service organizations face many of the same execution demands as manufacturers. Professional settings add friction because experts may resist administrative control and dispute how performance should be measured. Project management can turn a strategy into milestones and responsibilities, but should focus on a few priorities and remain a tool, not a bureaucracy. In highly interdependent professional organizations, key stakeholders must help shape decisions.
The applications show the model's range without requiring an entirely different theory for every industry. Their common thread is that strategic intent must be translated into roles, coordination, incentives, and feedback that fit the context. The M&A record underscores the cost of treating a transaction's announcement as evidence of value creation. Still, broad failure percentages can obscure differences among deal types, time horizons, and success measures. Likewise, project plans can make work visible while missing informal expertise. The strongest application combines formal milestones with local judgment, cultural understanding, and honest measurement.
Analysis
Making Strategy Work is a practice-oriented management argument organized around a recurring tension: organizations can formulate a strategy more easily than they can coordinate the people, structures, incentives, and adaptations required to deliver it. Its distinctive contribution is not one isolated tool, but an integrated view of execution. Strategy shapes required capabilities and organizational design; design creates patterns of dependence; dependence determines coordination needs; incentives and controls influence behavior; and power, culture, and change conditions shape every stage.
The book's examples make the argument tangible. AT&T's new division faced inherited culture and reward systems that its business-level plan could not simply wish away. Carrefour's centralized decisions contrasted with Leclerc's local responsiveness. GE's Work-Out process made cross-functional problem solving and follow-through visible. The failed or troubled merger cases show that strategic logic alone does not create operational integration. These stories help managers see execution as a system rather than a handoff.
The empirical base includes surveys and discussions with 443 managers, which gives the book a useful practitioner perspective. Its evidence is strongest as a map of recurring perceived obstacles, not as a controlled demonstration that one intervention causes superior performance. Many examples are tied to the business environment of the period, and failure rates for mergers depend on how success and time horizons are defined.
The model's main strength is its insistence that decisions interact. Its main risk is that a logical sequence can appear more linear than organizational life: political negotiation, learning, and external shocks often reshape strategy while implementation is underway. The book does recognize adaptation and contextual forces, but managers should use its sequence as a diagnostic guide, not a rigid recipe. Its lasting lesson is practical: plans become credible only when the organization can translate them into coordinated behavior, detect when assumptions fail, and change course without losing accountability.
Review Summary
The reviews for Making Strategy Work are mixed, with ratings ranging from 2 to 5 stars. Readers appreciate the book's insights on strategy implementation and execution, particularly for new managers. Some found value in specific chapters and diagrams. However, many critics note the book's repetitiveness and lack of novel ideas. While some readers found it educational and comprehensive, others felt it lacked depth in examples and new concepts. The book's emphasis on execution alongside strategy-making is seen as its primary strength.
Glossary
Process specialization
Grouping by shared workAn organizational design that groups people around similar functions, skills, or processes, such as engineering, manufacturing, or marketing. It can support expertise, repeated work, consistency, and economies of scale. Its costs include coordination across functions and the risk that specialists focus on their own tasks while losing sight of customers or overall results.
Purpose specialization
Grouping by intended outputAn organizational design that groups work around an output or focus, such as a product, customer type, or geographic region. Divisions and strategic business units are common forms. This design can sharpen market attention and responsiveness, but may duplicate resources, increase costs, or make units too autonomous from the wider organization.
Pooled interdependence
Separate units share outcomesA low level of task dependence in which units work largely independently, but their results contribute to a shared organizational outcome. Separate sales territories are an example. Common procedures and occasional hierarchical decisions may coordinate the work; extensive day-to-day lateral interaction is usually unnecessary.
Sequential interdependence
Work passes between unitsA pattern of dependence in which one unit's output becomes another unit's input. A supplier passing materials to a production division is an example. Because a delay or quality problem in one stage can affect the next, coordination must manage schedules, handoffs, information, and the terms of internal exchanges.
Reciprocal interdependence
Units adjust to one anotherA high level of task dependence in which several people or units repeatedly affect one another's work. New product development often has this pattern because marketing, engineering, production, and customers all influence the viable solution. It requires sustained communication, mutual adjustment, shared commitment, and clear resolution of disagreement.
Absorptive capacity
Ability to use new knowledgeAn organization's ability to recognize the value of outside knowledge, understand it, and apply it to useful ends. It depends partly on relevant knowledge and expertise already present in the organization. Without that foundation, a company may fail to evaluate or adopt a new technology, even when the information is available.
Strategy review
A planning and learning forumA recurring discussion that connects corporate and business strategy with execution and performance. Participants clarify roles, resources, and measures, compare actual results with agreed objectives, investigate causes of important gaps, and decide whether plans or execution methods need adjustment. It is intended to support communication and learning, not merely produce reports or assign blame.
Complex change
Many changes made simultaneouslyA change situation in which a large strategic problem must be addressed quickly through many concurrent actions. This can accelerate response, but creates heavy coordination and control demands. When results disappoint, the simultaneous changes make cause-and-effect analysis difficult, limiting organizational learning and increasing the risk of overloaded or unfair accountability.
Responsibility plotting and role negotiation
Clarifying execution rolesA facilitated method for identifying who is responsible, accountable, consulted, or informed for important tasks and decisions. Participants compare their individual views, discuss disagreements, and work toward a shared assignment of roles. The process is intended to uncover hidden conflicts and prevent responsibility from becoming so diffuse that no one owns the outcome.
FAQ
What's Making Strategy Work about?
- Focus on Execution: The book emphasizes the critical importance of executing strategies effectively, arguing that execution is often more challenging than strategy formulation.
- Integrated Approach: Lawrence G. Hrebiniak presents a model that connects factors like organizational structure, culture, and leadership to enhance execution.
- Real-World Applications: It uses empirical data and examples to show how effective execution can lead to competitive advantage and improved performance.
Why should I read Making Strategy Work?
- Practical Insights: The book offers actionable insights and frameworks that managers can apply to improve strategy execution.
- Addressing Challenges: It tackles common obstacles such as poor strategy formulation and inadequate communication, providing solutions.
- Comprehensive Coverage: Topics like change management, organizational structure, and culture are covered, making it valuable for leaders at all levels.
What are the key takeaways of Making Strategy Work?
- Execution is Key: Effective execution is crucial for achieving strategic goals, as highlighted by the book.
- Interdependence of Factors: Strategy, structure, and culture must align for successful execution outcomes.
- Need for Clear Strategy: A clear and focused strategy is essential, as poor strategy leads to poor execution.
What is the model of strategy execution presented in Making Strategy Work?
- Logical Framework: The model outlines key decisions and actions necessary for effective strategy execution.
- Components of the Model: It includes corporate strategy, business strategy, organizational structure, integration, incentives, and controls.
- Feedback Mechanisms: Feedback loops are incorporated, indicating that execution is a dynamic process requiring adaptation.
How does organizational structure impact strategy execution according to Making Strategy Work?
- Structure and Strategy Relationship: Organizational structure must align with strategy for effective execution.
- Centralization vs. Decentralization: The right structure depends on the strategic needs of the organization.
- Coordination Challenges: Clear responsibilities and effective communication channels are essential to overcome coordination issues.
What role does culture play in strategy execution in Making Strategy Work?
- Culture's Influence: Culture shapes how employees respond to strategic initiatives and change.
- Resistance to Change: Cultural factors can lead to resistance, making it crucial to manage cultural change effectively.
- Creating an Execution Culture: Organizations must foster a culture of achievement and accountability to enhance execution success.
How can leaders improve strategy execution according to Making Strategy Work?
- Execution-Biased Leadership: Leaders must focus on motivating teams and ensuring alignment with strategic goals.
- Creating a Supportive Climate: Encouraging ownership and accountability among employees is vital for successful execution.
- Communication and Engagement: Effective communication about the strategy enhances employee engagement and commitment.
What are the best quotes from Making Strategy Work and what do they mean?
- "Execution is a key to success.": Emphasizes that without effective execution, even the best strategies will fail.
- "Bad strategy begets poor execution.": Highlights the importance of sound strategy formulation.
- "Culture is important for execution.": Underscores the role of organizational culture in shaping employee behavior.
How does Making Strategy Work address the execution of global strategies?
- Global Strategy Demands: Emphasizes the need for coordination across different markets and regions.
- Matrix Structure: Suggests a matrix structure for global organizations to focus on product lines and geographical needs.
- Integration and Knowledge Sharing: Effective integration and knowledge sharing are crucial for maintaining competitive advantage.
What specific methods does Making Strategy Work recommend for effective execution?
- Define Power Bases: Managers should map out key dependency relationships affecting power within their organizations.
- Project Management Approach: Emphasizes clear objectives, timelines, and performance metrics for guiding projects.
- Cultural Integration: Advises on communication programs to ensure smooth transitions during mergers and acquisitions.
How does Making Strategy Work define the role of leadership in strategy execution?
- Critical Leadership Role: Leaders must actively engage in defining projects and ensuring alignment with goals.
- Support for Change: Effective leaders communicate and advocate for necessary changes to overcome resistance.
- Creating a Culture of Execution: Leaders should foster a culture that prioritizes execution, setting clear expectations and encouraging accountability.
What are the potential pitfalls of project management as discussed in Making Strategy Work?
- Excessive Formality: Overly formal processes can become bureaucratic and hinder execution.
- Means-Ends Inversion: Project management should not become an end in itself, but a means to achieve strategic goals.
- Conflict Between Routine and Autonomy: Tension between established routines and professional autonomy can impede decision-making.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.