Top 100 Decision Models for Strategic Thinking

The Eisenhower Matrix sorts work by two qualities that people habitually blur: how much a task matters and how soon it demands attention. It takes its name from Dwight Eisenhower, who in a 1954 speech drew a line between urgent and important problems and remarked how rarely the two coincide. The four-box grid came later; Stephen Covey made it famous in The 7 Habits of Highly Effective People in 1989, and it has lived on whiteboards ever since.

The real payoff is the top-left box. Work that matters but has no deadline is exactly the work that gets displaced, because urgency is loud and importance is quiet. Left alone, today's unscheduled important task becomes next month's crisis, and the Do now box fills with problems that could have been prevented.

The matrix misleads when urgency is treated as a fixed property rather than something often manufactured by other people's poor planning. It also assumes importance is obvious, when deciding what matters is frequently the hard part; the grid organises that judgement but cannot make it. And it says nothing about effort, so a vital two-minute task and a vital two-month project land in the same box. Used as a quick sort rather than a philosophy, though, it is hard to beat.

The Pareto Principle is the observation that outcomes are rarely spread evenly across their causes: a minority of inputs tends to produce a majority of results. The name honours Vilfredo Pareto, the Italian economist who noticed in the 1890s that a small share of the population held most of the land. The quality pioneer Joseph Juran later generalised the pattern to defects and their causes, calling them the vital few and the trivial many , and attached Pareto's name to it. The famous 80/20 split is shorthand, not law; real data might come out at 70/30 or 95/5, and the two numbers need not add up to 100 at all, since they measure different things.

Take a small online furniture shop whose returns are eating its margin. The founder pulls a year of return reasons and finds thirteen different causes. Sorted, the picture is stark: damage in transit accounts for 41 per cent of returns, colours that look different from the photos for 27 per cent, late delivery for 12 per cent and customers changing their minds for 8 per cent, with nine other causes sharing the last 12 per cent between them. Two causes out of thirteen drive more than two-thirds of the problem. Sturdier packaging for the most fragile products and recalibrated product photography become the quarter's priorities; the long tail gets a shared spreadsheet and no meetings.

Most problems are lopsided; the skill lies in measuring the lopsidedness rather than assuming it.

Opportunity cost is the value of the best alternative you give up when you choose something. Every yes spends time, money or attention that could have gone elsewhere, and the true cost of a choice is not just what it consumes but what that resource would otherwise have done. Economists had circled the idea for a long time before the Austrian economist Friedrich von Wieser gave it its name in the early twentieth century. It is now among the first ideas taught in any economics course, and among the first forgotten in any planning meeting.

Picture a two-person design studio with roughly six spare weeks. Option one is bidding for a large public tender: plenty of work if they win, but the bid alone eats two weeks and their odds are perhaps one in four. Option two is finishing their own template product, which they expect to bring in a modest, steady trickle of sales for years. Option three is filling the gap with routine client work they know will pay. On a rough expected-value basis the product comes out on top, the client work a close second and the tender last. So the opportunity cost of chasing the tender is the product, and the opportunity cost of building the product is the client work. Framed that way, the founders stop debating whether the tender is good and ask whether it beats the next-best thing. It does not, so they pass, and build the product.

Nothing is free; it is merely priced in a currency you were not watching.

The 5/25 Rule is a blunt method for choosing a small number of goals and protecting them from a large number of decent ones. It comes from a widely retold story in which Warren Buffett advises his personal pilot to write down his top 25 career goals, circle the five that matter most, and then treat the remaining twenty not as a backlog but as a list to avoid at all costs. The anecdote is popular and probably embellished, and its details have never been firmly confirmed, so it is best read as a parable rather than history. The idea stands on its own regardless.

Imagine a head teacher at a primary school at the start of a new academic year. Her honest list runs to 23 goals: a reading programme, a new behaviour policy, a garden club, a rebuilt website, an outreach scheme for parents, a staff wellbeing review and more. She circles five, including reading, attendance and the behaviour policy. The rebuilt website and the garden club are both good ideas with enthusiastic champions, which is exactly why they go on the avoid list in writing, with a note that they return to the table next September. When a governor proposes a fresh initiative in October, she can point to a list rather than defend a mood.

The second list is the useful one: anyone can name what they want, but fewer can name what they will refuse.

The Value vs Effort Matrix is the simplest way to compare a pile of ideas that all sound worthwhile. It has no single inventor. It grew out of lean, agile and product-management practice, where teams needed a quick, visual way to triage backlogs, and it travels under several names, including the impact–effort grid and the action priority matrix.

The model's strength is relative placement. Nobody needs precise numbers; the team only needs to agree that idea A is worth more than idea B and costs less. That is usually quick, and the disagreements that surface along the way are often the most useful part of the exercise.

The matrix misleads in predictable ways. Estimates of effort are almost always optimistic, so quick wins drift to the right once work begins. Value is often judged from one viewpoint only, usually that of whoever holds the marker pen. And a team that only ever takes quick wins will look busy for a year while avoiding every big bet that would change its position. The grid is a first cut, not a final ranking; follow it with a closer look at the top few.

MoSCoW is a way of agreeing what a project will and will not deliver when time or money is fixed. Dai Clegg devised it in 1994 while working at Oracle, and it was soon adopted by the Dynamic Systems Development Method, one of the early agile frameworks. The capital letters spell four categories; the lower-case o's are there only to make the word pronounceable.

The discipline lies in the definitions. A Must is not merely something important; it is something whose absence breaks the whole. The test is to ask what would happen if the item were missing on launch day. If the honest answer is that the launch should be cancelled, it is a Must. If people would be annoyed and use a workaround, it is a Should at best.

MoSCoW fails when everything becomes a Must, which happens whenever stakeholders suspect that Should is a polite word for never. It offers no ranking within a category, so twelve Musts give no hint about which to build first. And Won't lists are often quietly ignored, which defeats their purpose. The method works when someone with authority enforces the definitions and revisits the Won'ts at the start of the next round.

RICE scoring turns a debate about which feature to build next into an arithmetic problem with its assumptions on display. The product team at Intercom, the customer-messaging company, published it around 2016 after finding that existing scoring methods left too much room for pet projects. The acronym names the four factors in the formula.

Confidence is the factor that does the quiet work. It forces a team to discount exciting ideas that rest on a hunch, and to admit out loud when it does not really know.

RICE misleads when its inputs are reverse-engineered to justify a decision already made, which is easy because every factor is an estimate. Its tidy output also hides the fact that impact and confidence are subjective, and that one optimistic number multiplies through the whole score. It favours small, measurable improvements and can starve strategic bets whose reach only appears years later. The score should start a conversation, not end one.

The Kano Model explains why adding features does not always make customers happier, and why removing one can make them furious. It was developed by the Japanese quality researcher Noriaki Kano and his colleagues, who published it in 1984. Its central insight is that satisfaction does not rise in a straight line with what you provide; different kinds of feature behave in different ways.

Take a family-run hotel reviewing its rooms. Clean sheets, hot water and working Wi-Fi are Basics; guests never praise them, but one cold shower produces a scathing review. Wi-Fi speed, bed comfort and breakfast quality are Performance needs, and guests compare them directly with the place down the road. A handwritten note recommending a hidden local café, or a jar of homemade biscuits, is a Delighter that costs little and turns up in review after review. The owners realise they had been spending on bigger televisions, which their survey shows guests are indifferent to, while the shower pressure, a Basic, had been neglected for two years.

Customers never thank you for the floor, but they certainly notice when it gives way.

The Theory of Constraints holds that the output of any system is limited by one bottleneck at a time, and that improving anything other than that bottleneck is largely wasted effort. The Israeli physicist turned management thinker Eliyahu Goldratt set it out in The Goal , a 1984 business novel about a struggling factory, and refined it over the following years. The idea applies to any chain of dependent steps: a kitchen, a hiring pipeline, a software release, an emergency department.

The counterintuitive part is the third step. Keeping every station busy feels efficient, but when an upstream step outpaces the constraint, it simply builds a pile of half-finished work in front of it.

The theory misleads when people assume they know where the constraint is rather than looking at where work waits. In knowledge work the bottleneck can be one person's approval, a policy or the market itself, none of which shows up on a process map. It can also encourage endless polishing of a step that limits output today but has stopped mattering to the strategy. And when demand varies, the constraint moves, so it is worth watching regularly rather than once.

The Weighted Decision Matrix compares a handful of options against several criteria at once, each criterion carrying a weight that reflects how much it matters. It belongs to the family of methods known as multi-criteria decision analysis and is a close relative of the concept-selection matrix popularised by the engineer Stuart Pugh. It is common in engineering, procurement and public bodies, where decisions need to be explained as well as made.

Consider a county library service choosing between three sites for a new branch. The panel agrees five criteria and weights: access by public transport 30 per cent, running costs 25, floor space 20, nearby schools 15 and parking 10. The old bank on the high street scores top marks on transport and schools but poorly on space and parking. The retail park unit is huge, with ample parking, but badly served by buses. The community centre annexe is cheap to run and middling elsewhere. On the 1–5 scale the weighted totals come out at 3.5 for the old bank, 3.25 for the community centre and 2.85 for the retail park. The panel's instinct had leaned towards the retail park because of its size; the matrix shows that its weakness on the most heavily weighted criterion outweighs its strengths.

The table does not decide for you; it shows you what you have already decided matters.

A decision tree is a drawing of a choice and everything that might follow from it. It grew out of the decision analysis developed in the 1960s, most closely associated with Howard Raiffa at Harvard, who turned the arithmetic of probability into something a manager could sketch on a whiteboard. The ambition is modest: put your options and your uncertainties on paper in the order they happen, and let the structure do some of the thinking that anxiety usually does badly.

Take a baker with one successful shop who is weighing a second site. Opening another shop, she reckons, has a 60 per cent chance of being busy enough to add £80,000 over three years and a 40 per cent chance of being quiet and costing £50,000 to unwind. A weekend market stall is humbler: a 90 per cent chance of a steady £15,000 and a 10 per cent chance of a washout that costs £15,000. Doing nothing is worth nothing, reliably. Rolled back, the shop is worth about £28,000 and the stall about £12,000. The tree says shop. It also shows her, on a single branch, the £50,000 loss she would have to survive to get there, which is a different question from which branch is biggest.

