Ownership needs a field in which judgment can operate. Give people enough room to decide, enough clarity to know what they are protecting, and visible edges that tell them when another decision is needed.
Mika’s supervisor wanted her to take more ownership.
“You don’t have to ask me about everything,” he told her after another customer request had been escalated. “Use your judgment.”
Mika nodded. She wanted the same thing. Waiting for her supervisor slowed customers down, filled his day with decisions she believed she could make, and made her feel more like a messenger than someone trusted to solve problems.
The next afternoon, another unusual request arrived. The customer wanted an adjustment Mika thought was reasonable. She knew the amount involved. She understood why the customer was asking. She even had a solution in mind.
Then the questions started.
Could she make that promise herself? Would the amount be considered too high? What if another department disagreed? Would her supervisor support the decision if the customer complained later? The last time someone made an exception without asking, the discussion afterward had included a sentence everyone remembered: “Why didn’t you check with me first?”
Mika sent her supervisor a message.
“Can I proceed with this?”
From the manager’s side, it looked like another employee refusing to take ownership.
From Mika’s side, it looked like judgment.
“Use your judgment” still needs edges
Managers often say “Use your judgment” for good reasons. They do not want to micromanage. They want decisions closer to the work. They want people to think rather than wait for instructions.
The problem is not the desire for judgment.
The problem is asking people to exercise judgment when they cannot see the field in which they are allowed to exercise it.
An employee may understand the customer, recognize the problem, and even know the response that makes sense. But if the limits of authority exist only inside the manager’s head, waiting is often the safer play. Every independent decision carries the risk of discovering an invisible boundary only after crossing it.
That creates an organizational contradiction. Leaders ask for initiative while employees keep learning that permission is safer.
More encouragement rarely fixes that.
The decision space has to become visible.
Ownership needs boundaries
Freedom and boundaries are sometimes treated as opposites. In real work, they often depend on each other.
Give people no room to decide and they become dependent. Every unusual situation travels upward. Managers become bottlenecks, employees stop building judgment, and customers wait for decisions that could have been made closer to the problem.
Give people unlimited freedom without explaining what must be protected, and the experience can feel less like empowerment and more like abandonment. People are left to discover the limits through mistakes, criticism, or consequences they did not know they were authorized to create.
A useful boundary does something different. It creates a space inside which the employee is genuinely free to decide.
Freedom without boundaries can feel like abandonment. Boundaries without freedom create dependency.
The objective is not maximum freedom. It is enough decision space for useful ownership at an acceptable level of risk.
A boundary is not another rule
This distinction matters.
A rule tells people what to do.
A boundary tells people where they are free to decide.
Imagine a service employee is allowed to resolve routine recovery cases worth up to ₱5,000. If the organization then specifies the exact response for every possible situation, the employee does not really have a decision boundary. They have a procedure with a spending limit.
A true boundary leaves room for judgment.
It may identify the result that must be protected, the kinds of decisions the employee owns, the conditions that require another level of authority, and when the team will review what happened. Inside that space, the player chooses.
That is why a good boundary should not try to eliminate judgment.
A boundary should make judgment safer, not make judgment unnecessary.
This is especially important when the work changes quickly. No leader can anticipate every customer request, project complication, employee issue, or operational exception. A boundary gives people enough orientation to respond intelligently when reality produces a case nobody wrote down beforehand.
Start with the win, not the limit
Managers often begin boundary conversations with numbers.
“You can approve up to ₱5,000.”
“You can move the schedule by two days.”
“You can replace up to three units.”
Those limits may be necessary. But a number by itself does not tell the person what good judgment is trying to accomplish.
Mika needs to know more than how much money she may approve. Is she trying to protect the customer relationship? Restore a service promise? Resolve routine issues quickly without creating unacceptable financial or contractual risk?
The answer matters when the situation does not fit neatly into a category.
Suppose a request costs only ₱2,000 but would create a promise the operations team cannot keep. Mika is technically below the financial ceiling, yet approving it may work against the real objective.
The win helps her interpret the boundary.
The boundary tells you how far you may move. The win tells you what direction good judgment should move in.
So begin there.
What result should this person protect when making the decision?
Make that visible before discussing limits.
Mark the decision space
Once the win is clear, define what the person may decide without returning for permission.
The decision space should be concrete enough that the employee can recognize it in real work.
A manager might say:
“For routine recovery cases, you may choose the remedy yourself when the total value stays within ₱5,000, the customer is not asking us to change a contractual commitment, and the solution does not create work another team has not agreed to provide.”
That is much more useful than:
“Handle routine issues on your own.”
The person can now see the field.
Within it, they do not need to ask, “May I?”
They need to decide.
This also changes the manager’s job. If the employee stays inside the visible boundary and exercises reasonable judgment, the manager has to resist taking the decision back simply because they personally would have chosen differently.
Otherwise the written boundary says one thing while the consequences teach another.
That is exactly the kind of contradiction explored in Remove the Routine That Rewards the Old Behavior. People learn the real rule from what happens after they act. If reasonable independent decisions are repeatedly second-guessed, permission-seeking will return no matter how often leaders ask for initiative.
Red lines tell people when the decision changes category
Every useful decision space has edges.
A red line is not simply something that makes an employee nervous. It marks the point where the nature of the decision changes enough that another person, expertise, or authority should enter.
A customer request may cross a contractual obligation. A maintenance decision may create a safety risk. A hiring choice may trigger a legal requirement. A discount may affect margins beyond the person’s authority. A service recovery may create a promise another department must deliver.
Below the line, the person owns the judgment.
Across the line, another decision is required.
This makes escalation more intelligent because employees no longer have to escalate every unfamiliar situation merely because it feels uncertain. They can explain why a case has crossed a visible boundary.
That gives escalation a different meaning.
Escalation is not the opposite of ownership. Knowing when to escalate is part of ownership.
The person carries the decision as far as their authority allows, then brings forward the part that genuinely requires another level.
Permission-seeking and responsible escalation are different plays
Listen to the difference.
Permission-seeking sounds like:
“What should I do?”
Responsible escalation sounds like:
“This request is within the financial limit, but it changes a service commitment owned by operations, so it crosses the boundary we agreed. I see two workable options. I recommend the second because it protects the customer without committing operations to something they have not approved.”
The second employee is not handing the problem upward.
They are carrying ownership to the edge of their decision space.
That is a behavior worth designing deliberately. In some workplaces, the escalation itself may need its own Minimum Lovable Play: name the boundary crossed, show the evidence, bring reasonable options, and make a recommendation.
If you need to turn that response into something people can call consistently under pressure, Design One Minimum Lovable Play provides a useful way to design and test it.
Hidden boundaries manufacture dependency
Many managers believe their employees already know where the limits are.
“Of course Mika can handle an ordinary refund.”
“I don’t need to spell everything out.”
“She should know when something is serious enough to ask me.”
Perhaps.
But employees do not operate inside the manager’s intentions. They operate inside the signals they can actually see.
Imagine that Mika makes a decision she reasonably believes is inside her authority. Nothing terrible happens, but her manager later says, “Next time, run this past me first.”
A week later another case appears.
What is the boundary now?
The formal message may still be “Use your judgment.” The experienced boundary is closer to “Use your judgment when you are certain your manager will agree.”
That is much narrower.
After enough experiences like this, the manager begins receiving questions about everything. They become frustrated.
“Why does everyone keep asking me?”
Because asking has become the rational response to an invisible decision field.
This is why boundaries cannot live only in a leader’s head. If the employee is expected to act inside them, the employee needs to be able to see them.
A boundary can be too narrow or too wide
Boundary design can fail in two directions.
When the boundary is too narrow, routine decisions keep moving upward. Managers spend their time approving work that others could handle. Employees gain little experience making consequential judgments because the organization repeatedly removes the opportunity.
The symptom is often familiar:
“My people need to take more ownership.”
But the underlying design may be:
“My people are allowed to own very little.”
A boundary can also be too wide. An employee may be given decisions whose consequences they do not yet understand. Errors increase, risk grows, and managers react by pulling authority back—sometimes much farther than necessary.
The answer is not to choose between trust and control.
Design the decision space around the importance of the result, the risk involved, the person’s capability, and the quality of the support around them.
A junior employee may reasonably begin with a smaller space and an earlier checkback. An experienced employee with demonstrated judgment may work inside a wider boundary.
That does not have to be arbitrary or unfair.
A boundary can grow with demonstrated judgment.
When people can see that stronger decisions earn a wider field, ownership becomes developmental. The organization is not merely controlling risk. It is deliberately building the capacity to carry more responsibility.
Use checkbacks to grow judgment, not quietly take decisions back
The fourth part of a useful boundary is the checkback.
This is where managers can accidentally undo everything.
“You decide—but tell me before you act.”
Sometimes risk genuinely requires that. But if every decision needs advance approval, the employee does not actually own the decision.
For many situations, a better checkback happens after several real repetitions.
A manager might say:
“Handle the next five routine cases inside this boundary. Bring the exceptions and the outcomes to our Friday review.”
Now the employee acts.
The manager gets visibility.
Both learn.
The checkback creates a place to examine what happened: where the boundary was useful, where the employee hesitated, what new exceptions appeared, and whether the boundary needs to move.
For a new employee or a high-risk decision, the checkback may need to happen sooner. As capability and evidence grow, the distance between checkbacks can expand.
A checkback should help judgment grow, not quietly take the decision back.
This also connects naturally to Build a Weekly Execution Rhythm. A recurring review gives managers and players somewhere to bring real cases, learn from exceptions, and decide whether the next version of the boundary should change.
Let exceptions teach you where the real boundary belongs
No first boundary will anticipate every case.
That is not a reason to delay creating one. It is a reason to treat it as something the work can improve.
Suppose Mika escalates three similar service adjustments during the month because she believes they cross her authority. Each time, her manager approves exactly what she recommended. No new risk appears. The cases keep repeating.
That is evidence.
Perhaps the boundary is too narrow.
Instead of continuing to approve the same decision forever, the manager can ask whether that category should move into Mika’s decision space.
Then another case appears below the ₱5,000 limit but creates a legal commitment Mika had not considered. The financial limit alone is obviously not enough. The red lines need to become clearer.
That is evidence too.
The goal is not to produce a perfect boundary on the first attempt. The goal is to make enough of the decision field visible that people can act, then let real exceptions teach you where the field should expand, tighten, or change shape.
A good boundary learns.
Use the Boundary Play
When someone needs to act with more ownership, use four questions.
Name the win
What result is this person trying to protect or create?
Keep it close enough to the decision that it can guide judgment.
Mark the space
What may this person decide without asking permission?
Describe real categories of decisions, not vague encouragement to “take initiative.”
Mark the red lines
What changes the category of the decision?
Name the material conditions—risk, money, safety, legal exposure, contractual promises, another team’s authority, or other consequences—that require escalation.
Set the checkback
When will you look at what happened?
Use the checkback to inspect real cases, learn from exceptions, coach judgment, and decide whether the boundary should remain, widen, or change.
The shorthand is easy to remember:
Win → Space → Red Lines → Checkback
It can take only a few minutes to establish a first version. The harder work is keeping your own behavior consistent with the boundary after the employee begins using it.
Do not punish reasonable judgment after asking for it
This is where many empowerment efforts collapse.
An employee makes a decision inside the agreed space. The result is imperfect.
The manager says:
“Why didn’t you ask me first?”
The boundary has just moved.
If the decision ignored a clear red line, address that directly. Ownership includes respecting the decision field. But if the employee stayed inside the agreed space, used reasonable judgment, and encountered an outcome nobody could perfectly predict, the checkback should be used for learning.
Ask what they saw, how they reasoned, what evidence they used, and what the result teaches about the boundary or the play.
That does not mean accepting careless decisions. Judgment has standards.
It means refusing to teach people that independent decisions are welcome only when they produce exactly the outcome the manager hoped for.
People cannot develop judgment if they are allowed to exercise it only when nothing uncertain is at stake.
Make one invisible boundary visible this week
Listen for a recurring question that keeps coming back to a manager.
“Can I approve this?”
“Do you want me to proceed?”
“Should I escalate this?”
“Is this okay?”
Do not assume the employee lacks confidence or initiative. Look at the decision field.
What result should they be protecting? Which parts of this decision could reasonably belong to them? What conditions genuinely require another level of authority? When can you look at the next few real cases together?
Then make the first boundary visible.
If work is being assigned but nobody is clear who owns moving it after the conversation ends, Make Ownership Visible Before Work Leaves the Room can help turn agreement into an owner, next move, timing, and proof. If people know their authority but still return repeatedly to the familiar response because the workplace makes it safer, easier, or more rewarding, use Remove the Routine That Rewards the Old Behavior to examine the surrounding conditions.
Ownership does not grow because leaders say, “I trust you.”
It grows when people can see where they are trusted to decide, what they are expected to protect, where another decision is genuinely required, and how the field can widen as their judgment becomes stronger.
Give people room to decide—and make the edges visible enough that they can use that room with confidence and responsibility.