The Portfolio of Decisions
Judgment is invisible until it is made legible, and the evidence is decisions rather than output. What you chose, what it cost, what you turned down, and how you found out you were wrong. Most of what you have built is confidential and cannot be shown to anyone. Decisions travel anyway, because carrying one is just remembering out loud.
Framework 9 of 10 · Chapter 9: What They Can See
The standard advice is to build a portfolio, and for engineers the advice has always sat badly, because the good work is behind an NDA. You cannot show the repo. You cannot show the migration. You cannot show the incident.
Decisions do not have that problem. A decision can be described at any level of abstraction you need, in any room, without disclosing anything, and it is the only artifact that demonstrates judgment directly.
What travels: what you chose, what it cost, what you turned down, and how you discovered you were wrong.
When it applies
Interviews, promotion packets, performance cycles, and the conversations you are not in, where a former colleague is asked who they would want to work with again. All four read the same evidence.
How to run it
The record has to be written when it happens, not when you need it. Reconstructed reasoning is thin and audible.
- Write the why at the moment of the decision, wherever the work lives. In the fixture. In the comment above the rule. In the ticket.
- Once a quarter, pull the ones that never shipped as a feature. Those are usually the strongest, and they are the ones with no other trace.
- Keep one of them somewhere a person who was not in the room could find it.
Preparation then takes an evening instead of a fortnight, because the work was already done in small pieces for reasons that had nothing to do with a résumé.
Where it fails
Decisions are plentiful, records are not. Engineers who struggle with "walk me through a decision" almost never lack decisions. They lack any written trace of them, and memory returns the outcome without the reasoning.
Written for an audience. A decision log kept for a promotion cycle reads like one, and the tell is that everything in it turned out well. Include the ones you got wrong and how you found out.
Filed where nothing reads it. A record that lives only in your notes app helps you in an interview and nowhere else. At the seam, it also does work.
Practice
Write down three decisions from the past year that never shipped as a feature. What you chose, and what it cost. Then put one of them where someone who was not in the room can find it.