The weaknesses are just as visible. Probabilities invented to make the arithmetic work give a precise-looking answer built on guesswork. Trees sprawl: three options with three outcomes each, followed by another round of choices, soon become a hedge nobody can read, so prune to the branches that could actually change the decision. And the rollback assumes you care only about averages, when a single bad branch might be fatal.

Expected value is the average result of a choice if you could make it many times over. The idea comes from a 1654 exchange of letters between Blaise Pascal and Pierre de Fermat about how to split the stakes of an unfinished game of chance, and Christiaan Huygens set it out in print a few years later. Nearly four centuries on, it remains the backbone of insurance, betting and every spreadsheet that claims to weigh risk.

Consider a small consultancy with time to prepare only one tender this month. Bid A is a mid-sized contract: a 20 per cent chance of winning £150,000 of work, for about £8,000 of effort to write the bid, which nets an expected £22,000. Bid B comes from a repeat client: a 50 per cent chance at £40,000, costing £3,000 to prepare, so £17,000. Bid C is the moonshot everyone is excited about: a 5 per cent chance at £600,000, but £20,000 of senior time to chase it, so £10,000. The glamorous option comes last, and the dull repeat client sits far closer to the top than anyone in the room expected.

Its blind spot is that you live through one outcome, not the average. A choice with a handsome expected value and a small chance of ruin is a bad choice if ruin means you never get to play again; the average only arrives for those who survive long enough to collect it. Probabilities for rare events are also notoriously soft, so a large payoff multiplied by a made-up small number can justify almost anything. Use expected value to rank the options, then look separately and honestly at the worst case.

In February 2002, at a Pentagon press briefing about the evidence on Iraq, the US Defense Secretary Donald Rumsfeld distinguished between known knowns, known unknowns and unknown unknowns. The line was widely mocked at the time and has since been quietly adopted by project managers, engineers and risk officers, because it names something real. The underlying idea is older: the Johari window, devised by the psychologists Joseph Luft and Harrington Ingham in 1955, crosses what you know about yourself with what others know in a similar grid. The Rumsfeld Matrix is what planners call the version that crosses knowledge with awareness.

Picture a city council preparing a rental e-scooter scheme. Its known knowns include the fleet size and the terms of the operator contract. Its known unknowns: how many people will ride in winter, and how many scooters will end up in the canal. Its unknown knowns: the parking wardens already know which pavements are too narrow for a docking bay, but nobody has asked them. Its unknown unknowns are, by definition, impossible to list in advance; perhaps an insurer changes its policy, or a battery supplier quietly goes under.

The misuse is to treat "unknown unknowns" as an alibi, a way to describe a foreseeable failure as an act of fate. Many so-called surprises turn out to have been unknown knowns sitting in someone's inbox. The grid is also static while knowledge moves: today's unknown unknown becomes tomorrow's known unknown the moment someone asks the right question, so the useful work is moving items between cells, not admiring the categories.

The Cynefin framework (pronounced roughly kuh-NEV-in , a Welsh word for habitat or a place of belonging) was developed by Dave Snowden from 1999, initially while he worked at IBM. It starts from an observation that sounds obvious and is routinely ignored: different situations need different ways of deciding, and the most common mistake is reaching for the method that suited the last situation. Snowden has renamed the domains more than once over the years; the labels used here are the current ones.

Consider a hospital emergency department on a single Monday. The weekend staffing rota is clear: there is a rule, so follow it. Introducing new triage software is complicated: the vendor's engineers and the clinical safety officer can work out the right configuration if they are given time. Working out why frail patients keep returning within a week is complex: dozens of factors interact, so the team runs three small trials at once, a follow-up phone call, a pharmacist review and a link with a local care home, and keeps whichever moves the numbers. A power cut during the evening rush is chaotic: someone takes charge and acts first.

The usual misuse is to treat Cynefin as a two-by-two grid and drop every problem neatly into a box. Real situations straddle domains and drift between them, and a single project can have clear, complicated and complex parts at the same time. Nor is it a ranking: complex is not better or worse than clear, only different.

In his letter to Amazon shareholders published in 2016, Jeff Bezos divided decisions into two types. Type 1 decisions are consequential and irreversible, or nearly so: walk through the door and you cannot get back. Type 2 decisions are changeable: if you dislike what you find on the other side, you can step back through. The image of one-way and two-way doors stuck because it turns an abstract property, reversibility, into something you can picture yourself standing in front of.

Picture a small online homeware shop with eight staff. This month it faces two decisions: a new layout for its product pages, and a ten-year lease on a warehouse twice the size of the current one. The layout is a two-way door: show it to half the visitors, watch sales for a fortnight, roll it back if it disappoints. The lease is a one-way door: breaking it would cost more than a year's profit. The sensible split is to let the web designer decide the first by Friday and to spend a month on the second, with the founders, their accountant and a long look at worst-case volumes.

The model misleads when reversibility is assumed rather than checked. Some things are technically undoable but not in practice: a broken promise to customers, a public announcement, a key employee who leaves in protest. Treating such choices as two-way doors because the paperwork can be reversed is how teams talk themselves into a speed they cannot afford.

A post-mortem tells you why a patient died, which helps the next patient but not this one. The pre-mortem , described by the psychologist Gary Klein in a short Harvard Business Review article in 2007, moves the exercise to the moment it can still help: before the project starts. It draws on research into what psychologists call prospective hindsight , the finding that people come up with explanations more readily for an event imagined as having already happened than for one framed as merely possible.

Imagine a couple deciding whether to move from Leeds to Bristol for a new job. In a twenty-minute pre-mortem at the kitchen table, they imagine that it is next summer and the move has been a mistake. Their lists overlap less than either expected. One writes that the commute from the only area they could afford turned out to take ninety minutes. The other writes that their daughter never settled at a school she joined halfway through the year. Neither had said these things aloud, because saying them felt like doubting the plan. The fixes are modest: a trial commute on the day of the second interview, and a start date that waits until September.

It can go wrong in two directions. Run as a box-ticking ritual after the plan has already been approved, it produces a list nobody acts on. Run without a firm facilitator, it can turn into a gloomy free-for-all that sinks a perfectly good project. The output must be changes to the plan, with owners and early warning signs, not a mood.

Bayesian updating is the habit of treating beliefs as estimates that move with evidence, by the amount the evidence deserves. It takes its name from Thomas Bayes, an English minister whose essay on probability was published after his death, in 1763, by his friend Richard Price; Pierre-Simon Laplace developed the same idea more fully a few years later. The mathematics can become elaborate, but the core move fits on a napkin.

A software founder has a large customer coming up for renewal. Across her client base, about 70 per cent of accounts like this one renew, so her prior is 70 per cent, or odds of 7 to 3. Then she hears that the customer's internal champion has left. Looking back, she reckons champions leave in about 10 per cent of accounts that go on to renew, but in around 40 per cent of accounts that end up cancelling. The evidence is four times as likely if the customer is leaving, so her odds shift from 7:3 to 7:12, and her belief falls to roughly 37 per cent. Not doomed, but a different week: she books a call with the new decision-maker.

The model fails mostly through false precision. Priors and likelihoods in everyday decisions are judgement calls, and dressing them in decimals can make a hunch look like a calculation. It can also be gamed: a prior chosen to be extreme will resist almost any evidence. The value lies less in the exact posterior than in the direction and size of the move, and in the willingness to keep moving.

The phrase margin of safety belongs to the investor Benjamin Graham, who used it in Security Analysis , written with David Dodd in 1934, and later made it the subject of the final chapter of The Intelligent Investor (1949). Engineers had the same instinct long before: a bridge expected to carry ten tonnes is built to carry several times that, because loads, materials and calculations all contain error. The principle in both cases is to leave room for being wrong.

The founder of a cleaning company is offered the chance to buy a smaller local rival. Her optimistic valuation, assuming every contract renews and the new staff stay, is £1.5 million. Her central estimate is £1.2 million. If the two biggest contracts walk and integration drags on for a year, it is worth perhaps £900,000. The seller wants £1.1 million. On her central estimate that looks like a bargain, but it leaves nothing to spare in the bad case. She offers £700,000 and is ready to walk away; at that price, the deal survives the pessimistic version of the story with £200,000 to spare.

The misuse runs both ways. A margin that is too wide means never acting: a buyer who demands a huge discount on everything will rarely buy anything. And a margin calculated on the wrong number gives false comfort: if the pessimistic case is really just a slightly less optimistic one, the buffer is decorative. The test is whether your pessimistic case would make you wince.

The barbell strategy was popularised by the essayist and former options trader Nassim Nicholas Taleb in The Black Swan (2007) and Antifragile (2012), though bond investors had long used the word for a portfolio split between very short and very long maturities. Taleb's version is broader: put most of your resources somewhere boringly safe, a small part somewhere aggressively speculative, and nothing in the comfortable middle.

Consider a product designer in her thirties who wants to start something of her own but has a mortgage. The middle path would be to quit and freelance while building her product, a choice that looks balanced but exposes her to losing income and focus at the same time. Her barbell is different. She negotiates a four-day week with her employer, which covers the mortgage and her pension, and spends the fifth day building small things quickly and in public. If none of them works, she has lost some Fridays. If one takes off, she has a business with paying customers before she has resigned.

The barbell misleads when either end is mislabelled. A "safe" asset that can quietly lose a third of its value is not the safe end, and a speculative bet with open-ended losses, such as a personal guarantee on a loan, does not belong on the bold end at all. It is also easy to drift back to the middle, as the fifth day slowly grows into a half-hearted second job. The structure only works when both ends are protected deliberately.

Real options apply a piece of financial thinking to physical decisions: factories, leases, product lines, research. The term was coined by the MIT finance professor Stewart Myers in 1977, a few years after Fischer Black, Myron Scholes and Robert Merton had shown how to value financial options. The insight that carried across is simple: the right, but not the obligation, to do something later has value, and sometimes it is worth paying for.

A regional brewery wants to open a taproom in a neighbouring town but has no idea whether locals will come. Signing a lease outright is a big bet. Instead it pays the landlord £15,000 for a two-year option on a unit at a fixed rent. In the meantime it runs weekend pop-ups in a hired hall. By month nine it has sales data; by month fifteen it knows enough to decide. If the pop-ups have beaten their target, it exercises the option and signs the lease at the agreed rent. If not, it lets the option lapse. The worst case is the £15,000, a fraction of what a failed taproom would have cost.

