A week before the 2026 World Cup, Qlik surveyed 2,000 U.S. workers about how they'd handle the tournament. The numbers, released June 1, are a portrait of modern work: 90% plan to watch matches live during work hours, 68% will skip or reschedule meetings to do it, and 49% say they'll lean on AI "to catch up faster." Not to do better work. To look caught up.
That gap—between doing more and getting ahead—is the oldest tension in chess. Players call it material vs. tempo. This isn't about musical tempo, and it isn't about how fast you make decisions. It's about two completely different ways to be ahead: stacking up pieces (material) versus controlling the game so the other side has to react to you (tempo, or the initiative).
Here's the part that should worry every team lead. The busiest teams are almost always up material and down tempo. They ship a lot. They close tickets. And they slowly lose. This piece breaks down the trade-off, why your most "productive" team might be the one in trouble, and when to deliberately spend output to buy the initiative back.
What chess means by material vs. tempo
Start with the easy half. In chess, material is just your pieces and pawns. Each has a standard value: "1 point to a pawn, 3 points to a knight or bishop, 5 points to a rook, and 9 points to the queen." If your pieces add up to more than your opponent's, you have a material advantage. It's concrete, countable, and it feels like winning.
Tempo is slipperier. A tempo is "a 'turn' or single move." You "gain a tempo" when you reach your goal in one fewer move, and you "lose a tempo" when you waste one. Crucially, you also gain tempo "when a player forces their opponent to make moves not according to their initial plan"—because then they're the one wasting moves, not you.
Pile up enough tempo and you have the initiative. The definition is the most useful sentence in this whole article: initiative "belongs to the player who can make threats that cannot be ignored, thus putting the opponent in the position of having to spend turns responding to threats rather than creating new threats."
Read that again with your team in mind. The player with the initiative makes the moves. Everyone else answers them. That is the entire game.
And the two can be traded. A gambit is "a chess opening in which a player sacrifices material with the aim of achieving a subsequent positional advantage." The old rule of thumb: you should get "three moves of development for a sacrificed pawn." You give up something countable to buy time and position. Sometimes that's the best move on the board.
Why busy teams confuse material for winning
Material is seductive at work for the same reason it's seductive in chess: you can see it. Tickets closed. Features shipped. Hours logged. Messages sent. Slides made. It's the dashboard, the burndown chart, the green status dot. You can count it, so you manage by it.
The data on this is brutal. Slack's research found that 27% of executives "rely on visibility and activity metrics to measure productivity"—and in response, 63% of workers "make an effort to keep their status active online, even if they're not working." Slack named the loop precisely: productivity becomes "generating high inputs… to appear productive, versus outputs." That's not laziness. That's a rational response to being measured on material.
Meanwhile, the material itself is often hollow. Asana's Anatomy of Work Index found that 60% of a person's time goes to "work about work"—"communicating about work, searching for information, switching between apps, managing shifting priorities, and chasing the status of work." Motion that produces no position.
"One form of self-delusion is confusing motion for progress."
Now AI mass-produces material with zero tempo. BetterUp and Stanford gave the phenomenon a name—"workslop," AI output "that looks good, but lacks substance." Forty percent of U.S. desk workers received some last month. It costs about $186 per employee per month to clean up, and roughly $9M a year at a 10,000-person company. The output went up. The progress went down. That's a material gain and a tempo loss, in one tidy statistic.
The hidden cost of measuring material
Let's steelman the other side, because the "just ship more" instinct isn't wrong. A team that produces nothing fails fast and obviously. Output is honest signal—it's hard to fake a working feature, and "we're being strategic" is the favorite excuse of teams that are actually just stuck. Measuring activity is a real, useful correction for a team that's all talk. Give that its full due.
Here's the hidden condition. "Maximize output" only works if more material equals winning. But in chess you can be up a queen and still get checkmated, because your opponent has the initiative and you spent the whole game answering threats. The same thing happens to teams. The group buried in its own backlog, responding to every inbound request, is up material and down tempo. By the chess definition, it doesn't have the initiative—it's spending every turn "responding to threats rather than creating new threats."
This is the counterintuitive part, the one that makes it dangerous: the busier and more productive a team looks, the more likely it has quietly surrendered the initiative. Every reactive ticket feels like progress. The dopamine of closing things masks the fact that you're only ever answering someone else's move. One founder described the trap exactly:
"A lot of startups fail because they end up reacting to events around them and are constantly fire fighting. That usually means a lot of work gets done, people are very stressed, the goal posts keep on moving, and things don't actually progress a lot."
The reusable version, steal it: you don't win by making more moves; you win by making the other side answer yours. That's the difference between decision velocity—how fast you decide—and tempo, which is about whose agenda you're deciding on in the first place.
When to trade material for tempo
Material and tempo aren't enemies. The skill—the whole skill—is knowing which one to spend. Here's the decision framework.
Spend material for tempo when you're behind on the board
When a competitor set the agenda, when you're early and reacting, when every week is answering someone else's move: gambit. Deliberately let three deliverables slip to ship the one forcing move—the wedge feature, the public launch, the decisive bet—that makes the market react to you instead. Yes, your output number drops that week. That's the sacrificed pawn. You're buying the initiative, and like a gambit, the point is the position you get afterward, not the pawn you gave up. Find the one move that actually changes the board and overspend on it.
Bank material when you already have the initiative
Tempo is worth more early; material decides the endgame. Once you genuinely dictate play—your roadmap is the one others respond to—stop gambling and start converting. This is when shipping volume, hardening, and durable execution win, because position is already yours and now you cash it in. The mistake here is the opposite one: staying in permanent gambit mode, sacrificing for an initiative you already hold.
Watch for "lost tempo"—the move that takes two moves
In chess, losing a tempo means taking an extra move to reach a square you could've reached directly. At work that's rework, thrash, re-orgs, and the ticket treadmill—maximum motion, zero net advance. As one engineer put it, "a developer on the Scrum/Jira treadmill, working on one ticket at a time, will not have the leeway to step back and look at solutions holistically." Every context switch is a tempo you paid and didn't get back.
Ask one question: who is forced to react to whom?
This is the diagnostic, and it's free. Look at your team's last two weeks of work and sort it into two piles: moves you forced, and moves you answered. If the answer pile dwarfs the forcing pile, you've lost the initiative—no matter how high your output was. A team can look behind on material and be winning, and look buried in output and be losing. The pile sort tells you which.
Why distributed teams lose tempo without noticing
Remote and async work quietly tilt the whole game toward material—because material is the only thing that survives the distance. Across a distributed team, the conversation, the position, the board is invisible. What's visible is the artifact: the merged PR, the ticket count, the green status. So that's what managers measure (Slack's 27%) and reward, and that's what people perform.
Async also makes reacting the path of least resistance. Every Slack ping, every @-mention, every "quick question" pulls a move out of you. Optimize for responsiveness and you'll feel productive while handing the initiative to whoever pings most—which is its own kind of signal lost to noise. The team gets faster at answering and worse at setting direction.
The fix is to make the board visible again. A distributed team needs a shared surface where it can see its position—what it's forcing versus what it's answering—not just its output. This is the gap a tool like Coommit is built to close: by keeping the conversation, a live shared canvas, and contextual AI in one place, a remote team gets an actual board to read tempo on, instead of a backlog that only counts material. The point isn't another dashboard. It's managing by position and outcome, not visible activity. (And it's the inverse of zugzwang, where being forced to move is the disadvantage—here, forcing the moves is the whole prize.)
The bottom line
Material vs. tempo is the trade-off hiding behind every team that ships constantly and wins rarely. Output is real and it matters—but it's the pawn, not the game. The team that counts only what it produced is the chess player up a queen, wondering how they got mated.
So stop counting your moves and start counting whose moves you're forcing. The winning teams of the next decade won't be the busiest. They'll be the ones holding the initiative—the ones everyone else is reacting to. Give your team a board it can actually see, and you can finally tell the difference between being busy and being ahead.