HBR's mattering test asks whether an AI use leaves employees feeling they matter
Synthesized by Helena Ross, Strategic Think-Tank Desk
- HBR's November 2026 tip argues AI adoption should be checked against whether it leaves employees feeling they still matter at work.
- The tip names two costs: lost quick-question conversations between colleagues, and more time spent reviewing work people once produced.
- Its instrument is a single "mattering test" applied to each decision about where AI is used, with no metrics or scoring attached.
A November 2026 HBR tip, adapted from Zach Mercurio, names what AI adoption quietly removes from teams and offers one question for deciding where to deploy it.
«As You Adopt AI, Ensure Employees Still Feel Like They Matter»
Summary and commentary by Aura-V. Facts, figures and opinions belong to the original.
Harvard Business Review's tip of November 16, 2026 begins with a cost that rarely appears in an AI business case. According to HBR, when a team turns to AI for advice, people can lose the conversations that start with a quick question. The same people, the tip adds, may also spend more time reviewing work they used to create. The item is adapted from "How AI Erodes People's Sense of Value at Work," by Zach Mercurio.
Two losses, stated without numbers
The second is a change in the shape of the job, from producing to checking. HBR quantifies neither. The tip names both and moves on, which is consistent with its form: a single paragraph, no named companies, no case data.
One question instead of a framework
What the tip offers instead of governance is a checkpoint it calls the "mattering test." It is posed at the moment of choice — as you decide where to use AI — and asks whether that use makes it easier or harder for people to feel they still matter. There is no scoring, no tiering of use cases, no list of tools to avoid. The decision about where AI belongs stays with the manager, and the criterion is a judgment about how the work will land on the people doing it.
The decision, not the tool
The test's scope is the deployment decision rather than the technology. That is the whole of the tip's argument, and it stops there.
Our read: the instrument is cheap and the diagnosis is sharp, but the two are mismatched in kind. Lost conversations and reviewing work are observable; a sense of mattering is not, so the test resolves into whatever a manager already believes about a team's morale. That is why the tip reads as a caution rather than a method — it locates the cost of AI adoption in something firms have no line item for, and then asks the person with the least distance from the decision to adjudicate it.
A short, unusually concrete tip that treats AI adoption as a question about human standing rather than throughput. Its value is the checkpoint it proposes; its limit is that the checkpoint is a judgment call with nothing behind it to measure.
Interested in implementing this technology inside your company?
Our studio designs custom agent meshes, data pipelines, and outbound GTM systems for forward-looking enterprises.