Degrees of Freedom

Brian Manwaring

I once managed someone who would not let go.

She wanted to be involved in nearly every detail. Decisions that should have been made beneath her kept finding their way back to her. She was overloaded, exhausted, and at times told me how much she hated her job.

The diagnosis seemed obvious: she needed to learn to delegate.

That diagnosis was not wrong. It was incomplete.

When we talked seriously about why she held so tightly to decisions, we eventually got to trust. At first I thought the problem was that she did not trust her employees.

The more important problem was that she did not trust me.

She was afraid that if she allowed someone below her to make a decision and the result was bad, I would conclude that she had made a bad decision by giving them the authority.

I wanted her to delegate. But I had never made sufficiently clear how I would judge her when delegation produced an unwanted result.

That pushed me toward a harder question than How do I get managers to let go?

What exactly are we trusting when we delegate?

Managers say things like Use your judgment. Run with it. You own this. Keep me informed.

Those phrases sound like delegation. They often leave the most important question unanswered:

Am I authorized to act?

Can I investigate and bring you a recommendation? Can I decide? Do I need your agreement first? Can I implement and tell you afterward? Am I expected to involve you only when something unusual happens?

Work can be delegated while judgment remains almost completely centralized.

That distinction led me to think about delegation in terms of Degrees of Freedom.

Meaningful delegation allows someone else's judgment to move the organization. A Degree of Freedom describes how far that judgment may travel before another authority needs to become involved.

Put more precisely, it describes how much organizational consequence we are willing to place behind another person's judgment.

Where Judgment Becomes Action

My current scale looks like this:

The numbers are not a score. They are shorthand for an operating agreement.

The most important transition is not between 4 and 5.

It is between 2 and 3.

At Degrees 0 and 1, independent decision and action are not authorized. At Degree 2, the employee owns much more of the investigation and recommendation, but agreement still comes before implementation.

At Degree 3, something fundamentally changes.

I am willing to let your judgment create a result the organization may have to live with before I have personally approved it.

Degrees 4 and 5 extend that confidence. They do not mean communication disappears. Someone operating at Degree 5 may communicate constantly because coworkers, customers, other departments, or senior leaders need the information.

What decreases is communication required primarily so the manager can inspect the judgment.

That distinction matters. Otherwise we risk teaching people that autonomy means keeping others uninformed.

It doesn't.

Nobody Is a Level 5 Employee

My earlier thinking about Degrees of Freedom leaned too heavily toward upward progression.

Develop capability. Demonstrate judgment. Earn more freedom. Keep moving.

I still believe good leaders should develop people toward greater responsibility where greater responsibility makes sense.

But the right side of the scale is not inherently better.

A person is not a Level 5 employee.

The degree belongs to the domain and the circumstances, not permanently to the person.

A production manager might operate at Degree 5 in routine scheduling. I may have no need to inspect those decisions before they are made.

The same manager might operate at Degree 2 on a plant shutdown. The customer, financial, and operational consequences are different. I may expect that manager to investigate and recommend while requiring another level of agreement before implementation.

And the same person might operate at Degree 0 when confronted with a matter that company policy requires to be immediately escalated to Human Resources.

Stop. Notify. Wait.

That does not mean I suddenly stopped trusting the person.

I may be at Degree 0 on the same issue.

The decision simply does not belong to either of us.

Sometimes the highest expression of judgment is recognizing that the judgment is not yours to make.

That also means some responsibilities have a legitimate ceiling. Someone might reasonably develop from Degree 1 to Degree 3 on plant-shutdown decisions but never to Degree 5 because the organization has decided those decisions should always involve another authority.

Maximum freedom is not the objective.

Appropriate freedom is.

Making Judgment Visible

If freedom is not simply a reward for good results, what justifies increasing it?

I do not have a formula.

I am not sure I want one.

The assessment is subjective. But subjective does not have to mean arbitrary.

What I am trying to learn is how someone thinks when the answer is not obvious.

Do they identify the real problem? Do they investigate or wing it? Do they distinguish a symptom from a root cause? Do they challenge their first explanation? Do they consider second-order effects? Do they recognize what they do not know? Do they understand where legal, ethical, financial, or organizational boundaries constrain the answer?

A technically effective solution can sometimes convince me to place less consequence behind someone's judgment.

If the proposed solution to a difficult problem is to quietly skirt a regulatory requirement, I have learned something far more important than whether the workaround would succeed.

This is why collaboration matters so much at the lower degrees.

Its purpose is not primarily for the manager to provide the answer.

Its purpose is to make judgment visible.

Early in a working relationship, I may need to enter near the beginning of the decision. Later, the employee may bring me a diagnosis. Later still, a proposed solution.

Eventually I may see the reasoning only after the decision has already been made.

As my confidence in the judgment grows, I can enter the decision later.

That may be the simplest description I know of development through Degrees of Freedom.

Questions I once had to ask should gradually become questions the employee reliably asks themselves.

That does not mean they think exactly as I do.

If the only people I trust are people who reproduce my reasoning, I have not developed judgment. I have developed imitation.

What I need is a reasonable expectation of how someone will think and act when I can no longer inspect the reasoning before the consequence occurs.

Then Something Goes Wrong

This was the part of Degrees of Freedom that troubled me for years.

Suppose I decide someone is ready.

I let them act.

They make a decision.

The result is bad.

