# How to Do a Cost Benefit Analysis: 6 Steps and the Errors That Skew It Canonical URL: https://headwayskills.com/knowledge/decision-making/cost-benefit-analysis/ Markdown URL: https://headwayskills.com/knowledge/decision-making/cost-benefit-analysis.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving decision-making at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer A cost benefit analysis puts every cost and benefit in the same units so you can compare them. Here are the six steps, and the errors that quietly skew the result. ## Key facts - Title: How to Do a Cost Benefit Analysis: 6 Steps and the Errors That Skew It - Category: Decision Making - Primary skill: Decision-Making - Related skills: Influence, Communication - Primary keyword: cost benefit analysis - Source page: https://headwayskills.com/knowledge/decision-making/cost-benefit-analysis/ ## What this page covers - A cost benefit analysis puts every cost and benefit in the same units so you can compare them. Here are the six steps, and the errors that quietly skew the result. - Practical guidance for cost benefit analysis - How this topic connects to Decision-Making ## Detailed explanation A cost benefit analysis is a structured way to compare what a decision will cost against what it will return, by converting both sides into the same units — usually money — and seeing which side is larger. You frame the decision, list every cost and every benefit, put a price on them, adjust future amounts to what they are worth today, and compare the totals. If the benefits clear the costs, the case holds. The arithmetic is the easy part. Two people can run the same analysis on the same project and reach opposite conclusions, and it is almost never the math that separates them — it is what each of them decided to count. ## How to do a cost benefit analysis in six steps The published guides disagree about whether this is a four-step or a six-step process, but they are describing the same sequence with the boundaries drawn in different places. Harvard Business School Online compresses it into four steps; the project-management guides from Asana, Wrike, and ProjectManager spread the same ground across five or six. The six-step version is below, because the two steps that usually get folded into their neighbors — scoping at the front and stress-testing at the back — are the two most often skipped in practice. ### 1. Frame the decision before you touch a number Write down exactly what you are deciding, over what time period, and from whose point of view. Most guides open here for a reason: this step also fixes your objective, the resources and people involved, the timeline, and which data you are going to need. Everything downstream inherits this frame, so a vague question produces a vague answer no amount of later precision can rescue. The time horizon deserves a deliberate choice rather than a default. Forecasting accuracy falls off the further out a project runs, so extending the window does not make the analysis more thorough — it just makes the later years more fictional. Pick a period you can actually estimate, and say in writing that you picked it. ### 2. List every cost and every benefit, including the ones without invoices Costs come in four kinds, and the guides are consistent about them. Direct costs are the obvious ones — materials, labor, equipment. Indirect costs are the overhead the project draws on: utilities, rent, administration. [Opportunity costs](/knowledge/decision-making/how-to-calculate-opportunity-cost/) are the value of whatever you give up by choosing this option. Intangible costs are real effects that carry no price tag, such as a dip in morale or in customer satisfaction. Benefits divide the same way — direct, indirect, and intangible — where intangible covers things like improved morale, brand perception, and customer loyalty, and can reach past your own team into vendor collaboration or knowledge shared across departments. This is the step where analyses actually fail. Bright Hub PM identifies omitting relevant costs and benefits, whether by accident or by design, as the most common error in the whole method: the result is not merely imprecise, it is misleading, because the missing item is usually the one that would have changed the answer. Their fix is deliberately mechanical — map the direct and indirect effects of the action on a cause-and-effect flow chart before you price anything, so the gaps become visible while they are still cheap to fill. Opportunity cost is the item most often missed. The usual mistake is to treat only the alternatives already on the table as the cost of choosing, when the real comparison is everything else those resources could be doing. Miss that and you can end up confidently picking the best of three options when the correct answer was none of them. ### 3. Put both sides into the same currency You cannot compare a list of costs to a list of benefits until they are measured the same way, which in practice means assigning a monetary value to each line. Start with the items that already have figures attached — quotes, salaries, license fees — and work outward toward the ones that do not. The intangibles are where judgment enters, and where the second common error lives. Bright Hub PM's other headline mistake is flawed valuation: overestimating a benefit or underestimating a cost, often because a single generic appraisal technique gets applied to items that do not suit it. Where something genuinely [resists pricing](/knowledge/decision-making/weighted-decision-matrix/), the honest move is to name it, state the proxy you used and why, or leave it out of the total and flag it separately in the write-up. An intangible you have labeled is information; an intangible you have quietly assigned a convenient number to is a thumb on the scale. ### 4. Run the comparison Now the arithmetic, and it is short. Present value converts a future amount into what it is worth today. Net present value applies that to the whole project — total discounted benefits minus total discounted costs. The benefit-cost ratio divides one by the other. The decision rule the guides converge on is simple: a positive NPV and a ratio above 1 mean the project pays for itself, and the higher the ratio, the more room for error you have. Two figures are worth adding. The payback period tells you how long until accumulated benefits cover the initial outlay, which matters when cash timing constrains you as much as total return. And the discount rate you chose in step one can materially change the NPV on its own — which is exactly why the next step exists. ### 5. Stress-test the assumptions Sensitivity analysis is the step that separates a defensible case from a confident-sounding one. You change one variable at a time — cost of capital, sales volume, timeline, labor cost, demand — and watch what happens to the NPV, the ratio, and the payback period. What you are looking for is not a better number but a threshold: how far a given assumption has to move before the recommendation flips. Do not try to model every scenario. Testing the handful of variables most likely to shift is both more useful and more manageable than a sprawling matrix, and it tells you the one thing a single-point estimate never will — whether your conclusion is robust or balanced on a knife edge. ### 6. Make the call, and write down why [State the recommendation](/knowledge/communication/concise-communication/), and state it as a decision rather than as a number. A bottom line quoted to the nearest dollar implies a precision the estimates behind it cannot support, so give the figure with its range and its key assumption attached. Then record what you assumed, what you could not price, and what would have to change for you to decide differently. That record is what lets the decision be revisited later without starting over — and it is what protects you if the forecast turns out wrong for reasons that were flagged at the time. Notice what happens at this point in the process. Every step before it can be [checked by someone else](/knowledge/decision-making/getting-a-second-opinion/); this one cannot. The method narrows the range and exposes the assumptions, then hands the choice straight back to you — which is why it is worth having an honest read on [your own decision habits](https://assessment.headwayskills.com/) before a call this size lands on your desk. ## The habits that decide whether the numbers are worth anything Read back over those six steps and count how few of them are arithmetic. Framing, listing, valuing, stress-testing, recommending — each is a judgment call, and each gets better with practice rather than with a better spreadsheet. Three in particular do most of the work. **Decision-Making**, as a defined skill, is what keeps the process honest. It covers knowing whether the call is yours to make in the first place and what your organization's guidelines allow, working from data and hard facts rather than instinct, deliberately getting another opinion — including from someone likely to disagree — and accepting a good-enough answer instead of chasing certainty. It also means recognizing the traps that quietly corrupt an analysis from the inside: anchoring on the first estimate you saw, hunting only for the figures that support the option you already preferred, overconfidence in your own numbers, and the sunk-cost pull to keep funding something because of what has already gone into it. **Influence** is what happens to the analysis afterward. Almost nobody builds one of these for themselves; they build it to move someone who controls a budget or an approval. That means understanding what the approver actually values before you decide which benefits to quantify, presenting the drawbacks alongside the upside so the case reads as honest rather than sold, handling objections by listening to them fully instead of defending, and taking a partial win when full approval looks unlikely. Done this way it is the opposite of massaging the numbers — it is how a sound case survives contact with the people who have to act on it. **Communication** decides whether any of it lands. A finished analysis has to survive a five-minute conversation or a single page, which means leading with the recommendation instead of walking someone through your working, being brief, and being explicit about which figures are known and which are estimated. It also means picking the medium on purpose: writing when the numbers need to be documented and checked, a conversation when the assumptions are the thing in dispute. Sharpening those is less about learning another formula and more about knowing which of them is currently your weak link. That is what the free Work Skills Test measures — the full set of twelve work skills this framework treats as buildable, these three included — so you can [see which one to build](https://assessment.headwayskills.com/) rather than guess. You may already do parts of this without giving it a name: pausing on a rushed call, checking a figure before you trust a feeling about it, asking one skeptical colleague before you commit. Those instincts are the raw material. The distance between them and a case that holds up under questioning is mostly structure and repetition, not some aptitude you either have or lack — you can close it and still decide like yourself. It also tends to matter more as you go, because the decisions you own get larger and less supervised the further into a career you get, and a flawed method is cheapest to fix while the stakes are still small. If you have read this far measuring your own approach against these six steps, you have already done the part most people skip — examining how you decide, not just what you decided. ## Find out where your decision-making actually stands The only thing left is to get a straight answer about your own starting point. The Work Skills Test is a **free** self-assessment that scores you across all twelve work skills behind decisions like these — decision-making, influence, and communication among them — and tells you in plain terms which ones will make the biggest difference to the calls you make at work. It takes about 7 minutes and replaces a vague sense that you should get better at deciding with a specific place to start. **[Take the skills test](https://assessment.headwayskills.com/)** *Free, and about 7 minutes from start to results.* ## Who this is for - Professionals building practical workplace skills - Readers looking for specific, usable work advice - Managers, educators, and coaches supporting career readiness ## Common questions ### What is this guide about? A cost benefit analysis puts every cost and benefit in the same units so you can compare them. Here are the six steps, and the errors that quietly skew the result. ### Which Headway skill does this connect to? This guide connects primarily to Decision-Making. It also relates to Influence, Communication. ### What is the recommended next step? Use the free Work Skills Test to reflect on which work skill to improve next. ## Related pages - https://headwayskills.com/knowledge.md - https://headwayskills.com/knowledge/decision-making.md - https://headwayskills.com/knowledge/influence.md - https://headwayskills.com/knowledge/communication.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/decision-making/cost-benefit-analysis/ Preferred summary: "A cost benefit analysis puts every cost and benefit in the same units so you can compare them. Here are the six steps, and the errors that quietly skew the result." ## Change log - 2026-07-07: Content collection version published.