Teams Need Heat — But the Right Kind

There are endless analogies about teams as recipes. Mix the right ingredients — skills, personalities, behaviours — and something good will emerge.

But almost all of them miss one thing.

Heat.

Mix flour, eggs, milk, and butter and you get batter. To make pancakes, you need heat. Teams are the same. Capable people without heat create potential. Heat turns potential into movement. It turns ideas into value.

The question is not whether to apply heat — it is which kind.

Why capable people without heat remain batter

Different forms of heat produce different results. Some are sustainable. Some burn out quickly. Some are actively destructive over time. Understanding the difference is one of the most practical things a leader or manager can do.

Fear is a powerful form of heat — but almost never the right kind to apply deliberately. Individually, fear can catalyse change. I spoke recently with someone whose job was crushing her. Fear of what continuing would do to her — not the comfort of what quitting might cost her — drove her to leave without another role lined up. Fear moved her forward.

In organisations, fear applied by leaders is different. It burns bright and fast, like lighter fluid, then leaves nothing. Teams operating under fear-based leadership fall silent, disengage, and erode. Good people leave. Those who stay stop surfacing problems.

Deming's instruction was clear: drive out fear. Not because fear produces no movement — it does — but because the movement it produces is away from honesty, away from risk, away from the creative work that actually improves things.

There is one organisational context where existential fear is useful: startups running low on runway. The fear of not making payroll is real and legitimate. It concentrates energy. But this is fear as context, not fear as management style. The distinction matters.

Clarity and alignment is my heat of choice — by a significant margin. When people know where they are going, why their work matters, and how the obstacles they are solving connect to something worth building, energy and attention emerge naturally. Clarity does not need to be forced. It creates its own heat.

The conditions for this: a painted picture clear enough for everyone to move toward, a strategy credible enough to trust, and problems compelling enough to want to solve.

When these three things are in place and people are drawn to the challenge, the team generates heat almost without intervention. You are not manufacturing motivation. You are creating the conditions in which motivation is the rational response.

Deadlines are micro bursts of heat — contained sparks rather than sustained flame. The holiday packing example is real: there are always a myriad of things to do the day before a trip, and they all get done because the deadline is fixed and immovable.

Used well, deadlines create rhythm and urgency. Used poorly — arbitrarily, constantly, without realistic resourcing — they create stress and erode trust. The key is whether the deadline is real or mythical.

Growth generates intrinsic heat. When work develops people — when they can feel themselves becoming more capable, more confident, more themselves — they bring energy to it that is genuinely self-sustaining.

The manager's job here is to balance the demands of delivery with the development of the people doing it. When that balance is right and the development connects to a clear purpose, it is one of the most reliable forms of sustainable heat in any organisation.

Forced cooperation and the DevOps origin story

Misaligned team goals are one of the most common sources of wasted heat in large organisations. Teams generating energy — but in opposition to each other rather than toward shared outcomes.

I worked in one company where Development had a goal of new features and competitive releases, while Operations had a goal of platform stability at all costs. The goals were structurally counter to each other. To release software is to risk destabilising the platform. To maintain stability, the rational choice is to release as rarely as possible. The two teams were in constant friction — not because they were difficult people, but because their objectives were designed to conflict.

We set both teams the same goal: weekly releases, with 99.999% uptime. That single shared objective forced cooperation.

Development could not release recklessly without Operations pushing back. Operations could not hold the platform static without Development pushing back. The heat that had been wasted in conflict became heat directed toward a shared problem. We created DevOps before the name existed.

The principle generalises: when teams have competing goals, the energy they generate creates friction rather than forward movement. Set shared goals across silos and the heat aligns.

Incentives and competition — handle with care

Incentives are often treated as the primary engine of team heat, but they are easily misused.

Individual incentives are the most common failure mode. When individual rewards are the primary driver, people rationally optimise for the individual reward — which often means not sharing information, not helping colleagues, not taking risks that might benefit the team but not the individual. Collaboration becomes costly. Competition becomes rational.

Team incentives solve part of this but create their own problem: if half a team carries the other half, rewarding everyone equally feels unfair to those doing the carrying. Neither model works cleanly without strong behavioural standards and genuine shared ownership of outcomes.

The model I have seen work best is stakes in shared outcomes — equity, collective metrics, genuine shared accountability. When everyone wins together or struggles together, the incentive to cooperate becomes structural rather than aspirational. This is not always available, but it is worth designing toward where possible.

Competition as a management tool has the same flaw as fear: it produces short-term heat with long-term costs. When leaders make internal competition the primary source of energy, people stop sharing ideas, stop collaborating across boundaries, and start playing for individual position. You get heat — but aimed sideways rather than forward.

The heat I try to generate

The combination that works most consistently: a compelling picture of where we are going, a credible strategy for getting there, people drawn to the obstacles rather than dragged toward them, deadlines that create urgency without arbitrary stress, goals that force cooperation across silos, incentives tied to shared outcomes, and work that develops the people doing it.

When all of these are present, the team generates its own heat. The manager's job shifts from injecting energy to protecting the conditions that allow it to exist.

Without heat, teams remain batter. Capable, well-mixed, going nowhere.