The easiest response is:

I trusted you. It went badly. From now on, run it by me first.

That response is understandable.

It can also be terrible management.

A sound decision can produce a bad result. A poor decision can occasionally produce an excellent one.

If we judge decisions by outcomes alone, we eventually teach people to protect themselves rather than exercise judgment.

A coworker named Stacey changed how I think about this.

She shared a decision tree she used when investigating workplace accidents. Her purpose was different from mine, but one feature of the logic caught me immediately:

The unwanted outcome was the beginning of the investigation, not the verdict.

Her approach asked what the person knew, whether another reasonably comparable person might have acted similarly, whether something unusual affected the decision, and whether the surrounding system contributed.

I began applying that logic to delegated judgment.

When a decision produces an unwanted result, I want to know whether it was sound given the information reasonably available at the time.

I want to know whether something unusual changed the person's normal behavior. Fear. Personal benefit. Pressure. Exhaustion. Impairment. A desire to protect a number or avoid embarrassment.

I want to know whether another reasonably capable person, given similar information, authority, training, and circumstances, might plausibly have made the same decision.

And I need to look upstream.

Were expectations unclear? Was important information unavailable? Did we assign responsibility without enough authority? Did our incentives make the bad choice predictable?

The point is not to excuse bad judgment.

It is to identify what actually failed before deciding what the event says about future judgment.

A painful outcome may tell me nothing new about someone's fitness for freedom.

A lucky outcome may tell me a great deal.

If someone knowingly crossed an important boundary and simply got away with it, the good result does not make the decision sound.

An unwanted outcome should trigger investigation, not automatic withdrawal of authority.

The Same Test Has to Run Upward

That brings me back to the manager who would not let go.

She was deciding how much consequence to place behind her employees' judgment.

At the same time, I was deciding how much consequence to place behind her judgment that those employees were ready.

That was the part I had not made clear enough.

If one of her employees made a decision that failed, she might indeed have delegated irresponsibly.

Perhaps she gave authority to someone she had strong reason to believe was unprepared. Perhaps she ignored an integrity concern. Perhaps she failed to establish an obvious boundary. Perhaps she pushed a decision downward simply because she did not want to own it herself.

Those things should affect how I judge her.

But there is another possibility.

Her decision to delegate may have been completely reasonable given what she knew at the time.

The employee may have had appropriate capability. The authority may have matched the responsibility. Important boundaries may have been clear. The employee may simply have made a defensible decision in an uncertain situation that produced an unfavorable result.

If I treat those two cases the same, I teach managers not to delegate.

And managers learn quickly.

If every bad result underneath me becomes evidence that I cannot be trusted, then keeping important decisions for myself becomes rational self-protection.

I will approve more.

Review more.

Stay closer.

Make sure nothing consequential happens without my fingerprints on it.

Then the organization will wonder why I am exhausted, why my employees are dependent, and why decisions keep bottlenecking at my desk.

It may even send me to delegation training.

If leaders want judgment to move downward, they cannot punish every unwanted outcome upward.

Managers remain accountable. But we have to be precise about what they are accountable for.

They should be accountable for the quality of the delegation decision.

Was the authority appropriate? Was the person reasonably prepared? Were important boundaries clear? Did the manager provide the context and support they reasonably could?

If so, an unwanted outcome below the manager does not automatically mean the decision to delegate was wrong.

Delegation is recursive.

Every time a manager places consequence behind an employee's judgment, someone above that manager is deciding whether to stand behind the manager who made that choice.

One senior leader who repeatedly responds to bad outcomes with Why did you let them do that? can pull authority upward through several layers of an organization.

That is how a company can preach empowerment while structurally rewarding control.

Make Authority Explicit

A job description usually tells someone what they are responsible for.

It rarely tells them how far they are authorized to carry their judgment within those responsibilities.

That distinction should be discussable.

Manager and employee should be able to talk plainly about where authority currently sits, where another level of involvement is required, and whether greater freedom is actually desirable.

The numbers do not eliminate managerial judgment.

They make managerial judgment visible enough to discuss and challenge.

If I believe someone should remain at Degree 2, I should be able to explain why.

Maybe I have not seen enough of their reasoning. Maybe I have seen a specific gap. Maybe the consequence is unusually high. Maybe the role itself should never carry greater authority in that area.

The employee may disagree.

They should be able to say so.

What I should not be able to hide behind is:

Because I am responsible.

Of course I am responsible.

Leadership does not become responsible by collecting every consequential decision.

Where Judgment Should Live

I still believe leaders should develop people.

I still believe retaining decisions that others are capable of carrying creates dependence.

But Degrees of Freedom is not a ladder whose purpose is to push everyone toward 5.

Level 5 is not a prize.

Level 0 is not a punishment.

The question is whether judgment is sitting in the right place.

Too little freedom creates dependence, bottlenecks, and exhausted leaders.

Too much freedom without sufficient capability, judgment, integrity, context, or appropriate boundaries is not empowerment.

It is abdication.

Leadership lives between those failures.

The work is deciding where judgment should live, how much consequence should be allowed to follow it, and whether the people carrying that judgment are prepared to carry it well.

Sometimes that means releasing a decision sooner than feels comfortable.

Sometimes it means saying:

Stop. Call me.

And sometimes a manager's refusal to release control is not primarily a problem sitting below them.

It is sitting above them.