The reading room · Digna Legi
Before you delegate, ask yourself these 6 questions
/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. Evidence includes a substantive article plus promotional course material near the end.
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
Original article ↗ · about 6 min (publisher estimate)
Why read this
Kao treats poor delegation as missing context: purpose, inputs, quality bar, urgency, scope, and likely failure points.
AI brief · Checked against source text
The main idea
The central claim is that poor delegation often comes from unspoken context, not from the other person’s inability. Kao’s six questions force the delegator to externalize what is inside their head: what the recipient already knows, why the task matters, what inputs they need, what good work resembles, how urgent and scoped it is, and what is likely to go wrong.
Go a little deeper
Delegation starts with the recipient’s map
Kao’s first move is perspective-taking, but in a concrete way: distinguish what the person already knows from what is new to them. That prevents both overexplaining familiar material and skipping premises that feel obvious only because the delegator has been living with the task. The mechanism is calibration: useful context depends on the recipient’s current position, not the speaker’s expertise.
The why substitutes for supervision
For any task requiring judgment, step-by-step instructions are brittle. Kao argues that explaining the purpose lets the person make better calls when the delegator is absent, because they can reason from the goal rather than mechanically imitate directions. The broader project context also changes the work’s meaning: a small task becomes part of a larger chain of consequence.
Quality needs examples, not abstractions
The instruction to define what great looks like is not a demand for vague standards. Kao recommends mockups, screenshots, prior documents, analogies, and near-miss examples that let the recipient pattern-match. This is especially useful when the task is new: the delegator can say what the work should resemble and where it should differ, reducing ambiguity without pretending there is a perfect template.
Speed problems may be scope problems
Kao separates timeline, priority, and acceptable depth. Phrases like urgent or ASAP create stress without conveying a real deadline, and unclear expectations can cause someone to deliver more detail than needed. The useful move is to invite early warning when the estimate is wrong, because apparent slowness may reflect a mismatched definition of the task rather than poor execution.
A case from the article
Customer recommendations with bounded detail
Kao’s clearest case is a delegated customer-selection task. Instead of leaving the recipient to infer the expected depth, the delegator specifies that paragraphs of background are unnecessary; names and a few bullet points are enough, because the delegator will review profiles afterward. The example shows how risk prevention can be simple: define what not to do and where the work should stop.
How the case is made
The case is made through lived managerial experience, practical prompts, and concrete examples of better delegation language.
Where the idea has limits
The checklist is presented as a starting point, not a universal script; Kao explicitly says people should swap in or add questions for their own situation.
A question to take away · from Digna Legi
Which recurring task would become less fragile if you wrote down the context you usually assume is obvious?
What the original adds
The original includes the full six-question recap, example phrasing for several prompts, and a brief aside connecting the same context-sharing habit to cross-functional partners and AI use.
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.