The lie we tell ourselves I used to think I was good at estimating how long things take. I was wrong. Not slightly wrong. Catastrophically wrong. A website redesign? Two weeks, I'd say. It took six. A new client onboarding process? Three days. It took eleven. A simple automation? An afternoon. It ate an entire week. This pattern repeated for years. I would commit to deadlines, miss them, apologise, scramble, and then do it all again. The problem was not laziness or lack of skill. The problem was that I could not see time properly. Then I started using Gantt charts. Not because I wanted to. Because a client demanded one for a project we were running together. And something clicked. Why your brain lies about duration Humans are terrible at estimating time. There is research on this. Daniel Kahneman called it the planning fallacy. We consistently underestimate how long tasks will take, even when we have direct experience of similar tasks taking longer before. Why? Because when we think about a task, we imagine the best-case scenario. We picture ourselves working without interruption, with all the information we need, with no unexpected problems. We forget that the last time we did something similar, we got stuck waiting for feedback for four days, or the software broke, or we simply did not feel like doing it on Tuesday. A to-do list does not fix this. Neither does a calendar. Both let you lie to yourself. You can write "finish proposal" on Monday and "send proposal" on Tuesday without confronting the fact that finishing the proposal requires three rounds of internal review and your colleague is on holiday until Thursday. What a Gantt chart actually does A Gantt chart is just a visual timeline. Tasks sit on horizontal bars. The length of each bar represents duration. You can see, at a glance, what overlaps with what, what depends on what, and where the bottlenecks are. The power is not in the chart itself. The power is in what building the chart forces you to do. You have to break work into actual tasks. Not "sort out marketing" but "write email sequence", "design landing page", "set up tracking", "test on mobile". Each one gets its own bar. You have to assign duration to each task. Not "soon" or "ASAP" but "three days" or "one week". And when you see that bar stretching across your timeline, you feel it. You have to sequence tasks. Some cannot start until others finish. When you draw those dependencies, you suddenly see that the thing you promised for Friday cannot possibly happen because the thing it depends on will not be done until Wednesday, and you still need two days after that. This is where the honesty happens. The Gantt chart does not let you pretend. A real example from last month I was working with someone in London who runs a small food business. She wanted to launch a new product line. When I asked her timeline, she said four weeks. We built a Gantt chart together. Not a fancy one. Just a free tool and forty minutes of conversation. Here is what we mapped: sourcing new suppliers (one week), getting samples (two weeks, because international shipping), testing recipes (one week), designing packaging (two weeks, overlapping with recipe testing), getting packaging printed (ten days), setting up the online listing (three days), photography (two days), and a soft launch to existing customers (one day). When we laid it out, the realistic timeline was nine weeks. Not four. The gap was not because she was naive. It was because she had never seen all the tasks laid end to end, with their dependencies visible. She adjusted her expectations, told her customers the real date, and launched on time. No scrambling. No apologies. That shift alone probably saved her £2,000 in rush fees she would have paid trying to compress the impossible. The fear of looking slow I know why people resist this. It feels like admitting defeat. If you say a project will take eight weeks instead of four, you worry you will look incompetent. Slow. Expensive. But here is what I have learned: people respect accuracy more than speed promises you cannot keep. Missing a deadline damages trust far more than setting a realistic one in the first place. There is a report out this week warning that one in six young people in the UK will be out of work or training within five years without intervention. A lost generation, they are calling it. That kind of systemic problem happens when institutions consistently fail to plan properly, when optimism replaces realism, when nobody builds the timeline that shows the real cost of inaction. The same dynamic plays out in businesses, just on a smaller scale. Underestimating time is not a minor error. It compounds. You do not need software for this You can build a Gantt chart on paper. Draw a grid. Days or weeks across the top. Tasks down the side. Shade in the bars. Draw arrows for dependencies. If you want something digital, there are dozens of free options. I have used Notion, Google Sheets with conditional formatting, and dedicated tools like TeamGantt. The tool matters less than the discipline of filling it in honestly. At ALIRA., when we help people build operational structures, the Gantt chart often comes early. Not because it is sophisticated. Because it is clarifying. It turns vague plans into visible commitments. And once something is visible, you cannot unsee it. The uncomfortable truth You will not like your first honest Gantt chart. It will show you that you have been promising things you cannot deliver. It will reveal that the project you thought was two weeks away is actually six weeks away. It will make you feel behind before you have even started. That discomfort is the point. It is reality asserting itself. And reality, confronted early, is far easier to manage than reality discovered on the day you were supposed to deliver. What to do this week Pick one project you are currently working on. Something with a deadline, even a soft one. Break it into every task you can think of. Not categories. Tasks. Things you could tick off. Estimate each task in days, then add 50% to each estimate. This is not pessimism. This is accounting for the interruptions and delays you will definitely face. Lay them out in sequence. Use paper, a spreadsheet, or the free planning tools at alira.london. See where the end date actually lands. If it lands after your deadline, you have a choice: cut scope, get help, or reset expectations. All three are better than pretending and failing.