The Company Is Becoming a Protocol, Not a Place

What if the hardest part of remote work is not distance, technology, or culture? What if it is that most companies were never designed to function without a building around them?

A traditional office quietly performs thousands of coordinating tasks. People know where to go, whom to ask, when decisions are made, which information is current, and who has authority to resolve ambiguity. Remove the building and these invisible systems become visible. A video call can replace a conference room, but it cannot automatically replace trust, context, access, accountability, or judgment.

At the same time, the growth of independent professionals is challenging another assumption: that valuable work must happen inside the boundaries of a single employer. New labor platforms are beginning to treat work less like a collection of employees managed by a central firm and more like a shared protocol that allows many participants to coordinate, transact, and create value.

These developments appear to belong to different conversations. One concerns how established companies operate remotely. The other concerns how independent workers organize outside traditional employment. But they converge on a deeper question:

If the workplace is no longer defined by a common location or a common employer, what exactly holds productive cooperation together?

The answer is not simply technology. It is the quality of the organization’s operating protocol.

The Office Was a Protocol Disguised as a Building

When an executive asks, “How do I run the company through a WiFi connection?”, the question sounds technical. In reality, it is a question about institutional design. A company cannot become remote merely by transferring meetings to a screen. It must make explicit the rules and mechanisms that the office used to provide implicitly.

Consider a basic question: how does a person know what to do next?

In a physical workplace, the answer may emerge from casual observation. A colleague mentions a deadline in the hallway. A manager notices confusion during a meeting. Someone sees a draft on a desk and offers a correction. An employee learns priorities by listening to nearby conversations. These interactions are inefficient in some ways, but they provide a continuous stream of context.

Remote work removes much of this ambient coordination. The problem is not that people lack access to communication tools. The problem is that communication tools do not determine what deserves communication.

A company that operates through distributed work therefore needs explicit answers to questions such as:

• Where is the authoritative version of a decision?
• Which matters require a meeting, and which require written discussion?
• How quickly should different kinds of requests receive a response?
• Who can make a decision when the responsible person is unavailable?
• How are disagreements documented and resolved?
• What evidence determines whether work is progressing?
• How does a new participant acquire enough context to contribute intelligently?

These are not administrative details. They are the company’s operating system.

The office made many of these rules feel natural because physical proximity compressed the distance between information and action. In a distributed environment, every unanswered question becomes friction. A worker may spend an hour determining which document is current, wait two days for approval, or attend a meeting simply because no reliable record exists elsewhere.

This suggests a useful distinction: remote work is not a location strategy; it is a coordination strategy.

The companies that struggle most are often not those with the weakest collaboration software. They are those whose knowledge, authority, and trust were never encoded clearly enough to survive the loss of proximity.

From Employer to Protocol

The same issue appears from the perspective of independent work. Traditional organizations tend to divide people into two categories: insiders who belong to the company and outsiders who can be purchased when needed. This creates an “us versus them” relationship with freelancers. The employee is treated as part of the institution, while the independent professional is treated as a temporary object of procurement.

That distinction becomes less useful as specialized work grows more fluid. A product may require a researcher, designer, engineer, editor, legal specialist, and data scientist, but not all of them need to be permanent employees. What matters is not whether each person occupies a seat in the organization. What matters is whether the system can connect the right capabilities to the right problems, establish credible expectations, and distribute value fairly.

This is where the idea of a labor protocol becomes powerful. A protocol is not merely a marketplace or a directory. It is a set of shared rules that makes cooperation possible among participants who do not need to belong to one central hierarchy.

The internet itself provides an analogy. Email works because different providers agree on common protocols. A message can move between institutions because no single organization needs to own the entire system. The protocol establishes enough consistency for independent actors to interact.

A labor protocol could perform a similar function for work. It might define how people are discovered, how qualifications are demonstrated, how projects are scoped, how contributions are evaluated, how disputes are handled, and how participants receive compensation or influence. Once these foundations exist, many organizations can build services on top of them.

The important shift is conceptual. Instead of asking, “How do we control all the people needed to produce this outcome?”, an organization asks, “What rules and interfaces allow the necessary people to coordinate effectively?”

That is a profound change in the meaning of the firm. The company becomes less like a container holding labor and more like a platform that organizes capabilities.

The future organization may be defined less by who it employs than by the quality of cooperation it makes possible.

This does not mean hierarchy disappears. Someone still needs to set direction, allocate resources, and take responsibility for outcomes. But hierarchy becomes one component of the system rather than the system itself.

The Hidden Connection: Distributed Work Needs Public Goods

Remote companies and decentralized labor networks face the same fundamental challenge: they depend on shared assets that no single transaction pays for adequately.

A project team needs a reliable knowledge base. A freelancer needs a credible reputation. A client needs confidence that a specialist will deliver. Participants need clear procedures for resolving disputes. These assets benefit many people at once, but they are difficult to produce through isolated transactions.

Economists often call such assets public goods. In organizational life, they include trust, standards, documentation, identity, reputation, and common infrastructure.

A conventional company often funds these goods through a central budget. It pays managers to coordinate, maintains internal systems, trains employees, and absorbs the cost of building shared knowledge. But it can also hide the cost. Employees may rely on undocumented norms, personal relationships, and institutional memory without recognizing how much value those systems create.

A more distributed model must make these public goods explicit. If no one maintains the project archive, the archive decays. If no one validates expertise, reputation becomes marketing. If no one maintains decision rights, every issue escalates to the loudest or most senior participant.

