The engineer said three weeks and I wanted one
· 2 min read · Tim Cooley

Ask someone how long it'll take to clean out the garage and you'll get a number. Start the clock and watch that number be wrong, usually by a lot, and almost never in the direction anyone hoped.
An engineer told me a feature would take three weeks. I had told the board it would take one. My first move was to ask her to walk me through it — dependencies, testing, the parts that could run in parallel. I framed it as diligence. It mostly wasn't.
What it actually was: I had a date I'd already said out loud to other people, and her estimate made that date a lie. So I did what I've learned I do — I pushed. Not loudly, not even rudely, just a lot of "why" questions in a row, the kind that sound like curiosity and function like pressure. She held her ground. She was right. It took three weeks.
I've been slow to admit this pattern, because it doesn't feel like something I'd do — I trust people by default, that's not a policy for me, it's the starting point. But trust has a blind spot, and mine shows up exactly here: when someone's estimate collides with my calendar, I go looking for reasons to distrust the number instead of asking myself whether I'm the problem. I was doing a rougher version of trusting the person closest to the work for years before I ever heard someone put a name to it — she's the one building it, she knows the shape of it better than I do from a status update. The part I still haven't solved is telling the difference in real time between an estimate that's padded and an estimate that's just inconvenient. Those two things feel identical in the moment they land on you.
What I try to do now is name it before I ask anything else. I'll say, out loud, "I have a date problem, not a trust problem" — and then decide if I still have a real question after that. Sometimes I do. Usually the real question was never about the estimate.
For the people who think pushing on an estimate is exactly the job — how do you tell the difference between doing that and just wanting a different number?
perspectiveproducttrustengineering