Member-only story
As we grow in our Design careers — from Entry-level (junior) to Mid-Level to Senior, we are expected to generate new innovative ideas and have self-driven projects that would add more value to business/company. This requires stakeholders' buy-in or higher management approval. Because, well, the Sketch/Figma/XD file is not what our users will see or interact with. It has to be implemented and released out in the wild — by our developer friends. And development is expensive!
To get approval from stakeholders I usually create concepts, wireframes, sketches, etc. to put forth my ideas. But, if I don’t want to spend a lot of “time” on an idea that has the possibility of being rejected, I use a more iterative and more time-effective approach. This is where Product (Design) Proposals come in handy.
What are Product (Design) Proposals?
Simply put it is a short summary of what the final product will be and how it would help our users. I often send these out with a few wireframes attached in an email to all higher managers to capture their interests and have the idea floating out there.
These proposals have 3 different phases and with increasing difficulty levels.
Part 1: The Idea
Difficulty Level: ★★☆☆☆
Writing a skeleton brief for sharing your ideas with managers and team members.
- Heading
- Sub-heading
- Summary (as your customers would read it… )
- Your Quote
- Customer Quote
- Call to action
Example ↓
‘Just for you’ — Trip.com’s smart offering for travelers
Trip.com’s application now recommends travelers nearby cities to explore — in a smart way. It will recommend you Round Trips, Return Trip, & Multi-city flights — so you can save on Flight Bookings
Ever been in a situation where you had a few more days to kill at your travel destination but didn’t know which nearby…
