Skip to content

Trade Study

beta  ·  Family decision-docs  ·  Phase develop  ·  Sizes lean, full  ·  ~4,450 tokens

Compares a named set of technical alternatives against weighted criteria and records the recommendation that comparison supports, for a problem the organization has already decided to solve. Evaluates options; it does not have to be where the resulting decision is recorded, which is an ADR’s job.

Fast reference for using the trade-study bundle. For the full reasoning, history, and sources, read trade-study_companion.md. A fully worked instance is trade-study_example.md.

  • You already own the problem, and now have to choose among named technical approaches to solve it: a runner model, a message-ingestion technology, a persistence engine, an architecture pattern.
  • More than one approach is genuinely on the table, and the choice is not obvious from where you stand today.
  • The comparison needs to survive a reader who was not in the room: a reviewer, an auditor, or whoever revisits this decision in a year and wants to know what the road not taken would have cost.
  • Reasonable people on the team would weight the criteria differently, and writing the weights down, with a reason for each, is cheaper than arguing from memory later.
  • You are about to feed an ADR, an RFC, or an SDD a weighted comparison, rather than a paragraph of reasoning, for their own Alternatives Considered prose.
  • There was never a real second option. Skip this document and write the decision straight into whatever record normally follows one (see adr); companion section 4 names the source that says to skip it.
  • You are deciding whether to invest in something at all, not how to solve a problem you already own. No definition this bundle’s research read frames a trade study as an investment decision; cost sits inside the comparison as one criterion among several, not as the question itself. That is a business case’s job, and it is this bundle’s own boundary to draw, stated plainly rather than borrowed from a source (see companion section 1 and section 8).
  • The decision is already made and you want to justify it after the fact. A trade study with the answer chosen before the criteria is the predetermined-winner failure named below. Write the ADR honestly instead, or rerun the comparison for real.
  • You want feedback on a proposal before anything is decided. That is an RFC’s job: it asks for input before the call is made. This document evaluates named alternatives against stated criteria; it does not gather opinions on whether to proceed.
  • You are describing how a system will be built, not choosing among named approaches to building it. That is an SDD’s job. An SDD’s own Alternatives Considered section can cite a finished trade study instead of rebuilding the matrix in prose.
  • The alternatives cannot yet be named with confidence. A spike report exists to resolve that uncertainty first. Run it before the Alternatives section below can be filled in honestly.
Trade study RFC ADR SDD
Answers “Which named option wins, and why?” “Should we, and which way?” “What did we decide, and why?” “How will we build it?”
Timing Before the decision, once alternatives can be named Before the decision After the decision Before or while building
Produces A scored comparison and a recommendation A proposal A record A description
Records the decision itself No, it points to the record that does No Yes, immutably No

These are a division of labor, not four names for one job. A trade study’s Recommendation section may name the decision taken in one line; the ADR is where that decision is recorded for good.

Lean (five sections, the default): Problem and Decision Framing, Criteria and Weights, Alternatives, Scoring Matrix, Recommendation. Write lean when the stakes are contained and the comparison is between a small set of options whose tradeoffs are already mostly understood. The sources allow a short report as readily as a formal one (companion section 4).

Full (nine sections): adds Sensitivity Analysis, Risk and Benefit, Dissent or Independent Review, and References. Reach for full when the decision is high-stakes or hard to reverse, the team disagrees about the criteria or their weights, or a reviewer outside the immediate group will need to check the reasoning later.

Grow lean into full by adding sections; never reorder or rename the shared ones, because the full variant is a strict superset of lean. The scaling signal is how hard the decision is to reverse and how contested the criteria are, not the size of the system being decided about.

One caution that applies to either variant. If the do-nothing row in Alternatives is also doing the job of a scoring reference point (a Pugh datum), say so explicitly, because a poor or biased reference option can distort the entire comparison. A do-nothing baseline and a Pugh datum are not automatically the same thing; using one as both is a choice the author makes, not a default the template assumes (companion section 6.3).

