How would you evaluate your design?
How to evaluate the quality of your design
- Does the design fulfill its purpose? — Let’s start with the basics: what does the design need to achieve?
- Is the message easy to understand? — Design by Meella.
- Is it aesthetically pleasing? —
- Is the style appropriate for your audience? —
- Is the design original? —
How do you write a short design?
As a top level overview, a written design brief should include:
- An Overview of Your Business.
- The Objectives of Your Design Project.
- Your Target Audience and Market.
- The Problem You’re Facing.
- Project Specific Information.
- More About Your Business.
- Competitor Information.
- Project Timescales.
Which is the best explanation for a design decision?
As often as you can, connect your design decisions to the goals and objectives of the business. This might be the most obvious and common explanation for any design decision because everything we do is about designing around a particular use case, user story, or feature set.
When do you need to do a design review?
During a project build, it is necessary to evaluate the product design and development against project requirements and outcomes. A design review is a step of development that measures project success and prioritizes the next steps or features to continue developing. Design reviews are nothing new.
Why do we choose patterns for design decisions?
Designers spend a lot of time on other sites, apps, and devices learning about the newest useful design patterns, and so we naturally choose patterns that make the most sense to our audience and context.
When to circle back after making a decision?
It’s always useful, even after a decision has been made, to circle back and double-check your decisions against the documented use cases for which you hope to design. When you find your team getting off track, bring them back by reminding everyone what the use cases are and how our decisions affect them.