Design practice
Campaign-to-Product Redesign
Take a marketing landing page and redesign it as a product feature with states, flows, and edge cases
01 / Prepare
What you’ll
work on.
Take a marketing landing page (one you've designed or any public page) and redesign the core value proposition as an in-product feature. This exercise forces the mindset shift from campaign thinking to product thinking: you'll design for multiple states, consider edge cases, and think about the feature as part of a larger system.
Before you begin
- Figma proficiency (components, auto layout, prototyping)
- Understanding of the campaign-to-product mindset shift
- Familiarity with user flows, interface states, and product design basics
02 / Practice
The work,
step by step.
Work through these 4 parts at your own pace. Keep your notes and work together so you can review them when you finish.
Analyze the Landing Page
45 min
Choose a marketing page — A product landing page, pricing page, or feature announcement
Identify the core promise — What is this page selling? What user need does it address?
Map the funnel — What happens after someone clicks the CTA? Where does the marketing experience end and the product experience begin?
Define the Product Feature
60 min
Reframe the promise as a user task — "Sign up for premium" becomes "Upgrade your account and understand what changes"
Map the user flow — Entry point → steps → completion → confirmation
Identify states for each screen — Default (happy path), Loading, Empty (no data yet), Error (something went wrong), Edge cases (long text, missing data, permissions)
Design
120–180 min
Wireframe the flow — Low-fidelity first, focusing on information hierarchy and interaction
Build high-fidelity screens in Figma — Using components, not one-off designs
Design all states — Not just the happy path
Consider responsiveness — At minimum: mobile and desktop
Document
60 min
Write a brief explaining the shift — What changed between the marketing version and the product version? Why?
Annotate key decisions — Why this flow? Why these states? What trade-offs?
Spec one component — Full spec: spacing, color tokens, states, responsive behavior
03 / Review
Look at what
you’ve made.
Gather your deliverables, then use the criteria to find what worked and what you would change. They also give a peer something specific to respond to.
What to bring together
- Original landing page screenshot with analysis
- User flow diagram (entry → steps → completion)
- State inventory (default, loading, empty, error for each screen)
- Figma prototype (5–8 screens, mobile + desktop)
- Brief explaining the campaign → product shift
- One component spec
How to assess your work
- Mindset shift
- Clear evidence of thinking beyond the happy path
- State coverage
- All states designed, not just the default
- Systematic
- Uses components and tokens, not bespoke one-off designs
- Flow thinking
- User flow makes sense as a product experience, not a funnel
- Communication
- Brief clearly articulates what changed and why