The concept is abused when every vague possibility is called an option to justify spending. A real option has defined terms, a cost, an expiry date and a rule for exercising it; without those it is just hope with a budget line. Options also decay: keeping too many open drains money and attention, and an option nobody is prepared either to exercise or to abandon is merely procrastination with paperwork.

A first principle is a claim that cannot be broken down any further: a fact of physics, a law, a basic human need, a hard constraint. Aristotle used the term for the foundational propositions from which knowledge is built, and engineers have long worked this way. The idea has lately become fashionable in startup circles, mostly as a stick with which to beat reasoning by analogy , which is what most of us do most of the time: doing something because that is how similar things are done.

Take a founder starting a meal-kit business for small villages. The industry assumption is that fresh ingredients need refrigerated vans and next-day courier networks, which makes rural delivery uneconomic. Broken down, the claim becomes several smaller ones: the food must stay cold, it must arrive before it spoils, and someone must carry it the last mile. The fundamentals turn out to be narrower than the assumption. The food needs to stay below a safe temperature for a set number of hours; it does not need a van to do so. Rebuilt from there, the answer looks different: insulated boxes with ice packs rated for a full day, delivered once a week on a fixed route by a local driver who already passes every village. Nothing about it is clever. It simply was not visible from inside the analogy.

The aim is not to be original; it is to know which parts of the answer are load-bearing.

Most planning runs forwards: here is the goal, so what must we do to reach it? Inversion turns the question round: what would guarantee that we miss it? The mathematician Carl Jacobi is said to have urged his students to "invert, always invert", meaning that many hard problems become easier when restated backwards. The investor Charlie Munger made the habit famous well beyond mathematics, arguing that consistently avoiding stupidity tends to beat trying to be brilliant.

A head teacher planning the autumn parents' evening tried both. Forwards, the staff produced the expected answers: make it welcoming, give useful feedback, get a good turnout. Inverted, the question became how to make sure parents leave annoyed and none the wiser. The answers came quickly and were embarrassingly familiar. Let appointments overrun so the queues build; seat parents in a draughty hall with no idea where each teacher is; let teachers talk about marks without naming one thing the child should do next; hold it on the night of the local cup final. Each became a fix: a five-minute timer and a runner to keep slots moving, a printed floor plan at the door, one agreed next step per child, and a glance at the local calendar before setting the date. None of these had appeared on the forward list.

Success has many routes; failure tends to leave a clear set of fingerprints.

Every decision has an immediate effect, the one it was designed to produce. Second-order thinking asks what happens next: how people, markets and systems respond to that first effect, and what their responses cause in turn. The idea is old, since economists have warned about unintended consequences for centuries, but the investor Howard Marks gave it its current label, contrasting first-level thinkers, who stop at the obvious, with second-level thinkers who keep asking and then what?

Consider a market-town council worried about empty shops. The proposal is to make town-centre parking free. First order: more shoppers drive in, as intended. Second order: commuters and shop staff, who used to park at the edge of town to avoid the fees, now take the central spaces at eight in the morning and stay all day. By ten there is nowhere left for a shopper to stop. Third order: regular visitors learn that the town is impossible to park in and head for the retail park instead, so footfall ends up lower than before the change. A council that had thought one rung further might have chosen free parking with a two-hour limit, keeping the first-order benefit while blocking the second-order behaviour.

The first effect is the one you planned; the second is the one you will be remembered for.

Occam's razor is the principle that, among explanations that fit the facts equally well, the one requiring the fewest assumptions should be tried first. It is named after William of Ockham, a fourteenth-century English friar and logician, although the familiar wording and the name "razor" came later, and versions of the idea go back to Aristotle. The razor shaves away explanations that need more moving parts than the evidence demands.

A small software company noticed one Tuesday that sign-ups had fallen by roughly half. Within an hour the team had four theories. A competitor had launched a rival product that morning and was poaching visitors. A change in a search engine's ranking had cut traffic. A bot campaign was flooding the form so that the system was rejecting real users. Or Monday evening's release had broken something in the sign-up page. Counting assumptions changed the conversation. The competitor theory needed the launch to have happened, to have been noticed and to divert people instantly. The bot theory needed an attacker, a motive and a filter behaving oddly. The release theory needed only one thing: a bug in code that had changed the day before. Someone opened the form on a phone and found the submit button hidden behind a cookie banner. The fix took twenty minutes.

Start with the fewest leaps, and keep the others on the list.

Hanlon's razor says: never attribute to malice what can be adequately explained by stupidity. The line is usually credited to Robert J. Hanlon, who submitted it to a 1980 collection of jokes in the spirit of Murphy's law, though similar sentiments appear much earlier in literature. The blunt wording is part of its charm and part of its problem. A kinder and more useful version swaps stupidity for the ordinary causes of other people's irritating behaviour: error, haste, overload and not knowing what you know.

A project manager at a housing association discovered she had been left off the invitation to a meeting about a programme she ran. Her first reading was political: a colleague in finance was trying to sideline her. Before replying, she ran the tree. Malice would need a motive and a plan, and nothing else in their dealings suggested either. Error was plausible, since the invitation might have been copied from an older meeting that predated her role. Different information was possible too: the meeting might concern budget codes rather than the programme itself. She sent a one-line message asking whether she should attend. The answer came back within minutes, with an apology and a corrected invitation. The list had indeed been copied from last year.

Assume the muddle first; it is usually right, and it is always cheaper.

The circle of competence is the area in which your judgement is reliably good, because you have seen enough cases, made enough mistakes and received enough feedback to know how things usually go. Warren Buffett described the idea in his 1996 letter to shareholders, adding that the size of the circle matters far less than knowing where its boundary lies. His partner Charlie Munger made the same point in talks for years. The model is less about expertise than about self-knowledge.

A wedding photographer with fifteen years of work behind her had a superb feel for light, timing and nervous couples. A venue where she often worked offered her the chance to take over its whole events business: catering contracts, staffing, licensing and bookings. It felt like a natural step, since she had been to hundreds of weddings there. Mapping the circle made the picture clearer. Photography and the flow of the day were core. Client management and supplier relationships were the edge; she had watched them closely but never owned them. Catering margins, alcohol licensing and employing a dozen seasonal staff sat outside. She took a smaller deal: a paid advisory role on the guest experience, with an option to buy in after a year, once she had seen the books.

Knowing where your knowledge stops is the most valuable thing you know.

The phrase the map is not the territory comes from Alfred Korzybski, a Polish-American scholar who used it in a 1931 paper on language and meaning. His point was that every representation, whether a word, a model or a spreadsheet, is a simplification of something richer. A map is useful precisely because it leaves things out. The danger comes when we forget that it does, and start managing the map instead of the ground it describes.

A hospital trust used a bed-occupancy dashboard to decide when to open extra winter capacity. The dashboard counted a bed as free as soon as a patient was discharged on the system. On paper, occupancy hovered at a manageable level, so the extra ward stayed shut. On the wards, nurses described a different place: discharged patients often remained in their beds for hours, waiting for transport or medicines, and cleaning took longer than the system assumed. The map was not exactly wrong; it measured administrative discharge, which is a real thing. It simply was not the thing that mattered to a patient waiting on a trolley. After a manager spent two afternoons walking the wards, the trust added a field recording that a bed was physically ready, and the trigger for opening the extra ward moved earlier.

A map earns its keep only as long as someone keeps walking the ground.

Chesterton's fence comes from a 1929 essay by the writer G. K. Chesterton. He imagined a reformer who comes across a fence built across a road and, seeing no use for it, wants it cleared away. The wiser reformer, Chesterton argued, would say: go and find out why it was put there, and once you can tell me, I may let you remove it. The principle is not a defence of everything old. It is a rule about the order of operations: understand first, change second.

A new operations manager at a regional distribution warehouse found a rule that every outbound pallet loaded after three in the afternoon had to be checked by a second person. It cost two hours of labour a day, and nobody on the current shift knew why. Instead of scrapping it, she asked the longest-serving supervisor. The rule dated from a year when a late-shift error had sent a lorry of chilled goods to the wrong county, and the client had nearly walked away. The reason was real. Did it still hold? Only partly: the client remained, but the warehouse now had barcode scanning at the loading doors, which caught the same mistake automatically. She replaced the second check with a scan audit and kept a weekly spot check for that client. The labour came back; the protection stayed.

Every fence was once somebody's solution; find out to what before calling it a problem.

The ladder of inference describes how people get from what they see to what they do, often in seconds and without noticing the steps. It was developed by the organisational theorist Chris Argyris and reached a wide audience through Peter Senge's work on learning organisations in the 1990s. Its value lies in making a fast, invisible process slow and visible, so that two people who disagree can find the rung where they parted company.

A product manager ran a design review in which one senior engineer said almost nothing. She selected that silence from an hour of conversation. She added meaning: engineers on this team speak up when they care. She assumed he disliked the design, concluded that he would quietly resist the build, came to believe he was not committed to the roadmap, and acted by drafting a message to his manager. Before sending it, she walked herself back down the ladder and found that the only rung resting on data was the first. So she asked him directly. He had been up most of the night with a sick child, thought the design was fine, and had one concern about a database migration that he had been planning to write up. Her conclusion had used one fact and five inferences.

The higher the rung, the more it is worth checking the bottom one.

A straw man is a weak caricature of an opposing view, built to be knocked down. Steelmanning is the reverse: before arguing against a position, you construct its strongest possible version, stronger if you can manage it than the way its holder put it. The term spread through online debating and rationalist circles in the 2010s, but the idea is older. The philosopher Daniel Dennett popularised a set of rules he credited to the game theorist Anatol Rapoport, the first of which is to restate your opponent's position so clearly that they wish they had put it that way.

A couple living in a city flat were stuck on whether to move to the countryside. He wanted space and quiet; she thought it was a fantasy that would leave them isolated. Their arguments had settled into a loop in which each attacked the weakest version of the other's case: he heard her as afraid of change, and she heard him as romanticising mud. They agreed to try steelmanning. She restated his position, then improved it: lower housing costs would let one of them go part-time, the children would have room to roam, and both now worked remotely most of the week. He did the same for hers: friendships take years to build, rural transport is thin, and remote working might not survive a change of employer. With both cases at full strength, the decision became practical rather than personal: rent in a market town for a year before selling the flat.

