Decision Stack

Decision Stack is the critique framework you pull out when the work is nearly done and the team must decide what actually ships. It replaces vague open-ended reviews with four rigid buckets. The designer leads with the exact decision the room needs to make. Next they show every option they already explored and killed. Then they state their recommendation plus the reasoning behind it. Finally they list every risk they can imagine. Reviewers do not pitch new ideas. They test the stack. They probe the risks, challenge the weighting, and verify the designer did not conveniently forget a major downside. The entire meeting becomes a pressure test of the thinking instead of a last-minute brainstorm that should have happened three weeks earlier.

Decision Stack is not a presentation where the designer defends pretty mockups. It is not the place for random taste comments about button radius or gradient direction. It is not an early-stage exploration tool and it is not a group ideation session. If you walk in with one comp and ask what people think you are not running Decision Stack. You are wasting everyone's time. The framework demands homework. Skip the options-on-the-table section or soft-pedal the risks and the whole thing collapses back into the same ego-driven theater that makes designers dread critique.

Take the 2024 checkout redesign at Stripe. Designer Maya needed a decision on whether the new one-click Apple Pay prominence would hurt existing card conversions. She opened the critique with Decision required: Keep the prominent Apple Pay slot above the card form or move it below the fold. She then showed the three options on the table: the 2022 layout that buried payment methods and tanked conversion 19 percent, the maximalist version with every payment logo screaming for attention, and the tested hybrid that used progressive disclosure. Her recommendation was the hybrid because their Q3 A-B test on 240,000 sessions showed it lifted overall conversion 11 percent while keeping card flows intact. Risks included European users with lower Apple Pay adoption feeling secondary plus potential App Store review friction on prominence. The team spent twenty minutes stress-testing those risks against EU regulatory changes and recent competitor data instead of inventing new button treatments on the spot. Maya left with clear direction and the team avoided another round of half-baked revisions that would have delayed launch by two weeks.

Another concrete case happened at Notion in 2025 during their database overhaul. The designer needed sign-off on removing the legacy inline database toggle that 4 percent of users still touched daily. Decision required: Remove it entirely or keep a buried preference. Options on the table included the 2023 version that kept every toggle visible and created panel clutter, the radical removal tested in beta with 1200 users, and a compromise that hid it behind a power-user menu. Recommendation was full removal backed by usage logs showing the feature created more support tickets than value. Risks were loud complaints from a small set of enterprise users plus the inevitable Twitter thread from ex-Notion power users. Reviewers challenged the risk weighting with data from similar feature sunsets at Linear and Figma. The meeting ended with a documented mitigation plan instead of another month of indecision.

Use Decision Stack in pre-ship critique when the designer has already explored alternatives and the team is deciding what reaches production. Deploy it any time the work is 80 percent or more complete and the cost of changing direction is real. It shines in cross-functional rooms where engineers and PMs need to see the tradeoffs instead of watching a designer defend pixels. Do not use it during direction-setting or mid-fidelity stages when the work still needs broad exploration. Never use it if the designer has not prepared the options and risks in advance. In those cases the meeting will expose the lack of preparation and you will wish you had run Goal Rationale Feedback instead.

Decision Stack turns late-stage critique from opinion roulette into a focused stress test of the designer's actual thinking.