How do you communicate to a product designer what you want from them? Draw things on a whiteboard? Show a competitor's app and ask them to do yours like that, but better? Send them telepathic waves?
All of this is possible, although we don't recommend relying on telepathy too much. However, there are more effective ways to ensure a designer embodies your vision. And the most common is creating a design brief.
Today we'll talk about design briefs, how to use them, and if you can avoid them altogether. Spoiler: yes. Let's go!
Please like, subscribe, and hit the bell button if you find this video useful.
• How to Build a SaaS in 9 Steps – [ Ссылка ]
• Design Brief Example: How It Should Look Like and What It Should Contain – [ Ссылка ]
Check out Instagram for loads of Information on SaaS business:
[ Ссылка ]
Check out Eleken's blog, where we share our product design wisdom:
[ Ссылка ]
And make sure you're subscribed to stay updated with my latest videos.
Contact Us
• Website: [ Ссылка ]
• Instagram: [ Ссылка ]
• Facebook: [ Ссылка ]
• LinkedIn: [ Ссылка ]
#designbrief #uidesign #uxdesign #uidesignbrief #uxdesignbrief #eleken
00:00 – Intro
00:39 – What is a design brief, and why do you need it?
01:28 – How do you write a design brief?
01:47 – What does your company do?
02:10 – What tasks should the design solve?
02:36 – What is your target audience?
02:57 – Who are the competitors, and what differentiates your product from them?
03:13 – Do you have references?
04:12 – What is the timeline and budget?
05:11 – When classic design briefs don't work?
06:37 – Do you really need a design brief to start working with a designer?
