eTextbook: Management, EMEA Edition

If you manage anyone, or plan to, this is the operating manual. It compresses a century of management thinking into usable frameworks: decision-making steps, motivation theories, leadership models, control processes. Students get exam-ready structure; new managers get vocabulary for problems they already feel. Read it before your first direct report, not after.

1. 1Chapter 2 (also revisited in Chapter 13)

   The light that wasn't the point

   Western Electric's Hawthorne Works in Chicago, 1924. Researchers set out to test a simple question: does better lighting make workers more productive? They dim the lights. Output goes up anyway. They brighten them. Output still climbs. Whatever they do to the physical conditions, productivity keeps rising, and the puzzle deepens through the 1920s and 1930s. The eventual answer: workers weren't responding to illumination at all. They were responding to attention, to group norms, to the social dynamics of being studied. The 'Hawthorne effect' is born, and with it the recognition that people at work are social beings, not machines under a lamp.

   The idea

   The surprise is that the experiment failed in the most useful way possible. The researchers wanted a physical variable; they found a human one. Once you accept that group norms and social dynamics can outweigh working conditions, half of management changes meaning: morale, informal groups, and attention become performance variables, not soft extras. Every later theory in this book, from Maslow to McGregor, builds on that shift.

   Try this: This week, watch one team you're on for informal norms: who sets the pace, what counts as 'enough'. Name one norm out loud to yourself before trying to change anything.

2. 2Chapter 2 (also Chapter 14)

   Theory X bosses create Theory X workers

   Douglas McGregor looks at how managers talk about their people and finds two hidden scripts. Theory X assumes employees dislike work, are lazy, dodge responsibility, and must be coerced to perform. Theory Y assumes employees are creative, enjoy work, seek responsibility, and can exercise self-direction. The stakes: whichever script a manager carries shapes every assignment, every check-in, every rule. Treat people as lazy and you build controls that prove laziness; trust people with responsibility and many rise to it.

   The idea

   What startles readers is that these are assumptions, not findings. McGregor isn't saying workers are one way or the other; he's saying your belief acts like a self-fulfilling prophecy. Coercion designed for Theory X people can produce exactly the avoidance it expects. The practical move is auditing your own default script before designing any policy, because the policy will teach people how to behave.

   Try this: Before your next delegation, write down which theory you're assuming. If it's X, delegate one small task with full ownership instead and see what comes back.

3. 3Chapter 1

   Ten hats, one job title

   Henry Mintzberg watches what managers actually do all day and finds no tidy job description. Instead, ten roles, grouped three ways. Interpersonal: figurehead, leader, liaison. Informational: monitor, disseminator, spokesperson. Decisional: entrepreneur, disturbance handler, resource allocator, negotiator. The same person greets visitors as figurehead at nine, settles a turf war as disturbance handler at ten, and negotiates with a supplier before lunch. The insight lands: 'manager' isn't one role but a rotation through ten, and the mix shifts with level and situation.

   The idea

   The framework's power is diagnostic. When your week feels chaotic, Mintzberg says the chaos has structure: you were monitoring, allocating, negotiating. New managers often over-invest in the decisional roles and starve the informational ones, then decide badly because they stopped monitoring. Knowing the ten roles lets you notice which hat you never wear, and that gap is usually where your problems live.

   Try this: Log tomorrow's meetings and calls against the ten roles. Circle the one you played least; schedule something that forces you into it this week.

4. 4Chapter 1

   Skills that scale with your seat

   Robert Katz sorts managerial talent into three kinds: conceptual, human, and technical. The pattern that emerges is level-dependent. Technical skills matter most for first-line managers, close to the work. Conceptual skills matter most for top managers, seeing the whole business. Human skills, working with people, matter at every level, from the shop floor supervisor to the corner office. The story is the career itself: as you climb, the skills you're praised for change under you, and the ones that got you promoted are not the ones your new job needs.

   The idea

   This explains a quiet career trap. People get promoted for technical excellence, then fail because the new role rewards conceptual breadth instead. The constant is human skill; it never stops mattering, which is why 'good with people' isn't a junior compliment but a career-long requirement. If you're eyeing a promotion, start building the next level's skill before the title arrives.

   Try this: Rate yourself 1-5 on conceptual, human, technical. Compare against your target level's profile; pick the lowest gap and take one action on it this month.

