AI Design Presentation Generator

Follow the narrative arc: Context (the problem and why it matters), Process (how you approached it), Solution (what you designed and the rationale), Evidence (data, testing results, or principles supporting decisions), and Next Steps (what you need from the audience). This structure builds understanding before asking for feedback, preventing premature critique of solutions before the audience understands the problem.

Focus on business outcomes and user impact, not design craft. Instead of 'We used a 4-column grid with 24px gutters,' say 'We organized the dashboard so users can find their key metrics in under 3 seconds.' Use before-and-after comparisons, user quotes, and data to support design decisions. Show the problem first and let the audience feel the pain before presenting your solution.

Match duration to decision complexity. Sprint demos: 5-10 minutes. Design reviews: 15-20 minutes. Major proposals: 30-45 minutes. Allocate at least one-third of the time for discussion and feedback. If your presentation runs longer than planned, you are probably including too much process detail — show the final direction with selected highlights of the rationale, not every design exploration.

Separate feedback into two categories: preference-based ('I don't like blue') and principle-based ('The contrast seems low for accessibility'). For preference feedback, redirect to the research and goals: 'We chose this direction because user testing showed...' For principle-based feedback, acknowledge it constructively and discuss trade-offs. Never get defensive — frame pushback as collaborative problem-solving.

Selectively, yes. Showing 2-3 explored directions demonstrates thoroughness and helps the audience understand why you chose your recommended approach. However, do not show every exploration — too many options invite bikeshedding. Present rejected alternatives briefly with the reason you moved on, then spend the majority of time on the recommended direction and its rationale.