Key Takeaways
Use autonomy and cooperation to turn rising complexity into advantage, not bureaucracy.
Complexity is the challenge. Companies now face roughly 25 to 40 performance demands, often contradictory: for example, lower prices alongside higher quality. The authors report that business complexity grew sixfold from 1955 to 2010. The danger is not complexity itself, but complicatedness: the layers of procedures, scorecards, committees, and approvals added to control it. Their research found that complicatedness increased dramatically, while some employees in the most complicated firms spent 40 to 80 percent of their time on wasted work.
Trust judgment and connection. The book challenges both rule-heavy management, which tries to prescribe behavior, and feel-good initiatives, which try to change mindsets. Its alternative, smart simplicity, uses employee judgment while shaping work so people benefit from cooperating. Less bureaucracy is a by-product, not the main goal.
The useful distinction is between a difficult environment and the organizational friction layered on top of it. Complex systems rarely yield to exhaustive instructions because their exceptions cannot all be anticipated; people closest to the work often hold the most relevant information. Still, discretion is not automatically wise. In safety-critical or highly regulated work, explicit procedures protect people from preventable harm. The practical test is whether a rule manages a real risk or merely compensates for weak cooperation. Simplicity here means fewer obstacles to good judgment, not fewer safeguards by default.
Diagnose the behavior people actually choose before prescribing another process.
Start with the work. A work context is the mix of goals, resources, and constraints that helps explain what people do. Managers should observe actions and interactions, not just compare job descriptions with missed targets. InterLodge, a hotel company, first blamed receptionists for weak room sales and poor guest service. Training, incentives, and clearer procedures did not fix the problem.
Find the hidden problem. Receptionists were trying to avoid angry guests when rooms had maintenance faults. They kept rooms empty as a backup, offered discounts, or tried repairs themselves, which hurt occupancy, prices, and service. Housekeeping and maintenance were not cooperating well, leaving front-desk staff to absorb the consequences. These behaviors were understandable responses to their situation, not proof of a defective attitude. Changing the context proved more useful than another round of training.
This method counters a familiar attribution error: explaining a frustrating action by personality while overlooking the incentives and obstacles around it. A behavior can be locally sensible and collectively damaging, as the hotel staff's reserve rooms illustrate. That does not make every choice reasonable or beyond accountability. It makes the choice evidence. The diagnostic question becomes what problem the action solves for the person, and what costs it pushes onto others. This shift can also make change less accusatory, but only if employees are genuinely involved in describing their work rather than treated as objects of diagnosis.
Make frontline integrators powerful enough to make cooperation matter.
Give connectors real leverage. An integrator is a person or work unit that fosters cooperation for the organization's benefit. Unlike a coordinator who checks compatibility after separate teams have acted, an integrator is involved in the work and has both an interest in cooperation and enough influence to encourage it.
Put power near the problem. At InterLodge, receptionists had a strong reason to want better cooperation with housekeeping and maintenance, but little influence over those teams. The company gave receptionists a meaningful voice in evaluating their coworkers. Housekeepers began reporting room faults, and maintenance responded more readily to requests. Guest satisfaction, occupancy, and room rates improved; the hotel business unit's gross margin rose 20 percent in 18 months, and receptionist turnover fell sixfold. No new customer-centricity department was needed.
The case shows why customer focus is often an interaction design problem, not a slogan or a new office. Frontline staff heard customer complaints directly, so their feedback could reveal failures invisible to isolated back-office targets. The broader principle resembles distributed control: decision influence sits closer to the information needed to act. But giving one group an evaluative role can also create favoritism or retaliation. Credible integrators need clear scope, multiple sources of evidence, and a way to contest unfair judgments. Otherwise, the mechanism may replace one imbalance of power with another.
Create new sources of power instead of moving the same authority around.
Power is relational. In this book, power means the ability to affect something that matters to another person. A title or formal authority does not guarantee it. When cooperation requires people to depend on one another, each needs enough influence to take that risk.
Add a useful stake. GrandeMart had centralized many decisions, leaving store managers with responsibility but little leverage over employees. To support local promotions without giving up central purchasing and consistency, the company let managers choose which employees would help at checkout when lines grew. That decision mattered to employees and gave managers a practical way to mobilize teams. Cooperation around local events increased, and sales and customer traffic rose by multiple percentage points in stores using the approach. The intervention created power rather than simply transferring an existing decision right.
This positive-sum view is a helpful alternative to treating organizational authority as a fixed pie. A small decision can create leverage when it matters to the people whose cooperation is needed. In economic terms, it changes the terms of exchange without dismantling every centralized capability. The design question is whether the new stake supports the work or merely gives a manager a personal favor to distribute. Transparent criteria and recourse matter, particularly when the decision affects schedules, advancement, or other consequential opportunities.
Design roles so success depends on helping others deliver.
Make interdependence visible. Rich objectives combine three kinds of responsibility: a collective output, an individual's own contribution, and an overlap contribution that makes someone else's work more effective. The overlap is often the part that conventional metrics miss, such as making a handoff useful to the next person.
Build reciprocity into the work. At Industronal, category strategists developed purchasing strategies, while regional buying teams placed orders for internal customers. The organization needed to cut purchasing costs by 20 percent without harming quality or delivery. Strategists were responsible for practical guidance, and buyers for using the strategies effectively. The company also made purchasing harder to bypass, reduced some internal customers' budgets, and created recurring meetings where customers and both purchasing groups reviewed actual orders. Multiple peer networks exposed different parts of the work to scrutiny, a design the authors call multiplexity.
Rich objectives recognize that collaboration creates value through complements: one person's contribution can raise the effectiveness of another's. This is why assigning every result to a single owner can distort work that is genuinely shared. The approach also shows that objectives alone are weak unless the surrounding work makes interdependence consequential. Resource cuts can help expose that dependence, but indiscriminate cuts can remove buffers needed for resilience. Managers should distinguish slack that enables avoidance from slack that protects the organization against uncertainty, then test changes before making them permanent.
Bring tomorrow's consequences close enough to shape decisions today.
Shorten the distance to consequences. The shadow of the future is the influence that expected future outcomes have on choices made now. It can be extended by increasing the frequency of feedback, shortening projects, tying career prospects to others' success, or letting people experience the work their decisions create for someone else.
Let designers meet the results. MotorFleet struggled to make vehicles easier to repair while also controlling cost and preserving compact designs. A new reparability function, process, and set of measures had little impact. Instead, some engineers were assigned to work in after-sales garages and manage warranty costs for models they had designed. Faced with the consequences of design choices, engineers began working more closely across specialties and with service staff. The company matched a competitor's longer warranty, removed many interface roles, and reported a 20 percent productivity increase within three years.
Feedback works best when it is timely, specific, and connected to a decision-maker's ability to act. The garage assignment made a delayed cost concrete without requiring a giant new measurement system. This resembles experiential learning: consequences become information rather than an abstract report. Yet time horizons can be shortened too aggressively. A quarterly review may improve responsiveness while encouraging neglect of investments whose payoff takes years. The relevant goal is not simply faster feedback, but a feedback loop that matches the real consequences of the work and gives people enough discretion to improve them.
Judge whether people helped solve the problem, not who first caused it.
Change the accountability question. RapidTrain's on-time arrivals had fallen below 80 percent. Its investigations identified the technical cause of each delay and blamed the responsible unit. Staff then had reason to conceal problems and avoid asking for help, since doing so could make their unit look guilty.
Reward useful cooperation. Managers changed evaluations so that, once a unit disclosed a problem, other units could be held responsible for failing to help resolve it. Weekly reviews focused on how teams responded, not just where a fault began. Repeated failures to improve still mattered, but technical causation alone no longer determined blame. On major lines, punctuality reached 95 percent in four months, without new equipment or additional teams. The company also stopped spending thousands of hours on delay investigations.
This approach separates learning from scapegoating. A system can be technically accurate about where a fault began and still fail to produce the response that prevents a delay from spreading. Rewarding disclosure and assistance can make operational problems visible sooner, while preserving accountability for repeated, preventable failures. The distinction depends on fair conditions: teams must have a realistic ability to help, and managers must not punish employees for exposing risks they cannot control. Without those protections, a cooperation-focused evaluation can become another opaque instrument of blame.
Start from pain points, redesign context, then raise the target.
Follow the evidence. The book's practical sequence begins with a concrete problem, such as delays, turnover, or poor service. Identify the roles whose work affects it, describe what cooperation would look like, and determine what currently makes cooperation difficult. Look for goals, resources, constraints, and power relationships rather than assuming a missing process or a bad mindset is the root cause.
Make change testable. Adjust the smallest set of organizational levers that changes the work context: decision rights, evaluation, career paths, available resources, or feedback. Then set more ambitious performance goals based on the improvement that cooperation can plausibly deliver. This is not a rejection of structure, metrics, or management. It is a warning against choosing those tools before understanding how people will use them. Direct observation is essential, but the aim is to improve judgment, not supervise every move.
The sequence turns organizational change into a set of testable hypotheses: if this obstacle is removed, these people should be able to cooperate in this specific way, with this expected result. That is more informative than launching a broad transformation and hoping the culture follows. The cases make the logic vivid, but they are largely organizational examples rather than controlled comparisons, so their outcomes do not establish that every intervention will generalize. A careful manager can preserve the method's strength by piloting changes, checking for unintended effects, and revising the diagnosis when behavior does not shift.
Analysis
The book's core contribution is a change in the unit of management. Instead of treating the organization as a chart of roles and systems, it treats performance as the pattern produced by people adjusting to one another. That makes power, dependence, and the cost of cooperation central design questions. The six rules function less as a checklist than as a theory of context: understand the work, give some actors leverage to integrate it, and make the consequences of cooperation visible enough to shape choices.
This view has strong affinities with bounded rationality and organizational sociology. People have incomplete information and limited control, so they adapt to the resources and constraints they encounter. A seemingly irrational action may be a sensible defense against a locally dangerous outcome. The framework usefully shifts attention from stated intentions to observable behavior, while emphasizing that individual optimization can produce poor collective results.
Its most challenging proposition is that cooperation should become individually useful. That is a powerful design ambition, but not every worthwhile act can be aligned with immediate personal benefit. Public-service obligations, professional ethics, and care for vulnerable people may require action without a convenient reciprocal payoff. Nor is the organization a neutral arena: managers decide whose interests count, who bears adjustment costs, and what outcomes are rewarded. The analysis therefore needs explicit attention to fairness, safety, and voice, not just effectiveness.
The cases show plausible mechanisms and striking outcomes, but they do not by themselves prove that the mechanisms caused every reported improvement or will travel across contexts. The strongest practical reading is experimental: diagnose locally, make a small change in power or feedback, observe behavior, and revise. The title's simplicity lies in the number of design principles, not in the difficulty of applying them. Good use requires more attention to real work, not less management.
Review Summary
Six Simple Rules receives mixed reviews, with an average rating of 3.93/5. Positive reviews praise its insightful management theory, emphasizing simplicity and cooperation. Critics find the language overcomplicated and some ideas derivative. Many readers appreciate the practical examples and thought-provoking concepts, particularly the focus on understanding employees' work context and encouraging cooperation. Some reviewers feel the book could have been condensed into an article, while others consider it a must-read for managers. The six rules are generally seen as useful, though their implementation may require organizational change.
People Also Read
Glossary
Smart simplicity
Complexity managed through cooperationThe authors' approach to handling complex performance demands without adding layers of bureaucracy. It relies on people's judgment and autonomy, while changing the work context so that cooperation is useful to the individuals involved. Its aim is better collective performance; reduced complication is a consequence, not the primary objective.
Complicatedness
Organizational friction and overheadThe internal burden created when organizations respond to complexity with more procedures, reporting layers, committees, interfaces, scorecards, and approvals. The book distinguishes complicatedness from external business complexity. The former consumes time and attention, can obstruct cooperation, and may leave employees working harder on coordination and rework rather than on activities that add value.
Work context
Goals, resources, and constraintsThe conditions that shape people's actions at work. It includes the problems and stakes they are trying to address, the resources they can use, and the constraints they seek to avoid or manage. Organizational rules and systems influence behavior indirectly by changing this context; their effects depend on how people use them.
Adjustment costs
Personal costs of cooperationThe professional, emotional, reputational, or financial costs people bear when they adapt their preferred way of working to meet others' needs. Cooperation can improve the collective result while making individuals give something up. When one group avoids that cost, another group, a customer, or the organization may be forced to bear it instead.
Integrator
A cooperation-enabling actorAn individual or work unit that helps people cooperate in ways that benefit the organization. An effective integrator has both an interest in cooperation and enough power to influence others. Unlike a dedicated coordinator, an integrator acts within existing work and is involved where information and decisions are generated.
Rich objectives
Objectives linking interdependent contributionsA way to define responsibilities around work that depends on multiple people. Rich objectives combine collective output goals, individual contributions, and overlap contributions that improve the effectiveness of others. The overlap component makes shared work visible even when individual contributions cannot be measured precisely.
Multiplexity
Multiple views of shared workA design in which people participate in several complementary networks of interaction, each examining the same work from a different perspective. At Industronal, purchasing activity was reviewed by customers and purchasing groups, and strategists and buyers also met with their respective peers. Together, these interactions exposed multiple performance requirements without relying only on centralized rules.
Shadow of the future
Future outcomes shaping current choicesA game-theory concept used for the influence that expected future consequences have on present behavior. Extending it means making outcomes arrive sooner, recur more often, or become personally relevant to those making decisions. Feedback, shorter projects, career conditions, and direct exposure to downstream work can all connect today's choices to later results.
Six Simple Rules
A framework for cooperative performanceThe book's six-part management framework for dealing with complexity through behavior and work context. It combines understanding actual work, strengthening integrators, creating useful sources of power, increasing reciprocity, bringing future consequences closer, and evaluating cooperation. The rules are intended to work as a connected set, not as a universal procedural checklist.
FAQ
What's "Six Simple Rules: How to Manage Complexity without Getting Complicated" about?
- Overview of the book: The book, authored by Yves Morieux and Peter Tollman, explores how organizations can manage increasing complexity without becoming overly complicated. It introduces six simple rules to help managers foster cooperation and autonomy within their teams.
- Purpose of the book: The authors aim to provide a framework for organizations to create value and achieve competitive advantage by leveraging complexity rather than being overwhelmed by it.
- Focus on simplicity: The book emphasizes the importance of simplifying management practices to enhance productivity and employee engagement, moving away from traditional hard and soft management approaches.
Why should I read "Six Simple Rules: How to Manage Complexity without Getting Complicated"?
- Practical solutions: The book offers actionable strategies for managers to address complexity in their organizations, making it a valuable resource for leaders seeking to improve performance.
- Innovative approach: It challenges conventional management wisdom, providing fresh insights into how organizations can thrive in a complex business environment.
- Real-world examples: The authors use case studies from various industries to illustrate the application of the six simple rules, making the concepts relatable and easy to understand.
What are the key takeaways of "Six Simple Rules: How to Manage Complexity without Getting Complicated"?
- Six simple rules: The book outlines six rules that help manage complexity: understanding what people do, reinforcing integrators, increasing the total quantity of power, increasing reciprocity, extending the shadow of the future, and rewarding those who cooperate.
- Focus on cooperation: The rules emphasize the importance of fostering cooperation and autonomy among employees to improve organizational performance.
- Avoiding complicatedness: The authors argue that traditional management practices often lead to unnecessary complexity, and the book provides strategies to simplify processes and enhance productivity.
What are the six simple rules introduced by Yves Morieux and Peter Tollman?
- Understand what your people do: This rule emphasizes the importance of managers truly understanding the actions and motivations of their employees to improve performance.
- Reinforce integrators: It involves empowering individuals or units that can foster cooperation across the organization, replacing complicated structures with effective collaboration.
- Increase the total quantity of power: The authors suggest creating new sources of power within the organization to encourage cooperation and address complexity.
How does "Six Simple Rules" define and address organizational complicatedness?
- Definition of complicatedness: Complicatedness refers to the proliferation of cumbersome organizational mechanisms—structures, procedures, rules, and roles—that hinder a company's ability to leverage complexity for competitive advantage.
- Impact on performance: The book argues that complicatedness destroys productivity and employee engagement, leading to stagnant performance and dissatisfaction.
- Solution through simplicity: By applying the six simple rules, organizations can eliminate complicatedness, improve performance, and enhance employee satisfaction.
What is the "smart simplicity" approach in "Six Simple Rules"?
- Concept of smart simplicity: Smart simplicity is the approach introduced by the authors to manage complexity by leveraging people's intelligence and judgment rather than relying on rigid structures and processes.
- Combination of autonomy and cooperation: The approach emphasizes the need for both autonomy and cooperation among employees to effectively handle complex challenges.
- Practical application: The six simple rules provide a framework for implementing smart simplicity in organizations, leading to improved performance and engagement.
How do Yves Morieux and Peter Tollman suggest increasing reciprocity in organizations?
- Rich objectives: The authors propose designing rich objectives that include collective output objectives, individual input objectives, and overlap objectives to increase reciprocity.
- Eliminate internal monopolies: By making roles contestable and substitutable, organizations can break down monopolies that hinder cooperation.
- Reduce resources: Limiting resources can compel individuals to cooperate, as they become more interdependent and reliant on each other to achieve goals.
What role does power play in "Six Simple Rules," and how can it be increased?
- Understanding power: Power is defined as the ability to make a difference on issues that matter to others, and it is crucial for fostering cooperation in complex environments.
- Creating new power sources: The authors suggest creating new stakes that matter to individuals and relate to organizational performance to increase the total quantity of power.
- Positive-sum game: By increasing power, organizations can encourage more cooperation and innovation, leading to better performance and adaptability.
How does "Six Simple Rules" address the concept of strategic alignment?
- Critique of strategic alignment: The book argues that traditional strategic alignment often leads to complicatedness, as it adds layers of structure and processes that hinder performance.
- Alternative approach: Instead of aligning structures and processes, the authors recommend using feedback loops to connect actions with their consequences, fostering cooperation and adaptability.
- Avoiding the alignment trap: By focusing on cooperation and direct feedback, organizations can avoid the pitfalls of strategic alignment and improve overall performance.
What are some real-world examples used in "Six Simple Rules" to illustrate the application of the rules?
- InterLodge case study: The book describes how a hotel chain improved performance by empowering receptionists to influence back-office functions, leading to better cooperation and customer satisfaction.
- MobiliTele example: A telecom manufacturer reduced product development delays by turning a powerful unit into an integrator, fostering cooperation among engineering teams.
- RapidTrain story: A railway company improved on-time performance by changing evaluation criteria to reward cooperation, leading to better collaboration among operational units.
What are the best quotes from "Six Simple Rules" and what do they mean?
- "The real curse is not complexity so much as 'complicatedness.'" This quote highlights the book's central argument that unnecessary organizational mechanisms hinder performance more than complexity itself.
- "Cooperation has nothing to do with a touchy-feely conviviality." The authors emphasize that genuine cooperation involves addressing interdependencies and adjustment costs, rather than relying on good interpersonal relationships.
- "The simple rules are a way for managers to break out of this doom loop." This quote underscores the book's promise that the six simple rules can help organizations escape the cycle of complicatedness and improve performance.
How can managers implement the six simple rules in their organizations?
- Start with understanding: Managers should begin by understanding what their people do and why, using this knowledge to inform changes in the work context.
- Empower integrators: Identify and empower individuals or units that can foster cooperation across the organization, replacing complicated structures with effective collaboration.
- Create feedback loops: Use direct and indirect feedback loops to connect actions with their consequences, encouraging cooperation and adaptability in addressing complex challenges.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.