Every organization has rules.
Some are followed carefully because people understand why they matter; others remain in procedures, contracts, policies, or process documents even as daily work gradually develops a different way of operating. That divergence rarely begins with a deliberate decision to break a rule. People may be relying on an old assumption, trying to satisfy a customer, saving money, protecting a schedule, bypassing a process that feels too slow for a simple decision, or quietly solving a problem before anyone else needs to know.
Each choice may appear reasonable on its own, yet together they can create two increasingly different systems: the written system and the system that actually governs the work. That gap deserves attention.
The Written Process Is Not Always the Real Process
Rules serve different purposes. Some establish legal or contractual obligations; others protect quality, safety, cost, schedule, or consistency. Still others simply capture how someone once believed the work should be performed. The difficulty is that a rule can remain formally in place long after everyday behavior has begun to move around it. That does not necessarily mean the rule is wrong. People may not understand it, the process may be cumbersome, competing expectations may make compliance difficult, or the organization may have stopped reinforcing something it still claims is important.
Whatever the cause, repeated workarounds are useful information. When capable people repeatedly choose a path other than the documented one, the first question should not always be, “Why won’t they follow the process?” A better question may be, “Why does the process keep losing to the way the work is actually being done?”
Familiarity Can Become an Unwritten Rule
A follow-on contract can introduce new requirements even when nearly everything about the work feels familiar. An experienced workforce may have performed successfully for years, the customer and tasks may be well known, and the organization may already know how to staff the effort. If the new contract changes qualification requirements but the staffing model continues unchanged, no one may have consciously chosen to ignore the requirement. Instead, the organization keeps operating under an older, unwritten rule: these are the people who do this work. Operational experience continues to govern the decision even though the contractual requirement has changed.
The same drift can occur with planning assumptions. A maximum potential workshare becomes the figure used for forecasts; the forecast then flows into budgets and staffing plans and is repeated in meetings and presentations until a possibility begins to feel like an expectation. No written rule has changed, but repetition has changed the meaning. Eventually, the organization may behave as though something was promised that was never guaranteed. These are not dramatic acts of noncompliance. They are quieter examples of the operating system drifting away from the formal one.
Good Intentions Can Bypass a Safeguard
The same pattern appears when people are trying to help a customer. In one case, a customer requested what seemed to be a simple, one-time report, and a technical employee agreed because the request did not appear significant enough to justify a broader discussion.
After the report was delivered, however, the customer began expecting a similar 15-page report every month. A small informal decision had created a recurring expectation. The eventual solution was straightforward: determine what information the customer actually needed and incorporate it into an existing required report. Unfortunately, that conversation occurred only after the expectation had already been established. The coordination process was not intended merely to make a simple request more difficult; it existed to prevent an informal request from quietly becoming an ongoing obligation.
In another case, a customer wanted a substantially cheaper tool purchased from an online retailer rather than through the established supplier channel. Agreeing appeared both customer-friendly and financially responsible, but the cheaper tool could not perform the required task. The correct tool still had to be purchased, the original cost had to be absorbed, and the delay affected the schedule. Once again, the established process looked like an obstacle when the decision was made, but its purpose became much clearer after the problem occurred. That is one of the central challenges with rules and controls: when they work, we often notice their inconvenience more than the problems they prevent.
Silence Can Become an Unwritten Rule
Not every important rule is written. Consider how an organization communicates developing problems. Most organizations say they value early warning and do not want customers to be surprised, yet day-to-day behavior inside a project may communicate a different set of expectations: try to solve the issue first, do not escalate until you understand it, avoid worrying the customer unnecessarily, and bring the problem forward only when you have an answer. None of those instincts is inherently unreasonable, but together they can create a powerful unwritten rule: do not communicate uncertainty. That rule can become stronger than the organization’s stated commitment to “no surprises.”
A technical problem may remain within engineering while the team tries one solution and then another. The issue begins to affect the schedule, but everyone still believes recovery is possible, so communication is delayed until cost or a customer commitment is threatened. What appears to the customer as a sudden failure may actually have been developing internally for weeks. No one necessarily decided to conceal the problem; people simply followed the behavior the system had taught them—solve first, communicate later. In that moment, the unwritten rule won.
Repeated Workarounds Are Data
This is why I hesitate to dismiss ignored rules as nothing more than an employee-discipline problem. Sometimes that is exactly what they are: a clear, necessary, and reasonable requirement is not followed, and accountability matters. Even so, repeated noncompliance should tell us something about the surrounding system.
If people regularly commit to customer requests before the right functions are involved, why? If employees consistently bypass an approval process, what does the normal process make difficult? If forecasts routinely become commitments in people’s minds, where did the distinction disappear?
If teams repeatedly wait too long to communicate problems, what do they believe will happen if they raise uncertainty earlier? If a purchasing control is routinely dismissed as bureaucracy, does everyone understand the risk it is intended to manage? The workaround itself may be wrong, but understanding why it exists can reveal something important about the system around it.
Fix the Rule or Reinforce It
Once a gap becomes visible, an organization must decide whether to fix the rule or reinforce it. If the rule is necessary, it should be explained, consistently applied, and supported with a clear account of both its purpose and the risk it controls. If the process no longer fits the work, it should be changed. The worst option is often the one organizations tolerate the longest: leaving the written rule in place while everyone quietly understands that actual practice is different.
That tolerance creates two systems. One lives in contracts, procedures, policies, schedules, and presentations; the other lives in conversations, habits, shortcuts, assumptions, and experience. Long-tenured employees may learn how to move between them, while new employees, customers, auditors, managers, and other functions see only the formal version. Eventually, pressure exposes the difference, and someone asks why the process was not followed, why a requirement was missed, why the customer expected something different, or why a problem was not communicated sooner. The answer is often that the written system stopped being the system people were actually using long before the failure occurred.
Pay Attention to the Gap
Rules, processes, and contracts matter, but documenting them does not guarantee that they govern behavior. People learn a system partly by reading what is written and partly by watching what actually happens. They notice which approvals are expected, which requirements are enforced, which shortcuts are tolerated, which problems must be escalated, and which procedures everyone quietly works around. Over time, those observations become their understanding of how the organization truly operates.
That is why the rules we ignore are telling us something. Sometimes they tell us that people need to follow the process; sometimes they tell us that the process needs to change; and sometimes they reveal a fault line between what the organization says matters and what its daily behavior has taught people actually matters. The important thing is to notice that gap before pressure notices it for us.