Quality rubric (self-grade before you ship it)

Section titled “Quality rubric (self-grade before you ship it)”

Score each 0, 1, or 2. Under 14 out of 20 and the recommendation should not be acted on without a second look; send the document back for another pass before anyone treats it as settled.

Rows 7 through 10 grade sections the lean variant does not ship: Sensitivity Analysis, Risk and Benefit, Dissent or Independent Review, and References. Grade lean against the scope table below the main table instead of against all ten rows.

# Criterion 0 1 2
1 Question answered, not posed No question stated, or the title names a topic rather than a comparison A question is stated, but no decision maker is named or the decision it feeds is unclear A reader can point at the sentence naming the question, the decision it feeds, and who decides it
2 Weights justified and typed Weights appear with no stated reason Each weight has a reason, but the document never says whether a weight means importance or the swing between the best and worst option Every weight carries a stated reason, and the document names which of the two meanings its weights use
3 Do-nothing row scored No do-nothing or do-minimum row, and no line explaining its absence A do-nothing row exists, but it is a label with no real cost or risk behind it The do-nothing row is scored as a genuine alternative, or a specific reason for its absence is written in Alternatives
4 Scores have a basis Scores are bare numbers Some scores carry a basis, others do not Every score in the matrix carries a basis a reader could dispute, and the weighted total can be recomputed from the rows shown
5 Recommendation reasons from rows The recommendation restates the highest weighted total with no reasoning The recommendation names which rows it depends on, but states no condition under which it would change A reader can name the specific rows the recommendation depends on and the condition that would overturn it, and a genuine near-tie is reported as one rather than forced apart
6 Record pointer given No decision is named, and no record is pointed to A decision is named, but no record is pointed to, or the pointer is to this same document The line names the decision taken and a specific record elsewhere that holds it, or states plainly that no decision has been taken yet
7 Sensitivity tested (full) No weight or score was moved; confidence is asserted rather than tested A weight or score was moved, but the result is not stated either way A specific weight or score was moved by a stated amount, and the document says plainly whether the recommendation survives
8 Every contender covered (full) Only the recommended option has a risk or a benefit written down More than one option is covered, but the mitigation the leading option would need is missing Every alternative still in contention has a risk, a benefit, and the leading option’s mitigation is named
9 Reviewer independence stated (full) The section is silent, or says only that the team reviewed its own work A reviewer is named, but their stake in the outcome is not addressed A named person or group checked the scoring, and the document states how independent of the outcome they are, or says plainly that no independent check happened
10 References dated, checkable (full) Sources are named generically (“various documents”) or not at all Specific sources are named, but without a date Each criterion’s score traces to a named, dated source a reader could open and check

Score lean against this table instead of the headline threshold above.

Variant Rows that apply Maximum Score against
full all 10 20 14
lean 1-6 (it carries none of the four full-only sections) 12 9

Every cell above describes evidence, not a count. A rubric cell that can be satisfied by adding items will be satisfied by adding items, so none of them ask for a number of anything; each asks whether a reader could point at the specific sentence that does the work.

Each one is sourced in companion section 7.

  1. Criteria chosen after the alternatives, to fit the one already wanted. The list quietly favors the option someone preferred before scoring began. Set the criteria and their weights before anyone scores an option.
  2. A criterion with no way to measure it. A criterion only opinion can score gives a favored option somewhere to hide. Pick criteria that are transparent and measurable before scoring starts.
  3. A must-have outvoted by a pile of minor criteria. Weighting does not stop scoring from equalizing requirements, so enough small criteria can add up to select an option that fails something the team actually needed. Mark a must-have mandatory instead of only weighting it.
  4. A recommendation that survives no real test, because nothing was moved. If a minor change in one input changes the answer, the study is probably not sound, and a matrix with no sensitivity check has nothing to answer that criticism with.
  5. Scorers using the same scale differently, with no discussion to close the gap. One scorer uses the full range and another clusters in the middle. Left unaddressed, two scorers are not comparing the same thing.
  6. Averaging away a disagreement instead of resolving it. A quiet average, or a vote, hides exactly the disagreement a reader would want surfaced.
  7. A biased or unexamined datum, when the scoring method uses one. A poor reference option can distort the entire comparison. Naming the datum and testing whether the ranking survives a different one is the fix.
  8. Treating the weighted total as the decision rather than a prompt for one. The option with the highest score is not necessarily the one to choose. The total tells you where the discussion should focus, not what to conclude from it.

