Decide what matters before deciding anything else.
Chapter 1 · Part I
The Eisenhower Matrix
Dwight Eisenhower, 1954; popularised by Stephen Covey
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 grid puts importance on the vertical axis and urgency on the horizontal. Top right, important and urgent, is Do now: the burst pipe, the investor call moved to this afternoon. Top left, important but not urgent, is Schedule: the hiring plan, the pricing review, the conversation with a struggling colleague. Bottom right, urgent but not important, is Delegate: requests that are noisy and time-bound but would be handled perfectly well by someone else. Bottom left, neither, is Drop, and it is usually fuller than anyone admits.
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.
Consider the operations lead at a twelve-person logistics start-up on a Monday morning with nineteen items on her list. Sorting them takes ten minutes. Three are genuinely urgent and important: a failed customer integration, payroll sign-off and a driver shortage for Wednesday. Five, including a supplier contract renewal due in six weeks and a long-promised process document, are important but not urgent, so they get blocks in the diary this week. Six are urgent mainly for someone else, such as meeting invitations and a vendor's survey, and go to a colleague or get a two-line reply. The last five, among them a newsletter rewrite nobody asked for, simply leave the list. She ends the morning with eight items rather than nineteen, and two of them are the ones that would have bitten in a month.
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.
Try it: Take today's to-do list, mark each item U, I, both or neither, then put one important-but-not-urgent item in your diary before lunch.
Urgency will always find you; the matrix exists so that importance gets found too.
Fig 1 · The Eisenhower Matrix. Two questions sort any to-do list: does it matter, and must it be now?
Chapter 2 · Part I
The Pareto Principle
Vilfredo Pareto, 1890s; generalised by Joseph Juran
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.
The working method is simple. List the causes of an outcome you care about, count how often each occurs or how much each costs, sort them from largest to smallest, and see where the running total crosses most of the effect. The few causes above that line are where attention pays. Everything below it can wait or be handled by a standard routine.
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.
The principle misleads in three common ways. First, people assume the ratio instead of measuring it, announcing that a fifth of customers bring four-fifths of revenue without checking. Second, the tail is not always trivial: a rare cause can be catastrophic, and a single safety failure outweighs a hundred cosmetic ones. Third, cutting the trivial many can backfire when they are cheap to serve and quietly form the base the vital few grow from. Counting frequency is not the same as counting consequence, so the sort should use whichever measure actually matters.
Try it: Pick one recurring annoyance at work, list every cause you can think of in two minutes, then circle the two you suspect produce most of it and note what data would confirm it.
Most problems are lopsided; the skill lies in measuring the lopsidedness rather than assuming it.
Fig 2 · The Pareto Principle. A small share of causes usually drives most of the effect. Find them first.
Chapter 3 · Part I
Opportunity Cost
Named by Friedrich von Wieser, 1914; older roots
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.
The mechanics are straightforward. Lay out the realistic options for a scarce resource, estimate what each would return, and pick one. The opportunity cost of your pick is the return of the best option you rejected: not the average of the others, and certainly not the worst. If the option you chose returns less than its opportunity cost, you have made a loss, even if the accounts show a profit.
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.
The concept is easiest to misuse by ignoring it. Free things are the classic trap: a "free" conference costs two days, and an unpaid pilot costs the deal you would have chased instead. It also misleads when the alternatives are imagined too narrowly, since the best forgone option is often one nobody bothered to list, such as resting, waiting or doing nothing at all. And estimates of what you gave up are guesses by definition. You never see the road not taken, which makes opportunity cost easy to argue about and impossible to audit.
Try it: Look at the biggest commitment in your diary this week and write down, in one line, the single best thing you could do with that time instead.
Nothing is free; it is merely priced in a currency you were not watching.
Fig 3 · Opportunity Cost. The real price of any choice is the best thing you gave up to make it.
Chapter 4 · Part I
The 5/25 Rule
Attributed to Warren Buffett; the story is unverified
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.
The method has four moves. First, list up to 25 things you want to achieve over a set period, without editing. Second, circle the five that would matter most if they were the only ones completed. Third, and this is the hard part, label the other twenty an avoid list: these are not things to get to later, they are the most dangerous distractions you have, precisely because they are attractive. Fourth, put your time into the five and nothing else until they are done or deliberately revised.
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 rule's weaknesses are real. Twenty-five and five are arbitrary numbers; a team of fifty can carry more than five priorities, while one person may only manage two. Goals are not independent either. Sometimes one of the twenty is a prerequisite for one of the five, and banning it stalls the work that matters. The avoid list can also become a graveyard for things that were merely uncomfortable rather than unimportant. The rule works best as a periodic forcing exercise, revisited every few months, not as a vow.
Try it: Set a timer for three minutes, list every goal you hold for the next six months, circle the five you would keep, and write "avoid" above the rest.
The second list is the useful one: anyone can name what they want, but fewer can name what they will refuse.
Fig 4 · The 5/25 Rule. Write down 25 goals, circle 5, and treat the other 20 as things to avoid.
Chapter 5 · Part I
The Value vs Effort Matrix
Lean and product practice; no single inventor
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.
Each idea is placed on two axes. Effort runs left to right, from low to high; value runs from bottom to top. The four quadrants that result have conventional names. Top left, high value for low effort, is Quick wins: do these first. Top right, high value for high effort, is Big bets: worth doing, but they need planning, money and patience, so pick few. Bottom left, low value for low effort, is Fill-ins: fine for a slack afternoon, harmful as a strategy. Bottom right, low value for high effort, is Money pits, sometimes politely called thankless tasks: avoid them, and be wary of anyone who champions one passionately.
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.
Picture the parks team of a mid-sized town council with fourteen improvement ideas and a limited budget. They put sticky notes on a wall-sized grid. Fixing broken bins and adding signs to the busiest footpath land in Quick wins and are done within a month. A new adventure playground is a Big bet: high value and a great deal of work, so it gets a proper business case and a two-year timeline. Repainting railings nobody has complained about is a Fill-in, kept for a quiet winter week. An app for booking picnic spots, championed loudly at a public meeting, lands squarely in the Money pit once the team estimates the upkeep, and is politely shelved.
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.
Try it: Take five ideas from your current backlog, sketch the two axes on a scrap of paper, place each idea in under a minute, and note which one is the clearest quick win.
Easy and valuable is rare; when you find it, do it before someone schedules a meeting about it.
Fig 5 · The Value vs Effort Matrix. Plot each idea by what it is worth and what it costs, then start top left.
Chapter 6 · Part I
MoSCoW Prioritisation
Dai Clegg, Oracle, 1994; adopted by DSDM
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 four categories form layers. Must have covers requirements without which the delivery is pointless, unlawful or unsafe; if any Must is missing, the release has failed. Should have items are important and painful to leave out, but a workaround exists. Could have items are desirable and the first to go when time runs short. Won't have this time is the most valuable category, because it records, explicitly and in advance, what everyone has agreed not to do in this round. DSDM guidance suggests that Musts should take up no more than about 60 per cent of the effort, so that the lower layers act as contingency.
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.
Consider a small charity rebuilding its online donation page before a winter appeal. The wish list runs to twenty items. Taking card payments securely, complying with data-protection law and working properly on a phone are Musts. Gift Aid declarations are a Should, because they can be collected by follow-up email for a few weeks. A progress thermometer and personalised thank-you videos are Coulds. Integration with the old events system, which the trustees keep raising, is a Won't, written down and dated. When the developer falls ill for a week in November, the team drops the thermometer without a meeting, because that decision was taken months earlier.
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.
Try it: Take a project you are running, pick its five biggest requirements, and for each ask whether launch would be cancelled without it; whatever survives is your real Must list.
Agreeing what you will not do is the cheapest scope control there is.
Fig 6 · MoSCoW Prioritisation. Split requirements into Must, Should, Could and Won't, and mean it.
Chapter 7 · Part I
RICE Scoring
Intercom product team, c. 2016
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.
Reach is how many people the idea will affect in a set period, such as customers per quarter, counted rather than felt. Impact is how much it will move the goal for each of them, on a deliberately coarse scale; Intercom's version runs from 0.25 for minimal, through 0.5, 1 and 2, to 3 for massive. Confidence is a percentage reflecting how much evidence supports the other estimates, typically 100 for high, 80 for medium and 50 for low. Effort is the total work required, in person-months. The score is reach times impact times confidence, divided by effort: value delivered per unit of work.
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.
Picture a four-person product team at a gym-booking app weighing three ideas. A waiting-list feature would reach about 2,000 members a quarter, with an impact of 2, confidence of 80 per cent drawn from support tickets, and four person-months of effort: 2,000 × 2 × 0.8 ÷ 4 gives 800. A social feed for sharing workouts would reach more people, perhaps 5,000, but its impact is a guess at 1, confidence is 50 per cent and the effort is ten person-months, which gives 250. A one-tap rebooking button reaches 3,000 members with an impact of 0.5, full confidence and half a person-month of work, scoring 3,000. The modest button wins comfortably, followed by the waiting list. The social feed, which the founder loved, comes last, and the reasons are on the page rather than in anyone's head.
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.
Try it: Choose two ideas competing for your time, give each a rough reach, impact, confidence and effort in two minutes, and see whether the result matches your instinct.
A number with its workings shown is easier to argue with, which is exactly the point.
Fig 7 · RICE Scoring. Score each idea by reach, impact and confidence, then divide by effort.
Chapter 8 · Part I
The Kano Model
Noriaki Kano and colleagues, 1984
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.
Kano sorts features by how their presence and their absence feel to a customer. Basic needs, sometimes called must-be qualities, are simply expected: having them earns no credit, but lacking them causes outrage. Performance needs are proportional: the more you deliver, the happier people are, and they will readily compare you with rivals on them. Delighters, or attractive qualities, are unexpected: nobody complains when they are missing, but their presence produces a disproportionate lift. Two further categories complete the picture: indifferent features that nobody cares about either way, and reverse features that some customers actively dislike. Teams usually classify features with a short survey that asks how a customer would feel if a feature were present, and how they would feel if it were absent.
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.
The model has a built-in clock. Delighters decay into Performance needs and then into Basics as customers grow used to them and competitors copy them; free hotel Wi-Fi made exactly that journey. A Kano analysis is therefore a snapshot and needs repeating. It also varies by segment, since one guest's delighter is another's indifference, and survey answers about hypothetical features can differ from real behaviour. Finally, it says nothing about cost, so it is best paired with a method that does.
Try it: List five features of something you sell or run, mark each B, P or D for Basic, Performance or Delighter, and ask which Basic you might be quietly failing.
Customers never thank you for the floor, but they certainly notice when it gives way.
Fig 8 · The Kano Model. Some features prevent anger, some win praise, and a few create delight.
Chapter 9 · Part I
The Theory of Constraints
Eliyahu Goldratt, The Goal, 1984
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.
Goldratt's method has five focusing steps that loop. Identify the constraint: the step where work piles up waiting. Exploit it: get the most out of the constraint as it stands, so that it never sits idle and never works on anything defective. Subordinate everything else to it: other steps should run at the constraint's pace, even if that means they sometimes stand still. Elevate it: only now spend money or effort on increasing its capacity. Then repeat, because once that constraint is broken another step becomes the limit, and yesterday's rules must not become tomorrow's bottleneck.
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.
Consider a busy sandwich shop that cannot clear its lunchtime queue. The owner had been weighing a second till and more prep staff. Twenty minutes of watching shows that orders wait at the toaster, which handles four sandwiches at a time, while the tills and the prep counter are idle half the time. Exploiting the constraint means one person loads the toaster continuously rather than between other jobs. Subordinating means prep pauses rather than stacking cold sandwiches, and the tills group hot orders together. Only when that is not enough does the owner elevate by buying a second toaster. The queue then moves to the coffee machine, and the loop begins again.
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.
Try it: Pick a process you rely on, ask where work most often sits waiting, and write down one way to keep that step busy without spending anything.
Improving everything at once mostly improves the size of the pile in front of the slowest step.
Fig 9 · The Theory of Constraints. A system runs only as fast as its slowest step. Find it, then fix just that.
Chapter 10 · Part I
The Weighted Decision Matrix
Multi-criteria decision analysis; kin to Pugh's matrix
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.
The structure is a simple table, built in four steps. First, agree the criteria and give each a weight, as percentages that sum to 100, before anyone looks closely at the options. Second, score every option against every criterion on a fixed scale, say 1 to 5. Third, multiply each score by its weight and add up each option's total; the highest is the provisional winner. Fourth, test the result by nudging the weights to see whether the winner holds. The order matters: weights first, scores second, because setting weights after seeing the options is the easiest way to rig the outcome.
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 matrix misleads by producing false precision. A total of 3.5 against 3.4 is a tie dressed up as a decision, and scores on a five-point scale are judgements, not measurements. Criteria can overlap and count the same virtue twice, and a fatal flaw can be averaged away unless some criteria are treated as pass-or-fail before scoring begins. Testing sensitivity is the remedy: if a small shift in the weights changes the winner, the decision is closer than the table makes it look, and deserves a conversation rather than a calculation.
Try it: For a decision you are facing, write down three criteria and give them weights that add up to 10 before you score a single option.
The table does not decide for you; it shows you what you have already decided matters.
Fig 10 · The Weighted Decision Matrix. Decide what matters, weigh it, score each option, and let the totals talk.
Free preview · Part I
Keep reading
You have read the first 10 of 100 chapters of Top 100 Decision Models for Strategic Thinking. The full book has every chapter and plate, as PDF and EPUB in English, French, Polish and Spanish.