This morning, Mr. Yeser’s Underground reported that a company launched a trust initiative requiring employees to obtain approval before acting independently. The joke works because many organizations speak constantly about ownership while designing systems that prevent people from owning a meaningful decision.
Leaders tell employees to take initiative, solve problems, act like owners, and accept responsibility for outcomes. Then they reserve the authority to choose the method, approve the timing, control the communication, and reverse the decision.
That is not trust. It is responsibility without authority.
A person cannot own an outcome while every meaningful choice still belongs to someone else. The organization may have delegated the work. It has not delegated the decision.
Ownership requires a real decision
Ownership is not an attitude people can be instructed to display. It exists when someone is responsible for a result and has enough room to make the choices that produce it.
A principal cannot own the culture of a school if every staffing, schedule, discipline, communication, and budget decision must be approved elsewhere. A teacher cannot own a classroom if every response is reduced to a script. A department leader cannot own a deadline if another office controls the people, priorities, and sequence of the work.
Responsibility without authority turns ownership into exposure. The person closest to the work remains accountable when the result fails, but cannot change the conditions that keep producing the failure.
This is why some organizations appear full of people who wait. Waiting is often not laziness. It is learned accuracy. People have discovered that acting is praised in theory and punished whenever the action differs from the preference of someone with more authority.
Control does not disappear when the language softens
Modern organizations rarely announce that they do not trust their people. They talk about alignment, consistency, support, visibility, quality assurance, and stakeholder awareness. Each of those can be legitimate. Together, they can also create a permission system nobody is willing to name.
The meeting before the decision becomes collaboration. The form becomes documentation. The additional approval becomes partnership. The dashboard becomes transparency. The person making the decision receives every word associated with trust except the ability to act.
Language matters because it can hide the trade being made. Control may reduce variation. It may protect against a serious legal, financial, or safety error. It also slows decisions, moves responsibility away from the work, and teaches capable people that judgment is something to present rather than use.
The question is not whether a control sounds responsible. The question is whether the risk it prevents is worth the authority it removes.
Trust includes the possibility of an imperfect choice
Trust is not blind. It does not mean everyone can do anything without limits, evidence, or consequences. It means the organization accepts that a capable person may make a reasonable choice that is not the exact choice the leader would have made.
If only one decision is permitted, the system does not need judgment. It needs compliance.
This is the uncomfortable part of trust. A trusted employee may select a different vendor, answer the customer differently, organize the work in another order, or solve the problem without using the leader’s preferred language. Some choices will be better. Some will be worse. Many will simply be different.
Leaders who cannot tolerate difference often describe the issue as quality. Sometimes it is. Sometimes the result is acceptable and the real violation is that the leader was not the person who produced it.
Boundaries make authority usable
Real authority does not require removing every boundary. It requires making the boundary clear enough that a person can act without guessing where authority ends.
A useful boundary might define the budget, legal requirements, safety rules, deadline, audience, or outcomes that cannot be compromised. Inside that boundary, the person responsible for the work chooses. Outside it, the decision is escalated.
That is different from asking for approval because the leader may have an opinion. An opinion is not automatically a boundary. A preference is not automatically a risk. If every choice is escalated whenever someone higher in the organization might choose differently, the boundary is not clear. The boundary is the leader.
Good boundaries protect both sides. The employee knows which choices genuinely belong to them. The leader knows which risks remain protected. When something goes wrong, the conversation can focus on whether the boundary was clear, whether judgment was reasonable, and what should change next time.
Approval cultures teach people not to move
People adapt quickly to the actual system. If an independent choice creates a long review while waiting produces no consequence, they learn to wait. If leaders redo work instead of explaining the standard, people learn to submit unfinished work and let the leader complete it. If every mistake produces a new universal rule, one person’s error becomes everyone’s loss of authority.
Then leadership asks why nobody shows initiative.
The answer is often visible in the approval chain. Initiative has become a high-risk behavior. The employee who acts may be wrong, may be questioned, or may discover that the decision was never really theirs. The employee who waits can explain that the request remains with leadership.
An organization cannot train people to wait and then evaluate them for waiting. If it wants judgment, it must create places where judgment is permitted to finish the sentence.
Trust is learned by being given
People do not become ready for authority by being denied authority until they can prove they would use it perfectly. They become ready through smaller real decisions, visible consequences, honest feedback, and gradually wider responsibility.
Start with a decision that matters but can be repaired. Define the boundary. Let the person act. Review the result after the decision instead of converting every review into permission beforehand.
When judgment is poor, address the judgment. Make the next promise smaller if necessary. Clarify the boundary. Repair the harm. Extend authority again when the person is ready. Do not respond to every mistake by rebuilding the system around permanent suspicion.
Trust is not proven by the absence of risk. It is proven by what happens when risk becomes real: whether people tell the truth, take responsibility, repair what they can, and remain capable of earning another chance.
Give authority where responsibility already lives
Look at the people your organization already holds responsible. Ask what decisions they can make without waiting. If the answer is almost none, the organization is not asking for ownership. It is asking people to carry outcomes they do not control.
Move authority closer to the work. Keep the boundaries that protect people, law, safety, and the essential mission. Remove approvals that exist mainly because leadership is uncomfortable not being involved.
Then allow the decision to be different from yours without treating difference as disloyalty.
If every meaningful choice still belongs to you, you have not built a trusted team. You have built a waiting room.
