Asking people to think like owners sounds generous. It can also conceal an imbalance: the responsibility moves to the team while the information and authority remain with the leader. People are expected to take initiative, yet discover the limits only after acting. Under those conditions, waiting for permission may be a rational choice.

I believe ownership begins with a more demanding commitment from leadership. People need to understand where the business is going, why a priority matters and what tradeoffs the organization is willing to make. They need enough room to exercise judgment, with a clear understanding of the decisions that require a wider conversation.

That does not mean every decision should be shared or every boundary negotiated. A leader still has to set direction and protect the business. The question is whether those responsibilities create clarity for others or make the leader the permanent centre of every choice.

A boundary should make action possible

There is a difference between a useful limit and a permission system. A useful limit explains what must be protected: the customer promise, a commercial commitment, the purpose of the work. It helps someone decide what they can do. A permission system requires them to return for approval even when the relevant judgment could reasonably sit with them.

Moving from one to the other takes work. Leaders have to share context that may once have stayed in a smaller group. They need to explain their own reasoning and invite questions that expose an unclear priority. They also have to accept that a capable person may choose a sound route different from the one they would have chosen themselves.

That last point matters. Delegation loses credibility when authority is withdrawn whenever someone exercises it differently. Consistency does not require identical decisions; it requires a shared understanding of what the business is trying to achieve.

Development includes the difficult decision

Trust does not remove review. People deserve clear feedback, and the business needs honest examination of results. But a review should distinguish a careless decision from a considered choice that did not work as intended. Treating both in the same way can teach people to avoid the very judgment we want them to develop.

A useful conversation asks what was understood, what was uncertain and what should change. It can be direct about an error without making uncertainty itself unacceptable. Measured risk-taking needs that distinction if it is to mean anything in practice.

The leader must remain available, too. Giving someone responsibility and then disappearing leaves them to manage both the decision and the uncertainty around it. Support can mean listening, removing an obstacle, making a connection or helping someone think through a consequence. It need not mean taking the decision back.

The business should gain more leaders

The commercial reason to develop people is straightforward: a business needs judgment beyond the people at its centre. When more people understand the whole, it becomes possible to address problems closer to where they arise and to prepare others for larger responsibilities.

There is also a responsibility to the person. Development should expand their choices and their prospects, not simply increase what the organization asks of them. A conversation about ownership should include what they want to learn and where they want to go.

For me, empowerment is a continuing leadership obligation. Set a direction people can understand. Give them authority they can use. Stay accountable for the environment in which they decide. Then make room for their judgment to become stronger than it was before.

Technology is often introduced with a promise to free people for more valuable work. Whether that happens depends on the work we leave them with. A person can remain in a process yet have little real influence over it: approve the recommendation, manage the exception, accept responsibility when something goes wrong.

I believe a useful system should strengthen a person's ability to make a decision. That includes bringing relevant information together, making assumptions easier to see and giving someone a practical way to challenge the result. Speed matters, but so does understanding what the system is asking the business to do.

This is a commercial question before it is a technical one. The team needs to agree on the decision, the purpose it serves and the responsibility that should remain with people. Otherwise, the system can become a substitute for a conversation leadership has not finished.

A recommendation is a point of view

A purchasing recommendation, for example, reflects choices about demand, inventory and supply. Those choices give information a purpose, but they also create assumptions. The recommendation cannot be assessed well if the person reviewing it has no way to understand those assumptions or recognize when they no longer fit.

In my work on store-specific replenishment tools, sales, inventory and supply information feed purchasing recommendations that people review. The implemented capability supports the decision; the team remains responsible for submission.

I value that distinction. It creates a place for judgment before action. It also raises a continuing design question: does the person have what they need to make the review meaningful? A review step alone cannot answer that.

Involve the people whose judgment will change

Early involvement is often discussed as a way to improve adoption. It has a deeper purpose. People close to the work can explain which information is unreliable, which exceptions matter and where a decision carries consequences the proposed design has missed.

Listening does not mean every preference becomes a requirement. It means the team can see how the problem is being understood and can challenge that understanding before it becomes difficult to change. Leaders need to explain the purpose, make tradeoffs visible and respond seriously to concerns.

Training then needs to reach beyond which control to use. People should understand when a recommendation deserves closer examination, what authority they have to change it and how to raise a problem that belongs to the system rather than the individual user. Ownership needs that practical substance.

Keep responsibility understandable

There are decisions where greater automation is appropriate. Requiring manual attention for everything can create its own burden and make careful review less likely. The choice should depend on the consequences of an error, the reliability of the information and the business's ability to recognize when circumstances have changed.

Whatever level of automation is chosen, responsibility should remain intelligible. Someone needs to own the purpose and limits of the system. Someone needs to listen when the people using it find a mismatch between its recommendations and the work. Those responsibilities do not disappear after launch.

The question I return to is whether the technology makes the business more capable of understanding and acting on its choices. A system earns its place when it helps people do that work well, with authority that matches the responsibility we continue to ask them to carry.

A commercial opportunity rarely arrives at the exact moment an organization feels ready for it. Waiting for complete readiness can mean missing the opportunity. Moving ahead without examining what the business can carry can create a different problem: a plan that depends on people repeatedly making up the difference.

That tension cannot be solved by choosing ambition or discipline once and for all. Leaders have to keep bringing them into the same conversation. What is worth pursuing now? What must be strengthened along the way? What are we willing to stop doing so the important work has a realistic chance?

I believe a useful test of growth is the business it leaves behind. Has it developed people who can make harder decisions? Are responsibilities clearer? Does the organization understand its dependencies better? Those questions belong alongside the commercial opportunity, even when the immediate result is demanding attention.

Exceptional effort is not an operating plan

Committed people can carry a business through a difficult period. Their willingness to help is valuable, but it can also make weaknesses harder to see. If the same people must continually reconnect the same handoffs or resolve the same ambiguity, their effort may be protecting a problem from scrutiny.

The response should not be to devalue that commitment. It should be to ask what the business owes those people in return. Clearer decisions, better information, useful tools and stronger colleagues can turn individual effort into a capability others can use.

This requires commercial judgment. Every process does not need to be standardized, and every difficulty does not justify a new system. Some variation belongs close to the customer. The aim is to identify the recurring work that matters enough to strengthen without making the organization slow or rigid.

Make room for people to grow with the plan

Expansion can change a person's job before anyone changes their expectations or support. A decision that once involved a small group may begin to affect several functions. Informal knowledge may no longer reach everyone who needs it. A capable person can find themselves carrying a new level of responsibility with the old level of context.

Leaders need to notice those changes. Developing people means helping them understand the wider business and giving them opportunities to exercise judgment. Training matters, but so do access, feedback and the authority to act on what they learn.

It also means being honest about capacity. Adding a priority without reconsidering existing commitments is still a decision; it merely leaves the tradeoff for someone else to make. Leadership should make that choice visible and take responsibility for it.

Build for the next decision

Technology can help a growing organization share information and make work more repeatable. It should follow a clear understanding of where the business needs support. A system introduced around an unresolved question may simply make that question harder to change later.

I would rather ask what decision is becoming more difficult, who should own it and what would help them decide well. That keeps the conversation close to commercial purpose. It also makes it easier to judge whether the proposed change is useful.

Growth does not have to wait until every capability is complete. But it should come with deliberate choices about what to build, who to develop and which demands to remove. The next stage of the business should have more to stand on than the extraordinary effort that got it there.