How to turn a vague request into a clear brief

The sentence that felt clear when you said it

On Tuesday, Nia tells Omar, “Can you look at the signup form? Something’s off.” She knows what she means. Last month she saw a chart showing that many people stopped halfway through, and she wants a recommendation before Friday’s product review.

Omar knows none of that. Reasonable readings include fixing a bug, redesigning the page, rewriting the labels, or auditing the whole flow. He starts Wednesday on the one he thinks she means, and on Friday the two of them discover they were talking about different jobs.

Why vague requests cost more than they seem

The request feels like a small kindness: you trust the person to figure it out. What the other person receives is a guess about your intent. A meta-analysis of seven work stressors, pooling 169 samples and 35,265 employees, found that role ambiguity and situational constraints were most strongly negatively related to performance (abstract only). It reports correlations, so it cannot show that a vague request causes poor work. A 2022 systematic review of job performance in healthcare lists role clarity among individual-level factors that influence performance, but the support is one sentence citing two studies that also cover work engagement and autonomy. In our reading, both fit what many people have seen firsthand.

Applying this to a brief is an inference: a brief is a way to remove ambiguity about the result without turning the request into a procedure.

The second reason is asking. In our judgment, people often hesitate to say they did not understand. Edmondson’s survey study of 51 teams at one office-furniture manufacturer linked team psychological safety, a shared belief that it is safe to take interpersonal risks, to team learning behavior; the author notes the cross-sectional design cannot show causality. If Omar suspects Nia is busy or irritated, he may guess instead of asking. Our inference is that the brief should invite the question before it is needed.

What a short brief contains

Five lines are usually enough, and each answers a question the other person would otherwise have to ask. This list is practical guidance, not a research finding.

• The result: what you will be holding in your hand at the end, in one sentence.
• The reason: the decision or meeting it feeds, so they can judge what matters.
• The deadline, with the real date and time rather than “soon.”
• The limits: what they decide, what they should bring back to you first, and what is out of scope.
• The check: ask what else they are carrying, and offer a moment to talk partway through.

The version that sounds friendly and says little

The first message looks efficient. It uses an easy tone, trusts Omar, and takes ten seconds to write. But it contains none of the five lines. The reader has to supply the result, the reason, the date, and his own limits, and he cannot tell whether a question will be welcome. That is how a week of conscientious work can land in the wrong place.

The version Omar can start from

The second message is only a few sentences longer. It says what Nia will have on Friday, why, and what Omar can decide for himself, and it carves out what he should not do. The line about the form staying untouched matters as much as the line about the deliverable, because it tells him how far his authority runs.

It also asks a real question about his week. If the answer is no, Nia can move the date, narrow the task, or find someone else, before the work has started and before anyone is embarrassed.

If they push back, go quiet, or say it will not fit

A pushback such as “that’s not enough time” is the brief doing its work. Treat it as information about the plan and ask which part to change: the deadline, the scope, or something else on his list.

If Omar says “sure” without questions, ask a light version of the same check: “What’s your plan for starting?” His answer shows whether the same picture is in both heads.

If it turns out you described the wrong job, say so plainly and own the cost of the change. Do not make the person guess whether the new request is a correction or a criticism.

What the evidence does not show

These sources describe correlations between role clarity or ambiguity and performance, and between team safety and learning. None tests a written brief, and none shows that this five-line format is the best way to hand over work. The team study covers one company and, by its author’s account, cannot establish causation; the stressor meta-analysis was read at abstract level only.

A brief can create clarity about the result; it cannot create the time to do it or settle a conflict between priorities.

The advice also assumes a working relationship where the other person can say no. Where someone cannot refuse safely, such as a new hire speaking to a senior manager, a check about their workload may not produce an honest answer, and a quiet conversation with a different person may help more.

Nia and Omar are fictional and the examples are original. Nothing here shows that practicing with Leetsoul causes better outcomes. The practice linked below uses its own scene and asks you to write a brief of your own.