The Weight of a Leader’s Yes

A leader’s yes is a claim on someone else’s time. Before making that claim, decide whether the work deserves it and how the team will have room to deliver it.

A promise takes only a moment to make. Keeping it may occupy months of someone’s life. The meeting ends, but the commitment follows people back to their desks, into their calendars, and sometimes into hours they had promised elsewhere.

Authority makes that use of time my responsibility.

What we ask people to carry

I enjoy building things. One possibility opens another, and it is easy to keep following them. In The Inconvenient Human, I wrote that technology “expands what I can start much faster than it expands what I can responsibly carry.”

Leading people makes that question larger. I can see something worth pursuing and ask others to pursue it with me. My excitement can become their obligation. Their time enters the idea, along with the work they already owe someone else.

A worthwhile opportunity should move us to act. It may bring in revenue, solve an important customer problem, or give the business a better future. A team can take pride in doing difficult work together. People deserve to know what we are pursuing, why it matters, and what it will ask of them.

We still have to choose how it fits with the work already promised. We can delay something, narrow the new request, add resources, or use capacity the team confirms is available. If we expect a demanding stretch, we need to say what it involves and when we will review it.

Without that choice, people have to find hours we have never discussed. Someone works longer. Another promise slips. The person responsible for support inherits a problem that never appeared in the plan.

The cost still exists. Silence has only moved it out of the meeting.

A promise needs room to be kept

That starts with listening to the people who will carry the work. They know which commitments can move, where an estimate is uncertain, and what support would make a difference. Hearing them gives me a better basis for a decision I still need to make.

The return matters too. Revenue, customer value, and the direction of the business can make an investment worth its cost. Expected demand belongs in the discussion, along with the possibility that it will not arrive. We need a plan we can support while that outcome is still uncertain.

Then the decision needs to reach everyone affected. If we delay a commitment, the person waiting for it deserves to hear about the change. If I give someone responsibility, I owe them the time, information, and authority to carry it.

And we need to return to the decision after delivery. A finished task may have created more work for support. A report can improve while someone’s day becomes harder. I need to hear what happened to the people behind the result and let that account change what we do next.

They should be able to bring back a problem without having to protect my answer.

Before your next yes

Ask: What will make this promise possible, and what will it ask of the people keeping it?

Write down what will change: the work that waits, the date that moves, the resources you add, or the capacity the team confirms is available. Discuss it with the people affected before you commit, and set a time to see how the decision is working.

Give the promise a place in the plan.