Two Trade Studies, Same Problem
I have had two engineers hand me trade studies on the same week, comparing the same two options, built from the same data. One document told me exactly what to do next. The other told me nothing I could act on. Same inputs, same conclusion even, but one was useful and one was not.
That gap is where a lot of programs lose time they never get back. It is worth looking at closely, because the difference is not effort. The weaker document often took longer to build.
What the Weak Version Looks Like
The weak trade study reads like a spreadsheet with opinions attached. Every row has a score, every column has a weight, and the numbers add up to a clean recommendation. It looks rigorous. It is not.
The problem shows up the moment someone asks why option A scored a 7 on reliability and option B scored a 4. The answer is usually “that’s what felt right” dressed up in a number. The weighting was set after the scores, not before, so it quietly bends toward whichever answer someone already favored. Nobody can point to the assumption that would flip the result, because nobody wrote the assumptions down separately from the scoring.
This version is confident. It is also fragile. The first hard question in a review takes it apart.
What the Strong Version Looks Like
The strong trade study starts somewhere different: with the decision it is trying to support, written as a single sentence, before any scoring happens. Something like, “we are choosing a propulsion approach that can tolerate a two-year schedule slip without a redesign.” Everything else gets built against that sentence.
The weighting gets set and locked before the options are scored, not adjusted afterward to match a gut feeling. Each score has a one-line justification next to it that points to a real number: a test result, a vendor spec, a mass budget. And the whole thing includes a short section nobody asks for but every good one has: here is the assumption that, if wrong, changes the answer.
That last part is the tell. A strong trade study is not trying to look certain. It is trying to show exactly where the uncertainty lives, so the people reading it know what to watch.
The Habit Underneath It
The real difference between these two documents is not formatting. It is a habit: writing the decision down before you start collecting evidence for it.
Most engineers I have worked with jump straight to scoring because scoring feels like progress. You are filling in cells, the document is growing, it looks like work is happening. Writing a single sentence about what decision you are actually trying to make feels like a stall. It is not. It is the thing that keeps the scoring honest later, because you can check every row against it.
I have started asking people to send me that one sentence before they send me anything else. Not the spreadsheet, not the weighting scheme, just the sentence. If they cannot write it cleanly, the trade study is going to wander, no matter how much data goes into it.
What I Tell People Before They Start
Before anyone builds the matrix, I ask three things out loud. What decision does this answer. What would make us wrong. Who needs to be able to defend this in a room six months from now when they no longer remember today’s reasoning.
That last one matters more than people expect. A mission architecture decision made this year gets defended by someone else, later, often in a review where the original context is gone. A trade study that only makes sense to the person who wrote it fails that test immediately. One that shows its assumptions and its weighting up front survives it, because anyone in the room can trace the logic without having been there for the original argument.
The spreadsheet is never the hard part. The sentence that comes before it is.