Few occasions during the ideation phase will ever be as anticipated and well-attended as the unveiling of a new design concept. It’s like your own Apple Keynote - there you are sporting New Balance shoes and a black turtleneck.
When done right, concept designs are a glimpse into the future of your product. They’re not just pretty pictures, and I promise you, a high-five from the CEO is worth a thousand times more than a fist-bump from another designer. Know your audience and the purpose of your design.
A great concept is multifaceted — it checks boxes for multiple stakeholders and inspires them in different ways.
There’s much to gain from a well-composed design, so think strategically instead of only visually. Design for the user, business, marketing, and development.
It would be irresponsible to start with anyone other than the user since they’re the ones who have to put up with our font choice and color selections.
Serving the user is all about solving their pains in creative and efficient ways, so a design concept should tell a relatable story.
Take advantage of personas defined during user research to help you determine the most appropriate screen(s) to mock up for your concept. If the most active user in the product is doing tactical work, then show one of their common workflows or a screen where they’ll be accomplishing those tasks.
Since it’s rare for the end user to actually be in the room when you present concepts, stakeholders will need evidence that your proposed solutions are sound. Utilizing research will help you sell your vision; be sure to connect insights back to what you heard from customers. Serve the user and prove to the stakeholder(s) how and why you are doing so.
What to do:
Quite simply, businesses want to make money. They also have deeper missions to improve an industry, but in the end, revenue matters.
While you may not feel professionally equipped to make pricing and packaging recommendations to the stakeholder, your design can hint at how pricing may manifest itself inside of the product or feature.
An “Upgrade” button in the navigation or a “Pro” badge next to a feature can make a profound statement about product revenue opportunities. Cover obvious revenue models (like seat licenses), then creatively show one or two additional revenue stream ideas. The worst-case scenario is they’re left on the cutting room floor. But the upside is these ideas are added to the product roadmap.
Unless the company is well-resourced enough to build a fully proprietary product, integrations and partnerships are practical and sensible ways to scale the business. Since you’re designing the concept(s), you have the luxury of viewing the product from the inside out, so you’re well-positioned to see these kinds of opportunities where leadership cannot. Hints in the design of supportive integrations or business partnerships are subtle ways to make strategic impacts on the product roadmap, and they may end up saving the company months of time or money.
What to do:
There’s a much stronger tie between marketing and the product than just a few screenshots of the app on the website. With SaaS products shifting from B2B to B2U, this is more true every day. Marketing is the voice of the business, so the product should speak the same way.
Concept designs are an early opportunity to influence the outward tone of the business.
When someone in marketing sees design concepts, s/he ought to leave with a strong idea for how to talk about and sell the product—how a blog article might sound, what types of images are shared on Twitter, or how the user is addressed in a marketing email.
In-app help text, error messages, and upsell banners can inject personality into the product via text, but don’t forget iconography and imagery. A cactus illustration in an error modal might be more appropriate for your consumer-facing product than a red stop sign. Marketing folks eat this kind of stuff up, so give them a spark. They’ll take it from there.
What to do:
Concept designs are great and all, but they’ll eventually need to get built. Developers view concept designs through very different glasses than everyone else because they’re responsible for bringing them to life.
As a designer, you should always push the envelope, but recognize that someone, someday, will have to figure out a way to code that fancy glowing line chart.
If your design has anything unconventional or interactive (charts, maps, drag-and-drop editors, drawing canvases, etc.), spend a couple minutes during the presentation explaining how it will work. Developers will appreciate your consideration, and it will quell any negative knee-jerk reactions.
For bonus points, do some research into frameworks, APIs, or integrations that will help developers execute your design. They’ll feel more equipped to successfully implement your design if they know something similar has been done before.
Developers aren’t scared of new design concepts. Quite the contrary, in fact. Most love a good challenge and will be energized by something new. Design clean, consistent, and thoughtful concepts, and developers will help you carry out your vision.
What to do:
Product and feature concepts are the most fun designers will ever have because they get to think freely, innovate liberally, and influence the business. But before a product idea is sold to a customer, the vision must be sold internally. By thoughtfully designing with multiple internal stakeholders in mind, you’ll strengthen the likelihood of materializing your vision.
it’s critical to evaluate the effectiveness of a conceptual design from...
it’s critical to evaluate the effectiveness of a conceptual design from different angles prior to committing to development.Keep Reading