Research and synthesize evidence

Workplace synthesis should maintain a trace from each important conclusion to a current, authorized source. This principle matters because an AI system produces likely output from the context and instructions it receives; it does not automatically know the organization’s current facts, private policy, unstated intent, or acceptable risk.

Use the following sequence for this page: frame a focused research question; separate public, internal, and anecdotal evidence; require source links or document references; label contradictions, gaps, and confidence in the synthesis. The sequence is a guide, not a ritual. Skip a step only when its question truly has no effect on the outcome, and strengthen it when mistakes would be costly.

Return to the opening case: A strategy lead asks for a competitor brief combining public announcements, internal win-loss notes, and one salesperson’s opinion. Begin by rewriting the request as a small contract. Name the intended reader or user, the authoritative material, the operation to perform, the required output, and the review owner. If current information is required, identify where it will come from. If exact calculation or action is required, assign that step to a deterministic tool or an approved system rather than relying on prose generation.

A useful instruction could follow this shape:

Goal: help [reader] accomplish [outcome]. Use only [named sources or supplied material] for factual claims. Perform [specific operation] and return [format]. Mark missing information as TBD or ask a focused question; do not guess. Before the result is used, [named person or role] will check [criteria].

• Turning repeated claims into verified facts. This hides an important assumption or removes a review point. Replace it with an explicit rule, a source check, or a human decision.
• Mixing confidential context into public tools. This hides an important assumption or removes a review point. Replace it with an explicit rule, a source check, or a human decision.
• Summarizing so aggressively that exceptions disappear. This hides an important assumption or removes a review point. Replace it with an explicit rule, a source check, or a human decision.

Turn Research and synthesize evidence into a template you can reuse this week: job statement, required evidence, failure mode to catch, and reviewer. Store it next to your other work helper notes. When the job changes, rewrite only the job statement and re-run the same failure-mode list — do not invent a new workflow from scratch. Role of this page: Evidence playbook.