Defining the Brief

Every research project starts with a brief, even if that project is a thirty-minute sprint. The brief answers four questions before you open a chat window: What am I trying to learn? What is in scope and out of scope? What format does the final output need to be? What decisions will this research inform? Answering these upfront prevents the most common research failure — spending an hour exploring and ending up with interesting but unusable information.

1. Research Question One clear question that the project answers. Not a topic — a question. "Who are the three strongest competitors in our segment and what is each one's primary vulnerability?" is a question. "Competitive landscape" is a topic.
2. Scope Boundaries What is in and what is out. Geography, time period, company size, market segment. Explicit boundaries prevent scope creep and keep your AI conversations focused.
3. Deliverable Format Executive summary, comparison matrix, ranked list, decision brief. Choose the format first because it shapes how you collect and organize information throughout the project.
4. Decision Context Who will read this and what will they do with it? A brief for a CEO making a partnership decision looks nothing like a brief for a product team evaluating features. Context drives depth and framing.

Writing the brief takes five minutes. Skipping it costs an hour. I have watched researchers — experienced ones — dive into an AI chat, spend forty-five minutes exploring a topic, produce fifteen pages of notes, and then realize they cannot synthesize it into anything actionable because they never defined what "actionable" meant for this specific project. The brief is the cheapest insurance policy in research.