The best decision makers make their worst decisions at 4pm

Here is a paradox that product leaders rarely examine. The people who are best at making decisions are also the people making the worst ones, and the only variable separating their best calls from their worst is the time of day. Not complexity. Not information quality. Not stakeholder pressure. The clock.

And that should unsettle every senior product person reading this.

Product leaders make dozens of decisions daily. Most feel manageable. You approve a design direction before lunch. You settle a prioritisation dispute between two squads after your second coffee. You sign off on an experiment's success criteria during a stand-up. Each one, on its own, feels like a small exertion. And because the individual cost feels low, you treat them as free. But the cognitive resource that decision-making draws on is finite, and it depletes through the day in ways you cannot feel happening. By mid-afternoon, the account is overdrawn. But the invoices keep arriving.

This is decision fatigue, and in early 2024 it has become the hidden tax on product leadership that almost nobody is managing deliberately.

The Invisible Account

I want to introduce a concept I have started calling The Depletion Ledger. Every decision you make, regardless of its apparent stakes, withdraws from the same cognitive account. But there is no balance notification. No red warning banner. No overdraft alert. You simply start making worse calls, and the dangerous part is that you feel exactly as confident making them.

Decision fatigue is not tiredness. It is the quiet depletion of the resource you need most and notice least.

I learned this the expensive way at Adobe. We were deep in a product integration cycle, and I had spent the morning in back-to-back syncs, approving copy changes, resolving a minor API versioning disagreement, and reviewing three separate A/B test proposals. None of it felt taxing. But by 4pm, when the actual consequential meeting arrived, a session to decide whether we should pivot our onboarding strategy for a segment that represented roughly 30% of new revenue, I was already spent. I did not know I was spent. I sat in that room, listened to two well-argued positions, and picked the one that required fewer follow-up decisions. Not the better strategy. The easier one. The one that let me stop deciding.

It took three weeks to realise the mistake. Three weeks and a set of onboarding metrics that told a story I should have predicted. But the truly unsettling part was this: at the moment I made the call, it felt perfectly sound.

The decision was not hard. I had simply arrived at it empty.

Why the Day Runs Backwards

Most product leaders structure their days in a way that is precisely inverted from what the research supports. They frontload mornings with low-stakes calls and synchronous check-ins. Stand-ups at 9. One-on-ones at 10. Design reviews at 11. By the time the genuinely consequential work arrives, the strategic decisions about roadmap bets, partnership terms, or pricing model changes, the cognitive budget is already gone.

But here is what makes this worse. The low-stakes decisions feel productive. You clear your inbox. You unblock three people. You resolve a Slack thread. But each micro-decision nibbles at the same finite resource. And the high-stakes decisions that arrive later do not get a fresh budget. They get the scraps.

I have watched this pattern repeat across every organisation I have worked in. At Freshworks, I noticed it most clearly because the product team was spread across time zones, which meant the consequential calls often landed in the late afternoon for the India-based leaders. But the pattern was not about geography. It was about sequence. The leaders who scheduled their thinking work first consistently made better strategic calls. The ones who "got the small stuff out of the way" first consistently made worse ones.

The correlation was stark enough to be embarrassing.

The Two-Hour Vault

The specific practice that has been circulating among senior product people in early 2024 is deceptively simple: reserve the first two hours of each working day strictly for the highest-stakes thinking. No Slack. No stand-ups. No "quick syncs." No email triage. Just the decisions that carry the most weight.

I call this The Two-Hour Vault, and it sounds almost comically easy until you try to implement it.

The resistance is immediate. Your team wants morning alignment. Your manager wants a 9:30 check-in. Your calendar is a Tetris board someone else assembled. But the maths is unforgiving. If your best cognitive resources exist between 8 and 10am, and you spend them on decisions that a junior PM could make, you have traded your most valuable asset for your least valuable work.

When I moved from Bangalore to Wayanad, one of the unexpected gifts was that the slower mornings made it easier to protect that window. No commute eating into the first hour. No office small talk burning fifteen minutes of prime cognition. But I also learned something subtler. The vault is not just about blocking time. It is about what you do not allow into the first two hours. Every "quick question" you answer is a withdrawal. Every notification you glance at is a withdrawal. The vault only works if the walls are real.

A product leader who protects their first two hours is not being precious. They are being strategic about a resource that does not regenerate on demand.

The Decisions That Get Worse

At Boeing, early in my career, I watched a senior engineering manager who seemed to make effortlessly good calls. I assumed it was experience. But when I paid closer attention, I realised his calendar told a different story. He simply refused meetings before 10am. Not because he was lazy. Because he had learned, probably through failures he never discussed, that his first two hours were worth more than any meeting.

I thought he was eccentric at the time. I now think he was one of the few people who understood the ledger.

Not all decisions degrade equally under fatigue. The ones that suffer most are the ones requiring you to resist the default, to say no when yes is easier, to ask for more data when the room wants to move forward. Fatigued decision-makers default to the path of least resistance. They approve instead of questioning. They agree instead of pushing back. But they rarely notice the drift until the consequences arrive weeks later.

But this is precisely the type of decision that product leaders are paid to make well. The job is not to approve things. The job is to make the calls that shape what the product becomes.

The tragedy is not that product leaders make bad decisions. It is that they make bad decisions with their best thinking already spent on decisions that did not matter.

The calendar is not a schedule. It is a resource allocation plan for your cognition. And right now, most of those plans are badly misallocated.

Protect the mornings. Not because the afternoons do not matter, but because the decisions you make at 4pm are only as good as what you did not spend at 9am.