Library / Business / KEVOS® original book

Outcome-First Projects by the Numbers

Purpose, measures, baselines and targets first, then options, requirements and scope, worked through one family laundry's request for a new plant

Start a project from its outcome: write the purpose, define measures, baselines and targets, then derive options, trace requirements and test every scope item against them.

10 chapters · About 110 minutes · Free to read · Intermediate project definition, benefits and business case practice

Start reading
KEVOS® LibraryBUSINESSHANDOVEROutcome-FirstProjects by theNumbersKEVOS® ORIGINAL BOOK10 CHAPTERS

About this book

Most projects arrive as a request for a thing: a new machine, a building, a system, a plant. The thing is easy to describe, price and order, and the project quickly becomes the job of delivering it. Whether it was the right thing is decided later, if at all, when the money has been spent. Starting from the outcome reverses the order. The purpose comes first, written as a few measurable benefits with their value; then the measures, the baselines and the targets; then the causes of the gap; and only then the options, the requirements and the scope, each kept only if it traces back to a target.

This book works through that sequence with numbers. It begins with the difference between a deliverable and an outcome, and between ends and means. It turns the outcome into measures using the goal–question–metric method, measures a baseline that will stand up to scrutiny, and sets targets from the purpose rather than from last year’s figure. It then works back from the gap to its causes, maps the benefits to the business changes and enabling changes they need with a benefits dependency network, derives and compares options, traces every requirement and scope item to a target, and holds acceptance testing and benefit tracking to the same measures. Each chapter follows one running case, includes a plausible error and how it was found, and ends with an exercise and its worked answer.

It is for owners, managers, sponsors, engineers and finance staff in small and medium Australian businesses. It assumes spreadsheet arithmetic and nothing more. From Approval to Benefits covers what happens to benefits after a project is approved; this book covers the definition work that comes before approval and decides what is worth approving.

The running case

Every chapter follows one fictional decision. This is an illustration. A family-owned commercial laundry in a regional New South Wales city, run by its second generation, washes, dries, irons and delivers about 60,000 kg of linen a week over six production days for a group of four private hospitals and 22 hotels and serviced apartments. Its plant is a bank of eight washer-extractors, dryers and two flatwork ironer lines, one of them from 2009. The owners ask for a new plant: a tunnel washer with a press and new dryers, a 600 m² extension to house it, RFID linen tracking and refurbished amenities, about A$6.12 million excluding GST.

Working back from what the business needs reveals a different problem. The hospital contract, more than half the laundry’s volume, is to be re-tendered within a year, at a lower price and with a requirement for 98% of deliveries on time and in full, against the laundry’s measured 91.2%. The outcome the owners need is expressed in four measures: on-time-in-full delivery, cost per kilogram, and water and energy per kilogram. The book builds those measures, finds where the gap really comes from, and shows how an option derived from the outcome, costing about A$2.44 million, meets all four targets where the requested plant meets two.

The business, its customers, its people and every number in the case are invented. None describes KEVOS® work, a real business or a real project. All amounts are Australian dollars excluding GST.

How to use the book

Read Chapters 1 and 2 first: the outcome and its value are the yardstick for everything after them. Chapters 3 to 5 turn the outcome into measures, baselines and targets, and are best read in order. Chapters 6 and 7 work back from the gap to causes and to the changes that would close it. Chapters 8 to 10 derive the options, test the scope and requirements, and carry the measures into acceptance and benefit tracking. Every calculation was checked by running it, and the KEVOS® tools linked in the chapters reproduce the capacity and option arithmetic.

This book is one of a series of KEVOS® Library books on how projects are defined, decided and delivered, and it links to the others where their subjects meet. Demand and Benefit Forecasts by the Numbers covers how large and how certain the benefits defined here are likely to be. Front-End Planning by the Numbers places outcome definition within the wider planning done before a project is committed. Stage Gates and Stopping Rules by the Numbers covers the decision points, such as the case’s later gate on a tunnel washer, at which the outcome is used to continue, change or stop. Reference Class Forecasting by the Numbers corrects the cost, schedule and benefit estimates that the options in this book rely on.

Source limits and professional responsibility

The methods are established, and the sources are listed with what each was used for. Much of the published guidance on benefits comes from government and from information systems research, written for larger organisations than most readers work in; the book uses its principles, not its procedures, and says where a small business can do with less. The case’s prices, costs, rates and performance figures are teaching values, not market data, and a real decision needs its own measurements, quotes and advice. Commercial laundries handling hospital linen work under infection-control requirements, the applicable Australian Standard, work health and safety laws and their customers’ contracts; nothing here replaces those or the competent people responsible for them. This book is general information about defining and deciding projects. It is not financial, legal, engineering or investment advice.

Who this book is for

Owners, general and operations managers, project sponsors, engineers and finance staff in small and medium Australian businesses who turn a request for equipment, buildings or systems into a project and must show what it will achieve.

What you will learn

  • Separate a requested deliverable from the outcome it is meant to cause, and state the outcome as a few measurable benefits with the value at stake.
  • Derive measures from the questions the outcome raises, and define each one tightly enough that it cannot drift or be gamed.
  • Measure a defensible baseline and set targets from the purpose, with an averaging period and a minimum acceptable level.
  • Work back from the gap to its causes, map benefits to the business changes and enablers they need, and derive options from that map.
  • Trace every requirement and scope item to a target, remove what traces to nothing, and hold acceptance and benefit tracking to the same measures.

Inside this book

Chapters

  1. 01From a request for new plant to the outcome behind itA A$6.12m request for new laundry plant set against the outcome behind it: outputs, outcomes and benefits, four measures, and why perfect washing fixes 37 of 412 failures.
  2. 02Ends, means and the value at stakeSort the laundry's aims into fundamental and means objectives, place the new plant as one means, and value the hospital contract at about A$1.41m a year of contribution.
  3. 03Measures from questions: goal, question, metricGoal–question–metric turns the laundry's outcome into four tight measures: OTIF per delivery, cost per clean kg, L/kg and MJ/kg, with a 6.1% denominator error and an absolute-gas trap.
  4. 04Baselines you can defend26 weeks of signed dockets give 91.2% OTIF, not the 95.6% the dispatch system showed; a p-chart, the A$1.711/kg cost baseline, 14.0 L/kg, 6.00 MJ/kg and their seasons.
  5. 05Targets derived from the purpose, not from the baselineTargets from the tender and the price: 98% OTIF (at most 93 failures in 26 weeks), A$1.66/kg, 10.0 L/kg and 5.0 MJ/kg, with periods, dates and a stretch, against arbitrary round numbers.
  6. 06Working back from the gap to its causesA Pareto of 412 failed deliveries and a capacity check on effective rates: ironers and dispatch cause 83%, the ironers are 20% short on peak days, and the washers are not the constraint.
  7. 07Mapping benefits back to business changes and enablersA benefits dependency network links each target to business changes, enablers, owners and dis-benefits; a zero-capex customer agreement takes OTIF from 97.8% to 98.2%.
  8. 08Options derived from the outcome, and why the choice changedBusiness as usual, do-minimum, the A$6.12m new plant, the A$2.44m outcome-derived option and a staged option scored on all four targets and on time: only one passes.
  9. 09Tracing every scope item and requirement to a targetEach scope item priced in A$ a year and failures removed; RFID and amenities trace to nothing; five requirements derived from targets; the ironer rate checked on the customer's mix.
  10. 10Holding acceptance and benefit tracking to the outcomeAcceptance tests from requirements, monthly tracking of 93 failures in 4,680 deliveries (98.01%), a seasonal energy claim corrected from 1.38 to 1.154 MJ/kg, and the tunnel gate.

Apply This in Practice

Use these KEVOS® tools to try the method from this reading with your own numbers.

References and source notes

