Two Companies, One Roof: Reconciling Your Formal Structure with How Work Actually Gets Done

Every growing company reaches a point where its official organizational chart and its operational reality begin to drift apart. The chart says one thing. The Monday morning standup reveals another. Approvals that are supposed to travel through three management layers somehow resolve in a hallway conversation between two people who hold no formal authority over the matter. Projects move forward—or stall—based on relationships, institutional knowledge, and unwritten rules that no onboarding document has ever captured.

This is not a dysfunction unique to poorly managed companies. It is, in many respects, a natural byproduct of growth. The challenge is that when the gap between the formal and the functional becomes too wide, it creates serious downstream consequences—for compliance, for accountability, and for the organization's ability to scale with any consistency.

How Shadow Structures Form

Informal operating systems do not appear overnight. They accumulate over time, one workaround at a time. A new process is introduced, but it adds friction, so a faster path emerges. A department head becomes overwhelmed, so a high-performing individual contributor starts making calls that technically fall outside their purview. A cross-functional initiative lacks clear ownership, so whoever is most motivated simply absorbs the responsibility.

None of these moments feel significant in isolation. Collectively, they construct what organizational theorists sometimes call a "shadow hierarchy"—a parallel structure of influence, decision-making authority, and workflow routing that operates independently of the formal one. In many cases, this shadow system is remarkably effective. It is adaptive, efficient, and built on genuine trust. The problem is that it is also invisible to anyone who wasn't there when it formed.

For US businesses in particular, where rapid scaling and lean team structures are common, these informal networks tend to calcify quickly. What begins as a practical workaround becomes the institutional norm—and eventually, no one can remember why the formal process exists at all.

Why Leadership Rarely Sees It

Senior leaders are often the last to recognize the divergence between their stated operating model and the one actually in use. This is partly a function of position. The higher someone sits in an organization, the more filtered their view of daily operations becomes. They receive summaries, not raw data. They attend strategic reviews, not the conversations that precede them.

There is also a cognitive dimension at play. Leaders who built or shaped a company's formal structure have a natural investment in believing that structure works. Acknowledging that the org chart has become largely ceremonial requires confronting years of decisions, many of which made sense at the time they were made.

Finally, the informal system often does work—at least in the short term. Output continues, deadlines are met, and the absence of visible failure removes the urgency to investigate. The problems tend to surface only when the organization attempts something new: a major hire, a regulatory audit, a merger, or an expansion into a new market. At that point, the gap between the documented structure and the operational reality becomes impossible to ignore.

The Compliance and Accountability Stakes

For organizations operating in regulated industries—financial services, healthcare, manufacturing, and others—the divergence between formal and functional structure carries direct compliance risk. Regulatory frameworks are designed around documented accountability. When the actual decision-making chain differs from the one on record, organizations can find themselves unable to demonstrate who approved what, when, and under what authority.

Beyond regulatory exposure, informal structures create accountability blind spots that are difficult to address without first making them visible. When a decision goes wrong and no formal process governed it, there is no clear path to understanding the failure or preventing its recurrence. The organization is left managing consequences rather than causes.

Scaling compounds these risks. What functions as an informal understanding among twenty people becomes a source of significant confusion among two hundred. New employees cannot read the institutional memory that the shadow system depends on. They follow the documented process, encounter friction, and either disengage or begin building their own workarounds—adding yet another layer of informal complexity.

Mapping the Real Operating System

Addressing this challenge begins with honest observation. Before any redesign or realignment effort, organizations need an accurate picture of how work actually flows—not how it is supposed to flow.

Several approaches can facilitate this:

Process shadowing and workflow interviews. Structured conversations with employees across levels—not just managers—can surface the informal routing paths, decision shortcuts, and undocumented approval chains that have become standard practice. These conversations are most productive when framed as discovery rather than audit.

Decision mapping. Identifying a set of recurring decisions and tracing their actual path—who initiates, who consults, who approves, who is informed—often reveals significant divergence from the formal RACI or governance model. The gaps in that map are precisely where risk concentrates.

Network analysis. In larger organizations, communication and collaboration data (where permissible and appropriate) can reveal informal influence networks that are not reflected in the org chart. Individuals who serve as connectors or informal approvers often become visible through this kind of analysis.

The goal is not to eliminate the informal system. Much of it represents genuine organizational intelligence—accumulated expertise, trusted relationships, and adaptive problem-solving. The goal is to understand it well enough to make deliberate decisions about what to formalize, what to preserve, and what to redesign.

Aligning Structure with Reality

Once the real operating model is visible, organizations face a choice: update the formal structure to reflect how work actually happens, or invest in changing behaviors to match the stated structure. In practice, most successful realignments involve elements of both.

Certain informal practices deserve formal recognition. If a particular individual has been functioning as the de facto decision-maker in a domain, acknowledging that authority explicitly—and establishing the accountability that should accompany it—is often more productive than attempting to redirect decision flow through channels that have proven ineffective.

Other informal workarounds signal genuine process failures that should be addressed directly. If employees are consistently bypassing a formal approval step, the question worth asking is not how to enforce compliance with that step, but whether the step itself serves a legitimate purpose and, if so, how to make it less burdensome.

Formal governance documents, job descriptions, and process maps should be treated as living records—updated as the organization evolves rather than preserved as artifacts of a prior state.

The Strategic Value of Organizational Clarity

Companies that invest in aligning their formal and functional operating models tend to move faster, onboard more effectively, and respond to disruption with greater agility. They are also better positioned to demonstrate accountability when regulators, investors, or board members require it.

The informal organization is not the enemy of the formal one. In most cases, it reflects the genuine ingenuity of people trying to get things done. The opportunity lies in making that ingenuity legible—capturing it in a structure that can survive turnover, support growth, and hold up under scrutiny.

For organizations serious about sustainable performance, that kind of operational clarity is not optional. It is foundational.