← School

Free course

Communicating and leading, a lesson every weekday

A short daily lesson on saying the hard thing, asking for what you need, writing that works without you, and leading people. One framework, one story, one thing to try today.

Name two times: get a meeting on the calendar with one message.

Newest lesson · Lesson 68 · 5:51

You learn to schedule a meeting in one message by naming two specific times, stating your preference, and leaving an easy way out.

Listen to the lesson
  1. 56.Say the number you would bet on: give an estimate you will not have to apologize for.7:27You learn why the time estimate that feels right is usually too short, and three research backed ways to give one you can keep.
    Play lesson
    7:27

    Imagine you are a cabinet maker who runs a two person shop building custom kitchens. Today's lesson is about the two seconds after someone asks you when. When can you have it. When will it be installed. A number arrives in your head, it feels right, you say it, and weeks later that number is the thing you are apologizing for. For the cabinet maker the stakes are higher than they look. The number she says to a homeowner is not a guess between friends. It can become a date on a signed quote, and the homeowner plans the plumber, the countertop people and the family visit around it. This lesson is about why that number is almost always wrong in the same direction, why knowing that does not fix it, and the three things that actually do.

    The name for it is the planning fallacy, and Daniel Kahneman and Amos Tversky gave it that name in nineteen seventy nine. The study that made it concrete came fifteen years later, from Roger Buehler, Dale Griffin and Michael Ross, in nineteen ninety four. They asked students writing an honors thesis to predict when they would finish. Their best guesses averaged about thirty four days. The theses actually took about fifty five. Only about three in ten students finished by their own best guess. And here is the part that should stop you. They also asked for a worst case, the date if everything went as badly as it possibly could. Fewer than half finished even by that.

    The obvious explanation is that people do not know they run late. Buehler tested that, and it is wrong. When he asked students about their past projects, most remembered that those had run late too. They knew. They simply did not apply it. Each one treated the project in front of them as a special case, the one that would go the way the plan said. And the plan was built by imagining the steps, one after another, with nothing going wrong in between.

    Kahneman has a name for that way of estimating. He calls it the inside view. The alternative he calls the outside view. You ignore the details of this task and ask a duller question. What has happened to things like this before. In his book Thinking, Fast and Slow, from twenty eleven, he tells a story on himself. He led a team writing a new curriculum. When he asked everyone how long the book would take, the answers clustered around two years. Then he asked the one member who had watched other teams do the same job. That man said about forty percent of the teams he had seen never finished at all, and none of the rest had taken less than seven years. Everyone heard that, and everyone kept working to the two year plan anyway. The book took eight years. Kahneman, who studies exactly this for a living, did not change his estimate either. That is the point he wants you to take. The inside view does not lose the argument. It never has the argument. It just feels like knowledge.

    The largest test of this came from Bent Flyvbjerg, a Danish planner who went on to teach at Oxford. In two thousand two he and his colleagues published a study of two hundred fifty eight transport projects across twenty countries and seventy years. Nine out of ten ran over budget. And the size of the overrun had not improved across the whole seventy years. Decades of experience, better tools, better data, and the estimates were as wrong at the end as at the beginning. Flyvbjerg's own explanation was not innocent optimism. He argued that planners gave low numbers because low numbers get projects approved. That deserves a second of honesty from anyone who sells work. When you want the job, the short date is also the one that wins it. So there are two pulls on your number, and both pull the same way.

    Here is why this matters so much for the cabinet maker. For years she worked in someone else's shop, and her estimates were between her and herself. If a set of drawers took twice as long, she stayed late on Saturday and nobody knew there had been a date at all. With her own customers, the number she says becomes a plan someone else builds on. When the date slips, the homeowner does not experience a statistics problem. They experience her. A slipped estimate lands as a fact about her character, when it was never anything but a fact about estimates. And she feels that, which is where the frustration comes from. She gets annoyed at the customer for asking too much and at herself for being slow, when neither is true.

    There is one thing about her work that makes this worse, not better. A new panel saw and a good supplier of ready cut boxes make the building fast. So the inside view says, this kitchen is a week. But the building was never the slow part. The slow part is the other people's time: getting the homeowner to choose the door style, waiting for the hinges to arrive, getting the old cabinets out, getting someone home on the day to look at the finish and say yes. Her estimate covers her half. The date depends on both halves.

    So here are the three fixes, in order, and each one has a study behind it.

    First, unpack the job before you name a number. Justin Kruger and Matt Evans showed in two thousand four that listing the parts of a task before estimating it made the estimates longer and less optimistic. The inside view fails because it pictures the task as one smooth thing. Writing five lines breaks the smoothness. Make one of the five lines the part that waits on someone else.

    Second, look at the record, not your memory. Buehler found that when people recalled past projects and then explicitly connected them to the current one, the optimistic lean in their predictions went away. The key word is connect. Remembering that you ran late does nothing. Saying, this is the same shape as the last three, and those took two weeks each, does. And most people have a record. For the cabinet maker it is the job notebook on the shop wall and the dated invoices in the filing box. Look them up. Do not trust the feeling that this one is different. That feeling is the fallacy, wearing the face of expertise.

    Third, say the range and say the bet. Instead of one number, give two. Kitchens like this have taken me one to two weeks. I will say two. That sentence shows the reasoning, so the date reads as a forecast and not a promise. And it names the number you would actually bet on, which is the only one that should ever go on paper. If it depends on them, say that in the same breath. Two weeks from the day the door style is chosen.

    One thing to try today. The next time someone asks you when, do not answer in the first two seconds. Say, let me look at what the last few took, and I will give you a number within the hour. Then open the record, find three things of the same shape, write down what they actually took from first ask to finished and accepted, and send back a range with your bet at the far end. Nobody is disappointed by a two week estimate that lands in two weeks. Everyone is disappointed by a one week estimate that lands in two.

    That is the lesson. The number that feels right is the inside view, and the inside view is wrong in the same direction for a college student and a Nobel laureate. You are not slow. You are estimating like a human. The fix is not to try harder. It is to look outside your own head before you speak.

    Key terms

    planning fallacy
    The steady habit of predicting that a task will take less time than similar tasks have actually taken.
    inside view and outside view
    The inside view estimates from the details of this task, while the outside view asks how long things like it have taken before.
    unpacking
    Listing the separate parts of a job before estimating it, which makes the estimate longer and more realistic.

    Say it back

    1. What problem is this lesson helping you avoid?
    2. What is the first move you would make?
    3. Where could you use this in your next conversation?