Beat the best version of an argument, or you have not really won anything.

SWOT analysis sorts what you know about an organisation into four boxes: strengths, weaknesses, opportunities and threats. Its origins are hazy. It is often credited to work at the Stanford Research Institute in the 1960s, sometimes to Albert Humphrey in particular, but the record is thin and several business schools taught similar grids at the time. What is not in doubt is its reach: few strategy tools are drawn on more whiteboards.

Take a family-run garden centre on the edge of a market town. Its strengths are loyal regulars and staff who can diagnose a sick rose by sight. Its weaknesses are a website stuck in 2014 and a café that loses money every winter. The opportunity is a new housing estate of four hundred homes with empty gardens. The threat is a discount chain opening a garden section two miles away. Laid out like that, the obvious move appears: point the expert staff at the new estate with planting workshops and a simple online order-and-collect service, rather than fight the chain on price.

It misleads in other ways too. Teams flatter themselves, so the strengths box swells with things every competitor also has. Items are vague ("good culture") and unweighted, so a minor irritation sits beside an existential risk. And it is a snapshot; a threat today can be an opportunity next year. Treat each entry as a claim that needs evidence, keep each box to three or four lines, and date the page.

Porter's Five Forces explains why profit pools differ so much between industries. Michael Porter, an economist at Harvard Business School, set it out in a 1979 Harvard Business Review article and expanded it in his 1980 book Competitive Strategy . His point was that the intensity of competition is shaped by more than the firms you think of as rivals.

Picture a founder weighing a same-day bicycle courier service in a mid-sized city. Rivalry is fierce: three couriers already compete on speed. New entrants face almost no barrier, since anyone with a bike and an app can start on Monday. Suppliers are weak, because bikes and riders are easy to find. Buyers are strong: local businesses can compare quotes in minutes and switch on a whim. Substitutes loom large, from post-office tracked delivery to email replacing paper altogether. Mapped like this, the founder sees that the problem is not execution but structure. The better play may be a niche where forces are weaker, such as temperature-controlled delivery for pharmacies, where trust and compliance raise the barrier.

Used well, it turns a vague sense that "it's tough out there" into five specific pressures you can measure, avoid or soften.

PESTLE analysis is a structured scan of the forces outside an organisation that it cannot control but must live with: political, economic, social, technological, legal and environmental. The idea is usually traced to Francis Aguilar of Harvard, who in 1967 described scanning the business environment under four headings he labelled ETPS. Later writers rearranged the letters into PEST, then added legal and environmental factors to make PESTLE. Variants such as STEEPLE add ethics, but the purpose is the same.

Consider a regional transport authority planning to replace its diesel bus fleet. Politically, national clean-air targets and the prospect of grant funding push towards electric. Economically, battery costs have been falling but borrowing is dearer than it was. Socially, an ageing population means more passengers who rely on buses for hospital trips. Technologically, charging infrastructure is the bottleneck, not the vehicles. Legally, new accessibility standards will apply to any fleet bought this decade. Environmentally, depots in flood-prone areas need rethinking. Laid side by side, the authority sees that the critical issue is not which bus to buy but where and how to charge it, and that depot location sits at the junction of three letters at once.

The value of the scan lies not in what you write down but in what you choose to ignore.

The Ansoff Matrix maps the ways a business can grow by asking two questions: are we selling existing or new products, and to existing or new markets? Igor Ansoff, a mathematician turned strategist, published it in a 1957 Harvard Business Review article on diversification. Its staying power comes from how quickly it makes the risk of each growth route visible.

Take a craft brewery whose pale ale sells well in its home county's pubs. Penetration would mean more taps in nearby pubs and a loyalty scheme for the brewery shop. Product development would mean a low-alcohol range for the same drinkers, who keep asking for one. Market development would mean exporting the pale ale to cities in another region, or selling cans through supermarkets for the first time. Diversification might mean opening a chain of restaurants. Mapped out, the founders see that low-alcohol beer uses their brewing skills and their existing customer list, so it carries far less risk than the restaurants that one partner keeps championing.

Its best use is as a conversation tool. Plot every growth idea on the board, and the team quickly sees whether it is betting on several modest steps or one long jump.

The BCG growth-share matrix helps a company with several products or business units decide where to put its money. Bruce Henderson, founder of the Boston Consulting Group, introduced it around 1970. Its memorable labels have outlived much of the theory behind them, which is both its success and its risk.

Consider a mid-sized educational publisher. Its secondary-school maths textbooks dominate a flat market: a cash cow. Its new adaptive-learning app is growing quickly in a booming market, but share is small: a question mark. Its exam-revision guides lead a fast-growing segment: a star. A line of printed wall charts holds a small share of a shrinking market: a dog. The board's decision becomes sharper. Textbook profits should fund a serious push on the app, the revision guides deserve steady investment, and the wall charts are a candidate for sale or quiet retirement.

Used as a first sort rather than a sentence, it still asks the right question: where is the cash coming from, and where should it go next?

Blue Ocean Strategy contrasts two kinds of market. In a red ocean , rivals fight over the same customers with the same offer, and the water turns red with price cuts. In a blue ocean , a company creates uncontested space by offering something different enough that comparison stops making sense. W. Chan Kim and Renée Mauborgne of INSEAD popularised the idea in their 2005 book of the same name, building on research they had published through the 1990s.

Take a driving school in a crowded suburb where every competitor advertises cheaper hourly lessons. The owner runs the grid. Eliminate: the expensive branded cars, since learners care about passing, not paintwork. Reduce: generic hour-long lessons that repeat the same roundabouts. Raise: lesson flexibility, with short sessions booked by app at the last minute. Create: a test-route package that rehearses the actual local test routes at the real test times, plus a nervous-driver track with a calm instructor. The school stops being compared on hourly rate, because nobody else offers the same thing, and its costs fall even as pass rates rise.

Its lasting value is the discipline of questioning every industry assumption, one factor at a time, instead of simply trying to be a bit better at everything.

The value chain breaks a business into the activities it performs to deliver a product, so you can see which ones create value, which ones cost too much and where competitive advantage really lives. Michael Porter introduced it in his 1985 book Competitive Advantage . The idea is that a firm is not one thing but a sequence of discrete activities, and advantage comes from performing some of them better or more cheaply than rivals.

Consider a small furniture maker selling solid oak tables. Mapped along the chain, inbound logistics means sourcing timber from two local mills. Operations is the workshop, where three skilled joiners do the real craft. Outbound logistics is a hired van and a lot of breakages. Marketing relies on a well-photographed Instagram account. Service is a lifetime repair promise that customers mention in nearly every review. The picture is revealing. The owner had been thinking of cutting the repair promise to save money, but it is the activity customers value most and rivals do not offer. Meanwhile delivery damage quietly eats margin. The decision flips: keep the promise, fix the van.

Its strength is forcing precision. "We are good at quality" becomes a specific claim about a specific activity, which can be costed, protected or improved.

VRIO is a test for whether a resource or capability can give an organisation a lasting competitive advantage. It comes from the resource-based view of the firm, and especially from the work of Jay Barney, who in a 1991 paper argued that sustained advantage comes from resources that are valuable, rare, inimitable and non-substitutable. Barney later reshaped the test into VRIO, replacing non-substitutability with a question about organisation.

Consider a twenty-person software consultancy that believes its edge is "great developers". Valuable? Yes, clients pay for quality. Rare? Not really; good developers are available to anyone with a budget. So that is parity, not an edge. Then the partners try a second candidate: a decade-long relationship with the regional health service, plus a library of tested integrations with its old records systems. Valuable, rare, and very hard to copy because it took ten years of trust to build. But is the firm organised to exploit it? Sales still chases any project going, and the integration library lives in one person's head. The diagnosis is clear: a real advantage, unused. The fix is to document the library and point sales at other health bodies.

Plenty of things are valuable; the edge lies in the few that are also rare, hard to copy and actually used.

The Three Horizons model is a way of managing growth across different timescales at once. It was set out by Mehrdad Baghai, Stephen Coley and David White, then at McKinsey, in their 1999 book The Alchemy of Growth . Its core observation is that organisations fail not because they lack ideas but because the urgent demands of today's business starve the future of attention and money.

Picture a city library service under pressure to cut costs. Horizon 1 is book lending and study space: still the heart of the service, to be run efficiently with self-service kiosks and smarter opening hours. Horizon 2 is a digital-skills programme helping older residents with online forms, which is already oversubscribed and attracting funding from the council's health team; it needs dedicated staff and a proper budget line. Horizon 3 includes a tool library lending drills and sewing machines, and a pilot of after-hours study pods; each costs little and is judged on what it teaches, not on numbers. Seen together, the head of service can argue that cutting Horizon 2 to protect Horizon 1 would save money this year and lose the library its future relevance.

Today's business will always shout loudest, so tomorrow's needs a protected voice.

The Prisoner's Dilemma is the best-known puzzle in game theory: a situation in which two parties each act in their own interest and end up worse off than if they had cooperated. Merrill Flood and Melvin Dresher devised the game at the RAND Corporation in 1950, and the mathematician Albert Tucker gave it the story of two prisoners that made it famous.

Imagine two independent cafés facing each other across a high street. Each week they decide whether to hold prices or run a discount. Score the outcomes in points. Both hold: three each, healthy margins. One discounts while the other holds: the discounter wins the street's customers and scores five, the other scores nothing. Both discount: one each, busy and broke. Each owner, reasoning alone, discounts. A month later both are working harder for less. What breaks the trap is that the game repeats. In computer tournaments run by the political scientist Robert Axelrod around 1980, a simple strategy called tit for tat , submitted by Anatol Rapoport, did strikingly well: cooperate first, then copy whatever the other player did last. The cafés need not collude, which would be illegal; it is enough that each knows a discount will be met with one next week.

Its lasting lesson is about structure: when an outcome depends on the other side, think about the game you are in, and about the next round, not just this one.

The Business Model Canvas is a single sheet divided into nine boxes, each holding one part of how an organisation creates, delivers and captures value. It grew out of Alexander Osterwalder's doctoral work in the mid-2000s and became widely used after Business Model Generation , written with Yves Pigneur and published in 2010. Its appeal is that it replaces a forty-page plan with something a team can argue over around a table.

