The Moment Informality Stops Being Agile

In an illustrative growing company, two managers face almost the same customer exception in the same week. One sends a message to the founder, receives a two-line answer and resolves the matter before lunch. The other follows the published route, asks three functions for input and is still waiting two days later.

The first manager looks decisive. The second appears procedural. Yet their difference may have little to do with judgment. One knows which person can interpret the unwritten rule, how to frame the request and which prior exception will make the answer obvious. The other knows only the formal process.

This is the moment informality begins to change character. What once made the company fast starts making speed dependent on proximity. The organization still feels agile to insiders because they can move through it by relationship and memory. To everyone else, it is a maze whose shortcuts are visible only after years of participation.

Informality is a technology of shared context

Young companies rarely begin with complete role definitions, decision matrices or carefully maintained operating manuals. They begin with a small group that sees much of the same reality. People hear the same customer conversations, remember why a promise was made and understand which principle matters when two priorities collide. A five-minute exchange can carry enormous meaning because most of the relevant history is already present in the minds of the people involved.

In that setting, informality is not the absence of management. It is a highly compressed management technology. Shared context substitutes for explanation. Trust substitutes for verification. Direct access substitutes for a designed route to authority. Flexible roles allow work to move toward whoever can solve it fastest.

These arrangements can be a genuine advantage. A company should not bury useful judgment under process merely because it has started to grow. The error is to treat the early mechanism as if its performance came from having no structure at all. Its speed came from a structure that was largely social, remembered and overlapping.

As the company expands, that overlap narrows. New employees did not witness the trade-offs that shaped the current policy. Teams encounter different customers and begin accumulating different versions of what the company values. Senior leaders can no longer maintain direct relationships with everyone who needs a decision. The unwritten operating model remains, but access to it becomes uneven.

The organization has not become less informal. It has become selectively informal.

The network becomes unequal before it becomes slow

The earliest warning is often not a visible delay. It is a difference in who can avoid the delay.

Long-serving employees know whom to call before submitting a request. They understand which words will signal urgency without sounding alarmist. They know when a rule is a genuine boundary and when it is a statement designed for ordinary cases. They can predict which executive will support an exception and which stakeholder must be consulted privately first.

Newer employees may be equally capable, but they cannot act on knowledge they have not inherited. They use the process as written and discover that the written process does not contain the real path to a decision. Their work circulates until an insider translates it.

This creates more than inconvenience. It creates unequal operating power. The people closest to the informal network can offer customers faster answers, secure resources earlier and shape decisions before the formal discussion begins. Others become dependent on brokers who can decode the organization for them.

Because the difference is relational, it can be misread as talent. Leaders praise the people who "know how to get things done" without asking why getting things done requires private access. The organization begins selecting for navigation skill as much as business judgment. Employees learn that influence comes from knowing the route around the system rather than improving the route through it.

Over time, the network also becomes fragile. A few interpreters carry the connection between formal rules and actual practice. When one leaves, takes leave or moves roles, ordinary work slows because the organization has lost not only a person but a privately held map.

Bureaucracy is the wrong opposite

When leaders finally notice the problem, they often frame the choice badly. Either the company preserves its entrepreneurial informality or it becomes bureaucratic.

That choice invites two predictable mistakes. One is to defend every unwritten practice in the name of speed. The other is to document everything, add approval gates and turn judgment into compliance. The first protects unequal access. The second can destroy the discretion that made the company responsive.

Agility is not the absence of structure. It is the ability to move quickly with enough shared context and sufficiently clear authority. A company is not agile merely because a well-connected employee can obtain an answer in minutes. It is agile when similarly capable people can recognize the issue, find the relevant context and reach the person entitled to decide without reconstructing the organization each time.

The aim, therefore, is not to replace conversation with procedure. It is to make the route to judgment legible.

Some decisions should remain conversational because they are novel, consequential or genuinely ambiguous. But employees should know why the conversation is needed, who closes it and what happens to the learning afterward. Some rules should remain principles rather than scripts, but the examples that give those principles meaning should be accessible beyond the original circle. Some leaders should remain reachable, but access should not be the hidden permission system on which routine execution depends.

Make speed portable

A useful redesign begins with the recurring situations in which insiders move quickly and others stall. The question is not, "How do we force everyone through the formal process?" It is, "What does the insider know that the process fails to carry?"

Sometimes the missing element is a decision threshold. A manager can resolve a customer concession up to a defined commercial exposure, but nobody has made that boundary explicit. Sometimes it is precedent. Several similar cases have already been decided, yet the rationale remains in private messages. Sometimes it is ownership. Multiple functions provide input, but the person who can reconcile those views is unnamed. Sometimes it is language: a policy uses broad terms such as material, strategic or exceptional without examples that allow judgment to become consistent.

Making these elements visible does not require a manual for every possibility. It may require a small number of durable mechanisms: a clear owner for a recurring outcome, explicit limits within which local judgment is trusted, a searchable record of meaningful precedents, and an escalation route that distinguishes consultation from permission.

The design should also preserve the quality of informal exchange. A manager should still be able to call a colleague, test an interpretation and learn from experience. The difference is that the organization no longer depends on that private exchange to establish who is allowed to act. Conversation enriches the system rather than secretly replacing it.

Leaders play a decisive role in whether this transition succeeds. If they continue rewarding only the people who reach them privately, employees will correctly conclude that formal authority is decorative. If leaders answer recurring questions without asking why the route remains unclear, they become the help desk for an unwritten model. If they explain the principle, identify the owner and allow the decision to stand within agreed boundaries, they convert personal access into organizational capability.

The test is whether agility survives distance

Informality should be judged by what happens when shared history, physical proximity and personal familiarity decline.

Can a capable manager in another location resolve the same class of issue without knowing the founder personally? Can a new leader understand not only the rule but the trade-off the rule protects? Can the person closest to the work act within known boundaries and receive fair review afterward? Can a meaningful exception teach the wider system, or does its reasoning disappear into a private conversation?

These questions do not ask the company to become impersonal. They ask whether its speed belongs to the organization or only to a network inside it.

The transition point is easy to miss because informality continues to work for the people with the strongest access. They may sincerely experience the company as responsive and low in bureaucracy. Meanwhile, everyone outside the inner map is spending time locating context, seeking sponsorship and protecting themselves from invisible boundaries.

That is not agility at scale. It is a fast lane available to those who already know the road.

A growing company preserves its entrepreneurial advantage when it makes judgment easier to exercise, not when it keeps the route to judgment unwritten. The goal is not to formalize every conversation. It is to ensure that capable action does not depend on private geography.

Informality stops being agile when speed can no longer travel without the people who remember how it used to work.