Write a Research Brief a New Teammate Can Execute

An experienced researcher can often rescue a vague request because they know the company's history, the seller's preferences, and the meaning behind shorthand. A new teammate cannot reliably supply that missing context. The assignment needs to carry enough information for someone competent but unfamiliar to begin without guessing.

This is a brief for doing research, not the account summary produced afterward. Its test is simple: can the recipient explain the question, boundaries, and stopping point before opening a source?

Replace the broad request with a decision

Find everything about Cedar is not a usable assignment. Neither is find the decision-maker when nobody has specified the project or decision involved. Start with what the requester will do differently after receiving the answer.

A good brief might support deciding whether one operating site falls within a maintenance provider's service scope. That requires site identity and relevant activity. It does not automatically require revenue estimates, employee biographies, or a complete buying committee.

Separate required facts from useful background. If a field would not change the intended decision or explain an important limitation, leave it out of this assignment. More requested detail can increase work without improving the answer.

A complete fictional assignment

The following is an invented brief for a new research teammate:

• Request ID: RQ-46; requester: service-planning lead; reviewer: account-data steward.

• Decision: decide whether the Riverton workshop of fictional Cedar Equipment belongs in our current on-site maintenance review.

• Entity anchor: supplied internal account CE-14 and the company-authored location reference; do not substitute a similarly named business.

• Required questions: is this an operating workshop rather than a sales office, what activity is directly supported, and is the site inside the defined service boundary?

• Permitted inputs: the supplied company pages, relevant official public records, and approved internal account notes; no scraping, personal-data enrichment, or external contact.

• Output: one short answer per question, source reference, source date where known, checked date, uncertainty, and proposed internal disposition.

• Stop point: after the named source types and internal history are checked, return a supported answer or a specific unresolved question; do not invent missing evidence.

• Acceptance: the reviewer can identify the site and reproduce the reasoning without asking the researcher what Cedar means.

The brief also supplies the actual service-boundary definition. A phrase such as local area would leave the new teammate making a commercial policy decision rather than performing research.

Include a boundary example

The training example says: a current company page describes equipment demonstrations at the site, while a separate page says repairs are handled at another location. Acceptable output distinguishes demonstration activity from a repair workshop. It does not classify the site as a workshop because equipment is present.

A second acceptable result is unresolved when the sources do not establish the activity. The researcher explains what was checked and what would resolve the gap. That result may complete the assignment without making the account ready for contact.

The W3C: An Overview of the PROV Family of Documents links information to its origins and production activities. For this brief, requiring source references and review context makes the eventual answer traceable. The assignment structure is a practical editorial proposal, not a prescribed technical implementation.

State the decisions the researcher does not own

The new teammate may recommend review, but cannot change the service area, merge uncertain entities, authorize outreach, or promise delivery capacity. Name the owner for those decisions. Without explicit boundaries, an eager researcher may try to finish the task by resolving policy questions they were never assigned.

If the requester changes the site or asks for contacts halfway through, record the scope change and reassess the checkpoint. Do not silently expand a small verification task into a broad account investigation.

Run a brief-only rehearsal

Before assigning live work, ask the teammate to read the brief and state the first source they would inspect, the first identity check, and an outcome that would make them stop. Do not correct the answer immediately; note where the brief itself is ambiguous.

If they cannot explain the required unit or decision, improve the assignment before treating the hesitation as a training failure. A complete brief transfers the necessary context while leaving room for professional judgment. It should make a defensible unknown easier to return than a confident guess.

Continue with Plan a First Sales Hire's Research Training or Create a Useful Sales Research Service-Level Agreement.