5. 5Chapter 4 (also Chapters 5, 6)

   The drug Merck gave away

   Merck & Co. develops Mectizan (ivermectin), a drug that treats river blindness, onchocerciasis, a disease that blinds people in some of the world's poorest regions. The commercial market barely exists: the patients who need it most cannot pay. In 1987, Merck makes its call: it commits to donate Mectizan free of charge to all who need it, for as long as needed. The program has since treated millions of people at no charge. A company built to earn profits chooses a decision its own accountants could never justify, and keeps it for decades.

   The idea

   This is the book's anchor for what values-driven management looks like when it costs something. The decision wasn't charity bolted onto strategy; it expressed an identity, and identity is what guides decisions no rulebook can cover. Notice the phrasing, 'for as long as needed': it's an open-ended commitment, the kind that tests whether values are real. When your own hard decision has no spreadsheet answer, ask what kind of organization you claim to be.

   Try this: Write your team's equivalent of 'for as long as needed': one commitment you'd keep even when it's inconvenient. Post it where decisions get made.

6. 6Chapter 3 (also Chapter 6)

   Five dimensions of doing business abroad

   Geert Hofstede mines data from IBM employees across more than 40 countries and finds that national cultures differ along five measurable dimensions: individualism versus collectivism, power distance, uncertainty avoidance, masculinity versus femininity, and long-term versus short-term orientation. The stakes appear the moment a manager crosses a border: a flat, first-name organization that feels empowering in one country can read as disrespect in a high power-distance one. The same incentive plan, the same meeting style, the same feedback habit lands differently depending on where the map says you are.

   The idea

   The surprise is that culture turned out to be quantifiable at all, and from one company's workforce worldwide, which controls for industry while varying nation. The five dimensions give managers a vocabulary for friction they previously filed under 'personality clash'. Use them as hypotheses, not stereotypes: they describe central tendencies of national workforces, and individuals vary. But walking into a negotiation knowing which dimension will bite is a real advantage.

   Try this: Before your next cross-border call, check where the other country sits on power distance and uncertainty avoidance; adjust how directly you deliver one piece of feedback.

7. 7Chapter 7 (also Chapters 2, 6)

   Eight steps between problem and verdict

   A manager faces a mess: sales slipping, morale wobbling, options multiplying. The book lays out the discipline: identify the problem, identify decision criteria, allocate weights to those criteria, develop alternatives, analyze the alternatives, select one, implement it, then evaluate whether the decision worked. The tension in the story is that most managers start at step five, jumping straight to alternatives and picking a favorite. The eight steps exist because skipping the front end, defining the problem and weighting what matters, is where decisions quietly go wrong.

   The idea

   The steps that feel bureaucratic, criteria and weights, are actually where your values get operationalized. Choosing weights is choosing what you care about, and doing it explicitly prevents the post-hoc rationalization that makes bad decisions feel inevitable. The last step, evaluating effectiveness, is the one almost everyone skips, which is why the same bad decision returns yearly. Slow at the front, honest at the back, fast in the middle.

   Try this: Take one decision pending this week. Write the problem in one sentence and list your top three criteria with weights before you allow yourself to list options.

8. 8Chapter 7 (also Chapter 6)

   Bounded brains, good-enough choices

   Two models of the deciding mind face off. The classical model assumes managers make optimal decisions: full information, perfect logic, the best choice. Herbert Simon's administrative model says otherwise: managers are rational, but only within the limits of their ability to process information, a condition he calls bounded rationality. Real managers can't map every alternative, so they satisfice, accepting the first good-enough option instead of searching forever for the best one. The scene is every manager's Tuesday: seventeen emails, partial data, a deadline at five.

   The idea

   Simon's insight reframes 'good enough' from a failure into a design principle. If information is always partial, optimizing is a fantasy and satisficing is what competence looks like. The practical corollary: spend your limited thinking on the few decisions where the stakes justify real search, and build routines that satisfice well for the rest. Knowing you're bounded is the beginning of deciding well within the bounds.

   Try this: Sort this week's decisions into two piles: reversible and irreversible. Satisfice fast on reversible ones; reserve full eight-step treatment for the irreversible pile.