Take a two-van mobile bike-repair business in Leeds. Its segments are commuters and offices with bike-to-work schemes. The value proposition is a repair done at the kerb while the owner is at their desk. Bookings arrive through an app, relationships are kept through a monthly service plan, and revenue comes from one-off fixes plus subscriptions. Behind that sit two vans and three mechanics, a parts wholesaler as a key partner, and costs dominated by wages, fuel and parts. Drawn out, one tension becomes obvious: the subscription promise depends on mechanics' time, the scarcest resource on the sheet. That is the box to test first.

Used well, it is a thinking surface: change one box and watch what the others now have to do. Sketch two or three alternative canvases for the same idea and the choices become visible in a way a spreadsheet hides.

Jobs to Be Done starts from a simple shift in question. Instead of asking who the customer is, it asks what progress they are trying to make, in a particular situation, and what they "hire" to make it. The idea has several parents: Theodore Levitt's often-quoted line about people wanting the hole rather than the drill is usually cited as an ancestor, Tony Ulwick built a formal method around customer outcomes in the 1990s, and Clayton Christensen popularised the language of hiring and firing products in the 2000s.

Consider a town-centre public library that noticed weekday visits rising while book loans fell. Interviews revealed that many visitors were remote workers. Functionally, they were hiring the library for reliable wifi, sockets and quiet until five. Emotionally, they wanted to feel productive and less isolated than at the kitchen table. Socially, they wanted somewhere that looked professional behind them on a video call. Seen this way, the library's competitors were cafés, coworking spaces and spare bedrooms, not other libraries. The response was modest and cheap: bookable booths for calls, more sockets, and a quiet floor kept genuinely quiet. Visits held up, and the library had a clearer argument for its budget.

When it works, Jobs to Be Done widens the view of competition and narrows the view of what matters, which is a useful combination.

Crossing the Chasm describes a dangerous gap in the life of a new technology product. It comes from Geoffrey Moore's 1991 book of the same name, which built on Everett Rogers' Diffusion of Innovations . Rogers sorted adopters into five groups along a bell curve: innovators, early adopters, the early majority, the late majority and laggards. Moore's insight was that the groups are not a smooth continuum. Between early adopters and the early majority lies a chasm , where many products stall.

Moore's prescription is to stop chasing everyone and pick a beachhead : one narrow segment of pragmatists whose problem you can solve completely, including service, integration and training, the "whole product". Win that segment decisively, and its members become the references that let you move into neighbouring segments.

The model has limits. Rogers' percentages describe an idealised curve, not a law, and many products never face a sharp break between groups. Consumer products spread by fashion or network effects can jump straight to the majority. The chasm can also become an alibi, used to explain away a product that simply does not solve a painful enough problem. And picking a beachhead takes nerve, since it means deliberately saying no to revenue elsewhere.

The Product Life Cycle treats a product like an organism with a lifespan. Sales start slowly, accelerate, level off and eventually decline. The idea circulated in marketing thinking through the 1950s and was popularised by Theodore Levitt's 1965 Harvard Business Review article urging managers to exploit it. Its value is less as a forecast than as a reminder that the right strategy at launch is the wrong one later.

A small company that makes protective cases for one particular phone model lives through the whole cycle in about two years. At introduction it ships to two specialist stockists and spends heavily on product photos. In growth, demand surges as the handset sells, but copycat cases appear within months, so the founders invest in a recognisable design and faster delivery. At maturity, the cases are discounted across marketplaces and the sensible move is to cut costs and stop new colours. When the manufacturer announces the next model, the firm runs down stock and moves its design budget to the new handset. Knowing the shape in advance lets them plan the exit at the same time as the launch.

Every product is somewhere on the curve; the mistake is managing it as if it were somewhere else.

The Hype Cycle is a sketch of how expectations about a new technology rise and fall over time. It was introduced by the research firm Gartner in 1995, with analyst Jackie Fenn usually credited, and Gartner still publishes annual charts placing technologies along it. The shape is easy to remember: a sharp peak, a deep dip, and a long, gentle climb.

Consider a county council exploring drones for inspecting bridges. The trigger is a supplier's demonstration flight, which impresses everyone. Within months there are plans to survey every bridge, monitor flooding and check roofs. Then the trough arrives: battery life is short, flight permissions take time, image analysis needs skills the council lacks, and the bill is larger than forecast. Several projects are quietly dropped. A small team keeps going and finds two uses that pay off: inspecting the undersides of high bridges without closing roads, and photographing flood damage quickly. Those become routine. Years later, drones are just another inspection tool, and nobody holds a meeting about them.

It is a heuristic, not a measurement. Many technologies never reach the plateau; some skip the trough; others repeat the cycle more than once. Placing a technology on the curve is a judgement, and nobody can say with confidence how long each phase will last. Treat it as a way to read the mood around a technology, not as a timetable.

Pirate Metrics is a framework for tracking a customer's journey through a product in five stages whose initials spell AARRR, hence the pirate. It was set out by investor Dave McClure in a 2007 talk aimed at start-ups that were measuring plenty but learning little. The point is to replace one vague growth number with a chain of specific ones, so a team can see exactly where people drop away.

Take a meal-planning app. In one month, twenty thousand people visit the site. Five thousand sign up and plan their first week of meals, which the team defines as activation. Fifteen hundred are still planning in week four. Three hundred invite a friend, and four hundred pay for premium. Laid out like this, the conversation changes. The marketing team had wanted more spending on ads, but the figures show the bigger leak sits between activation and retention: most people plan one week and never return. The team adds a Sunday reminder and a shopping list that carries over unused ingredients. Retention rises, and every later stage rises with it, without an extra pound of acquisition spend.

Fix the biggest leak first; it is rarely the stage everyone is arguing about.

The Flywheel describes growth as a heavy wheel that is hard to start and hard to stop. Each push adds a little speed, and once it is turning, every further push counts for more. Jim Collins used the image in Good to Great in 2001 to argue that lasting success rarely comes from a single dramatic move but from consistent effort in one direction. Amazon's leadership became known for sketching their business as a flywheel, and the term spread through the technology industry.

Consider a regional vegetable-box company. Its loop runs like this. Fresher produce, picked the day before delivery, leads to happier customers who tell their friends, so subscribers grow. More subscribers mean bigger, steadier orders, so local farms commit volume and offer better prices and first pick. Larger orders lower the cost of each box, and the company reinvests those savings in freshness rather than taking them as profit. That makes the produce better still, and the wheel turns again. Once the founders drew this, several decisions became easier: a discount promotion that would attract bargain hunters with poor retention was dropped, because it did not push any part of the wheel, while paying for faster refrigerated vans was approved, because it pushed the first link.

A flywheel rewards patience, but only if every spoke is real.

A network effect exists when each extra user makes a product more valuable to the others. A telephone is useless if you own the only one, and early telephone companies understood that their networks became more attractive as they grew. The idea was later linked to Robert Metcalfe, whose name was attached in the 1990s to the observation that the number of possible connections grows much faster than the number of users. With ten users there are forty-five possible pairs; with a hundred, nearly five thousand.

Consider a neighbourhood tool-lending app. It is two-sided: lenders list their ladders and hedge trimmers, borrowers request them. At launch it has the classic chicken-and-egg problem: no borrower opens an app with three tools, and no lender bothers listing for an empty audience. The organisers solved it by seeding one side themselves, buying forty common tools for a community shed and listing them, and by launching street by street rather than across the whole city, since nobody will cross town to borrow a drill. Once a few streets had dense supply, borrowers came, and some became lenders. The network effect was real, but it was local: density mattered more than total size.

Network effects are powerful once they exist; getting the first dense patch is the real work.

Disruptive innovation names a particular way that newcomers overtake established firms. It was set out by Joseph Bower and Clayton Christensen in a 1995 article and developed in Christensen's 1997 book The Innovator's Dilemma . The word has since been stretched to mean any exciting change, but the original theory is narrower and more useful.

Imagine a training company that sells two-day classroom courses on management skills at a high price to large firms. A newcomer offers short video courses for a small monthly fee. At first its customers are tiny businesses that never bought training at all; the incumbent does not lose a single client and dismisses the product as superficial. Each year the videos improve, add practice exercises and coaching calls, and mid-sized firms start switching. The incumbent responds by moving further upmarket into bespoke executive programmes, where margins are higher. Each step is sensible on its own. Taken together, they shrink its market year by year.

Its real value is as a warning about your own rational choices: the customers you are happiest to lose may be where the next competitor learns its trade.

The Long Tail describes what happens to demand when the cost of offering one more product falls close to zero. Chris Anderson, then editor of Wired , set out the idea in a 2004 article and a 2006 book. Plot sales against rank and you get a tall head of a few bestsellers, followed by a long, thin tail of items that each sell rarely. In a physical shop, the tail is cut off because shelf space is expensive. Online, it can be kept, and its many small sales can add up to a large share of the total.

Picture an independent online sheet-music shop that sells digital downloads. Its ten most popular pieces, wedding favourites and exam staples, might make up around a fifth of sales. The next ninety add a little more. But beyond them sits a catalogue of tens of thousands of arrangements for unusual instrument combinations, each bought a handful of times a year, and together they bring in the largest share of revenue. Because the files cost nothing to store, the owner keeps adding arrangements and invests mainly in search and tagging, so a cellist looking for a duet with bassoon can find one. A general retailer cannot compete on that range, and the bestsellers alone would not sustain the shop.

The long tail rewards whoever makes the niches easy to find.

A feedback loop exists whenever the result of an action circles back to shape the next action. The idea comes from engineering and was given its general form by Norbert Wiener's cybernetics in the late 1940s; Jay Forrester's system dynamics work at MIT in the 1950s then carried it into business and policy. The insight is simple and permanently useful: most of what puzzles us about organisations, markets and habits is a loop we have not drawn yet.

Take a small subscription bakery. Happy customers tell friends, sign-ups grow, more revenue buys a second oven, and the loop spins faster. That is reinforcing. But each new order adds pressure on two bakers, delivery slots fill, loaves arrive late, and complaints rise until sign-ups flatten. That is balancing, and it was always there, quietly waiting for volume. The founder who blames the marketing for the plateau is looking at the wrong loop. The useful move is to name the constraint that the balancing loop is protecting, here baking capacity, and decide whether to expand it or to slow growth deliberately.

Once you can tell an engine from a brake, most strange behaviour stops being strange.

Every system holds things that accumulate. Money in an account, people on a team, trust between partners, bugs in a codebase, carbon in the air. Each of these is a stock , and it can change only through its flows : what comes in and what goes out. The language comes from Jay Forrester's system dynamics, developed at MIT from the late 1950s, and it reached a wide audience through Donella Meadows' Thinking in Systems . The familiar picture is a bathtub, a tap filling it and a plughole draining it.

Consider a software team of forty. The head of engineering wants sixty by next year and pushes recruiters hard. They hire four people a month. Meanwhile three people a month leave, a figure nobody had written down. Net growth is one person a month, so the team reaches roughly fifty-two in a year, not sixty. Doubling the recruiting budget treats the inflow; the cheaper lever might be the outflow, since keeping one more person a month is worth as much as hiring one, without the onboarding cost. The same arithmetic applies to customer churn, a backlog of support tickets or the stock of goodwill in a marriage.

Before you open the tap wider, check whether the plug is in.

The Iceberg Model is a way of looking below a single event to the forces that keep producing it. It circulates widely in systems-thinking teaching, and is often linked to the circle around Peter Senge and Daniel Kim in the 1990s, though no single inventor is clearly established. The metaphor does the work: what you see above the water is a small part of what is there, and the part you cannot see is what sinks ships.

Imagine a local council that keeps getting complaints about potholes on one estate. Event thinking sends a crew to fill this week's hole. Looking for patterns shows the holes reappear every spring on the same roads. Looking at structure reveals that the repair budget pays for patching per hole, not for resurfacing, and that contractors are paid by the job, so cheap patches that fail are rewarded. Underneath that sits a mental model: roads are a cost to be minimised this year rather than an asset to be maintained over twenty. A council that only reacts at the tip spends more every year; one that changes the contract and the budgeting assumption can stop the spring ritual.

Fixing events keeps you busy. Changing structures and beliefs keeps you from having to.

Leverage points are the places in a system where a small shift produces a large change in behaviour. The idea was set out by the environmental scientist Donella Meadows in her 1997 essay Places to Intervene in a System , which ranked twelve kinds of intervention from least to most powerful. Her list is less a formula than a warning: the places people instinctively push are usually the weakest.

Picture a hospital trust trying to cut waiting times in its emergency department. The first instinct is a parameter: add three more staff to night shifts. Waits improve briefly, then drift back. A step up is information: a live screen showing every ward's free beds, so patients are not stuck in corridors while beds sit empty upstairs. Higher still is a rule: wards must accept admissions within an hour, with discharge planning starting at admission rather than on the final morning. At goal level the question changes from "how fast do we clear the department?" to "how fast does a patient get to the right place?", which makes the whole building responsible for flow.

When pushing harder has stopped working, push somewhere else.

The Five Whys is the simplest root-cause method there is: state the problem, ask why it happened, then ask why that happened, and keep going until you reach a cause that, if fixed, would stop the whole chain from recurring. It is credited to Sakichi Toyoda, founder of the Toyota group, and was made central to the Toyota Production System by Taiichi Ohno, who described it as the basis of Toyota's scientific approach. Five is a rule of thumb, not a law. Sometimes three questions get there; sometimes seven are needed.

A florist that delivers across a city notices that wedding orders keep arriving late. Why? The van left forty minutes behind schedule. Why? The arrangements were not finished at loading time. Why? The stems arrived from the wholesaler at nine rather than seven. Why? The order was placed the afternoon before instead of two days ahead. Why? The booking form lets couples confirm a wedding with less than forty-eight hours' notice, and nobody had linked that form to the supplier's cut-off. The fix is not a faster driver or a stern word with the florists. It is a booking rule and an automatic supplier order, which ends every late wedding delivery of that kind at once.

Stop asking only when the answer is something you can redesign.

The Fishbone Diagram , also called the Ishikawa or cause-and-effect diagram, maps the possible causes of a problem in one picture. It is associated with Kaoru Ishikawa, a leading figure in Japan's post-war quality movement, who popularised it in the 1960s. The name comes from its shape: the problem sits at the head of the fish, a spine runs back from it, and the main categories of cause branch off like bones, each carrying smaller bones of specific causes.

Take a coffee roaster whose wholesale customers complain that the espresso blend tastes inconsistent. Under machines: the roaster's temperature probe drifts. Under materials: the Brazilian component changed farm in March. Under methods: two roast profiles are in use and the labels are ambiguous. Under people: the new roaster learnt the job from notes, not from a colleague. Under measurement: nobody cups a sample from every batch. Under environment: the warehouse heats up in the afternoon and beans rest longer in summer. The team's hunch was the new green beans. The diagram shows five other candidates, and cupping two weeks of batches against the roast logs points to the profile mix-up as the main culprit.

Draw the whole skeleton before you pick a bone.

The OODA Loop stands for observe, orient, decide, act. It was developed by John Boyd, a US Air Force fighter pilot and military strategist, through briefings he gave in the 1970s and 1980s. Boyd's starting point was air combat, but his argument was general: in any contest, the side that cycles through the loop faster and more accurately can disorient its opponent, who ends up reacting to a situation that has already changed.

Picture a small online retailer of camping gear when a larger rival suddenly undercuts its best-selling tent by a fifth. A slow loop looks like this: the drop is noticed in the monthly report, a pricing meeting is scheduled, and a matched price goes live five weeks later, by which time the rival has moved on to bundles. A fast loop looks different. The founder watches daily sales and competitor prices, so the drop is seen within a day. Orientation asks what the rival is actually doing, clearing old stock rather than starting a price war, which suggests not matching at all. The decision is to promote a waterproofing kit with the tent instead, and the result is visible in two days, ready for the next turn of the loop.

Speed matters, but only after you have learnt to see straight.

Plan–Do–Check–Act , often shortened to PDCA, is a four-step cycle for improving a process through small, deliberate experiments. Its roots lie in the work of the statistician Walter Shewhart at Bell Labs in the 1930s, and it was carried to Japanese industry and then the wider world by W. Edwards Deming, who later preferred "Plan–Do–Study–Act" to stress learning over inspection. It underpins much of lean thinking and the Japanese practice of kaizen , continuous improvement.

A GP surgery wants to reduce missed appointments, which run at about one in ten. The plan: text patients a reminder two days ahead, with a link to cancel, and predict that no-shows will fall to one in fifteen. The team does it for one doctor's list for a month. The check shows no-shows fell to one in fourteen, close to the prediction, but also that most cancellations came in the final evening, too late to rebook. The act stage adopts the reminder for every list and sets up the next cycle: try a second reminder the morning before, with a small waiting list ready to take freed slots.

Progress is a habit of small, honest experiments.

Goodhart's Law warns that a measure stops being reliable once it becomes a target. The economist Charles Goodhart made the original point in 1975, about monetary statistics: when a central bank leans on a particular indicator to steer policy, the relationship that made that indicator useful tends to break down. The crisp version most people quote, "when a measure becomes a target, it ceases to be a good measure", is the anthropologist Marilyn Strathern's later paraphrase.

A broadband company's support centre is judged on calls handled per agent per hour. The measure was sensible: busy agents with short queues meant customers got help quickly. Once bonuses are linked to it, call lengths fall, and so does the share of problems actually fixed. Agents transfer awkward calls, promise call-backs that never come, or end calls once the customer is told to restart the router. The figure goes up every month. Repeat calls, cancellations and complaints go up too, but they sit on another team's dashboard. Management has bought a better number and a worse service.

Watch what the number is for, not just where it is.

The Tragedy of the Commons describes how a shared resource can be ruined by people who each act reasonably. The idea was sketched in 1833 by the economist William Forster Lloyd, using the example of cattle on common pasture, and made famous by the ecologist Garrett Hardin in a 1968 essay in Science . Each herder gains the full benefit of adding one more animal but bears only a fraction of the damage, which is shared with everyone. So each adds another, and the pasture fails.

Modern commons are everywhere. An office kitchen fridge becomes a science experiment because nobody owns the clean-up. Shared cloud budgets in a company get eaten by teams who each spin up a few more servers, since the bill lands centrally. Picture a start-up with eight squads and one cloud account: within a year spending has tripled, and every squad can justify its own share. The fix is not a plea for virtue. It is giving each squad its own visible budget, a monthly report of who used what, and a simple rule for what happens when a team overspends.

Shared things last when their users can see each other and agree the rules.

In 1955 two American psychologists, Joseph Luft and Harrington Ingham, sketched a simple grid for a workshop on group dynamics and named it after their own first names: the Johari Window . It has outlived most management tools of its era because it asks an awkward question with unusual politeness. What do you know about yourself, what do others know about you, and where do those two pictures disagree?

Consider a five-person product team whose lead, Priya, prides herself on being decisive. In a retrospective she asks each person for one thing she does that slows them down. Three of them, separately, name the same habit: she rewrites tickets after they have been estimated. That is a blind spot moving into the open. In return she shares something from her hidden pane: she rewrites because the board keeps changing scope on her, and she has been absorbing it quietly. Within ten minutes the team has a better diagnosis than months of grumbling produced, and a fix: scope changes now come to the whole team, in writing.

The window is a mirror with two sides, and you only ever hold one of them.

In 1943 the American psychologist Abraham Maslow published a paper titled A Theory of Human Motivation . Its central idea, now known as Maslow's hierarchy of needs , is that human needs come in an order of urgency, and that a higher need tends to grip us only once the ones below are reasonably met. The famous pyramid is not Maslow's own drawing; others added it later, and it made the theory both more memorable and more rigid than he intended.

For decision-makers the useful move is diagnostic. When a team rejects a perfectly good plan, ask which level the plan threatens. Take a regional charity merging two offices. Leadership presents the merger as a chance for staff to grow into broader roles, a pitch aimed squarely at the top of the pyramid. Staff hear something else: will my job survive, will my commute double, will I lose the colleagues I trust? Those are safety and belonging questions, and no amount of talk about growth reaches people standing on a cracked floor. When the charity publishes a no-redundancy pledge and keeps existing teams intact for a year, the same growth pitch suddenly gets a hearing.