The manuscript and worked examples are original KEVOS® writing. References inform particular concepts; their authors do not endorse this book. Web references were consulted on 28 October 2026.

  • Bent Flyvbjerg and Dan Gardner. How Big Things Get Done (2023). Supplied source, © Connaught Street Inc. and Bent Flyvbjerg, in copyright. Used as a subject map only, for the idea of beginning a project with its purpose and working backwards. No passages, chapter structure, stories, heuristics or figures are reproduced.
  • John Ward and Elizabeth Daniel, John Wiley & Sons. Benefits Management: How to Increase the Business Value of Your IT Projects (2nd edition) (2012). Main source for benefits management as a discipline and for the benefits dependency network, which links investment objectives and benefits to the business changes and enabling changes they depend on. Used in Chapters 7 and 10. The book's examples are its own; the network drawn for the case is the book's.
  • Joe Peppard, John Ward and Elizabeth Daniel, MIS Quarterly Executive 6(1). Managing the realization of business benefits from IT investments (2007). Source for the argument that benefits come from the business changes a technology makes possible rather than from the technology itself, and for building the benefits dependency network from a set of questions about the investment, with an owner for each change.
  • Infrastructure and Projects Authority (UK). Guide for Effective Benefits Management in Major Projects (2017). Source for the distinction between outputs, outcomes and benefits, for its definition of a benefit as a measurable improvement from an outcome that stakeholders see as an advantage and that contributes to organisational objectives (paraphrased), and for benefits-led planning across the project life cycle.
  • HM Treasury. The Green Book: Central Government Guidance on Appraisal and Evaluation (2022 edition) (2022). Named for its practice of setting SMART objectives before generating a longlist of options, and of appraising a shortlist against business as usual and a do-minimum option. Used in Chapters 5 and 8 for those points only.
  • NSW Treasury. TPG24-31 Benefits Management Guide (2025). Australian guidance, issued February 2025 and not mandatory, describing benefits management applied early to define the problem and shape options, used to compare options and set up monitoring, and then to track performance, and noting that it informs but does not replace evaluation. Its companion plan template records a baseline, a target and a target date for each benefit.
  • Digital Transformation Agency, Australian Government. Benefits Management Policy (2024). Named as the Australian Government policy that requires benefits to be planned and managed for digital and ICT-enabled investments by non-corporate Commonwealth entities. Cited as evidence that outcome-led benefits planning is required practice in Australian public investment; its requirements are not applied to the case.
  • Infrastructure Australia. Assessment Framework, Stage 1: Defining problems and opportunities (2021). Named for its sequence of defining the problem or opportunity with evidence before identifying a longlist of options and filtering it to a shortlist. Infrastructure Australia notes that the framework is changing, so readers should check the current version.
  • Ralph L. Keeney, Harvard University Press. Value-Focused Thinking: A Path to Creative Decisionmaking (1992). Source for starting decisions from values rather than from the alternatives on the table, and for structuring objectives into fundamental objectives and the means objectives that serve them. Used in Chapter 2.
  • Victor R. Basili and David M. Weiss, IEEE Transactions on Software Engineering SE-10. A methodology for collecting valid software engineering data (1984). Origin of goal-directed data collection, in which goals lead to questions and questions to the data collected, and source for the finding that without validation as much as half of the collected change data may be wrong. Used in Chapters 3 and 4.
  • Victor R. Basili, Gianluigi Caldiera and H. Dieter Rombach, in Encyclopedia of Software Engineering, John Wiley & Sons. The Goal Question Metric Approach (1994). Standard description of the goal–question–metric method: a measurement goal stated for an object, purpose, viewpoint and focus, refined into questions, each answered by metrics. Chapter 3 applies it outside software.
  • Robert E. Park, Wolfhart B. Goethert and William A. Florac, Software Engineering Institute, Carnegie Mellon University. Goal-Driven Software Measurement: A Guidebook (CMU/SEI-96-HB-002) (1996). Source for extending goal–question–metric with indicators, so that each measure is traced to a business goal and to the chart or table that will be used to decide. Used in Chapter 3.
  • George T. Doran, Management Review 70(11), 35–36. There's a S.M.A.R.T. way to write management's goals and objectives (1981). Origin of the SMART test for objectives, in Doran's wording specific, measurable, assignable, realistic and time-related. Chapter 5 uses it as a writing check, not as a method for choosing target values.
  • Orlena C. Z. Gotel and Anthony C. W. Finkelstein, Proceedings of the IEEE International Conference on Requirements Engineering, 94–101. An analysis of the requirements traceability problem (1994). Source for the distinction between tracing a requirement back to where it came from (pre-specification traceability) and forward into design and test (post-specification traceability), and for the finding that most traceability problems lie in the first. Used in Chapter 9.
  • ISO, IEC and IEEE. ISO/IEC/IEEE 29148:2018 Systems and software engineering: Life cycle processes: Requirements engineering (2018). Named by number and scope as the international standard for requirements processes and the information items they produce. No clauses are quoted.
  • Standards Australia. AS 4146:2024 Laundry practice (2024). Named by number and scope as the Australian Standard for handling, laundering, transporting and storing clean and soiled textiles in hospital and other laundries, which superseded AS/NZS 4146:2000. Treated in the case as a constraint every option must meet; no clauses or values are quoted.
  • Amazon. Leadership Principles (current online statement). Primary source for the company's stated principle that leaders start with the customer and work backwards. Quoted once in Chapter 1, with Bryar and Carr's account of how the practice is used.
  • Colin Bryar and Bill Carr, St. Martin's Press. Working Backwards: Insights, Stories, and Secrets from Inside Amazon (2021). Former Amazon executives' account of writing a press release and frequently asked questions for a proposed product before building it. Mentioned in Chapter 1 as one practitioner form of working backwards; no passages are reproduced.

Continue exploring

← All Library books