top of page

FIELD NOTE | 

June 11, 2025

The Price of Trust

When you have authority over someone else's work, how much understanding are you entitled to require before you let their judgment actually be theirs?

I know what it is like to be capable and unconventional and need room to work. To see a connection before I can explain every intermediate step. To have a difference in method interpreted as a lack of judgment.

So when I finally had positional authority, I didn't want to reproduce that.

I had spent a lot of my career assuming that if someone above me didn't understand how I was thinking, the burden was mine to keep explaining until they did.

Sometimes that was necessary. Sometimes I had context they didn't, or they had context I didn't, and explanation made the work better.

But sometimes the real requirement was simpler: my reasoning had to become sufficiently similar to theirs before it could be trusted.

Those are not the same thing.

When I had authority myself, I started noticing how easy it would be to reproduce that dynamic. I could ask someone to explain a decision because I genuinely saw a risk they hadn't considered. Or I could ask because I wouldn't have done it that way.

Authority makes those two things dangerously easy to confuse.

This is not the same as having no standards.

I have high standards. Sometimes probably unreasonably high ones.

I've started to think that trusting other people requires a certain amount of trust in myself.

Not confidence that I know better.

Almost the opposite.

I have to trust that I know which edges actually need holding. That I can recognize a risk worth intervening in without intervening simply because I would have chosen differently. That if someone makes a decision I wouldn't have made, I can respond to what actually happens rather than trying to prevent every outcome I can't predict.

I don't need to eliminate my own uncertainty before someone else gets to exercise judgment.

So I became interested in being very clear about the edges and giving people a lot of autonomy inside them.

What are we trying to accomplish? What constraints are real? What commitments have we already made? What information do you need? What decisions are yours? Where do I need to be involved?

Then: go.

Mary Parker Follett wrote about the distinction between "power-over" and "power-with" more than a century ago. I like the distinction because authority is real. Pretending hierarchy doesn't exist doesn't make it disappear. Someone can hire you, fire you, change your compensation, redirect your work, withhold information, approve your budget, or make a decision you cannot override.

The question isn't whether power exists.

It's what we use it to make possible.

I used to think authority mostly meant having the responsibility to make good decisions.

Increasingly, I think one of the most consequential uses of authority is deciding who gets to decide.

Judgment requires practice.

You cannot ask people to exercise judgment while continually overriding them the moment their judgment diverges from yours.

And you cannot build someone's confidence in their own decisions by making yourself the final test of whether those decisions are good.

Sometimes leadership meant answering a question. Sometimes it meant asking, What do you think?

Not performatively. Not because I already knew the answer and wanted them to guess it.

Because I wanted them to learn to hear their own answer before reaching automatically for mine.

If every meaningful choice has to travel upward, you haven't built a strong team. You've built a queue.

And if people have to continually prove that their reasoning matches yours before you trust them to act, you may have hired expertise only to make it imitate you.

The goal wasn't to understand everyone's reasoning so completely that I could have produced it myself. If that were the standard, I would only ever be able to trust people who thought like me.

Some of the best leaders I have worked for did something that felt almost radical: they got out of my way.

They didn't need to understand every boundary I crossed because they trusted that I was crossing it for a reason. They challenged me when it mattered. They asked questions. They gave me context I didn't have.

But they did not need to understand every decision exactly as I understood it before they trusted me to exercise judgment.

I try to give that to my teams.

There is risk in this. Trust can be misplaced. Someone can make a decision you wouldn't have made. They can take longer. They can fail.

But eliminating those risks eliminates something else too.

Agency.

That's part of the price of trust.

If I give you enough room for your judgment to actually be yours, I also give up the guarantee that you'll choose what I would choose.

And you take on something too. Real agency means you can be wrong. You can make a decision and have to live with what it produces. You can no longer locate all of the responsibility in the person who told you what to do.

Trust asks something of both of us.

Autonomy doesn't mean doing whatever you want. It means having enough real authority to be responsible for an outcome rather than merely responsible for executing someone else's instructions.

Giving someone authority doesn't mean leaving them to guess where its boundaries are.

Ambiguity can be useful when we're exploring something new. Hidden rules are different. If people can't tell which decisions are theirs, what constraints matter, or when they're expected to seek approval, they aren't operating with meaningful autonomy. They're trying to predict what someone else will later consider acceptable.

Trust requires room for judgment. It also requires enough clarity for people to know when that judgment is theirs to exercise.

If I tell you exactly what to do and you do it, I own more of the outcome than organizations often admit.

If I give you a goal, context, constraints, resources, and genuine decision-making authority, then you can actually exercise judgment.

That requires trust in both directions.

I have to trust you enough to let you hold the decisions that are yours. You have to trust that I will hold enough of the surrounding architecture that you can actually make them.

Neither of us gets certainty.

I used to think having authority meant being responsible for making good decisions.

I still think that's part of it.

But I think another part is knowing which decisions shouldn't belong to you.

The point of giving someone authority isn't to let them make the decisions I would have made.

It's to create enough clarity around the edges that their judgment has room to actually be theirs.

bottom of page