Chapter 27: The Mechanics of Timing

The Manager as a Vendor

As stated earlier, a manager is fundamentally a salesperson of ideas. You are constantly pitching—selling upwards to the client, and selling downwards to the team.

In the physical world, the success of a sale relies heavily on timing. A vendor sells ice cream in July and hot pies in January, never the reverse. They intuitively read the environment and present an offer exactly when the target is most receptive to it.

As a manager, you must develop this exact same situational awareness.

If a developer barely slept, got splashed by a truck on the way to the office, had their foot stomped on the subway, and found their favorite coffee mug shattered in the breakroom—this is absolutely not the moment to cheerfully pitch a "heroic weekend push" to deliver a milestone early.

Pitching to the Client Under Fire

This applies equally to your clients. If you just deployed a new build to production and critical bugs are actively blocking their operations, do not pitch them on spending extra budget to integrate a trendy new UI library. It will end in a shouting match.

However, pitching a necessary, funded refactoring sprint to pay down the exact technical debt that caused the outage? That idea might land perfectly, because the pain of the problem is currently acute. You are selling the cure while they are feeling the disease.

Selling Heavy Ideas to the Team

Pitch demanding, innovative, or unfavorable ideas only when your people are in a neutral or elevated emotional state. If your team is exhausted, frustrated, or crushed by a deadline, they need cover fire, not another heavy cognitive load.

Imagine an engineer who just spent nine hours grinding through legacy code. That is not the time to enthusiastically announce a migration to a new project management framework because "it has better dashboard widgets." At best, the information will be completely ignored. At worst, it will be met with open, aggressive hostility. A tired mind rejects new variables.

The Ecology of the 1-on-1

One-on-one meetings are a distinct operational tool. They are mandatory because they prevent engineers from feeling like anonymous cogs in a machine and provide a secure channel for raw, unfiltered field data. They allow you to know what an engineer actually thinks before they suddenly hand in their resignation.

But that channel only opens if the engineer feels secure and unhurried.

You must time 1-on-1s when the individual is free from immediate operational distractions. Never initiate a deep-dive conversation when the engineer is hungry, rushing out the door to pick up their kids, or holding a production database transaction open. If you force the timing against the environment, the 1-on-1 devolves into a useless, defensive formality—an HR checkbox exercised strictly for your own administrative comfort.