The model's limits are well known. The strict ordering does not hold up reliably in research: people go hungry for causes, artists trade safety for meaning, and many cultures rank belonging above individual esteem. Maslow himself described the levels as overlapping rather than as a staircase. Use the pyramid as a checklist of needs, not as a ladder people must climb one rung at a time.

The Hungarian-American psychologist Mihaly Csikszentmihalyi spent years asking climbers, surgeons, chess players and factory workers when they felt most alive. Their answers converged on a state he called flow : total absorption, a sense that time had bent, action and awareness merging. From the mid-1970s he described the conditions that make it likely, and the most practical of them fits on one chart. Put skill on one axis and challenge on the other. Flow lives in a diagonal band, the flow channel , where the two rise together.

The channel is a moving target. Every time you master a level, your skill rises and the old challenge slides you towards boredom; the cure is to raise the challenge. Every time you take on something new, you start in anxiety; the cure is to build skill or shrink the task. Staying in flow is a zigzag, not a destination.

The model has limits. Flow feels good, but feeling good is not proof of value; people can slip into flow while gaming, scrolling or polishing a slide nobody needs. Some essential work, such as compliance checks, will never be flow-friendly and needs other kinds of design. And the chart says nothing about meaning. A person in perfect flow on the wrong task is efficiently lost.

Ikigai is a Japanese word that roughly means a reason for being, or what makes life worth living. In Japan it is used modestly: an ikigai can be a grandchild, a garden, an early walk to the fish market. The diagram that made the word famous abroad is a much later Western remix. In 2014 the British blogger Marc Winn placed the word at the centre of an existing four-circle Venn diagram about purpose, and the image spread through careers advice. It is worth knowing both versions, because they answer different questions.

Imagine a hospital pharmacist, Daniel, considering a move into health-tech product work. He scores his current role: good at it, paid fairly, clearly needed, but the love has faded after twelve years. The new role scores high on love and promising on pay, while skill is partial and need is uncertain, since the start-up has not yet proved anyone will buy. The diagram does not make the decision for him. It tells him what to test: a three-month evening project with the start-up would show whether the skill gap can be closed and whether the market need is real, before he gives up a role that already sits in three circles.

Use the circles to see the gaps, and the original word to remember that meaning does not need a business model.

Nearly two thousand years ago the Stoic teacher Epictetus opened his Handbook with a distinction: some things are up to us and some are not. In 1989 Stephen Covey gave the idea a modern diagram in The 7 Habits of Highly Effective People , contrasting a large circle of concern with a smaller circle of influence inside it. Many trainers now draw three rings, with a tight circle of control at the centre, and that is the version most people mean by the name.

Take Mei, who runs a small café on a high street where the council has announced six months of roadworks. Her first week goes on concern: furious emails, late-night forecasts, refreshing the council's website. Sorting the problem into rings changes the second week. Control: she can move to a pre-order app, offer delivery to the two office blocks behind the shop and fit staff hours to the new footfall. Influence: she can join other traders to ask the council for clear signage and a loading bay, and ask her landlord for a temporary rent holiday. Concern: the roadworks themselves, the weather, whether commuters change route for good. She accepts the outer ring, works the inner two, and the café comes out of the summer smaller but intact.

Worry is energy with nowhere to go; the rings give it an address.

The Stanford psychologist Carol Dweck spent decades studying how people, especially students, respond to failure. Her work, popularised in the 2006 book Mindset , distinguishes two beliefs about ability. In a fixed mindset , intelligence and talent are largely set, and each task is a test of how much you have. In a growth mindset , ability can be developed through effort, good strategies and help from others, and each task is a chance to get better. Most people hold a mix, and the mix shifts by domain. Someone can be growth-minded about cooking and fixed-minded about maths.

Picture a ten-person marketing agency that loses a major pitch. The founder's first instinct is fixed: we are not good at big accounts, so let us stop chasing them. A growth reading asks what specifically failed. The debrief shows the creative work scored well, but the agency could not explain how it would measure results. That is a skill gap, not a destiny. The founder pairs with a freelance analyst for the next two pitches and builds a simple measurement section into the template. The third big pitch lands. Nothing about the agency's talent changed; its response to failure did.

Ability is a verb more often than people assume.

In 1999 two Cornell psychologists, Justin Kruger and David Dunning, published a paper with a memorable title: Unskilled and Unaware of It . Across tests of logical reasoning, grammar and humour, the participants who scored lowest tended to overestimate their performance by a wide margin. In the paper's own summary, those in the bottom quarter scored around the 12th percentile but placed themselves around the 62nd. The pattern became known as the Dunning–Kruger effect .

Imagine a council procurement team taking on its first software contract. The lead officer has bought furniture and vehicles for years and is sure software is just another purchase: list requirements, compare quotes, pick the cheapest compliant bid. He does not know what he does not know about data migration, licensing terms or exit clauses, so his specification looks complete to him. A twenty-minute review by a colleague who has bought software before turns up eleven gaps. The fix was not more confidence or less; it was a cheap outside check at the very point where his own judgement had no way of working.

The least visible gaps are in the instrument you use to look for gaps.

Psychologists have long described two modes of thinking. In 2000 Keith Stanovich and Richard West gave them neutral labels, and in 2011 Daniel Kahneman made those labels famous in Thinking, Fast and Slow . System 1 is fast, automatic and effortless. It reads faces, finishes sentences, senses danger and produces impressions without being asked. System 2 is slow, deliberate and effortful. It does long division, compares contracts and follows rules it has to hold in mind. Kahneman stressed that the two systems are useful fictions, characters in a story about the mind rather than places in the brain.

Take Lena, a hiring manager at a logistics firm, finishing a final interview. Within minutes System 1 has delivered a verdict: strong hire, confident, sharp, reminds her of herself at that age. On an ordinary day System 2 would approve the verdict and move on. But she has a rule: any decision that costs more than a quarter's salary gets a slow pass. She opens the scorecard agreed before the interviews and scores each criterion with evidence. The candidate is strong on two, average on three, and weak on the one that matters most for the role, managing difficult carriers. The impression was not wrong about the person; it was answering the wrong question.

Trust intuition where it has earned the right, and audit it everywhere else.

Economists call costs that have already been paid and cannot be recovered sunk costs . Textbook logic says they should play no part in deciding what to do next: the money is gone whichever path you choose, so only future costs and future benefits differ between the options. People find this remarkably hard to apply. In a well-known set of studies published in 1985, Hal Arkes and Catherine Blumer showed that people who had paid more for something were more likely to keep using it, even when it no longer served them. The tendency is known as the sunk cost fallacy , or the sunk cost trap.

Consider a software start-up that has spent £200,000 building an enterprise feature for one large prospect. The prospect has gone quiet. Finishing the feature would cost another £80,000 in engineering, and the realistic return, now that the anchor customer is wavering, looks like £50,000 over the next year. The founders' instinct is to finish: walking away seems to waste the £200,000. The tree tells a different story. Finishing nets minus £30,000; stopping nets zero and frees two engineers for the self-serve product customers are already asking for. The £200,000 is spent on both branches. Stopping does not waste it; finishing would add to the loss.

Yesterday's spending is a lesson, not a vote.

The writer and former Harvard Business Review editor Suzy Welch developed the 10/10/10 rule as a personal habit and set it out in her 2009 book 10-10-10 . The method is almost embarrassingly simple. Before deciding, ask how you will feel about each option in ten minutes, in ten months and in ten years. The numbers are not magic; they are a device for dragging attention away from the present moment, where emotion tends to dominate, towards the stretches of time where most consequences live.

Take Sam, operations lead at a furniture maker, who learns on a Tuesday that a large order for a hotel client will ship three weeks late because a supplier has failed. Option one is to say nothing yet and hope to claw back time. Option two is to call the client today. At ten minutes, calling is horrible: an irritated customer and an awkward escalation. At ten months the picture flips: the client has had time to replan its opening and the relationship has survived, whereas silence would have meant a late surprise and probably a lost account. At ten years, Sam's firm is the kind of supplier people recommend because bad news arrives early. Sam picks up the phone before lunch.

The moment of choosing is the shortest part of living with a choice.

In 1965 the psychologist Bruce Tuckman reviewed dozens of studies of small groups and noticed that they tended to pass through the same sequence on the way to doing useful work. He gave the stages rhyming names that have outlived almost everything else written about teams that decade: forming, storming, norming and performing. In 1977, with Mary Ann Jensen, he added a fifth, adjourning, for the moment a group disbands.

Picture a council setting up a six-person team to redesign its bin collection routes. In the first fortnight everyone is cordial and nothing much happens. In week three the data analyst and the depot manager clash over whether residents' complaints or lorry mileage should drive the design, and two meetings end in frosty silence. The team lead resists the urge to smooth it over. Instead she gets both to agree on a single measure, missed collections per thousand homes, and a rule that whoever owns a route's data has the final say on it. Within a month the meetings are shorter, the arguments are about evidence rather than turf, and the new routes go live on time. When the project closes, she runs a short retrospective so the lessons travel with the people.

The caution is that the stages are a tendency, not a timetable. Tuckman's original review drew largely on therapy and laboratory groups, and real teams loop back: a new member, a reorganisation or a missed deadline can send a performing team straight back into the storm. Some teams skip a stage; some never leave one. Treat the labels as a diagnosis to test, not a progress bar to fill.

Situational Leadership grew out of work by Paul Hersey and Ken Blanchard in the late 1960s, first published as the life cycle theory of leadership. The two later developed rival versions, Blanchard's known as SLII, which is why the labels vary depending on which training course you sat through. The core idea survives both: the right way to lead depends less on the leader's personality than on the follower's readiness for a particular task.

The phrase on this task does most of the work. Take a small engineering firm promoting its best developer, Priya, to lead a team. On code review she needs delegation; interfering would insult her. On running her first performance review she is a beginner, enthusiastic and slightly overconfident, so her manager directs: a script, a rehearsal, a debrief. By her third review she has seen one go badly and her confidence has dipped, so he shifts to coaching, still giving direction but spending more time on her reasoning and doubts. Six months later he is merely available. Same manager, same report, four styles in a year, all of them correct.

Its weaknesses are real. Academic tests of the model have produced mixed support, and the neat path from novice to expert is an idealisation; people do not always move through the quadrants in order. Diagnosing development level is also a judgement that can quietly harden into labelling. The best protection is to say it out loud: tell people which style you are using and why, and ask whether it fits.