This leads to a practical framework for designing distributed organizations. Every organization should deliberately build four layers:

1. The identity layer

Who is participating, and what can they credibly claim to know or do? Identity does not have to mean a résumé. It may include verified work, peer endorsements, past outcomes, or demonstrated competence in a specific context.

2. The transaction layer

How does work begin and end? This includes project scopes, commitments, timelines, payment terms, ownership of outputs, and definitions of completion. Ambiguity here creates conflict later.

3. The governance layer

Who makes decisions, who can challenge them, and how are disputes resolved? Governance is not bureaucracy for its own sake. It is the mechanism that prevents coordination from depending on personal power or constant executive intervention.

4. The learning layer

How does the system improve? A completed project should leave behind more than a deliverable. It should produce reusable knowledge, better templates, clearer standards, and improved judgment.

Many companies invest heavily in tools while neglecting these layers. They purchase messaging platforms, project management systems, and digital whiteboards, then wonder why work remains fragmented. The tools are visible. The protocol is not.

The Danger of Mistaking Flexibility for Freedom

Distributed work is often celebrated for its flexibility. But flexibility without structure can become insecurity, and autonomy without information can become abandonment.

An employee who is told to work independently but cannot discover priorities is not empowered. A freelancer who can choose projects but has no credible way to signal quality is not participating in a healthy market. A team that can communicate at any hour but lacks rules for attention may become permanently available and intermittently productive.

This is why the most important design principle is not maximum freedom. It is bounded autonomy.

Bounded autonomy means giving people meaningful control within a structure that makes cooperation predictable. A surgeon does not experience a sterile operating procedure as an attack on creativity. A skilled pilot does not regard navigation standards as a denial of autonomy. Constraints can increase freedom by reducing the amount of uncertainty people must carry.

For a distributed team, bounded autonomy might look like this:

• Individuals choose how to complete a task, but the intended outcome is explicit.
• Teams control local decisions, but the boundaries of their authority are documented.
• Meetings are optional when a written decision record is sufficient, but decisions must be visible to affected participants.
• Freelancers retain independence, but project agreements define deliverables, feedback cycles, and escalation paths.
• Leaders set direction and standards, but do not require personal approval for every operational choice.

The goal is to replace supervision with visibility. In a low trust organization, managers ask for constant presence because they cannot see progress. In a well designed distributed organization, progress is legible through artifacts, milestones, decisions, and outcomes.

This also changes the role of leadership. Leaders become less like supervisors of motion and more like designers of conditions. Their job is to clarify the mission, establish interfaces between groups, maintain shared resources, and intervene when the protocol fails.

A Practical Test: Could a Stranger Join the Work?

There is a simple way to evaluate whether an organization has truly adapted to distributed work. Ask whether a competent outsider could join a project and become useful without relying on a long chain of private conversations.

The test does not require instant productivity. Every complex project requires learning. But the organization should provide a path through which a newcomer can understand:

1. What problem is being solved.
2. Why the problem matters.
3. What decisions have already been made.
4. Which assumptions remain uncertain.
5. Who owns each decision.
6. What a successful result looks like.
7. Where to find the relevant evidence and materials.

If the answer depends primarily on “talk to Sarah, she knows how things work,” the organization has a person dependency, not a protocol. Sarah may be invaluable, but the system is fragile because knowledge is trapped in an individual relationship.

This test is especially revealing when companies combine employees and independent professionals. The worst model gives outsiders responsibility without context, access, or influence. They are expected to deliver like insiders while being treated as disposable suppliers. The result is predictable: shallow commitment, defensive behavior, duplicated work, and little investment in shared knowledge.

A better model treats every contributor as a participant in a common system, while still respecting different forms of engagement. The independent professional does not need the same contract or benefits as an employee. But they do need a fair interface with the organization: clear expectations, timely decisions, access to necessary information, and a credible way to raise concerns.

The distinction is not between permanent and temporary people. It is between integrated contribution and extractive procurement.

Key Takeaways

• Design the protocol before selecting the tools. Write down how decisions, information, accountability, and escalation should work. Then choose technology that supports those rules.
• Make invisible coordination visible. Document priorities, decisions, ownership, deadlines, and definitions of completion. Do not assume proximity will supply missing context.
• Invest in shared public goods. Maintain reputation systems, knowledge bases, templates, standards, and dispute procedures even when their benefits are difficult to measure immediately.
• Use bounded autonomy. Give people freedom over methods and local choices, while making outcomes, authority, and constraints explicit.
• Apply the stranger test. Regularly ask whether a capable new contributor could understand the work without depending on private networks or institutional folklore.

The transition to distributed work is often described as a choice between the office and the home. That framing is too small. The deeper transition is from organizations held together by proximity to organizations held together by protocols.

A building can create accidental alignment. A protocol must create intentional alignment. A hierarchy can assign responsibility. A distributed network must make responsibility legible. An employer can retain knowledge inside its walls. A more open labor system must create reasons for participants to contribute knowledge to a shared commons.

The winners will not necessarily be the companies with the most flexible policies or the largest pools of freelance talent. They will be the companies that make cooperation easiest for people who do not share a desk, a schedule, or even an employer.

The real question is therefore not, “Where should people work?” It is this: What system would allow excellent work to continue even when the people involved are separated by geography, organizational boundaries, and time?

Once that becomes the design question, remote work stops looking like an emergency arrangement. It becomes a test of whether the organization has built a company at all, or merely accumulated people around a place.