9. 9Chapter 8 (also Chapter 9)

   Five forces, one industry map

   Michael Porter hands managers a map for asking why some industries are brutal and others comfortable. Five forces: the level of rivalry among existing competitors, the threat of new entrants, the bargaining power of large suppliers, the bargaining power of large customers, and the threat of substitute products. Picture a strategy meeting where the team blames a bad year on a lazy salesforce. The five forces widen the lens: maybe rivalry is intense, maybe customers hold the power, maybe a substitute is eating your lunch. The framework turns 'the market is hard' into five specific, testable problems.

   The idea

   What surprises people is that competition isn't only about competitors. Suppliers and buyers can squeeze margins as effectively as a rival with a lower price, and substitutes can kill an industry without anyone in it doing anything wrong. The model also explains why average profitability differs by industry before any firm does anything: structure, not effort, sets the starting odds. Strategy begins by reading the structure you're actually in.

   Try this: Sketch the five forces for your industry in ten minutes. Circle the strongest force; that's the one your next strategy conversation should be about.

10. 10Chapter 9 (also Chapters 17, 2)

    Just in time, not just in case

    Toyota builds its Production System around a radical inversion of factory logic: inputs arrive only when needed, just in time for assembly. No mountains of parts, no warehouses aging between deliveries. The payoff is lower inventory holding costs and less waste, and the approach becomes a cornerstone of lean manufacturing that companies worldwide adopt. The tension is obvious the moment you picture it: a line with no buffer has no room for error, so the system only works if quality and coordination are relentless. Toyota bet that discipline beats stockpiling, and the bet reshaped global manufacturing.

    The idea

    JIT is really a philosophy about hiding problems. Inventory is a cushion; cushions let defects and delays hide underneath. Remove the cushion and every weakness surfaces immediately, forcing it to be fixed. That's why copying JIT without copying the discipline fails: the low inventory isn't the trick, the exposed-and-solved problems are. The same logic applies beyond factories, to any buffer you keep because it feels safe.

    Try this: Find one buffer in your work, stockpiled reports, backlog, extra approvals, and ask what problem it's hiding. Try shrinking it by a third and see what surfaces.

11. 11Chapter 11 (also Chapters 12)

    Forming, storming, and the teams that skip class

    Bruce Tuckman's model gives team life a plot: forming, when everyone is polite and unsure; storming, when conflict surfaces; norming, when the group settles its rules; performing, when it actually works; and adjourning, when it ends. The scene is every kickoff meeting you've sat through: smiles and agendas, everyone nice, everyone careful. That's forming, and the storm is coming. The model's honest footnote matters as much as the stages: not all teams pass through all stages. Some stall in storming; some never quite perform.

    The idea

    The relief this model offers is naming the fight. Storming feels like failure to new team leaders, when it's actually a stage with an exit. The danger isn't conflict, it's teams that avoid storming and carry unresolved norms into performing work, then fracture under pressure. Knowing the map lets you diagnose where your team is stuck and what the next stage requires, instead of wondering why everyone suddenly hates the meetings.

    Try this: Diagnose your team against the five stages today. If you're storming, schedule the conflict: one meeting where the disagreements get said out loud.

