16 August 2021
This post collects the ten design principles featured in Bressler groups Design defined volume 2, with plenty of links out to more info and, hopefully, a whole lot of inspiration. It represents the span of Bressler groups disciplines, from user research and design strategy to electrical and software engineering.
Also check out volume 1 of these principles.
Source: Design Defined, v2: 10 More Design Principles for Better Products
People often think of brand consistency as it relates to the colors, logos, terminology, and tone used in advertising and communications, but it’s just as important for designers of physical products to consider brand consistency as it relates to form, finish, usability, and user experience.
Forecasting predicts probable future scenarios based on trend analysis and helps companies determine their ideal outcome. Backcasting works in reverse to plan the steps it will take to get there.
The law explains why having too many options negatively impacts a user’s experience and makes it harder to complete a task. It’s a reminder not to overload a user with choices, and it’s one reason that well-designed remotes have fewer buttons.
Devices capable of OTAU require more work upfront. Electrical engineers have to build devices to be smart enough to detect firmware versions, safely download, update, and go back to work.
If your design isn’t pushing the limits of what’s possible or challenging conventional wisdom about what a product can be, it’s not radical innovation. To get there, sometimes you need to break your process, throw away your plans, and acquire a counterintuitive mindset.
STEEPLE stands for social, technological, economic, environmental, political, legal, and ethical. The framework pushes us to consider how each factor will impact society — and how products and services will fit into future scenarios.
Tell, Don’t Ask is a modular approach, which makes it easier to test and maintain embedded devices.
No matter how capable users are most of the time, mistakes happen. By predicting why a user might misuse a product (e.g. a sleep-deprived doctor using a medical device), designers can add safeguards and workflows to minimize the chance of failure.
In the generative research phase, moderators seek insights to drive key design decisions. In the evaluative research phase, moderators are looking to learn what users think of the product before “design freeze” sets in.
Designers should begin thinking about accessibility on day one. Mobile, voice, and “interface-less” applications should consider accessibility before the first line of code is written or the first wireframe is constructed.
People often think of brand consistency as it relates to the colors, logos, terminology, and tone used in advertising and communications, but it’s just as important for designers of physical products to consider brand consistency as it relates to form, finish, usability, and user experience.
Forecasting predicts probable future scenarios based on trend analysis and helps companies determine their ideal outcome. Backcasting works in reverse to plan the steps it will take to get there.
The law explains why having too many options negatively impacts a user’s experience and makes it harder to complete a task. It’s a reminder not to overload a user with choices, and it’s one reason that well-designed remotes have fewer buttons.
Devices capable of OTAU require more work upfront. Electrical engineers have to build devices to be smart enough to detect firmware versions, safely download, update, and go back to work.
If your design isn’t pushing the limits of what’s possible or challenging conventional wisdom about what a product can be, it’s not radical innovation. To get there, sometimes you need to break your process, throw away your plans, and acquire a counterintuitive mindset.
STEEPLE stands for social, technological, economic, environmental, political, legal, and ethical. The framework pushes us to consider how each factor will impact society — and how products and services will fit into future scenarios.
Tell, Don’t Ask is a modular approach, which makes it easier to test and maintain embedded devices.
No matter how capable users are most of the time, mistakes happen. By predicting why a user might misuse a product (e.g. a sleep-deprived doctor using a medical device), designers can add safeguards and workflows to minimize the chance of failure.
In the generative research phase, moderators seek insights to drive key design decisions. In the evaluative research phase, moderators are looking to learn what users think of the product before “design freeze” sets in.
Designers should begin thinking about accessibility on day one. Mobile, voice, and “interface-less” applications should consider accessibility before the first line of code is written or the first wireframe is constructed.