The reading room · Digna Legi
On managing up and how to do it
/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. The evidence is long and concrete, but parts approach basic advice and offer no research support.
Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.
How scoring works →This brief · about 3 min with detail
Why read this
Managing up reduces perception gaps between senior context and local reality through visible work, risks, reasoning, and needs.
AI brief · Checked against source text
The main idea
The central claim is that managing up means deliberately helping managers and stakeholders understand your work, risks, reasoning, and needs so their broader context can meet your closer operational view. It works by reducing perception gaps: managers cannot trust priorities, tradeoffs, or judgment they cannot see, so reliability requires communication before surprises, not merely competent execution.
Go a little deeper
Perception is part of the work
The author’s strongest distinction is between intent and perceived action. Competent managers may make sensible tradeoffs yet still lose confidence if stakeholders see only delay, silence, or new friction. Managing up is therefore not cosmetic self-promotion; it is the operational discipline of making the what, how, and why of work legible to people who experience only its effects.
No surprises is a trust mechanism
Status updates matter because surprise forces managers and stakeholders to act from incomplete information. The author argues that even contained problems should be surfaced, because hidden risk can trigger late interventions that undermine the work. The practical standard is not constant noise; it is enough proactive communication that the people accountable above you are never blindsided.
Bring problems with ownership attached
The piece separates useful escalation from problem broadcasting. Reporting a risk builds trust when paired with a mitigation plan and a clear request for help; merely naming everything that is broken can become another management burden. This preserves the manager’s broader view while showing that the person closest to the work has judgment, agency, and follow-through.
Close loops upward and sideways
A subtle recommendation is to manage accountability in both directions after meetings. Recapping what was discussed, agreed, owned, completed, and still outstanding makes your follow-through visible while also preventing senior commitments from evaporating. This is not a power move; it is a shared memory system for work that otherwise disappears between conversations.
A case from the article
Engineering brought into ideation
The author describes taking over a team where product, design, and engineering worked in sequence, causing late feasibility objections and repeated rework. They changed the process so engineers joined earlier feature discussions. The change was rational from their perspective, but others initially experienced it as extra meetings, illustrating the gap between a leader’s intended improvement and the team’s perceived cost.
How the case is made
The case is made through practical observation, one lived team example, and a taxonomy of recurring manager-stakeholder interactions.
Where the idea has limits
The advice assumes a manager or stakeholder who can use transparent information constructively; the source does not address hostile, punitive, or politically distorted reporting environments.
A question to take away · from Digna Legi
Where are you relying on good intent to be inferred when the visible evidence points somewhere else?
What the original adds
The source gives more concrete meeting habits than this brief can fully preserve, especially recap prompts for prior commitments, ownership, progress, and outstanding follow-up.
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.