Research briefs vs decision briefs: choosing the right workflow
Compare research briefs and decision briefs using the same inputs, distinct worked outputs, complete briefs, and a practical decision test.
Quick answer
A research brief defines what to investigate and which evidence will answer the question; a decision brief organizes the evidence around an owner’s available choices. Use the same observations while keeping an open inquiry distinct from a recommendation request.
Two outputs from the same inputs
Research briefs: An investigation plan with questions, source routes, evidence gaps, scope, and criteria for adequate coverage.
decision briefs: A reviewed choice packet with options, observed tradeoffs, unresolved assumptions, and the decision owner.
Both start from the same approved facility requirements, site notes, and vendor information. Choose the purpose before asking Righthand to prepare the result; otherwise a polished draft can answer the wrong question.
Worked comparison
The following records are synthetic examples. They illustrate output differences, not product test results or customer outcomes.
| Shared input | Research briefs output | decision briefs output |
|---|---|---|
| S1: site access hours unverified | Add access-hours verification to the research questions | Mark access constraint unresolved before comparing options |
| S2: two sites meet stated room needs | Plan comparable evidence collection for both | Show room-fit evidence side by side without inventing other advantages |
| S3: quoted cost excludes setup | Request a complete scoped quote through an authorized owner | Keep cost comparison incomplete and identify the missing setup amount |
Brief A: prepare the first workflow
Use the approved facility requirements, site notes, and vendor information for October 12–16, 2026. Source fields: requirement ID, option ID, observation, source date, source link, budget boundary, unresolved question, owner. At Monday 9 AM America/Los_Angeles, prepare the research briefs output shown above as source-linked Markdown in my private review thread. Preserve original record IDs and mark uncertainty. I review the draft against the first table column’s purpose. Do not book sites, contact vendors, accept terms, promise availability, or spend money. Result check: each entry matches its source and the intended first-workflow output.
Brief B: prepare the second workflow
Use exactly the same input slice, fields, date window, and timezone. Prepare the decision briefs output shown above instead. Keep the underlying observations separate from interpretation, with a named owner for unresolved questions. Return the draft to the same review thread for my approval. Apply the same action boundaries. Result check: compare each output with the third table column; do not merely relabel Brief A’s artifact.
Righthand can help with both preparation jobs when the sources are supplied or accessible through verified assigned connections. An explicit export is a valid input route; it does not promise a native connector or continuous synchronization. See the Righthand documentation for setup and Features for task fit.
Choose by the decision ahead
Choose research when the team does not yet know which questions or facts are necessary. Choose decision preparation when the owner has a defined choice and needs evidence arranged around it. If key information is missing, the decision packet can recommend further inquiry as its next procedural step without inventing a preferred option.
Failure checks and a first-run test
A research brief may predetermine its conclusion by choosing only favorable sources. A decision brief may hide an assumption inside a numerical comparison. Preserve source dates and explain which criteria came from the owner. Prices, availability, and access conditions should be verified from their current authoritative sources before a real commitment.
Ask the reviewer to trace S3’s missing setup cost in both outputs. The research plan should name how to obtain it; the decision packet should show how it limits the comparison. Keep purchases, bookings, vendor contact, and budget approval outside these preparation briefs. Keep the accepted source system authoritative, and record any approved change there through its supported process. A comparison draft is evidence for your decision, not permission to alter the workflow on its own.
Review Pricing against the actual preparation and review workload. The useful evaluation is whether the accepted artifact reduces work for its intended reader, including correction effort.