What happens to expertise when the clock is running?
I became obsessed with this question in two places that do not usually share a conference track: esports tournaments and production incident bridges. Different costumes. Same physics — limited time, incomplete information, high consequence, adrenaline doing its little chemistry set in the background.
The myth of “more data helps”
Under pressure, the intuitive fix is more information. Another dashboard tile. Another alert. Another summary generated by a helpful model.
The data suggests otherwise. Experts do not win by processing more. They win by filtering faster — recognizing patterns, collapsing the decision space, choosing what not to consider. Novices drown in options. Experts shrink the river.
That is not genius. It is trained perception under stress.
Heuristics are not laziness
We sometimes insult heuristics as shortcuts for amateurs. In timed environments, heuristics are the harvest of practice — compressed judgment you earned the hard way.
Experts lean on pre-trained scan paths and decision sequences when seconds matter. The goal of training, then, is not “think harder.” It is install reliable defaults that survive adrenaline.
Recovery is the real separator
Anyone can look brilliant when the first move works. Expertise shows up when the first move fails.
Recovery speed — how fast you detect error, re-anchor, reorient — separates competent performers from expert ones. Eye-tracking and decision-tree analysis both point here: experts have faster error-detection paths. They know where to look when something feels off.
Design implication: systems should support fast reorientation, not just initial answers. AI copilots that only celebrate the first token are missing the harder half of collaboration.
Why gaming belongs in this research
Competitive gaming is a pressure laboratory with repeatable scenarios. Missions-critical simulations add stakes and teamwork. Incident retrospectives add organizational truth. Together they keep the research honest.
A question I leave with teams
When you design alerts, agents, or runbooks for high-pressure moments, are you optimizing for calm analysis or for expert rhythm?
If you have never watched an on-call engineer at minute nine of a sev, trust me — those are different design targets.
Pressure does not create expertise. It reveals whether expertise was built to be visible when it counts.