Business writing borrows heavily from sport and the military, and most of what it borrows is decoration. Teams get called squads, quarterly targets become missions, difficult periods become the fourth quarter, and someone gives a speech that would be at home in a locker room and is faintly embarrassing in a conference room.
The borrowing is understandable. Both environments produce coordinated performance under pressure, which is what organisations want. The problem is that the parts most often imitated are the visible ones, and the parts that actually produce the performance are quiet, procedural, and rarely mentioned.
Separating the two is worth doing, because a handful of practices genuinely transfer and the rest is theatre.
Why the Metaphors Usually Fail
The structural differences matter more than the surface similarities.
Sport has a defined opponent, fixed rules, an agreed scoreboard, and a season that ends. Business has none of these reliably. The competitor set shifts, the rules change underneath you, success is measured several ways simultaneously, and there is no offseason.
Military operations have a clarity of purpose and a chain of command that most organisations neither have nor should want. Consequences differ by orders of magnitude, and language borrowed from a context where people can be killed lands oddly when applied to a product launch.
The most common failure is emotional. A rousing speech works in an environment where the required output is a burst of coordinated effort over a defined period. Most business problems are not solved by intensity. They are solved by sustained attention over months, and intensity is a poor fuel for that.
Which is why the useful transfers are almost never the inspirational ones.
Preparation Is the Transferable Part
High-performing teams in both environments spend an enormous proportion of their time preparing for situations that may not occur, and almost none of it looks impressive.
What they practise specifically is the situation going wrong. Not the plan, which everyone understands, but the contingency: what happens if this fails, if that person is unavailable, if the information turns out to be incorrect.
Most organisations do the opposite. They plan for the intended path in detail and improvise everything else, then treat the resulting scramble as an unforeseeable event when it was entirely foreseeable and simply unrehearsed.
The transferable practice is narrow and useful: for any significant initiative, spend time in advance on how it could fail and what the response would be. It costs a meeting and it removes most of the improvisation from the moment when improvisation is most expensive.
Debriefs That Are Not About Blame
The single most transferable practice from military environments is the structured debrief, and the reason it works is a discipline most organisations cannot maintain.
The format is simple. What was supposed to happen. What actually happened. Why the difference. What changes as a result.
The discipline is that rank is set aside during it and the question is what happened rather than who is at fault. That is the entire mechanism. A debrief where people are protecting themselves produces a sanitised account, and a sanitised account teaches nobody anything.
Most corporate versions of this fail on exactly that point. A post-mortem that everyone understands to be an inquiry into responsibility will surface the safest possible narrative, which is worse than not holding one, because it produces the appearance of learning.
Two conditions make it work. Successes get debriefed as well as failures, so the process is not associated with trouble. And the most senior person present is willing to name their own errors first, which is the only reliable way to establish that it is genuinely safe to do so.
Roles Get Clearer Under Load
Teams that perform under pressure tend to have unusually explicit role definition, and it applies specifically to the moments when things are going badly.
Everyone knows what they are responsible for, who makes which call, and what happens when the person who normally decides is unavailable. That clarity is established in advance because establishing it during an incident is not possible.
Organisations frequently have clear roles for normal operations and none for exceptions. When something goes wrong, several people assume someone else is handling it, or several people handle it simultaneously in different directions.
The transferable question is straightforward and rarely asked: when this goes wrong, who decides, and who decides if that person is not available.
Standards Are Held Sideways
In environments where performance genuinely matters, standards are not maintained primarily by supervision. They are maintained by peers, because supervision cannot be everywhere and because the people doing the work know first when something is off.
That only happens where raising an issue with a colleague is normal rather than an escalation, which is a cultural condition rather than a policy. It also requires that raising something is not treated as disloyalty, which is where a lot of organisations quietly fail.
The practical version for a workplace is that if problems only ever travel upward to a manager and then back down, the organisation has a single point of quality control and it is a bottleneck. Teams where colleagues can say to each other that something is not right catch considerably more, considerably earlier.
Recovery Is Scheduled, Not Earned
This is the practice organisations borrow least and would benefit from most.
In serious athletic environments, recovery is part of the programme rather than a reward for finishing something. It is scheduled, protected, and understood as a component of performance rather than as an absence of work. Nobody treats it as slacking because everybody understands what happens without it.
Workplace culture generally treats rest as what is left over. It is taken when the work allows, cancelled when the work does not, and quietly regarded as a sign of lower commitment.
The transferable principle is that sustained output requires planned recovery, and that this is a scheduling question rather than a character question. Teams working intensively toward a deadline should have the period afterward planned as deliberately as the period before it, rather than rolling directly into the next thing and wondering why the quality drops.
What Does Not Transfer
An honest account includes the parts that should stay where they are.
Command hierarchy does not transfer well. Most organisational problems benefit from distributed judgement rather than from a clearer chain of orders, and the environments being borrowed from use hierarchy in circumstances that do not resemble a normal workplace.
Physical dominance and confrontational culture do not transfer at all, and the workplace versions of them are corrosive rather than motivating.
Season structure does not transfer. Sport has an offseason and a defined endpoint, and business does not, which is precisely why the intensity model fails when imported.
And sacrifice rhetoric does not transfer. Language about giving everything, borrowed from contexts where the stakes were genuinely extreme, does real damage when applied to quarterly targets. It is also the language most associated with the conditions that produce burnout, which makes it an unusually poor import.
Where an Outside Perspective Helps
These practices are simple to describe and difficult to establish, largely because they require behaviour change at the top rather than a new process.
Outside voices help partly because someone without a position in the organisational hierarchy can name things that are difficult to say internally, and partly because a shared reference point makes the subsequent internal conversations possible.
What matters is whether the speaker draws real distinctions rather than trading on the background. A keynote speaker such as Caleb Campbell, a West Point graduate, former Army officer and former NFL linebacker who speaks on what he calls living resilience, works with leadership teams on capacity and performance under pressure alongside leadership training and a limited coaching practice. Whoever an organisation engages from a background of this kind, the question worth asking beforehand is which lessons they say do not apply, since a speaker who claims everything transfers has not thought about it carefully.
Key Takeaways
- The imitated parts of high-performance culture are the visible ones; the effective parts are procedural and quiet.
- Intensity suits defined bursts and is poor fuel for problems solved over months.
- Rehearse how an initiative could fail, not only how it should go.
- Structured debriefs work only when rank is set aside and the senior person names their own errors first.
- Establish in advance who decides when something goes wrong, and who decides if they are unavailable.
- Standards held between peers catch more than standards held only by supervision.
- Recovery is a scheduling question rather than a character question, and it belongs in the plan.
Frequently Asked Questions
Why do sports metaphors fall flat in most workplaces?
Because the structural conditions differ. Sport has a defined opponent, fixed rules, an agreed scoreboard, and an endpoint. Business has shifting competitors, changing rules, several simultaneous measures of success, and no offseason. Borrowing the language without the conditions produces something that sounds motivating and does not describe the actual work.
What makes a debrief different from a post-mortem?
Mainly the question being asked. A debrief asks what happened and why; a post-mortem, in practice, frequently asks who is responsible. People answer the second question defensively, which produces an account that is safe rather than accurate. Debriefing successes as well as failures, and having the most senior person go first on their own errors, are what keep it from drifting into the second form.
Is psychological safety the same as being agreeable?
No, and it is often the opposite. It means people can raise problems, disagree, and admit errors without the relationship or their standing suffering. Teams with it argue more openly, not less, and the argument happens early enough to be useful rather than after the decision has been made.
How do you build peer accountability without it becoming policing?
By making it normal, specific, and reciprocal rather than exceptional and directed downward. It works where raising something is treated as ordinary rather than as an escalation, and where the person raising it expects to receive the same in return. It fails where it is introduced as a management initiative aimed at other people.
Does any of this apply to a small team?
Most of it applies more readily, since the practices depend on habits rather than infrastructure. A team of five can rehearse failure modes, debrief honestly, clarify who decides under pressure, and plan recovery after an intense period. Larger organisations need more structure to achieve the same behaviours.
Where should an organisation start?
Usually with debriefs, because the practice is small, produces visible value quickly, and establishes the conditions the other practices depend on. Beginning with a success rather than a failure makes the first one considerably easier to run honestly.
Conclusion
The useful inheritance from high-performance environments is not the speech before the game. It is rehearsing the failure, debriefing without blame, knowing who decides when things go wrong, holding standards between colleagues, and treating recovery as part of the plan. None of it is stirring and all of it is transferable, which is roughly the opposite of what gets borrowed most.
