4 Starting a Business The Default Library ======================================== The Smallest Possible Version ----------------------------- Almost every failed first business fails the same way: someone spends months building something nobody asked for, then finds out too late. The fix isn't a better idea — it's building the smallest possible version of the idea first, and letting real people tell you whether to keep going before you've spent your savings finding out. If you have little or no experience starting something, this is the single most important idea to absorb before any other business advice: you don't know if your idea works until a stranger pays for it (or clearly would). Everything else — the logo, the perfect website, the business plan — can wait. Validation can't. The trap almost everyone falls into The instinct, when excited about an idea, is to go build it: the app, the product line, the polished storefront. This feels like progress — you're doing something. But building in isolation means you're making a hundred guesses (what people want, what they'll pay, how they'll use it) without checking any of them, and you only find out which guesses were wrong after you've spent the time and money on all of them at once. The smallest possible version isn't a worse product. It's the fastest, cheapest way to learn whether you should build the bigger one at all. This idea has a name in the startup world — the Minimum Viable Product (MVP) — but don't let the jargon shrink it. The core insight applies to a bakery, a consulting practice, or a jewelry line just as much as a tech startup: find the smallest thing you can offer real people that tests your core assumption, before committing to the full version. What "smallest possible" actually looks like It's smaller than most beginners think. A few real patterns: Sell it before you build it. Take orders, deposits, or firm interest for a product that doesn't fully exist yet — then build only once you know people actually want it. A famous early example: a founder built a fake "working" software demo, and when people tried to use it, a person behind the curtain manually did the work by hand. It looked automated; it was really just a person, testing whether the idea mattered before writing a line of real code. Do it manually first. Before automating or scaling anything, do the service yourself, by hand, for a handful of real customers. A meal-subscription idea can be tested by cooking and delivering meals yourself for two weeks before touching kitchen equipment or hiring anyone. If it doesn't work manually and small, it won't work automated and big. Offer the narrowest possible slice. Instead of "a platform for all local services," start with just one service, in one neighborhood, for one type of customer. A narrow version that actually works beats a broad version that's never been tested. Use what already exists. A landing page instead of a full app. A spreadsheet instead of custom software. A folding table instead of a storefront. Borrowed, cheap, or manual tools are a feature at this stage, not a compromise — they let you test the idea before you've invested in the infrastructure. The question every small version should answer Before building anything, get painfully specific about the one belief your whole idea depends on — the thing that, if false, means the idea doesn't work. Then design the smallest, cheapest test of exactly that belief. Not "will people like this?" (too vague to test) but "will at least 10 people in my target group pay $20 for this within two weeks of me offering it?" A sharp, falsifiable question turns a vague hope into a real experiment — one with an actual answer, not just a feeling. Talk to people before you build anything at all Before even a small version, the cheapest test of all is a conversation. Real prospective customers, asked well (see How to Talk to Customers), can tell you an enormous amount about whether a problem is real and worth solving — for free, before you've spent a dollar. Skipping this step is the second-most common beginner mistake, right behind building too much too soon. Why this feels uncomfortable (and why that's fine) Building small feels unsatisfying — it doesn't look like the "real business" you pictured, and a rough version invites rejection faster and more visibly than a polished one you can hide behind for months. That discomfort is the point. A small, embarrassing version that gets honest feedback in two weeks is worth more than a polished version that gets honest feedback in eight months — by then, you've spent the eight months either way. The only question is whether you spent them learning or guessing. When to build the bigger version Once your small version gets a real signal — people actually paying, actually returning, actually referring others, not just being polite when you ask — that's your cue to invest further. Growth from there is still gradual: expand the smallest version that's working rather than leaping straight to the full vision. Each stage earns the next. The takeaway Most first businesses fail from building too much before checking whether anyone wants it. Build the smallest possible version that tests your core assumption — sell before you build, do it manually before automating, offer the narrowest useful slice — and get a sharp, falsifiable answer fast and cheap. Talk to real customers before spending a dollar. Discomfort with a rough version is normal; it's the price of learning fast instead of guessing expensively. Try this: write down the one belief your idea depends on most, in a single testable sentence ("X people will pay $Y for Z within N weeks"). Then design the cheapest, fastest experiment you can run this week to test exactly that — not the whole idea, just that one sentence. Sources & Further Reading Sources - The Minimum Viable Product concept is central to Eric Ries's Lean Startup methodology, itself building on earlier "customer development" work by Steve Blank. Go deeper - 📘 The Lean Startup — Eric Ries (the foundational text on this whole approach) - 📘 The Four Steps to the Epiphany — Steve Blank (denser, more rigorous customer-development roots) - 📘 The $100 Startup — Chris Guillebeau (small, real-world examples across many industries) - 🌐 Companion piece: How to Talk to Customers (in this library) Where Money Actually Comes From ------------------------------- "Revenue," "margin," "cash flow" — three words that sound like accounting homework but are really just the answer to one question every business must answer: does more money come in than goes out, and does it arrive in time to pay the bills? Here's the whole picture, and a calculator to make it real. You don't need an accounting degree to run a business well. You need to genuinely understand four ideas, because almost every business failure traces back to a gap in one of them. Revenue is not profit Revenue is all the money that comes in from sales — the big, exciting number. Profit is what's left after everything it cost you to earn that revenue. A business can have booming revenue and still be losing money every single day, if costs run ahead of it. "We're doing great, we sold $50,000 this month!" means nothing on its own — the only honest question is what was left after every cost was paid. Margin: the percentage that decides everything Margin is the slice of each sale that's actually profit, after the direct cost of delivering it. Sell a $25 item that costs you $10 to make, and your margin is $15 — 60%. Margin is the single number that tells you how much room you have: high-margin businesses can survive slow months and mistakes; razor-thin margins mean every inefficiency threatens survival. Fixed vs. variable costs Costs come in two flavors, and confusing them is a classic beginner trap. Fixed costs stay the same whether you sell one unit or a thousand — rent, insurance, a salary. Variable costs rise and fall directly with how much you sell — materials, packaging, payment processing fees. Understanding this split tells you exactly how many sales you need before you stop losing money and start making it — which brings us to the most useful number in this whole piece. See your breakeven point Set your own numbers below and watch exactly how many sales it takes to cover your costs — and how profit changes above and below that line: Interactive · Breakeven Calculator 💰 Fixed costs per month$2,000 🏷️ Price per sale$25 📦 Variable cost per sale$10 🛒 Units sold this month100 $2,500Revenue 60%Margin –$500Profit / Loss You don't need to sell "a lot." You need to sell past one specific number — your breakeven point — and every sale after that is where the business actually happens. Cash flow: the killer nobody warns beginners about Here's the trap that catches even genuinely profitable businesses: profit and cash are not the same thing, and timing can kill you even when the math works. If you have to pay your supplier today but your customer doesn't pay you for 60 days, you can be profitable on paper and still unable to pay rent this month — a very real, very common cause of failure called a cash flow gap. The trapYou pay for materials or staff now; your customer pays their invoice weeks or months later. The gap between "money out" and "money in" has to be survived somehow. Why it killsEven a healthily profitable business can run out of actual cash in the bank during that gap — and once you can't pay a bill, it doesn't matter how good next quarter looks. The fixesGet paid faster (deposits, shorter payment terms, invoicing promptly), keep a cash buffer for exactly this gap, negotiate longer terms with your own suppliers, or watch it closely enough to see a gap coming before it arrives. The one habit that prevents most of this You don't need fancy software starting out — a simple spreadsheet, checked weekly, tracking money in, money out, and what's coming in the next 30 days, catches most cash problems while there's still time to act. The businesses that get blindsided are almost always the ones that only look at their numbers once a quarter, or never at all. The takeaway Revenue isn't profit; margin tells you how much room you have per sale; fixed and variable costs together determine your breakeven point — the number of sales where you stop losing money. And even a profitable business can fail from a cash flow gap, when money owed to you arrives later than money you owe. Track your numbers weekly, not quarterly, and know your breakeven point cold. Try this: plug your own real (or planned) numbers into the calculator above and find your actual breakeven point. If it's higher than you expected, that's not bad news — it's exactly the kind of thing better to learn now, on a slider, than three months into the real thing. Sources & Further Reading Scope. Standard small-business financial concepts (revenue, margin, fixed/variable costs, breakeven analysis, cash flow) presented for general education — not accounting or tax advice for your specific situation. 📘 Profit First — Mike Michalowicz (a practical, cash-flow-first approach for small businesses) 📘 Simple Numbers, Straight Talk, Big Profits! — Greg Crabtree 🌐 Search "cash flow vs profit small business" — short, practical explainer videos 🌐 Companion piece: Pricing Without Fear (in this library) Pricing Without Fear -------------------- Almost every first-time founder makes the same mistake, and it's not the one they worry about. It's not pricing too high. It's pricing too low — out of fear, guilt, or a guess dressed up as strategy. Pricing well is less about spreadsheets and more about confronting a feeling. Here's how to do it with your eyes open. Setting a price feels like stating your worth out loud, which is exactly why it's terrifying — and exactly why beginners flinch and underprice. But price isn't a moral statement about you. It's a business decision with real mechanics, and once you see the mechanics clearly, the fear loosens its grip. The trap: pricing based on your own comfort, not the customer's value The instinct is to ask "what would I feel okay charging?" — and that question is quietly sabotaging you before you've even started, because it has nothing to do with what the customer is actually getting. The right question is entirely different: what is this worth to the person paying for it? You're not pricing your time or your materials. You're pricing the value of the outcome someone gets from you. A plumber who fixes a burst pipe in twenty minutes isn't charging for twenty minutes — they're charging for stopping your basement from flooding. A consultant's advice that saves a company $100,000 isn't worth an hourly rate — it's worth a meaningful share of what it saved. Price disconnected from the value delivered is just a guess wearing a number. Two ways to price, and why one usually wins Cost-plus pricing — add up your costs, tack on a markup — is simple and intuitive, which is exactly why beginners default to it. Its problem: it caps your price at "my costs plus a bit," completely ignoring how much the outcome is actually worth to the customer. You can end up leaving enormous value on the table for a customer who would have gladly paid far more. Value-based pricing — starting instead from what the outcome is worth to the customer — nearly always allows for a higher, fairer price, especially for services and expertise rather than commodity goods. It requires more discipline (you have to genuinely understand your customer's situation) but it's the pricing model nearly every profitable service business eventually grows into. For physical products with real competition, cost-plus and market-rate comparison still matter as a floor and a reality check — but even there, value (brand, quality, convenience, trust) explains why two nearly identical products can carry very different prices. The psychology worth knowing A few well-documented patterns in how people actually perceive price, useful once you understand them and dangerous if you don't: Price signals quality, for better and worse. In the absence of other information, people often use price itself as a proxy for value — a too-low price can trigger suspicion ("what's wrong with it?") rather than excitement. Underpricing doesn't just cost you margin; it can actively hurt how your work is perceived. Anchoring shapes perception. The first number a customer sees sets a mental reference point that colors everything after it (see The Biases That Fool Everyone). Showing a higher-tier option first, or a reasonable "regular price" before a discount, genuinely changes how the same lower price feels. Round numbers feel different from precise ones. Prices ending in .99 can feel like a deal (rounding down psychology); a very precise, "custom-calculated" number can feel more justified and less arbitrary for premium services. Neither is universally right — it depends on the positioning you want. Options change the decision, not just the price. Offering three tiers instead of one often increases average revenue, because customers compare options to each other more easily than they judge a single price in isolation — and a well-placed middle option often becomes the obvious, comfortable choice. A simple way to actually find your number Research the real range. What do comparable options actually cost? This sets a plausible floor and ceiling, not your final answer. Estimate the value delivered, as concretely as you can — money saved, time saved, pain avoided, or joy created. This is your ceiling's true justification. Price meaningfully below that value, so the customer clearly wins too — value-based pricing isn't about extracting the maximum possible; it's about a fair trade where both sides come out ahead. Say the number without an apology. No "sorry, but," no over-explaining, no hedging in your voice. A price stated plainly is taken far more seriously than the same price stated nervously. Raising prices later is normal, not a betrayal New founders often fear that raising a price later is somehow unfair to earlier customers. In reality, pricing evolves constantly as you understand your value better and your costs and demand shift — nearly every successful business raises prices over time, and most customers barely notice or mind, because value evolves too. Being underpriced forever isn't loyalty to your customers; it's often a slow drain on the very business that serves them. The takeaway Beginners underprice far more often than they overprice, usually from pricing off their own comfort instead of the customer's actual value received. Value-based pricing (start from the outcome's worth to the customer) usually beats cost-plus pricing (start from your costs) for anything beyond a basic commodity. Price signals quality, anchoring shapes perception, and multiple tiers change how people decide. Research the range, estimate the value, price meaningfully below it, and state your number plainly. Try this: for whatever you're pricing (or considering pricing), write down the real value it delivers to the customer in concrete terms — money, time, or pain saved — before you write down a single dollar figure for yourself. Let the value number come first. Sources & Further Reading Sources - Value-based vs. cost-plus pricing is standard marketing and pricing strategy; the psychology of price-as-quality-signal, anchoring, and tiered-option effects are documented in behavioral economics and pricing research (e.g., work associated with Dan Ariely and others on choice and pricing). Go deeper - 📘 The Strategy and Tactics of Pricing — Nagle, Hogan & Zale (the standard pricing-strategy text, more advanced) - 📘 Predictably Irrational — Dan Ariely (the psychology of price and decisions, very readable) - 🌐 Search "value based pricing vs cost plus" for accessible practical breakdowns - 🌐 Companion piece: Where Money Actually Comes From (in this library) — for the margin math behind any price you set The Legal Bare Minimum ---------------------- Most first-time founders either ignore the legal side entirely until something goes wrong, or freeze up trying to "get everything perfect" before starting anything. Neither is right. Here's the actual short list of legal basics that matter early — enough to protect yourself without stalling for months on paperwork. This isn't legal advice for your specific situation — rules vary significantly by country, state, and industry, and a real lawyer or accountant is worth the money once you're earning real revenue. But knowing the shape of what matters lets you ask the right questions and avoid the mistakes that catch beginners most often. Business structure: the decision that actually matters early The core early decision is what legal "shape" your business takes, because it determines your personal liability — whether your house and savings are at risk if the business gets sued or can't pay a debt. Sole proprietorship / being unincorporated. The default if you do nothing — you and the business are legally the same entity. Simplest to start, but it means no separation between business and personal liability: if the business is sued or owes money, your personal assets are exposed. Fine for very low-risk, low-liability side activities; risky once real money or real risk is involved. LLC (or local equivalent — many countries have a similar "limited liability" structure). Creates a legal separation between you and the business, so in most cases your personal assets are protected if the business faces a lawsuit or debt it can't pay. Relatively cheap and simple to set up in most places, and the most common recommendation once you're operating for real, not just testing an idea. Corporation. More complex, more paperwork, more formal governance — usually only worth it once you're raising outside investment, bringing on co-founders and shareholders, or reaching a scale where its specific tax and structural advantages start to matter. Most beginners don't need this on day one. The single biggest legal upgrade a beginner can make is the move from "just me" to a liability-limiting structure — it's often the cheapest insurance you'll ever buy. Contracts: get the important ones in writing, even informally A surprising amount of small-business risk comes from agreements that were never written down. A few worth prioritizing early: With clients or customers, even a simple written agreement — scope of work, price, payment timing, what happens if something goes wrong — prevents the majority of disputes, which usually arise from two people remembering a verbal conversation differently, not from bad faith. With co-founders or partners, in writing, from day one: who owns what percentage, who decides what, what happens if someone wants to leave. This feels unnecessary among friends starting out excited together — which is exactly why it matters most then, before money or disagreement makes it emotionally loaded. With contractors or freelancers you hire, a basic agreement covering scope, payment, and who owns the resulting work product (this isn't always automatic — clarify it). A short, clear written agreement, even one page, beats an elaborate verbal understanding every time a disagreement actually happens. Taxes: separate from day one, and know your rough obligations Two habits prevent nearly all early tax pain: Open a separate business bank account immediately, even before you're required to. Mixing personal and business money is the single most common cause of tax-time chaos and headaches for new founders — untangling a year of mixed transactions is far harder than never mixing them. Set aside a percentage of every payment you receive for taxes, in a separate savings account, the moment it arrives. Many new founders spend what looks like "all profit" and then face a tax bill they didn't save for — the fix is embarrassingly simple: pay yourself taxes first, treat that money as already gone. Beyond that, tax obligations (sales tax, self-employment tax, quarterly estimated payments, and more) vary enormously by location and business type — this is the area most worth a short paid consultation with a local accountant early on, since a single conversation can prevent expensive mistakes. Licenses and permits: check, don't assume Depending on your location, industry, and business type, you may need a local business license, a specific professional license, health or safety permits, or sales tax registration. There's no universal list — it depends entirely on where you are and what you're doing. The reliable move: check your local government's small business resources directly rather than assuming either "I definitely need permits" or "I definitely don't." Insurance: the protection people forget until they need it General liability insurance (protecting against claims of harm caused by your business) and, if relevant, professional liability insurance (protecting against claims your advice or work caused a loss) are inexpensive relative to the protection they offer, and most beginners skip them entirely until an incident makes the gap painfully obvious. (See Insurance: Paying to Not Be Wiped Out, in this library, for the broader logic of why insurance is worth it.) What can genuinely wait Not everything needs to be perfect on day one. Trademark registration, detailed employee handbooks, complex intellectual property filings, and elaborate governance structures can usually wait until you have real revenue, real risk, or real reason — spending weeks perfecting these before you've validated your idea (see The Smallest Possible Version) is a classic way beginners stall without ever actually starting. The takeaway The legal bare minimum for most beginners: choose a liability-limiting business structure (often an LLC or local equivalent) once real risk is involved, get important agreements in writing even informally, separate business and personal finances from day one and set aside taxes as you earn, check local licensing requirements rather than assuming, and consider basic liability insurance. Everything more elaborate can usually wait until the business has proven itself. Try this: if you're taking your idea seriously, do two things this week regardless of anything else: open a separate bank account for the business, and look up your local government's small-business licensing page for your specific activity and location. Both are free or cheap, and both prevent real future headaches. Sources & Further Reading Sources - General small-business legal structure concepts (sole proprietorship, LLC, corporation and their liability implications) are standard across most jurisdictions, though specific rules, names, and tax treatment vary significantly by country and region — this piece describes the shape of the decision, not jurisdiction-specific advice. Go deeper - 🌐 US: SBA — choosing a business structure - 🌐 UK: gov.uk — set up a business - 📘 The Small Business Start-Up Kit — Peri Pakroo (practical, US-focused but broadly instructive) - 🌐 Search "[your country] small business legal requirements" as a starting point, then confirm with a local professional This is general information, not legal or tax advice for your specific situation — confirm details with a local lawyer or accountant before relying on them. How to Talk to Customers (Before You Build Anything) ---------------------------------------------------- You can validate or kill a bad idea in an afternoon of honest conversations — before spending a single dollar building it. Most beginners skip this step, or do it in a way that quietly lies to them. Here's how to do it right. Talking to potential customers sounds obvious and easy. It's actually a skill most people get subtly wrong in the same way: they ask questions that feel like research but are secretly designed to get reassurance instead of truth. Fix that one flaw and customer conversations become the highest-leverage hour you can spend before building anything (see The Smallest Possible Version). The trap: leading questions that flatter you Ask someone "would you use an app that helps you cook healthier meals?" and almost everyone will say yes — it's a hypothetical, it's polite, and agreeing costs them nothing. This is the single most common mistake in early customer conversations: asking about a hypothetical future, which people answer with hope and politeness rather than truth. You walk away encouraged by data that was never real. People are terrible at predicting what they'd do. They're excellent at accurately reporting what they've already done. The fix is a shift that changes everything: stop asking about the future, and ask about the past. Instead of "would you," ask "did you" or "when was the last time." Past behavior is real data. Hypothetical future behavior is often just kindness wearing a lab coat. The Mom Test: a simple filter for good questions A useful mental test, borrowed from a well-known startup guide: would this question get an honest, useful answer even from your own mother, who loves you and doesn't want to hurt your feelings? "Do you think my business idea is good?" fails instantly — of course she'll say yes. "How do you currently handle this problem?" passes — it's about her actual life, not your idea, so even someone who loves you unconditionally would answer it honestly, because it isn't a referendum on you at all. Every question you plan to ask can be run through this filter. If the honest answer requires the other person to risk hurting your feelings, rewrite the question so it doesn't. Questions that actually work "Walk me through the last time you dealt with [the problem]." Real, specific, recent behavior — the gold standard of customer research. "What have you already tried to solve this?" Reveals whether the problem is painful enough that people have already spent effort or money on it — a much stronger signal than any opinion about your idea. "What's the hardest part about that?" Digs past the surface complaint toward the real friction, which is often not what you assumed going in. "Tell me about the last time that happened." If someone struggles to recall a recent, specific instance, the problem likely isn't urgent or frequent enough to build a business around — a genuinely useful negative signal, delivered gently. "What are you using now, and what do you like or dislike about it?" Existing behavior and existing tools reveal real constraints and real competition your idea will actually face. What to avoid entirely Don't pitch during discovery. The moment you describe your idea, you contaminate the conversation — people start being nice to your idea instead of honest about their problem. Keep discovery conversations focused entirely on their experience; save the pitch, if you need one at all, for later and separately. Don't ask "would you pay for X?" — a hypothetical about money is just as unreliable as any other hypothetical. A far stronger question: "would you pay for it right now?" — a real, immediate ask (even a small deposit or pre-order) is the only thing that reliably separates true interest from polite enthusiasm. Don't only talk to people who already like you. Friends and family are the least reliable source of honest feedback about a business idea, precisely because they don't want to hurt you. Seek out strangers in your target group whenever possible. How many conversations is enough You don't need a formal study — somewhere between 5 and 15 real conversations with people genuinely in your target group is usually enough to spot a clear pattern: either the same problem and frustration keeps coming up unprompted, or it doesn't. A consistent pattern across even a handful of honest conversations is a far stronger signal than a hundred hypothetical "yes" answers to a leading survey question. The takeaway Customer conversations are only useful if they surface truth instead of politeness. Ask about specific past behavior, not hypothetical future behavior — "when did you last," not "would you." Run every question through the Mom Test: would even your mother answer honestly? Avoid pitching during discovery and avoid hypothetical money questions; a real ask (a deposit, a pre-order) beats any amount of polite enthusiasm. A handful of honest conversations beats a hundred leading ones. Try this: write down the exact three questions you'd ask a prospective customer this week, then run each one through the Mom Test before you ask anyone anything. Rewrite any question your mother couldn't answer honestly without risking your feelings. Sources & Further Reading Sources - The "Mom Test" framework and the emphasis on past-behavior over hypothetical-future questions comes from Rob Fitzpatrick's widely-used customer-discovery methodology, itself building on Steve Blank and Eric Ries's customer-development and Lean Startup work. Go deeper - 📘 The Mom Test — Rob Fitzpatrick (short, sharp, and entirely built around this one idea) - 📘 The Four Steps to the Epiphany — Steve Blank (deeper customer-development methodology) - 🌐 Search "customer discovery interview questions" for further real-world question banks - 🌐 Companion piece: The Smallest Possible Version (in this library) Reading the Business You Work For --------------------------------- Most employees, including talented, hardworking ones, never learn to read the business they work inside — what actually makes it money, what its numbers mean, or how their own role connects to either. That gap quietly caps careers. The people who advance fastest almost always understand the machine, not just their part of it. You don't need an MBA to think like an owner. You need a handful of concepts that most companies never bother explaining to their own employees — not out of secrecy, usually, just habit. Once you have them, meetings, strategy decks, and your own promotion case all start making a different kind of sense. Your company has a business model — find out what it actually is Every company answers the same basic question in its own way: who pays us, for what, and why do they keep paying? This is the business model, and it's rarely stated as plainly as it should be internally. Is your company selling one-time purchases or ongoing subscriptions? Who is the actual customer — is it the end user, or someone else who pays on their behalf (as with advertising or many B2B software deals)? Is growth coming from new customers, from existing customers spending more, or both? If you can't explain in two sentences how your company actually makes money, you're working in the business without understanding it. This isn't trivia. It changes how you interpret nearly everything you see at work — why leadership is obsessed with a metric that seems oddly specific, why a reorganization happened, why one team gets resources and another doesn't. The P&L: the document that explains most decisions A Profit & Loss statement (P&L) is simply revenue minus costs, and most strategic decisions inside a company trace back to someone trying to move a number on this document. You don't need to read a full financial statement to benefit from the concept — you need to know the shape: Revenue — money coming in. Cost of goods/services — what it directly costs to deliver what's sold. Operating expenses — everything else it costs to run the business (salaries, rent, marketing, tools). Profit — what's left. Once you see this shape, a huge amount of corporate behavior stops feeling mysterious. A hiring freeze, a "do more with less" push, a sudden focus on "efficiency" — these are usually the P&L talking, even when nobody in the room says so directly. Learning to ask "which line on the P&L does this affect?" is one of the fastest ways to understand why a decision is happening, not just that it's happening. Connect your own role to the money This is the single highest-leverage shift available to any employee: stop thinking of your job only in terms of tasks, and start tracing how your work actually connects to revenue or cost. Every role connects somehow — some obviously (a salesperson closing deals), some less obviously (an engineer's reliability work preventing costly outages, a support team's speed protecting renewal revenue). Employees who can clearly articulate this connection — "my work matters because it does X, which affects Y, which the business cares about" — are consistently seen as more valuable and more promotable than equally skilled peers who can't make that link. It's not political spin; it's genuinely a different, more useful way of understanding your own work. What "moving the needle" actually means You'll hear this phrase constantly, and it has a precise meaning worth internalizing: a needle-moving contribution is one large or strategic enough to visibly affect a metric leadership actually tracks — revenue, retention, cost, a key operational number — as opposed to work that's real and useful but too small or indirect to show up at that level. This isn't a judgment on smaller work's worth — most work in any company is, appropriately, not needle-moving on its own. But understanding the distinction explains a lot about how promotion and visibility decisions actually get made, often in ways that feel unfair from the inside until you can see the underlying logic: the same hours of effort get valued very differently depending on how directly they connect to something the business is measuring. Reading a room of executives Executives, in meetings, are almost always asking a small number of underlying questions, however they're dressed up in the moment: does this grow revenue, protect revenue, cut cost, or reduce risk? A proposal, an update, or a request framed in those terms — explicitly, not left for them to infer — tends to land dramatically better than the same substance framed only in terms of effort or process. This isn't about flattery; it's about speaking the language the room is actually thinking in, whether or not anyone says so aloud. Why this understanding compounds over a career Early career, most people are evaluated on execution: can you do the assigned task well? As careers progress, evaluation increasingly shifts toward judgment: can you decide what should be done, and why it matters to the business? That shift is exactly where business literacy stops being optional. Two equally hardworking people can have very different trajectories, and the difference is often that one of them learned to see the machine — the model, the P&L, the metrics leadership actually watches — and the other never did, through no fault of their own, simply because nobody handed them this lens. How to actually build this literacy You don't need permission or a course. Read your company's public materials if it's public (earnings calls and investor materials are usually surprisingly plain-spoken about what the business actually cares about). Ask your manager directly: "which metrics does leadership look at for our area, and how does my work affect them?" — a question that signals seriousness rather than ignorance. And when you see a decision that puzzles you, practice the habit of asking "what business problem might this be solving?" before assuming it's simply arbitrary. The takeaway Understanding the business you work for — its actual business model, the shape of a P&L, and how your specific role connects to revenue or cost — is one of the highest-leverage things an employee can learn, and most never do. It explains puzzling decisions, changes how your work is perceived, and is exactly the shift careers increasingly reward as they progress from "can you execute" to "do you understand what should be done and why." None of this requires an MBA — it requires asking a few better questions and paying attention to the machine, not just your part of it. Try this: in your next 1:1, ask your manager directly which metrics leadership actually watches for your team, and how your work connects to them. Most managers are glad to be asked — and the answer will change how you see your own job. Sources & Further Reading Sources - General business-literacy concepts (business models, P&L structure, the shift from execution to judgment across a career) reflect widely-taught management and career-development frameworks. Go deeper - 📘 Financial Intelligence — Karen Berman & Joe Knight (finance for non-finance managers, genuinely accessible) - 📘 The Personal MBA — Josh Kaufman (a broad, readable survey of core business concepts) - 🌐 Search "how to read a P&L" and "[your company] investor relations" if public — free, direct insight into what leadership tracks - 🌐 Companion piece: Where Money Actually Comes From (in this library) — for the underlying mechanics of revenue, margin, and cash flow The Mental Models Top Operators Use ----------------------------------- Ask people who've run large organizations, built companies, or made careers of consequential decisions what actually separates good judgment from bad, and the same handful of thinking tools keeps coming up — not tied to any industry, any title, or any org chart. These are those tools. A mental model is a compact way of thinking about a situation — a lens you can apply again and again across completely different problems. Nobody is born with these; they're collected, usually the hard way, over years of decisions that went right and decisions that went expensively wrong. This piece hands you a working set without the tuition. They apply whether you're running a company, leading a team of five, managing your own career, or just deciding what to do with a Saturday. Executives prize them because executives face an unusually high volume of consequential, ambiguous decisions — but the models themselves belong to anyone willing to actually use them. Thinking about trade-offs Opportunity cost Every choice is really a choice against every other thing you could have done with that same time, money, or attention. The true cost of a decision isn't just what you spend — it's the best alternative you gave up to spend it. Use it when: evaluating whether something is "worth it" — the real comparison is never "this vs. nothing," it's "this vs. the next-best use of the same resource." Margin of safety Build in a buffer between what you expect to happen and the point where things actually break — because your estimates are always somewhat wrong, and reality rarely cooperates exactly on schedule. Borrowed from engineering (bridges are built to hold far more than expected load) and value investing. Use it when: setting budgets, timelines, or any commitment based on a forecast — assume the forecast is optimistic, and plan for that. Optionality Some choices open future doors; others close them. All else equal, a decision that preserves your ability to change course later is worth more than an identical-looking decision that locks you in — because the future is uncertain, and keeping options alive has real value even when you can't yet say which option you'll want. Use it when: comparing two similar-looking paths — ask which one leaves you more able to adapt if you learn something new next month. Thinking about problems Inversion Instead of asking "how do I succeed at this," ask "what would guarantee failure here" — then make sure you're not doing any of those things. Working backward from disaster is often faster and clearer than working forward toward an ambiguous goal, because failure modes are usually easier to name than success paths. Use it when: stuck on a hard, ambiguous goal — flip the question and see how much clarity the reverse view provides. First-principles thinking Instead of reasoning by analogy ("this is like that, so we should do what worked there"), break a problem down to its fundamental, verifiable truths and reason back up from there. Analogy is fast but inherits other people's hidden assumptions; first principles is slower but occasionally finds an answer analogy never could. Use it when: everyone assumes something "has to be done this way" — ask what's actually, physically or logically true, versus what's just convention. Second-order thinking The first effect of a decision is rarely the only one — ask not just "then what happens," but "then what happens after that." A policy that solves today's problem can quietly create next year's bigger one; the best operators habitually run at least two steps ahead before committing. Use it when: a decision looks obviously good — push past the immediate, appealing effect and ask what it sets in motion next. Thinking about focus The 80/20 rule (Pareto principle) In many systems, roughly 80% of results trace back to roughly 20% of causes — a small share of customers, features, or efforts often drive most of the value. This isn't a precise law, but the pattern recurs often enough to be a genuinely useful first question. Use it when: everything feels equally urgent — ask which small slice of your effort is actually producing most of your results, and protect that slice fiercely. Occam's razor Among competing explanations that fit the facts equally well, the simplest one is usually right. Not because complexity is impossible, but because every added assumption is another place to be wrong — simple explanations have fewer ways to fail. Use it when: diagnosing what went wrong — resist the elaborate theory until the simple one has genuinely been ruled out. "What would have to be true?" Instead of arguing directly for or against a plan, ask what facts and conditions would need to hold for it to succeed — then go check, honestly, whether those conditions actually exist. This reframes debate away from opinion and confidence, toward specific, checkable claims. Use it when: a team is stuck arguing opinions in circles — redirect the conversation to naming and testing the underlying assumptions instead. Thinking about time Compounding Small, consistent advantages — in skill, reputation, relationships, or systems — build on themselves and grow non-linearly over time, exactly like compound interest (see Compound Interest Will Blow Your Mind). The temptation is always to judge an effort by its unimpressive early returns; the discipline is trusting the curve long enough for it to bend. Use it when: deciding whether to keep investing in something slow-building — ask whether the mechanism genuinely compounds, not just whether this week's result looks small. Reversible vs. irreversible decisions Sort decisions by whether they can be undone. Reversible ones ("two-way doors") deserve speed — decide, learn, adjust. Irreversible ones ("one-way doors") deserve real deliberation. A common failure mode is applying slow, careful process to fast, reversible decisions, and fast, careless process to the few that truly can't be undone. (See How to Make a Hard Decision.) Use it when: a decision feels stuck in analysis-paralysis — check whether it's actually reversible; if it is, that alone should speed you up. None of these models are clever tricks. They're just disciplined habits of asking a better question before committing — which is most of what good judgment actually is. Why executives lean on these so heavily People in senior decision-making roles face an unusual combination: high stakes, incomplete information, and a volume of decisions too large to fully analyze each one from scratch. Mental models are a way of pre-compiling good judgment into fast, reusable questions, so that even under time pressure, a decision gets run through a few battle-tested lenses instead of pure instinct or panic. This is exactly why operators who've made many decisions, across many years, tend to speak in these patterns almost automatically — they're not smarter in the moment, they're running better-tested software. The genuinely good news: none of this requires a title. A first-time founder weighing a pivot, an employee deciding whether to take on a new project, a person deciding whether to move cities — all of these are exactly the kind of high-stakes, ambiguous, information-poor decisions these models were built for. Rank matters far less than the willingness to actually run the question through the model instead of reacting on instinct. The takeaway A working set of mental models — opportunity cost, margin of safety, optionality, inversion, first-principles thinking, second-order thinking, the 80/20 rule, Occam's razor, "what would have to be true," compounding, and reversible-vs-irreversible — turns ambiguous, high-stakes decisions into a series of better, faster questions. Experienced operators lean on these not because they're smarter in the moment, but because the models are pre-tested shortcuts to good judgment, available to anyone willing to actually use them. Try this: take one decision you're currently sitting on and run it through just two of these — "is this reversible?" and "what would have to be true for this to work?" Notice how much clearer the decision gets before you've done anything else. Sources & Further Reading Sources. These models are drawn from a range of well-documented sources: Charlie Munger's writing and talks on "a latticework of mental models," Jeff Bezos's shareholder letters (reversible/irreversible decisions, "one-way and two-way doors", 2015 letter), Roger Martin's strategy work ("what would have to be true", in A. G. Lafley and Roger Martin, Playing to Win, 2013), classical logic and philosophy (Occam's razor), engineering and value-investing practice (margin of safety), and general decision science (opportunity cost, second-order thinking, the Pareto principle). 📘 Poor Charlie's Almanack — Charlie Munger (the original "latticework of mental models" case) 📘 The Great Mental Models (series) — Shane Parrish / Farnam Street 📘 Principles — Ray Dalio (decision-making frameworks from an investing career) 🌐 Companion pieces in this library: How to Make a Hard Decision and The Biases That Fool Everyone Co-Founders: Choosing, Splitting, and Not Breaking Up ----------------------------------------------------- Two friends start a company at a kitchen table. Neither wants to make it awkward, so they shake hands on "fifty-fifty" and get to work. Eighteen months later one of them is doing all the work, the other has taken a job elsewhere, and he still owns half the company. Nobody did anything illegal. They just never had the conversation. Choosing a co-founder is one of the biggest decisions in an early business, and it is usually made faster and more casually than choosing a flatmate. This piece is about doing it on purpose. Do you even need one? A co-founder is not a requirement. Plenty of businesses, especially service businesses, shops and one-person products, are started and run by one person. A partner is worth it when they bring something you genuinely lack and can't easily hire: a skill (one builds, one sells), a network, capital, or simply the stamina of two people carrying a hard thing together. A partner is not worth it just because starting alone feels lonely, or because a friend is enthusiastic. Enthusiasm is cheap in month one. What matters is who is still showing up in month twenty. A co-founder is not a hire you can let go. Choose them the way you would choose someone to share a mortgage with. The questions to ask before you shake hands Most partnerships that break do so over things that could have been discussed at the start. Before you commit, sit down and answer these out loud, together: Time: Is this full-time for both of us? If not, when, and what happens if one person can't make that jump? Money: Who is putting in cash? How long can each of us go without a salary? (Two people with very different savings have very different patience.) Roles: Who decides what? Who has the final word on product, on money, on hiring? Ambition: Is this a lifestyle business that pays us well, or a company we want to grow big and maybe sell? Both are fine. Wanting different ones is a slow-motion breakup. Exit: If one of us wants out in two years, what happens to their share? If a question feels too awkward to ask now, it will be far more awkward to argue about later, when there's money on the table. Try a small project first. The best test of a working partnership is working together. A weekend build, a pilot with five customers, a month of real effort. You learn more about someone from one missed deadline than from ten enthusiastic dinners. Splitting the equity Equity is who owns what share of the company. There's no single correct formula, but there are two traps. Trap one: the reflexive 50/50. An equal split can be exactly right when two people really are contributing equally. The trouble is when it's chosen to avoid a conversation. Researchers Thomas Hellmann and Noam Wasserman studied 1,476 founders in 511 young companies and found that roughly a third of teams split equally. Equal splits were linked to lower valuations when the companies first raised money, and the effect was strongest in teams that decided the split quickly. The authors argue this mostly reflects teams glossing over real differences between founders, rather than equality being bad in itself. Trap two: deciding by who had the idea. Ideas are cheap; execution is the business. Weigh what each person will contribute over the next few years (time, skills, money, risk taken) more heavily than who said "what if" first. Ask about each founder Why it matters Full-time or part-time? Time is the main thing being contributed early on Cash put in? Money at risk deserves recognition (or treat it as a loan) Salary given up? A founder working unpaid is investing too Hard-to-replace skill? The person who can build or sell the product carries the most weight early Vesting: the clause that saves friendships The single most useful protection is vesting: founders earn their shares over time instead of receiving them all on day one. If a founder leaves early, the company can buy back the unearned part. Typical schedules run three to five years, often with a "cliff" of six or twelve months, meaning nothing is earned until the cliff date, and then shares are earned steadily after that. Go back to the kitchen-table story. With vesting, the friend who left after eighteen months would keep only the part he had earned, and the rest would go back to the company, available for whoever actually builds it. Without vesting, the person still working is stuck carrying a passenger. Vesting isn't about distrust. It protects whichever of you ends up staying, and neither of you knows yet who that will be. In the US there's a tax detail founders often miss: if you receive shares that vest over time, you may need to file an 83(b) election with the IRS, and the legal deadline is 30 days after the shares are transferred. Missing it can create a large tax bill later. Rules elsewhere differ, so this is exactly the moment to pay for an hour of a lawyer or accountant's time. Put it in writing Everything above belongs in a founders' agreement (or a shareholders' agreement, depending on your country and company type): who owns what, the vesting schedule, roles, how decisions are made, and what happens if someone leaves, gets ill, or wants to sell. As The Legal Bare Minimum in this library puts it, write this down on day one, while everyone is still friends. It is the cheapest insurance a young company can buy. This is general information, not legal or tax advice. Company structures, equity rules and tax treatment vary by country. Have a qualified local professional review your agreement. The takeaway A co-founder should bring something essential you can't easily hire, and should share your answers on time, money, roles, ambition and exit. Test the partnership on a small project before committing. Split equity by what each person will contribute over the next few years, not by who had the idea or by reflex. Make founders' shares vest over time, and put the whole deal in writing while everyone is still on good terms. Try this: if you have, or are considering, a co-founder, each of you write down your answers to the five questions above (time, money, roles, ambition, exit) separately. Then swap papers. The places where your answers differ are your first agenda. Sources & Further Reading Sources - Hellmann, T. & Wasserman, N. (2011), The First Deal: The Division of Founder Equity in New Ventures, NBER Working Paper 16922 (1,476 founders in 511 ventures; about a third split equally; equal splits linked to lower pre-money valuations, especially when decided quickly). - Vesting periods and cliffs: typical US practice as summarized in standard references on equity vesting (3–5 years; 6- or 12-month cliffs). - 83(b) election deadline: US Treasury Regulation 26 CFR § 1.83-2(b) ("not later than 30 days after the date the property was transferred"). Go deeper - 📘 The Founder's Dilemmas — Noam Wasserman (built on data from about 10,000 founders of 3,500 startups; the definitive book on co-founder decisions) - 🌐 NBER — The First Deal (Hellmann & Wasserman) - 🌐 Companion piece: The Legal Bare Minimum (in this library) — structures, contracts and the other early paperwork Starting Something Inside a Company ----------------------------------- In 1968, a chemist at 3M named Spencer Silver was trying to make a super-strong glue and made a weak one instead: it stuck, but peeled off cleanly. He spent about five years promoting it inside the company and couldn't convince anyone it was useful. Then in 1974 a colleague, Art Fry, used it to keep bookmarks from falling out of his church hymn book. Even then, the first test launch in 1977 flopped. The product only took off after a second, better-designed trial, and reached shops nationwide in 1980 as the Post-it Note. The lesson isn't "good ideas win." It's that good ideas inside companies need someone to carry them, often for years, past people who are busy and skeptical. That person is doing something very close to starting a business, just with someone else's money. You don't have to quit to be an entrepreneur The word for this is intrapreneur, coined by Gifford and Elizabeth Pinchot in a 1978 paper and later defined by Gifford Pinchot as "dreamers who do": people who take responsibility for creating an innovation inside an organization. In 1985 Steve Jobs described the original Macintosh team in exactly these terms. The appeal is real. You get the company's customers, money, brand and expertise, and you keep your salary. The trade-off is also real: you don't own the result, and you have to win over people who can say no. Inside a company, your first customer isn't the market. It's the person who controls the budget. Everything from the founder pieces in this library still applies: start with the smallest possible version, talk to customers before you build, know where the money comes from. What changes is how you get permission and resources. Step 1: Find a problem leadership already cares about The fastest way to get an internal idea killed is to pitch it as your idea. The fastest way to get it funded is to pitch it as the answer to a problem someone senior already worries about. Before you pitch anything, find out what your leadership is measured on (see Reading the Business You Work For for how). Then frame your idea in those terms: Weak pitch Strong pitch "I'd love to build a self-service help center." "Support tickets grew faster than headcount last year. A help center could absorb the most common questions. I'd like to test it on our top ten." "We should try a subscription option." "Our biggest customers reorder every month anyway. A subscription could lock in that revenue. Can I trial it with twenty of them?" Step 2: Get a sponsor Almost no internal project survives without a sponsor: someone with enough authority to protect it, find it a little money, and defend it in meetings you're not invited to. Your manager may be that person, or may help you find them. A sponsor is not someone who likes your idea. A sponsor is someone who will spend a little of their own reputation on it. Ask directly: "If this pilot works, would you back taking it further?" Step 3: Ask for a small, time-boxed pilot Executives say no to big, open-ended requests and yes to small, bounded ones. Don't ask for a team and a year. Ask for: A narrow scope — one product line, one region, twenty customers. A fixed time — six or eight weeks. A clear measure of success, agreed in advance — "If at least 30% of the trial customers stay on after the free period, we propose a wider rollout." A clear way to stop — what result would mean you drop it. Setting the stop condition yourself is powerful. It shows you're managing risk, not just asking for money, and it makes "yes" much easier to say. Step 4: Write it down, briefly Many companies run on documents. A one-page proposal, written plainly, travels further than a slide deck, because people can forward it. Amazon is well known for a version of this: teams write the press release and FAQ for a product before building it, to force clarity about who it's for and why they'd care. Your page needs only five things: the problem (in the business's terms), the proposed test, what it costs, how you'll measure it, and what you'll do with each possible result. Step 5: Report honestly, including failure When the pilot ends, report the numbers you agreed on, good or bad. A clean "it didn't work, here's what we learned, here's what I'd try next" builds more trust than a stretched success story. People who run small, honest experiments get given bigger ones. A few honest warnings Famous "free time" policies are less than they seem. Google's "20% time" is often credited with creating Gmail, but its creator, Paul Buchheit, has said it was never a 20% project, and by 2013 reporters were describing the policy as largely dead (Google said in 2020 that it still existed). In most companies, side projects happen on top of your real job. Don't let one quietly sink your main responsibilities. Credit can be messy. Ideas that succeed acquire many parents. Keep a simple written record of what you proposed and when, and give generous credit to others; it tends to come back. Know your contract. Many employment contracts say that work you do related to the company's business belongs to the company. If your idea is really a business you want to own, read your contract before you build it on company time. The takeaway You can be an entrepreneur without leaving your job: an intrapreneur borrows the company's customers and resources and, in exchange, has to win permission. Frame your idea around a problem leadership already cares about, find a sponsor who will spend some of their credibility on it, ask for a small, time-boxed pilot with success and stop conditions agreed in advance, write it down on one page, and report the results honestly either way. Try this: write one paragraph for an idea you've had at work, structured as: "Problem leadership cares about → the smallest test I could run → how we'd know in six weeks whether it worked." If you can't fill in the first part, that's the thing to find out first. Sources & Further Reading Sources - Post-it Note history (Silver's adhesive 1968; Fry's hymnal bookmark 1974; failed "Press 'n Peel" test 1977; US launch 1980): standard histories of 3M's product, as summarized in the Wikipedia entry Post-it Note and its cited sources. - "Intrapreneur" coined by Gifford and Elizabeth Pinchot (1978 white paper, Intra-Corporate Entrepreneurship); "dreamers who do" from Gifford Pinchot's Intrapreneuring (1985); Steve Jobs's 1985 Newsweek remark about the Macintosh team. - Google 20% time, Paul Buchheit's statement that Gmail "was never" a 20% project, the 2013 Quartz report and Google's 2020 statement: as summarized in the Wikipedia entry Side project time and its cited sources. Go deeper - 📘 Intrapreneuring — Gifford Pinchot III (the book that named the idea) - 📘 Working Backwards — Colin Bryar & Bill Carr (former Amazon executives on the press-release-first method and written proposals) - 🌐 Companion pieces in this library: Reading the Business You Work For and The Smallest Possible Version Judging a Proposal: The Outside View ------------------------------------ In 1957, the Sydney Opera House was budgeted at £3.5 million and scheduled to open in January 1963. It opened in October 1973, ten years late, and cost A$102 million. The building is now one of the most loved in the world, which makes the point more uncomfortable, not less: the people who approved it were not fools, and the plan was not obviously bad. The estimate was simply built the way almost every estimate is built, from the inside. If part of your job is saying yes or no to other people's plans, the most valuable skill you can learn is how to look at a proposal from the outside. The planning fallacy In 1979 the psychologists Daniel Kahneman and Amos Tversky named a pattern they kept seeing: people predicting how long a task will take tend to imagine how this project will go, step by step, and underestimate how long it will actually take. They called it the planning fallacy. Later work by Dan Lovallo and Kahneman widened it to include underestimating costs and risks and overestimating benefits. It shows up even in small, familiar tasks. In a well-known 1994 study by Roger Buehler and colleagues, students estimated when they'd finish their senior thesis. Their average guess was about 34 days. Even their worst-case guess averaged about 49 days. The actual average was about 56 days, and only around 30% finished within their own estimate. The people writing the plan are the ones most likely to believe it. That's not dishonesty. It's what being close to a project does to everyone. Inside view vs. outside view Kahneman described two ways to forecast: The inside view: start from this project's own plan (its tasks, its team, its schedule) and add it up. This is how nearly all proposals are written. It feels rigorous, and it systematically leaves out the things nobody has thought of yet. The outside view: ignore the details for a moment and ask, how did similar projects actually turn out? What did the last five software migrations, product launches, or office moves really cost and take? The outside view usually wins, because the reference projects include all the surprises the planners couldn't foresee. Formalized as reference class forecasting, the method was developed for practical use by the planning researcher Bent Flyvbjerg and adopted as official guidance by the UK Department for Transport in 2004. One worked case: Edinburgh's tram line was forecast at £320 million, including a 25% contingency. A reference-class analysis put a more cautious estimate at £400 million. The line opened three years late at a final cost of £776 million. The outside view wasn't perfect, but it was much closer. Seven questions to ask about any proposal You don't need a database of megaprojects to use this. You need better questions. Next time a plan lands on your desk: Question What it's testing "What happened the last few times we, or someone like us, tried this?" Pulls in the outside view. If nobody knows, that's a finding. "What's this estimate based on?" Separates measured numbers from hopeful ones. "What would have to be true for this to work?" Turns opinions into checkable claims (see The Mental Models Top Operators Use). "What's the smallest version we could test first?" Shrinks a big bet into a cheap experiment. "Imagine it's a year from now and this failed. Why?" The pre-mortem, from psychologist Gary Klein. It gives people permission to name the risks they're privately worried about. "What result would make us stop?" Agreeing a stop condition in advance protects you from sinking more money in just because you've already spent some. "Is this reversible?" Easily undone decisions deserve speed; hard-to-undo ones deserve this whole list. Notice what isn't on the list: "How confident are you?" Confidence is the one thing the planning fallacy guarantees in large supply. How to say it without crushing people Leaders who interrogate every plan can teach a team to stop bringing ideas. The goal is a better plan, not a defeated planner. A few habits help: Ask questions, not verdicts. "What did the last migration take?" lands better than "This will never be done by March." Separate the idea from the estimate. You can love the idea and still double the timeline. Reward honest numbers. If people who give realistic estimates get turned down while optimistic ones get funded, you will get optimism. Your reactions set the incentive. Approve in stages. "Yes to a six-week pilot, and we'll decide on the rest with real data" is often better than either yes or no. The honest limits The outside view is a correction, not an oracle. Sometimes there's no good reference class, because the project really is new. Sometimes the past is a poor guide because the world has changed. And ambitious projects do sometimes beat the odds, which is part of why people keep attempting them. Flyvbjerg and his co-author Dan Gardner argue that the answer isn't to stop building big things, but to spend more time planning and testing before committing, when changes are still cheap. The aim is not to say no more often. It's to say yes with your eyes open. The takeaway Almost every proposal is built from the inside view, and the inside view is reliably too optimistic about time, cost and benefits: the planning fallacy. As the person deciding, your job is to supply the outside view by asking how similar efforts actually turned out, what the numbers are based on, what would have to be true, what a small first test looks like, what would make you stop, and whether the decision can be undone. Ask in a way that rewards honest estimates, and approve in stages where you can. Try this: pick one project currently being planned around you and ask just one question: "How long did the last similar project actually take, compared with its plan?" Then compare that ratio with the current plan. Sources & Further Reading Sources - Sydney Opera House: original 1957 estimate £3.5 million with a January 1963 target; opened 20 October 1973 at A$102 million (see the Sydney Opera House's documented history, summarized in Wikipedia's entry and its sources). - Planning fallacy: Kahneman & Tversky (1979); broadened by Lovallo & Kahneman (2003). Thesis study: Buehler, Griffin & Ross (1994), average predicted 33.9 days, worst case 48.6, actual 55.5, about 30% on time. - Reference class forecasting: developed for practice by Flyvbjerg and COWI (2004); UK Department for Transport guidance (June 2004); Edinburgh Tram Line 2 figures (£320m forecast; £400m reference-class P80; £776m outturn). - Pre-mortem: Gary Klein. Flyvbjerg & Gardner on longer planning: How Big Things Get Done (2023). Go deeper - 📘 Thinking, Fast and Slow — Daniel Kahneman (the inside and outside views, in Kahneman's own words) - 📘 How Big Things Get Done — Bent Flyvbjerg & Dan Gardner (why projects overrun, and how the successful ones plan) - 🌐 Companion pieces in this library: The Mental Models Top Operators Use and How to Make a Hard Decision