How I take a feature request from a ticket to five working concepts and a design review the team can act on.
In the Flight Plan chat, the right panel showed a static message and four inactive pills. It did not reflect what the agent had learned, did not preview the plan, and gave no sense of how close the plan was to being built.
The ask: make it dynamic. Show progress as Content, Demographic, Budget and Timing are learned, say what is still needed, and hand off to the finished plan when all four are known.
The ticket (MSS-4355) says the right panel is static: four inactive pills, no sense of progress. I restate it as a goal: show what the agent has learned, say what is missing, hand off when done.
Instead of one answer, I explore five concepts before anyone commits, using my design system and Figma as prompt fuel so the first round is already on-brand.
Each option is a working HTML prototype where you can toggle Content, Demographic, Budget and Timing in any order and watch the state change.
I write acceptance criteria up front and mark each one met or partial, honestly, so reviewers see gaps without hunting.
I end with the questions the team has to answer, not a single recommendation dressed up as finished.
Same four inputs, same finished plan. Each concept answers a different question about how much progress the panel should show and how.
Blurred deal cards sharpen as each answer lands, finishing in real deal cards built from the Reco Card.
A sentence with blanks that fill in as the agent learns each item.
A plane moves to each stop on a route as items are learned.
Households and budget numbers appear as the answers that unlock them arrive.
A ticket fills in and its barcode prints. Added in the prototype after the Figma round.
Pick an option, then use the swapper inside to mark Content, Demographic, Budget and Timing as learned, in any order.
Every review page starts with the criteria from the ticket. I mark each one met or partial and say why. Three of six are fully met; two are partial and the page says so.
A good review ends with decisions, not a pitch. These went to product and engineering with the prototype.
The same template works for any feature: ticket, Figma, working prototype, criteria, open questions. It keeps reviews short, keeps feedback specific, and lets a team of designers work the same way without me in the room.
See the AI workflow behind it, or the FlightPlan case study this feature belongs to.