12. 12Chapter 13

    What employees actually want

    Two theories of motivation share a chapter and disagree about pay. Maslow stacks human needs in five levels: physiological, safety, belongingness, esteem, and self-actualization; a satisfied level stops motivating, and the next one up takes over. Herzberg splits the same workplace down the middle: motivators like achievement and responsibility satisfy needs, while hygiene factors like pay and working conditions only prevent dissatisfaction. The scene is the raise that fails: a manager improves pay, a hygiene factor, and three weeks later the same grumbling returns, because preventing dissatisfaction was never the same as creating motivation.

    The idea

    The two models converge on an uncomfortable point: the things managers most often adjust, pay and conditions, are the ones that can't produce lasting motivation. Herzberg's split explains why fixing hygiene feels productive but changes nothing about engagement. Maslow adds the sequence: you can't skip levels, so safety concerns will always drown out esteem projects. Diagnose which level or factor is actually the problem before spending your budget on the wrong fix.

    Try this: List your team's last three morale fixes. Label each hygiene or motivator. If they're all hygiene, plan one achievement or responsibility change this month.

13. 13Chapter 13

    The math of why effort happens

    Victor Vroom asks why the same bonus ignites one employee and leaves another cold, and answers with three multiplying terms. Expectancy: the belief that effort will lead to performance. Instrumentality: the belief that performance will lead to rewards. Valence: the value of that reward to the person. The scene is a sales contest announced to a team: one rep doesn't believe the target is reachable, expectancy near zero; another doesn't believe the prize will actually be paid, instrumentality near zero; a third just doesn't want the prize, valence near zero. All three put in no extra effort, for three different reasons.

    The idea

    The multiplication is the insight: if any term is zero, motivation is zero, no matter how strong the others. That's why motivational speeches fail, they usually address valence, 'this prize is great', when the real leak is expectancy or instrumentality. Diagnosing which term is broken changes the fix entirely: training and resources for expectancy, credible payoffs for instrumentality, personalized rewards for valence. One question per term, asked honestly, beats any pep talk.

    Try this: For one underperformer you manage, ask yourself which term is near zero: can they do it, will it be rewarded, do they want the reward? Fix that term first.

14. 14Chapter 14 (also Chapter 15)

    Leaders are made of behaviors, then fitted to situations

    The search for what makes a leader starts with traits, then the Ohio State studies shift the question to behaviors, finding two independent dimensions: consideration, caring about people, and initiating structure, organizing the work. Then Fred Fiedler complicates everything with his contingency model: leader style, task-oriented or relationship-oriented, is fixed, and effectiveness depends on matching style to how favorable the situation is, determined by leader-member relations, task structure, and position power. The scene is a leader thriving in one job and drowning in the next, same person, same style, different situation.

    The idea

    The combined insight is that 'what makes a great leader' is the wrong question. Behaviors can be learned, which is the good news from Ohio State; but Fiedler says style is fixed, so the lever isn't changing yourself, it's changing the fit, the situation, or the leader in the seat. That's why star managers fail after transfers: the situation's favorableness flipped. Audit the three favorableness factors before judging any leader, including yourself.

    Try this: Rate your current role on leader-member relations, task structure, and position power. If the situation is unfavorable for your style, change the situation, not your personality.

15. 15Chapter 20 (also Chapter 16)

    Watch, compare, correct

    The book ends where management does: with the loop. Control is the process of monitoring, comparing, and correcting work performance, in three steps: establish standards of performance, measure actual performance, compare performance against the standards and take corrective action. The scene is the review meeting that goes wrong because nobody defined the standard in advance: the manager measures, the team argues about what 'good' meant, and the correction becomes a negotiation. The three steps exist because control without pre-set standards isn't control, it's opinion.

    The idea

    The step everyone skips is the first one, and it's the one that makes the other two possible. Standards set in advance turn evaluation from argument into arithmetic. The last step matters just as much: comparison without corrective action is just surveillance, and correction without comparison is guesswork. The loop is what makes management a discipline rather than a personality trait, you can run it on anything, including your own goals.

    Try this: Pick one goal you're pursuing. Write its standard in one measurable sentence today, so next month's comparison is arithmetic instead of argument.

Students in management or business courses who need the canonical frameworks in one place, and new managers who suspect there's a system behind the chaos. Also useful for experienced leaders who want shared vocabulary for team problems they've been solving by instinct.

FAQ