The views expressed here are solely my own. They do not represent the opinions, positions, or policies of any current or former employer, client, or affiliated organization.
Every cross-functional enterprise project is essentially a high-stakes match of ranked Overwatch played with strangers. You are thrown together with five people you did not hire, who do not report to you, and who hold wildly different incentives, skills, and temperaments. In both environments, trying to force compliance through volume or structural authority fails. True leadership in zero-trust, temporary systems is diagnostic. It requires mapping the existing operating model of your team in real-time, identifying the human bottlenecks, and aligning individual incentives around a single, immediate outcome.
The Reactance Trap: Why Directives Breed Resistance
When operations break down, the default managerial instinct is to issue direct orders. In a multiplayer lobby, this looks like screaming: "Switch to hitscan" or "Heal me." In an enterprise, it looks like mandating a new software tool. Both interventions fail for the same systemic reason.
In their foundational work on lateral leadership, Influence Without Authority, Allan Cohen and David Bradford establish that cooperation occurs when people perceive that you are helping them achieve their goals, not yours. In a competitive match, the shared goal is to win.
When you issue a direct command, you trigger what psychologists call reactance theory. When individuals feel their autonomy is threatened by an external controller, they instinctively do the opposite to reclaim dominance.
Directives signal that the recipient is failing. Proposals signal that the system can be optimized.
Consider the difference in operational friction between these two protocols:
The Directive: "Switch to hitscan." This attacks the player's identity and competence, ensuring resistance.
The Proposal: "If we have a hitscan, we can deal with Pharah pretty easily." This reframes the problem from a personal deficit to a systemic opportunity.
In a corporate setting, the parallel is clear:
The Directive: "You must use the new project management tool for all status updates starting Monday." This ignores the team's existing workflow and triggers immediate pushback.
The Proposal: "If we move our status updates to the new tool, we can eliminate the manual spreadsheet consolidation that currently takes us three hours every Friday." This reframes the tool as a solution to a shared pain point.
By shifting the language, you bypass the ego threat. You are no longer ordering; you are presenting a structural solution to a shared bottleneck.
The Information Protocol: OODA Loops and Crisis Leadership
Under high cognitive load, human bandwidth shrinks. When a team is under stress, long-form explanations and retrospective critiques become operational noise.
To lead without authority, you must reduce uncertainty faster than the environment creates it. This is the core of John Boyd’s OODA Loop (Observe, Orient, Decide, Act). The individual who provides the most reliable, low-noise data naturally becomes the operational anchor of the team.
This requires a strict communication protocol: share high-utility information, not subjective opinions.
High-Noise Opinion: "Why are we pushing? Stop feeding." This provides zero actionable data and increases emotional contagion.
Low-Noise Information: "Reset. We have ult advantage." This diagnoses the structural state and provides immediate direction.
In a boardroom or project meeting, the same principle applies:
High-Noise Opinion: "This campaign is failing because the creative team isn't aligned with the strategy." This is subjective, inflammatory, and provides no path forward.
Low-Noise Information: "The current conversion rate is 1.2% against a 2.5% target, and the primary drop-off is at the landing page. Let's test a simplified CTA." This diagnoses the data and proposes a specific action.
In crisis leadership, brevity is a safety mechanism. When the system is lagging or under attack, the team cannot process complex paragraphs.
[System Stress Level: High]
> Avoid: "Guys, we really need to stop staggering because otherwise..."
> Execute: "Reset." / "Back." / "Left."
By keeping messages clinical and brief, you preserve the team's remaining cognitive capacity for execution.
The Human Infrastructure: Managing the Emotional Host
A system is only as stable as the human nodes running it. When a single node experiences operational failure—what players call "tilt"—the dysfunction spreads across the network.
According to Self-Determination Theory, human performance relies on three psychological pillars: autonomy, competence, and belonging. Standard corporate criticism—much like lobby toxicity—destroys all three.
When a teammate fails, the default human error is the Fundamental Attribution Error: assuming the failure is a result of personal incompetence rather than environmental constraints like lag, a new hero, or poor support.
To maintain system stability under pressure, the operational architect applies three rules:
Criticize situations, never people: Say "No shield" instead of "Tank diff." In a business context, say "The data integration failed" instead of "The engineering lead is incompetent."
Provide immediate feedback loops: A simple "Nice pick" or "Huge shatter" reinforces high-value behavior instantly, using Cialdini’s principle of consistency to lock in that performance. In a project, a quick "That summary saved us two hours of review" achieves the same effect.
Establish reciprocity early: Acknowledging support with a quick "Thanks heals" builds social capital before you need to ask for a tactical adjustment. Similarly, offering a peer help on their task builds the credit you will need when you eventually need to ask for theirs.
The Limits of Lateral Influence
Intellectual honesty requires acknowledging the boundary of this model. You cannot force cooperation on a node that is actively determined to sabotage the system.
In The 7 Habits of Highly Effective People, Stephen Covey distinguishes between the circle of concern and the circle of influence. You cannot control the mechanical skill or the emotional stability of four strangers. You can only control the quality of the information you inject into the system and the friction you remove from their path.
Incentives drive behavior. If you align the communication to the player's existing incentive—winning—the need for formal authority disappears.
Speak to Coordinate, Not to Correct
The ultimate lesson of the multiplayer lobby is that authority is an expensive substitute for clarity. When you build a system that reduces threat and increases situational visibility, leadership becomes an emergent property of the system itself.
Speak to coordinate, not to correct. Describe the next step, not the past error. Share information, not frustration.
When you strip away the noise, the complaints, and the need to be right, you are left with a lean, highly responsive coordination engine. The technology and the platform are merely the arena; the operating model you run inside it determines the outcome.
Juan Carlos Vásquez has spent ten years inside enterprise content operations, repairing content supply chains before scaling them. Fix to Flow is the discipline that work produced. The views here are his own.