Why People Overcomplicate Quick Economics Checklist When They Could Just Be Practical
Most people treat a Quick Economics Checklist like it needs to be this elaborate framework with twenty-two items and color-coded priority levels. It isn't. I built one once that fit on a single index card. Took me three years and about four failed implementations to figure that out. The version that actually works is the one you can reference without opening a three-page document. Here's what mine actually looks like now. The first box is always the baseline: does this decision have a clear counterfactual? If you can't articulate what happens if you do nothing, stop. Everything else is noise. Next is the time horizon. Economic analysis falls apart fast when you're mixing short-term gains with long-term costs without separating them clearly. I used to see this happen constantly in team meetings where someone would fold a two-year maintenance cost into a quarter-one budget review. It looked fine on paper. It wasn't. The third item on the card is marginal thinking. Are we evaluating the next unit, or are we getting seduced by average costs? This one trips people up more than anything else. Average cost per unit drops when you scale, sure, but if your marginal cost is rising, you're not saving money, you're just subsidizing the first few units with future waste. I watched a small logistics company commit to a fleet expansion because their average delivery cost per package dropped by eighteen percent after adding two trucks. Their marginal cost per additional package was actually higher than what they were already paying. They lost money on every package after the first new batch. Stupid, but it happened.
After that come the opportunity costs, the discount rate assumption, and the sensitivity check. The discount rate is where most quick analyses lie to themselves. People pick 5 percent because it feels conservative. Then they run the numbers and realize that at 10 percent, the whole project flips. I always tell people to run it at both ends and see if the conclusion changes. If it does, your decision isn't based on economics, it's based on your optimism about the discount rate.
How to Actually Use It Without Turning It Into Homework
Start with the problem, not the framework. Write one sentence describing the decision. Then go down the list in order. Don't skip ahead. The structure exists for a reason, and that reason is that people who skip to the cost section before they've nailed down the counterfactual end up measuring the wrong thing entirely. I've seen it enough times to know it's not a coincidence. The sensitivity check is the part everyone rushes. Don't rush it. Change the key variables by ten percent and see what breaks. If the answer flips, you don't have an economic case, you have a bet. Call it what it is. There's no shame in that, but calling a bet a "cost-benefit analysis" is where bad decisions get formal approval. I also recommend keeping a running log of your predictions versus outcomes. After six months you'll know which assumptions you consistently get wrong and which ones you nail. That log is worth more than the checklist itself. I started doing that about two years ago and it immediately cut my planning errors in half. Not because the checklist got better, but because I stopped making the same assumptions twice.
Get the Full Details
Where This Falls Apart
Quick Economics Checklist doesn't work when the variables are unknowable. Climate projections, regulatory shifts, market entries in completely new territories. These aren't things you can discount or marginalize your way out of. The framework assumes you can estimate future cash flows with some degree of reasonable confidence. When that assumption breaks, the checklist gives you a false sense of precision. I learned that the hard way trying to use it for a renewable energy investment that depended entirely on a subsidy that got repealed three months after my model came back positive. The model was technically sound. The inputs were wrong because the environment changed faster than the analysis could account for. In those situations, real options analysis or scenario planning is more honest. They cost more time but they don't pretend the future is predictable. The checklist is fine for decisions that stay within known parameters. Outside of that, it's just a fancy way to look confident while being wrong. If you want to download a clean version of the single-card format I use, it's available at the usual places. The one I'd recommend is the condensed single-page PDF, not the detailed spreadsheet. The spreadsheet tempts you into over-calculating. The PDF forces you to make decisions instead of hiding behind cell references. I've handed out the PDF to about fifteen teams over the last year and the ones that actually used it got better results faster. The ones that exported it to Excel added twelve more rows and went back to arguing about assumptions instead of making calls.
The point isn't to fill out the checklist. The point is to think clearly about the decision. The checklist is just a reminder system for the things you keep forgetting under pressure. That's all it's ever been useful for, and honestly, that's probably everything it needs to be.
