Main idea

Working for a long time on a topic that nobody knows will actually be done produces an effect no capacity plan measures: the intensity drops. Not out of laziness, but out of a reasonable calculation — "anyway, this may never get prioritized". A workshop gets prepared a little less, an analysis stops a little earlier, a hypothesis is dug a little less deep.

The cause is neither the difficulty of the work nor how interesting it is. It is the break between the effort and the decision it was meant to serve. Product work earns its worth from what it lets you settle; deprived of that outlet, it becomes an exercise, and it gets done like an exercise.

The resulting fatigue is therefore moral as much as intellectual, and it differs from overload: a team can be exhausted having produced little, precisely because it has concluded little.

Why it matters

It adds to the benefit of clear prioritization an effect nobody ever credits it with: the quality of upstream work. A topic committed or refused makes the effort around it useful again.

It also prevents a common and false diagnosis. A team that seems less invested is not necessarily demotivated by its management or its product; it may simply have learned that its conclusions lead nowhere.

Nuances and limits

Part of discovery work legitimately has no outlet: exploring a lead in order to close it is a result. The loss of intensity comes from prolonged uncertainty, not from abandonment.

And the effect varies by person and by tenure: someone who has already seen their work put to use withstands a period of uncertainty better than someone who has just arrived.

Open questions

• In a team that is slowing down, how do you tell the loss of a decision outlet from demotivation of another origin?