The reading room · Digna Legi
Generated and suppressed demand.
/100
80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.
Evidence-reviewed score based on available publisher text. Assessment relies on the supplied article excerpt, which appears substantive but does not prove broader empirical validation.
Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.
How scoring works →This brief · about 2 min with detail
Original article ↗ · about 3 min (text estimate)
Why read this
Better execution can make recovery look like failure when suppressed stakeholder demand reappears as trust returns.
AI brief · Checked against source text
The main idea
Lethain adds suppressed and generated demand to his team-recovery model: better execution can reveal work that stakeholders had stopped requesting. This makes progress look like failure, because the team may clear backlog, regain trust, and then face a fresh wave of demand created by its own effectiveness.
Go a little deeper
Recovery can hide inside bad metrics
A backlog growing again after a recovery cycle is not automatically evidence that the recovery failed. It may mean the team restored confidence, so stakeholders resumed asking for work they had silently abandoned. The practical consequence is that leaders must distinguish operational regression from visibility into previously suppressed demand.
Interface breadth predicts the second wave
The author’s useful predictor is how many people or workflows a team touches. Broad-interface teams are more likely to unlock large invisible backlogs because many groups have accumulated unmet needs. Narrow-interface teams may have a finite queue: once the initial backlog is cleared, little new demand appears.
How the case is made
The argument is made through operational observation, one concrete team example, and an analogy to latent reliability incidents.
Where the idea has limits
The diagnosis applies most strongly to teams with broad interfaces; the author explicitly says narrow-interface teams may clear their backlog without much generated demand.
What the original adds
The original includes the prior four-stage recovery model and a useful distinction between broad-interface teams, such as customer operations or developer experience, and narrow-interface teams.
About this brief
AI-written, then separately checked for source support, useful detail and clarity. The author’s claims and our editorial question are kept separate. The original remains the author’s work. How we select and summarise →
How was this brief?
Rate this summary, separately from the author’s article.
Optional. Saved in this browser; shared only if you allow analytics.
How was the original article?
Rate the author’s original after reading it.
Optional. Saved in this browser; shared only if you allow analytics.
Digna legi. Worth reading.