Two people ask AI the same question: “How should I handle a team member who is consistently missing deadlines?” One is a first-time manager dealing with a junior employee on a small team where everyone can see the problem. The other is a senior director managing a high performer who has started missing deadlines after years of excellent work, during a period that may involve a personal crisis. They received the same advice. General guidance on documentation, direct feedback, performance improvement frameworks. Applicable to the abstract problem. Wrong for both of the specific situations. The question was the same. The context that would have made the answer useful was completely absent in both cases.
What Context Actually Does in a Brief
Context is the part of a brief that converts a general answer into a specific one. It is the information that makes your situation different from the average situation — and therefore makes useful AI output different from generic AI output. Without context, AI answers the type of question rather than the specific question. The type of question “how do I handle a missed deadline” has standard answers that appear in management handbooks. The specific question — this employee, this history, this team dynamic, this moment — has a much narrower set of useful answers. Context is what converts the type question into the specific one. Most briefs include a task (“write a proposal for X,” “help me prepare for Y,” “analyze Z”) and skip the context entirely. The task tells AI what to produce. The context tells it what the output actually has to do — and who it has to work for.
The Three Things Context Has to Establish
Useful context answers three questions that a good advisor would always ask before beginning any work. First: what is the specific situation? Not the category — the actual circumstances. Not “I’m dealing with a performance problem” but the specific situation in enough detail that the advice can be tailored to it rather than to the general case. Second: what has already happened? AI has no knowledge of what you have tried, what has failed, what decisions have already been made, or what constraints have already been established. This prior history is often the most important context, because it determines what options are still available and what approaches have already been ruled out. “I’ve had this conversation twice and the behavior hasn’t changed” is a different context than “I’m about to have this conversation for the first time.” Third: what makes your situation different from the average case? This is the question most people don’t ask themselves, but it is where the useful context almost always lives. The thing that distinguishes your situation from the standard version of the problem is almost always the thing that determines which advice actually applies.
What Good Context Looks Like Versus What Most People Write
Most people write context like this: “I’m a manager dealing with a team performance issue.” This establishes a category. It tells AI nothing it couldn’t infer from the question. Useful context looks like this:
Context: I manage a team of six in a professional services firm. The team
member in question has been on the team for three years and was previously
a top performer. The pattern of missed deadlines started approximately two
months ago, coinciding with what appears to be a personal situation she
has not disclosed. I have had one informal conversation in which I
mentioned the concern without framing it as a performance issue. I do not
want to activate a formal process if the underlying cause is personal —
but I also have client commitments that depend on her output and cannot
be renegotiated.
The second version establishes the specific situation, the relevant history, and the constraint that makes this case different from the standard performance management scenario. The advice that follows has something to work with.
The Specificity That Context Provides Is Irreplaceable
No role instruction and no output format specification compensates for missing context. A precisely calibrated expert role with a detailed output format and no context will produce well-formatted expert advice that applies to the general problem and not to the specific one. Context is the variable that determines whether the output is about your situation or about a situation like yours. Those are not the same thing, and the difference between them is often the difference between advice you can act on and advice that sounds right but doesn’t quite fit. This is why context is consistently the most underused part of any AI brief. It requires thought — not about what you want AI to produce, but about what makes your situation specific. That thought is the work. The brief is where it goes. Briefing Fox is built around this problem: generating the questions that surface context the person briefing may not have thought to include, ensuring the brief is built on the specific situation rather than the abstract category.
The Test for Whether Your Context Is Sufficient
Before submitting any brief, read the context section and ask one question: could this context describe someone else’s situation, or does it specifically describe mine? If it could describe someone else’s situation, it is a category, not context. Add the specifics that make it yours: the history, the constraint, the thing that makes this case different from the standard version of the problem. The output that follows will be built on your situation rather than on the type of situation. That is what context is for. It is the part of the brief that makes the output only possible to have been written for you. Try Briefing Fox free at www.briefingfox.com.