The RACI matrix has no famous inventor. It emerged from project and organisational design practice in the second half of the twentieth century, sometimes under the drier name of responsibility assignment matrix, and spread because it solves a problem every organisation has: work that falls between chairs. The grid lists tasks down one side and people or teams across the top, and each cell gets one of four letters.

Consider a mid-sized charity launching a new donation page. The first attempt stalled for weeks because the digital team thought fundraising owned it and fundraising thought digital did. A one-hour session produced a grid. For the launch, the web developer and a copywriter are Responsible, the head of fundraising is Accountable, the data-protection officer and finance are Consulted because the page handles money and personal details, and trustees and the supporter-care team are Informed. Two things fell out immediately. The head of digital had been acting as a second A, which explained the stalemate, and supporter care had never been told the page existed, which explained why nobody could answer donors' questions. Neither problem needed a reorganisation; both needed a letter in a box.

Where it misleads is in its tidiness. A RACI chart records an agreement; it does not create one. If the head of digital never accepted giving up the A, the grid simply becomes a document to argue about. Overuse is the other trap: charting every minor task produces a spreadsheet nobody reads, and generous C's quietly turn consultation into a veto. Variants such as RASCI add a Supporting role, which helps on large programmes and complicates everything else.

In 1974 Kenneth Thomas and Ralph Kilmann published a questionnaire, now known as the Thomas–Kilmann Conflict Mode Instrument , building on an earlier grid by Robert Blake and Jane Mouton. Its claim is modest and useful: when people disagree, each of them behaves along two independent dimensions, and the combinations produce five recognisable modes.

Take the two co-founders of a coffee-roasting business arguing about whether to open a café. One wants the margin and the visibility; the other fears the cash it will swallow. For months they avoid the subject, which is itself a choice, and the tension leaks into everything else. When they finally meet, they almost compromise on a pop-up stall that satisfies neither. Instead they collaborate, asking what each is really protecting. It turns out to be brand presence on one side and runway on the other, and they land on a partnership with an existing café that gives them a counter and their name on the menu with no lease. That answer was only reachable because both stayed assertive and cooperative at once, which is tiring and slow.

The weakness is that the model describes behaviour in a single conflict between equals. It says little about power, about culture, or about repeated disputes where today's accommodation sets tomorrow's expectations. People also rate their own modes more flatteringly than colleagues would, so asking someone who has argued with you is more accurate than any questionnaire.

Robert Cialdini, a social psychologist, spent part of his research years observing sales trainings, fundraising operations and advertising firms from the inside, watching what reliably got people to agree. His 1984 book Influence distilled it into six principles of influence , and in 2016 he added a seventh. Each is a mental shortcut that usually serves people well, which is precisely why it can be exploited.

A small software company trying to move customers onto its new invoicing feature shows how they combine honestly. It offers existing users a free hour of set-up help before asking for anything. The in-app prompt asks a tiny question, whether they invoice monthly, and later reminds them they said so. The landing page shows that most accounting firms of their size have switched, which is true and specific. The guide is written by the company's in-house chartered accountant and says so. The support team is the same friendly people customers already email. The early-adopter offer ends on a stated date that really is the date. Uptake rises, and nobody feels tricked, because every lever points at something real.

There are limits beyond ethics. The principles were mostly studied in particular cultures and settings, effects vary in size, and some of the underlying studies have not replicated as cleanly as popular retellings suggest. Stacking all seven on one page is noisy and faintly desperate. The more reliable use is defensive: when you feel a sudden urge to say yes, ask which principle is pulling, and whether the thing would still look good without it.

Patrick Lencioni, a management consultant, set out the five dysfunctions of a team in a 2002 book written mostly as a fable about a struggling technology company and its new chief executive. The model is a pyramid, and the order matters: each dysfunction makes the one above it likely, so fixing the top while ignoring the bottom rarely works.

Imagine the five-person leadership team of a regional housing association. On paper it is fine: targets set, meetings held. In practice repair times keep slipping. Working down the pyramid explains why. The repairs director misses deadlines, but peers never challenge her because nobody wants a row. The operations head privately disagrees with the repairs target but never said so in the meeting that set it. And that silence traces back to a chief executive who treats any admission of a mistake as weakness. So the fix starts at the base. The chief executive opens the next away-day by describing a decision of hers that went badly. Over the following months meetings get noisier, the repairs target is argued about and reset, and when it slips again a colleague raises it, unprompted, within a week.

The caveats are worth stating. The model comes from consulting experience and a fable, not from controlled research, and its neat chain of causes is a simplification; trust and conflict feed each other in both directions. It fits small senior teams far better than large groups. And trust built through staged confessions at off-sites can feel performative; it is earned in ordinary behaviour, week after week.

Stakeholder thinking was put on the management map by R. Edward Freeman in 1984, who argued that a firm answers to everyone who can affect it or is affected by it, not just to shareholders. The practical tool that grew up around the idea is the stakeholder map , and its most common form is the power–interest grid usually credited to Aubrey Mendelow. It turns a long, anxious list of people who might object into four piles with four different treatments.

Suppose a secondary school's head teacher wants to move to a later start time. She lists everyone affected and places them. The governing body and the local bus operator, which would have to change its routes, land in the top right, so she meets them before announcing anything. The local authority has power but little interest, and a short briefing note keeps it comfortable. Parents and students sit bottom right, intensely interested but without a veto, so they get a clear explanation, a consultation and regular updates. Nearby shops, mildly affected, are simply monitored. The exercise produces one surprise: the bus operator, which she had nearly forgotten, is the only party that can make the plan impossible, so it gets the first meeting.

Its limits come from its simplicity. Power is not one number; there is formal authority, the ability to delay, and influence through others. The grid also encourages treating low-power groups as things to be handled rather than people with legitimate claims, which is ethically shaky and tends to backfire. And placing people is guesswork until you have talked to them, so treat the first draft as a hypothesis.

Daniel Pink's 2009 book Drive popularised a three-part account of what motivates people doing complex, creative work: autonomy, mastery and purpose . Pink did not invent the underlying science; it rests largely on decades of research by the psychologists Edward Deci and Richard Ryan into intrinsic motivation, later formalised as self-determination theory. His contribution was packaging it for managers, with a pointed message: for many kinds of work, carrots and sticks do less than we assume, and sometimes do harm.

A family-run bakery chain with six shops and high staff turnover offers a concrete case. Its first response, a bonus for shops that hit sales targets, produced creative waste logs and little else. The owners then tried the other route. Shop teams were given control of their own rota and two shelf slots each for bakes of their own devising. Bakers who wanted to learn laminated pastry got a monthly session with the head baker and a clear ladder of skills to climb. And the chain began giving its end-of-day bread to local food banks, with each shop choosing its partner. Turnover fell over the following year, and two of the shop-designed bakes became bestsellers across the chain.

It is weaker on routine, rule-following work, where Pink himself acknowledges that conventional rewards can work well, and it can be misused as cover for low pay dressed up as meaningful work. Autonomy also needs guardrails: total freedom for a team that lacks skill or shared direction is not empowerment but abandonment. The precondition is not optional.

Radical candour comes from Kim Scott, who drew on her management experience at Google and Apple in a 2017 book, spelled Radical Candor in the American original. Its premise is that good feedback requires two things at once, and that most people instinctively trade one off against the other.

Picture the editor of a small news website with a talented new reporter whose stories keep running long and burying the point. For weeks the editor softens it: great work, maybe tighten a little. That is ruinous empathy, and the next pieces are no better. A colleague's instinct is to rewrite them with a sarcastic note, which would be obnoxious aggression. The editor instead sits down, says she hired the reporter for her nose for a story and wants to see her on the front page, then puts two versions side by side: the reporter's opening and a rewrite that leads with the news. She asks what made the reporter hold it back. Within a month the openings sharpen, and the reporter starts asking for this kind of critique before filing.

The familiar misuse sits in the word radical . People quote it to license bluntness, taking the challenge and skipping the care, which is just obnoxious aggression with a slogan. Care cannot be asserted in the moment; it is built in the relationship beforehand, which is why the same words land differently from different people. Norms about directness also vary widely between cultures, and what reads as candour in one office reads as rudeness in another.

BATNA stands for best alternative to a negotiated agreement, a term coined by Roger Fisher and William Ury of the Harvard Negotiation Project in their 1981 book Getting to Yes . The idea sounds obvious and is ignored constantly: before you negotiate, work out exactly what you will do if no deal is reached. That alternative, not your hopes or the other side's opening, is the yardstick for every offer on the table.

Consider a freelance illustrator negotiating a year-long contract with a publisher that wants exclusivity and a lower day rate. Her options if it falls through: carry on with her current mix of clients, pitch to two other publishers who have shown interest, or take a part-time teaching post. She finds the second strongest, so she spends a week making it real, getting one of those publishers to a firm offer of steady work. Her walk-away is now concrete: she will not accept exclusivity on terms that pay less than that offer would. In the meeting she does not need to bluff or even mention the rival; she calmly declines the first proposal, and the publisher, which has its own deadline, drops exclusivity.

It can mislead in three ways. An imagined BATNA is not a BATNA, and overrating your alternatives leads to walking away from deals you needed. Many things do not compare cleanly, such as relationships and reputation, so the comparison needs judgement as well as numbers. And in long relationships, brandishing the alternative can win the round and sour everything after it.

Most meetings do not fail for lack of brains. They fail because everyone is thinking in a different mode at once: one person lists risks, another pitches ideas, a third is quietly annoyed and a fourth wants the numbers. Six Thinking Hats , set out by Edward de Bono in his 1985 book of the same name, fixes this with one rule: the whole group wears the same hat at the same time. He called it parallel thinking . Instead of arguing across the table, everyone looks in the same direction, then turns together.

Picture a housing association board deciding whether to turn a disused garage block into six small homes. Blue opens: one decision, forty minutes. White gathers what is known (planning status, a surveyor's rough estimate) and flags what is not: the drainage. Red goes round the table, and two members admit they dislike tenants losing parking. Said in thirty seconds, that feeling no longer leaks into every later point. Black lists contamination and neighbour objections. Yellow names rent income and a long waiting list. Green suggests modular units, or a phased start. Blue closes the loop: commission a drainage survey, then decide. One meeting instead of three.