Hey Reader,

This morning I spent forty-five minutes on something important, and it wasn't the most important thing on my list. I knew that about twenty minutes in.

Like a dog with a bone, I got on the task and I just needed to finish it. I didn't have the discipline to stop and ask whether it was still the right thing to be doing. I didn't pause it, and I certainly didn't kill it.

Forty-five minutes isn't a catastrophe. It's a Tuesday, and it's also exactly how a quarter gets spent, forty-five minutes at a time. It's why I've put the same question to leadership teams since I was running companies: what is your investment thesis on those hours, and are you getting the return you wanted?

We already know how to do this with money.

Put in X, get back Y, over a period you can name. You can run that math on capital without notes, usually to the decimal, usually before someone finishes opening the deck.

Almost nobody runs it on time. You spend the hours, look around Friday, and go, what happened?

The gap isn't discipline and it isn't intelligence. Behavioral researchers have a cleaner explanation than either: money is easy to measure, so you hold yourself accountable for it, and time is ambiguous to measure, so you don't. Most of us have never treated time as an investment asset, so there was nothing to check the result against.

What changed is how fast you can spend it.

Two years ago, building something custom meant finding a developer, defending a budget, and waiting out a quarter. Now I sit down with Claude Code after dinner and have it working before bed, which is real leverage and I use it.

It also removed the last thing that reliably made you stop and think first. At six weeks and $40,000, the price of being wrong made you decide before you started. At four hours, you just start, and four hours becomes ten, and ten becomes twenty, because stopping now would mean admitting the first ten were a bet you lost. Activity is the enemy, and AI has no off switch.

The Time Thesis.

You can't measure a return without a thesis to measure it against. That's the whole gap. So write one, four questions, before the block starts rather than after it ends. Thirty seconds, not a system.

Thesis. What do I believe this delivers? Say it as a result, not a task, because the two get confused constantly. "Build the dashboard" is a task. "Cut the Monday reporting scramble from three hours to twenty minutes" is a result.

Price. How many hours will this actually take? Write down the honest number, then check it against what the last thing like it actually cost you when you were done.

Return. What is different when it's done? If the only honest answer you can give is that a thing now exists that didn't before, you don't have a return. You have an output.

Alternative. Is this the next best use of those same hours? That's the real competition, not doing nothing. If those four hours could go to the two conversations that unstick your leadership team, the build loses and it isn't close.

Then track three blocks a week.

Not your whole calendar, just three blocks, the biggest ones, the discretionary ones where you actually made a choice about how the time got used. Write the thesis before each one starts. Then Friday afternoon, take five minutes and grade them: returned, partially returned, or didn't.

Inside a month you'll have twelve data points and a pattern clear enough to act on. Better than that, you'll start catching yourself defending hours instead of deciding about them.

Write it down, because you will not catch this from memory. In a controlled study last year, experienced developers worked real tasks in their own code with AI help randomly allowed or blocked. They expected it to make them 24% faster and finished still believing it had. The measurement said they were 19% slower.

Kill it, don't coast it.

The hardest move isn't writing the thesis. It's what you do when the price runs past it. That's where I failed this morning, and it's where most of us fail, because stopping feels like throwing away everything already spent.

Sunk cost runs harder on your time than it ever runs on your money. You would walk away from a $40,000 project the week it stopped making sense, and you would brief the board on exactly why you did it. You will not walk away from thirty hours. Nobody counts the hours the way they count the dollars, so nobody ever makes you.

Give yourself permission to kill it outright, because pausing is only second best and coasting isn't on the list at all.

Your answer sets the ceiling for your team.

This was never a productivity topic for me. If you can't say what your own hours returned last quarter, nobody who reports to you will be able to say it about theirs either. They watch how you spend yours and they calibrate to what they see rather than to what you tell them.

Two warnings before you take this anywhere. Don't hand it to your team as a tracking exercise, because pointed at your own decisions this is leadership, and pointed at your people it becomes surveillance. And leave one line wide open, because some of the highest-return hours of your life will never survive this question asked in advance: the unplanned call, the long walk, prayer. Ask those to justify themselves and you will lose them.

You'll get more capital. You will not get more time. Those hours are the one asset you actually control, which makes them worth more than the money, and the only thing that changed is how fast you can now spend them before anyone thinks to ask what they bought.

dusty

P.S. Pick three blocks this week, write the thesis before each one, and grade them Friday. Tell me what you find. Hit reply, especially if the answer is uncomfortable.

P.P.S. Episode 39 of Leadership Unlocked podcast is the practical half, how top-performing CEOs build the calendar once they've decided what deserves the time: