Leader writing notes during a decision discussion with teammates around a table

What Your Decisions Teach People

“Like technical debt, management debt is incurred when you make an expedient, short-term management decision with an expensive, long-term consequence.”

Ben Horowitz, The Hard Thing About Hard Things

I recently read Ben Horowitz’s The Hard Thing About Hard Things, and one idea has stayed with me more than I expected: sometimes what looks like a one-off decision is not really one-off at all. It becomes the example people remember the next time they are trying to figure out what is allowed, what is rewarded, and what will happen if they push.

Horowitz talks about management debt: the kind of debt created when a leader chooses the expedient answer now and leaves the organization to pay the interest later. That framing resonated because decisions do not live only inside the moment where they are made. They become part of the story people tell about how the company actually works.

The Decision Becomes The Example

A decision does not only solve the situation in front of you. It teaches people what to expect next.

A leader might make an exception for one person, one project, one deadline, or one customer. In the room, it can feel practical. The context is special, the pressure is real, and the decision may even be the right call.

The hard part is that the full reasoning behind that decision may not be visible to everyone else. What people see is the outcome: someone got the exception, a team bypassed the process, a deadline moved for one group and not another, or a behavior had consequences while another did not. People learn from the visible pattern.

That does not mean every decision needs to become a rigid rule. Leadership would be impossible if every exception had to be defended forever. But a leader has to understand the teaching effect of a decision, especially when the decision is visible.

People Infer The Policy

In an organization, there are the written policies and values that people refer to. In parallel, people infer policy from the decisions leaders make, especially when the choice is visible and the tradeoff is real.

A team that cuts corners to hit a date learns something about quality. An engineer who raises a risk and gets a defensive reaction learns something about escalation. A person who goes around everyone else and still gets celebrated learns something about collaboration.

This Applies Outside Management Too

The policy people remember is often the exception you made under pressure.

The same dynamic is present in all our professional relationships. How we handle one disagreement teaches people what future disagreements with us may feel like. How we respond to bad news teaches people whether to bring it earlier next time. How we treat a missed commitment teaches people whether commitments are real, negotiable, or mostly theater.

Over time, our behavior becomes a forecast. People decide whether to tell us the uncomfortable truth, ask for help, include us early, challenge a weak plan, or trust us with something unfinished.

A Leader’s Voice Carries Weight

The impact is broader when you have authority because your choices affect more than your own reputation. A manager’s decision can become team precedent. A director’s exception can signal something across multiple groups. A CTO’s reaction in one meeting can change what people are willing to say in the next one.

That does not mean leaders should become stiff or afraid to make exceptions. It means the exception needs to be named. Why are we doing this here? What is special about this situation? What should people not infer from it? What do we need to clean up afterward so this does not become hidden policy?

Does This Decision Set Precedent?

People take their cues from what leaders do under pressure.

Before making a visible decision, it helps to pause for one extra question: if people treated this as the precedent, would I be comfortable with that?

If the answer is yes, the decision reflects the standard you want. If the answer is no but the situation still demands it, it is worth naming the context directly so people understand the exception without turning it into the new rule.