trade-study_template-lean.md · ~4,450 tokens

---
title: "{{title}}"
status: "{{status}}"
date: "{{date}}"
decision_makers: ["{{decision_makers}}"]
doc_type: trade-study
size: lean
source_template: trade-study
source_template_version: 0.1.0
---
<!--
LEAN TRADE STUDY. The five sections this bundle treats as the minimum comparison: Problem and
Decision Framing, Criteria and Weights, Alternatives, Scoring Matrix, and Recommendation. This is
the right default. A practical reading of every source that addresses formality points the same
way: write lean when the stakes are contained and the comparison is between a small set of
options whose tradeoffs are already mostly understood. To grow this into a full trade study, ADD
sections (see trade-study_template-full.md); never rename or reorder the ones below, because the
full variant is a strict superset of this one. See trade-study_companion.md section 4 (Variants
and sizing).
Microsoft's own engineering playbook goes further and names the condition for skipping the
exercise entirely: "Trade studies should be avoided if there is a clear solution choice." When
there is a clear design, it says, "the trade study should be omitted, and an entry should be made
in the Decision Log documenting the decision." If there was never a real second option, write
nothing and log the decision directly instead of filling this out for its own sake.
THIS IS NOT A BUSINESS CASE, AND THAT DRIFT IS THE EASIEST MISTAKE TO MAKE HERE.
A trade study compares named technical approaches to a problem the organization has already
decided to solve; cost sits inside the comparison as one criterion among several, not as the
question itself. No definition this bundle's research could read frames a trade study as the
decision whether to invest. If you are actually asking whether to invest in something at all,
rather than how best to solve a problem you already own, write a business case instead. See
trade-study_companion.md section 1 (Orientation) and section 8 (Relationships to other
artifacts).
THIS EVALUATES OPTIONS; IT DOES NOT RECORD THE DECISION.
This bundle's own division of labor hands the decision itself to an ADR, written once the
recommendation below is acted on. An RFC or an SDD whose own Alternatives Considered prose needs
a weighted comparison can cite this document instead of rebuilding the matrix in prose. A spike
report, if one came first, reduced the uncertainty that let these alternatives be named with
confidence in the first place. See trade-study_companion.md section 8 (Relationships to other
artifacts).
THE DO-NOTHING BASELINE IS THIS BUNDLE'S OWN REQUIREMENT, NOT A DOCUMENTED CONSENSUS.
NASA notes only that "(Sometimes doing nothing or not making a decision is an option.)" The FHWA
is just as conditional: "It is often good practice to include a" ... "alternative as the base
case, depending on the nature of the trade study." Several other named outlines mention no such
row at all. This bundle requires it anyway: adding
or dropping a do-nothing row can change which live option ranks first, because that is exactly
the mechanism a rank reversal describes. A comparison with no credible do-nothing option should
say so in one line in Alternatives, rather than silently drop the row. See
trade-study_companion.md section 3 (Anatomy > Alternatives, Including a Do-Nothing Baseline).
WHERE THIS FILE GOES: wherever your team keeps design and decision records. This bundle
prescribes no location. Once a decision is taken from this comparison, link this document from
the ADR that records it; do not fold the two together.
HOW TO FILL THIS IN
1. Read the comment under each heading: WHAT it wants, WHY it matters (with a pointer into
trade-study_companion.md for the deep reasoning), guiding questions to ASK, a GOOD and a WEAK
example, and the TRAP to avoid. For a table, PRIORITY explains the coverage rule and ROW HINT
says what a good row contains.
2. Replace each {{placeholder}} with your content. If a section does not apply, write "N/A" and
one line of why, rather than deleting it.
3. Before you ship it: self-grade against trade-study_guide.md, then DELETE every HTML comment.
They are guidance, not content.
-->
# {{title}}
<!-- WHAT A title naming both the problem this study is solving and, once you know it, the option it
recommends. A statement, not a topic.
WHY A comparison filed under a topic name alone, such as CI runner options, tells a later reader
nothing about what was decided; a title naming the recommendation lets them judge in one line
whether to open the rest.
Deep dive: trade-study_companion.md section 3 (Anatomy > Problem and Decision Framing).
ASK What problem does this comparison solve? Once you have an answer below, does the title still
read true, or does it only describe the question?
GOOD "CI runner model for the platform team: recommend self-hosted over the hosted service"
WEAK "CI options" (a topic, not a comparison; nobody can tell what was found)
TRAP Titling the technology area instead of the comparison. A title can be written before you start
and revised once you finish; revise it, rather than shipping the question as if it were the
answer. -->
## Problem and Decision Framing
<!-- WHAT The question this study answers, the decision it feeds and who decides it, and the
constraints and assumptions every alternative below must respect.
WHY The FHWA puts this first for a reason: "First, define the question the trade study is to
answer." Everything below is only as good as the question it is answering, and drift here is
where the predetermined-winner failure gets its opening, when criteria get written to fit an
answer already chosen rather than the other way around.
Deep dive: trade-study_companion.md section 3 (Anatomy > Problem and Decision Framing), section
6.7 (The predetermined-winner critique).
ASK What question is this study actually answering? What decision does the answer feed, and who
makes that decision? What constraint or assumption must every alternative respect, whether or
not anyone ever says it out loud?
GOOD "Question: should the platform team keep the current shared CI runner pool, or move to a
different model, before the fourth product team onboards next quarter. Decision this feeds:
which runner model to standardize on for the next two years. Decided by: the platform lead,
with sign-off from the three onboarding teams' leads. Constraints: must support the existing
container build images without a rewrite; budget ceiling of 4,000 dollars a month."
WEAK "We need a CI solution." (no question evidence could answer, no named decision maker, no
constraint)
TRAP Writing this section after the alternatives are already chosen, to justify them. A question and
a decision maker written down before the comparison starts is what keeps the criteria in the
next section from being reverse-engineered to fit an answer you already picked. -->
* Question this study answers: {{the_question}}
* Decision this feeds, and who decides: {{decision_and_decision_makers}}
* Constraints and assumptions every alternative must respect: {{constraints_and_assumptions}}
## Criteria and Weights
<!-- WHAT Each criterion this study will score alternatives against, its weight, why it was chosen and
weighted that way, whether it is mandatory, and the scoring method and scale in use.
WHY The FHWA's sequencing exists on purpose: criteria are set "before the alternatives are
selected, to avoid subconsciously biasing the criteria to favor a pre-determined preferred
alternative." ECSS requires the weighting itself to be justified, not merely stated. A weight
also carries one of two different meanings, importance or how much the best and worst
alternative actually differ (a swing weight), and this template asks you to say which one you
mean rather than picking one for you.
Deep dive: trade-study_companion.md section 3 (Anatomy > Criteria and Weights), section 6.2 (A
separate must-have screen, or one weighted pass), section 6.4 (One weight, two meanings).
ASK What criteria actually matter here, and why these and not others? Is each weight measuring
importance, or the swing between the best and worst alternative on that criterion, and have you
said which? Is any criterion mandatory, meaning an alternative that fails it is dropped
outright rather than merely docked points?
PRIORITY Set every criterion and its weight before you look hard at the alternatives in the next
section, to avoid biasing the criteria toward an answer you have already chosen. Mark a
criterion mandatory only when failing it should drop the alternative outright, not merely cost
it points.
ROW HINT A good row states the weight and the reason for that number, not the number alone.
"Reliability, weight 30" with no reason cannot be checked six months later; "weight 30, because
an outage here is customer-visible within minutes" can.
GOOD | C1 | Queue wait at peak load | 30 | No | Weighted this high because the fourth team's
onboarding is what forces this decision, and the shared pool already hits its job cap at peak |
WEAK | C1 | Good support | High | | Because it matters |
TRAP Picking the criteria after seeing how each alternative would score, so the list quietly favors
the one you already wanted. If a criterion only occurred to you after looking at the options,
say so and weigh honestly whether it belongs. -->
Scoring method and scale in use: {{scoring_method_and_scale}}
What a weight means here (importance, or the swing between the best and worst alternative on that
criterion): {{weight_meaning}}
| ID | Criterion | Weight | Mandatory? | Justification |
|---|---|---|---|---|
| {{criterion_id}} | {{criterion_name}} | {{weight}} | {{mandatory_yes_no}} | {{criterion_justification}} |
## Alternatives, Including a Do-Nothing Baseline
<!-- WHAT Every alternative actually considered, including a do-nothing or do-minimum baseline, and, if a
larger field was narrowed first, how.
WHY The FHWA's own advice: "Be sure that all reasonable alternatives are on the table." NASA's trade
tree is the named tool for narrowing a large field before detailed analysis begins. The
do-nothing row is this bundle's own requirement, not a documented consensus; see the note at the
top of this file and the reasoning behind it.
Deep dive: trade-study_companion.md section 3 (Anatomy > Alternatives, Including a Do-Nothing
Baseline), section 6.3 (The Pugh datum and the do-nothing baseline are not the same thing).
ASK What alternatives were genuinely on the table, not just the one you expect to win? If the field
started larger, how was it narrowed, and on what basis? What would doing nothing, or the
minimum, actually look like here, and what would it cost?
PRIORITY Every comparison needs a do-nothing or do-minimum row, even when it is rejected in one line.
If a comparison genuinely has no credible do-nothing option, write one line here saying why
rather than silently dropping the row.
ROW HINT A good row names a real alternative a reasonable team could actually choose, with what it
would concretely involve. A weak row is a label with nothing behind it, or a straw alternative
built to lose.
GOOD | A1 | Keep the current shared runner pool (do-nothing) | No new cost, but queue time grows
once the fourth team onboards | Yes |
WEAK | A3 | The obvious choice | | No |
TRAP Treating this table's do-nothing row as the same thing as a scoring reference point (a Pugh
datum), if you are also using one. A datum is what every score is measured against; a
do-nothing row is a candidate being scored in its own right. Say explicitly if the same
alternative is doing both jobs. -->
How the field was narrowed to the alternatives below (or "N/A, nothing was narrowed"):
{{how_the_field_was_narrowed}}
| ID | Alternative | Description | Do-nothing or do-minimum baseline? |
|---|---|---|---|
| {{alternative_id}} | {{alternative_name}} | {{alternative_description}} | {{is_do_nothing_baseline}} |
## Scoring Matrix
<!-- WHAT The completed comparison: each criterion against each alternative, a weighted total per
alternative, and the basis for each individual score, laid out so a reader outside this team
could still follow it.
WHY The FHWA's orientation is this template's default, alternatives on one axis, criteria on the
other, with a readability requirement stated directly: the matrix "should be easily
comprehensible to management and other stakeholders". ASQ gives the arithmetic and the caution
in one breath: the highest score "will not necessarily be the one to choose, but the relative
scores can generate meaningful discussion".
Deep dive: trade-study_companion.md section 3 (Anatomy > Scoring Matrix), section 6.1 (Is
weighted scoring reliable, or only as reliable as its inputs).
ASK What is the basis for each score, in one phrase a reader could check or dispute? Does each
weighted total actually equal score times weight, summed across criteria? If two scorers
disagreed on a cell, did you discuss it to a real answer, or quietly average the disagreement
away?
PRIORITY Every criterion from Criteria and Weights gets exactly one row here; every alternative from
the table above gets its own column. Add a column for each further alternative and a row for
each further criterion.
ROW HINT A good row scores every alternative against one named criterion and gives the basis for
each score beside the number. A row of bare numbers with no basis cannot be checked, disputed,
or trusted later.
GOOD "Queue wait at peak load, weight 30: self-hosted runners score 8, because the team can add
machines as the fourth team's builds arrive; the hosted service scores 4, because its plan caps
concurrent jobs at the level the shared pool already reaches at peak."
WEAK "Queue wait: 8 / 4." (numbers with no basis; nothing here can be checked or disputed)
TRAP Treating the highest weighted total as the decision rather than a prompt for one. The total
tells you where the discussion should focus, not what to conclude from it; write Recommendation
as reasoning from specific rows below, not as a restatement of this total. -->
| Criterion | Weight | {{alternative_1_name}} | {{alternative_2_name}} |
|---|---|---|---|
| {{criterion_name}} | {{weight}} | {{score}} ({{basis}}) | {{score}} ({{basis}}) |
| **Weighted total** | | {{weighted_total_1}} | {{weighted_total_2}} |
## Recommendation
<!-- WHAT The option the matrix supports, the rows it depends on, the conditions under which it holds, a
genuine near-tie reported as one outcome rather than forced apart, and the decision actually
taken, in one line, with a pointer to the record that holds it for good.
WHY The FHWA's own instruction is plain: "Select and document the preferred candidate". ECSS
requires both the choice and its conditions. NASA and Microsoft both allow a genuine near-tie,
or a list of open questions, rather than forcing a false precision onto a comparison that cannot
support it. This bundle's own division of labor stops the recommendation short of the permanent
record, which belongs to an ADR.
Deep dive: trade-study_companion.md section 3 (Anatomy > Recommendation), section 6.5 (One
recommended option, or every closely ranked one), section 8 (Relationships to other artifacts).
ASK Which option does the comparison actually support? Which specific rows does that depend on?
Under what condition would this recommendation no longer hold? If two options are genuinely
close, say that plainly, rather than reporting a winner the matrix cannot support. What decision
was actually taken, and where is it recorded?
GOOD "Recommended: the self-hosted runner, ahead by 4 points on the current weights, conditional on
queue wait staying the team's top priority. Re-run this comparison if the hosted plan raises
its concurrent-job cap; queue wait was the deciding criterion. Decision
taken: adopt the self-hosted runner, recorded in ADR 0091."
WEAK "We recommend the self-hosted option because it scored highest." (restates the matrix total,
names no condition, points to no record)
TRAP Forcing a clean winner out of a genuine near-tie. If two alternatives are within noise of each
other on the weights you actually trust, say that plainly and name what would separate them,
rather than dressing up a coin flip as a confident recommendation. -->
* Recommended alternative, or alternatives if genuinely close: {{recommended_option}}
* Rows this depends on: {{dependent_rows}}
* Conditions under which this holds: {{conditions}}
* Decision taken, and where it is recorded for good: {{decision_and_record_pointer}}

The reasoning, the history and every source, in the repository:

  • Companion - the long-form argument: why these sections, where the sources disagree, and what the bundle refuses to claim
  • History - what changed in this bundle, and when
  • Research log - every source consulted, with what each one actually supports
  • Catalog metadata - the machine-readable record this page is generated from

Catalog record: 10 sections across 1 format(s).