Once leaders repeatedly bypass a process for one person, the exception quietly redesigns the organization. This is what I think of as the law of permission: whatever a leader consistently permits eventually becomes part of the company’s real policy, whether or not it appears in an employee handbook, performance framework or operating manual.
People pay attention to what leaders allow. They observe the behaviour that receives a correction, the missed deadline that passes without consequence, the poor performance that is repeatedly explained away and the standard that changes whenever a particular person is involved. From those observations, they learn how the organization actually works.
The written policy may say one thing, but the leader’s response teaches something else. When the two conflict, people will usually believe what they repeatedly see.
This is why seemingly small exceptions matter. An exception may begin as compassion, convenience or an attempt to avoid an uncomfortable conversation, but when it continues without a clear reason or boundary, it establishes a precedent. Other people begin to expect the same treatment, managers lose confidence in enforcing the original standard and the company gradually becomes something its leaders never consciously decided to build.
What you permit teaches the organization
A few days ago, we were having a meeting at my office and someone was making a presentation remotely. The person’s internet connection was poor, so the audio kept breaking and the presentation repeatedly stopped. This continued for several minutes while everybody waited and tried to understand what was being said.
Eventually, I interrupted and asked the meeting coordinator why our time was being wasted.
I was not blaming the presenter for having a bad internet connection because some circumstances are outside a person’s immediate control. My concern was that the coordinator had allowed the meeting to continue even though it was obvious that the format was no longer working. The person could have been asked to record a video, send the presentation, move closer to a better connection or return to the discussion at another time. There were several reasonable alternatives, but allowing everybody to remain in an unproductive meeting was not one of them.
The issue was not merely the internet connection. It was the standard being communicated to everyone present. If a meeting can continue when nobody can hear the presentation, we are silently teaching people that time does not matter, that the coordinator does not need to make a decision and that everyone else should tolerate inefficiency to avoid a moment of discomfort.
Leaders must respect people’s time. When several people attend a meeting, the company is spending all of their time simultaneously. A ten-minute delay involving ten people is not only ten minutes; it is one hundred minutes of collective working time. The coordinator of a meeting therefore has a responsibility to determine whether the conversation remains useful and to intervene quickly when it does not.
Sometimes leadership is simply the willingness to say, “This is not working. Let us stop, choose another approach and continue when we can use everybody’s time properly.”
Failure to decide is still a decision
I have also had to intervene when some leaders were weak in evaluating the performance of members of their teams. The evidence showed that someone was underperforming, but the leader kept postponing the decision, offering new explanations or hoping that the problem would somehow resolve itself.
My response was that the leader had to make a decision.
When a leader refuses to address persistent low performance, the leader is not remaining neutral. The leader has made a decision to permit the performance. That permission affects more than the individual involved because everyone else can see what is happening.
Strong performers notice when weak performance has no consequences. They see that the company demands more from them while continuing to accommodate someone who contributes less. Over time, they either reduce their own effort, lose confidence in the leader or leave for an organization where excellence is protected.
This is how mediocrity becomes culture. It does not usually arrive through a formal announcement that the company has lowered its standards. It enters through delayed conversations, repeated exceptions and leaders who know what should be done but do not want to carry the emotional burden of doing it.
There was a recent situation in which members of the team tried to persuade me to retain someone even though the person’s performance was average. My response was no, because the decision was not only about the person currently occupying the role. Keeping an average person in an important position also prevents an exceptional person from entering the organization and doing what the role requires.
Every position has an opportunity cost. When a company continues to employ someone who cannot produce the required outcome, it is not simply paying that person’s salary. It is also losing the value that a stronger person could have created with the same authority, information, budget and time.
This does not mean leaders should dismiss people impulsively or refuse to help them improve. Expectations should be clear, feedback should be honest, appropriate support should be provided and people should have a reasonable opportunity to demonstrate progress. However, once the evidence is sufficient, refusing to decide is unfair to the company and to the people who are carrying more than their share of the work.
Exceptions require boundaries
Organizations will always need exceptions because people are human and circumstances differ. Someone may experience illness, bereavement, a family emergency or another situation that deserves compassion. A strategic customer may require an unusual commercial arrangement. A promising employee may need additional time to grow into a demanding role.
The danger is not the existence of every exception. The danger is an exception that has no stated reason, owner, duration or point of review.
If a leader chooses to make an exception, the leader should be able to explain why it serves the company’s values or objectives, how long it will last and what must happen before the normal standard resumes. Otherwise, temporary accommodation quietly becomes permanent entitlement.
There is also a difference between mercy and the abandonment of standards. A leader can treat someone with kindness while remaining honest about what the role requires. Compassion should help a person through an exceptional season; it should not force the organization to pretend that an unacceptable outcome has become acceptable.
When exceptions are necessary, they should be deliberate. When they are accidental, repeated and unexamined, they become policy.
Leaders must challenge inherited assumptions
The same law of permission applies to the way companies adopt technology and pursue ambitious targets. My co-founder and I recently made a decision to increase our use of AI agents because I kept returning to a basic question: if we have an important target that must be achieved within ten weeks, why are we assuming that the answer is simply to hire more people or extend the deadline?
There has to be a clear explanation for why the work cannot be completed within the available period. Perhaps the technology required will cost $100,000 and the company currently has only $10,000. That would at least reveal the actual constraint and allow us to make an intelligent trade-off between money, scope and time. What I do not want to hear is that the company needs several more months merely because the team plans to continue working in the same way it has always worked.
Companies around the world are redesigning work around AI agents and significantly smaller teams. Some are reducing their engineering headcount because a few strong people, using the right tools and systems, can now produce what previously required a much larger team. We should not observe that change and continue planning as though the economics and speed of building have remained the same.
If leaders continue approving additional headcount without first asking whether technology can multiply the existing team, hiring becomes the company’s default response to every capacity problem. That is another form of permission. The leader has taught the organization that it does not need to redesign work, remove unnecessary steps or explore better tools before requesting more people.
The proper question is not simply, “How many people do we need?” It is, “What is the fastest, most intelligent and most economical way to achieve the required outcome?” The answer may still involve hiring, but hiring should follow the redesign of the work rather than replace it.
Challenge people without becoming unreasonable
One of the responsibilities of a leader is to challenge people beyond the limits they have accepted for themselves. Teams can become attached to familiar processes, conventional timelines and assumptions that were formed before better tools became available. Without pressure from leadership, those assumptions may survive long after they have stopped making sense.
Challenging people does not mean setting impossible targets and blaming them when they fail. It means refusing to accept an explanation merely because it sounds familiar. It means asking what the true constraint is, what assumptions have not been tested, what could be automated, what could be removed and what an exceptional person or team would do differently.
The leader must also be willing to provide the resources, authority and clarity required for the higher standard. It is unreasonable to demand an ambitious outcome while withholding the decisions, tools or budget that make the outcome possible. Excellence requires accountability on both sides: the team must own the outcome, and leadership must remove avoidable obstacles.
However, once the objective is clear and the necessary support is available, the organization should not keep negotiating with mediocrity. A company cannot become excellent while continually making peace with average execution.
Culture is built through intervention
Leaders sometimes believe culture is created mainly through speeches, value statements and onboarding materials. Those things can help, but culture is formed more powerfully in the moments when something goes wrong and people watch what the leader does next.
What happens when a meeting wastes everyone’s time? What happens when a leader refuses to evaluate a weak performer? What happens when an important deadline is missed without a credible explanation? What happens when a team requests more people before redesigning its work? What happens when a high performer violates a value that everybody else is expected to respect?
The answers become the culture.
This is why I sometimes intervene quickly. It is not because the individual incident is always catastrophic, but because leaving it unaddressed teaches the wrong lesson. The longer an undesirable behaviour remains visible and permitted, the more difficult it becomes to correct without appearing inconsistent.
Intervention does not always require anger or punishment. Sometimes it requires a question, a reminder, a private conversation or a clearer process. At other times, particularly when the pattern has continued despite feedback, it requires a firm decision. The appropriate response will vary, but silence is also a response, and people will interpret it as permission.
Leaders must therefore pay attention to the small things they repeatedly allow. A delayed decision can become a performance standard. A poorly managed meeting can become the company’s attitude towards time. An unnecessary hire can become the operating model. One favoured person’s exception can become everybody’s expectation.
Policies are not created only when leaders write them down. They are also created whenever leaders repeatedly demonstrate what the organization will tolerate.
Every exception does not have to become a policy, but every repeated exception eventually will. The leader’s responsibility is to notice the moment when compassion, convenience or indecision begins to redesign the organization, and to intervene before permission becomes culture.
Leave a Reply