Risograph print inspired by Lisa Champ, Brooklyn NY
The wedge is conservative. The destination is bold. Putting them in that order is the right move.
I wrote a doc this quarter that proposed evolving our design system squad from a small embedded team without a true home into a fully-funded cross-functional product with three executive-owned legs. Engineering, Design, and Product. One year out. I led with the destination.
The destination is bigger than what I’m actually asking for. That’s on purpose. The actual ask, buried later in the doc, is a thin wedge: one skill that codifies how prototypes should be built against our design system, plus spec automation in Figma. Contained inside existing engineering capacity. No new platform headcount. The Design Technologist hire that’s already sourced joins as the design-side partner.
I learned this pattern by accident a few years ago and have been refining it since. The temptation when you’re proposing a real change is to scale your ask to what you think will pass. You read the room, take the temperature, ask for the version that won’t get rejected. The version that won’t get rejected is also the version that won’t change anything. You spend political capital protecting a request that wasn’t worth protecting.
The inversion is to ask for the version you’d want if the room were already aligned, and then narrow. Open with the destination. Let the room react. Watch where the resistance forms. Then bring the ask down to the wedge, which now reads as the modest version of something the room has already half-engaged with.
A senior designer on my team noticed I’d done this on the design system doc and asked me about it in our one-on-one. He thought I’d softened my position in the meeting. I told him I hadn’t softened anything. I’d opened with the bold state on purpose, watched the room engage with it, and then narrowed to the wedge. The wedge was what I’d always been asking for. The destination was what made the wedge readable.
The reason this works is that skeptical stakeholders are more comfortable approving a step toward a vision they’ve already engaged with than approving an isolated request. The isolated request reads as a budget line. The step toward a vision reads as alignment. The first one gets debated. The second one gets approved.
The technique has limits. It only works if the destination is real. If the bold state is theater, the room can smell it, and you’ve used your one shot to look serious. The doc I wrote has a real one-year-out org chart with real people in real boxes. Our most seasoned Design System engineer evolves into AI lead. His partner in development into component lead. The Design Technologist hire arrives in the seat that already exists. The Senior PM box is explicitly marked “if earned,” with the condition that the wedge has to demonstrate the queue volume to justify it. The destination isn’t aspirational decoration. It’s the actual plan. The wedge is the first step.
If you can’t write the destination doc with that kind of specificity, you don’t have a destination. You have a wish. The technique won’t save you.
The other limit is that the technique has to be used sparingly. If every doc you write opens with a bold state, the room learns the pattern and starts discounting the bold state on arrival. You’re back to negotiating the wedge in isolation. The move has to be earned by track record. The first time you do it, the room takes the destination seriously because they don’t know yet that you’re going to narrow. The fifth time you do it, they’re waiting for the narrowing before you start.
I use it sparingly for that reason. It’s a tool for the moments when the gap between what’s possible and what would get approved by default is wide enough that the wedge would otherwise look like a budget line item instead of an investment. The design system was that gap. Most weeks aren’t.
The pattern is in the same family as a craft technique I’ve used since I was an IC. When you’re presenting design work, you don’t open with the version you expect to ship. You open with the version that pushes the conversation past where it would otherwise land. You let the room react. You bring the work back to the version you always intended to ship. The room thinks they moved you. They didn’t. They moved themselves toward a version they would have rejected if you’d opened with it.
This is the leadership version of that move. The artifact is bigger. The room is harder to read. The cost of misjudging is higher. But the mechanics are the same. You don’t get the version you want by asking for it. You get the version you want by asking for the version above it, in good faith, with the real specifics, and then narrowing on purpose.
The destination is the doc. The wedge is the ask. The room sees alignment. You shipped your plan.