Study smarter with Fiveable
Get study guides, practice questions, and cheatsheets for all your subjects. Join 500,000+ students with a 96% pass rate.
In Design Strategy and Software I, you're being tested on your ability to create interfaces that users can actually use—not just interfaces that look pretty. These ten principles form the foundation of every design decision you'll make, from button placement to error handling. Understanding them means understanding why certain designs succeed while others frustrate users into abandoning your product entirely.
The principles you'll learn here connect directly to broader concepts like cognitive load theory, human-computer interaction, and inclusive design. You'll see these ideas resurface in usability testing, design critiques, and portfolio reviews. Don't just memorize definitions—know what problem each principle solves and when to apply it. That's what separates students who can recite terms from designers who can actually build things people want to use.
The brain has limited processing power. Great UI design respects this constraint by making information easy to find, understand, and act on.
Compare: Visibility vs. Hierarchy—both help users find what they need, but visibility ensures elements are present and noticeable while hierarchy ensures they're organized by importance. If an exam question asks about prioritizing information, reach for hierarchy; if it's about discoverability, that's visibility.
Users need to feel in control and understand what's happening. These principles create trust through predictability and responsiveness.
Compare: Feedback vs. User Control—feedback tells users what happened, while user control lets them change what happened. Both reduce frustration, but feedback is passive information while control is active agency. Strong designs need both.
Good interfaces make the right action obvious and the wrong action difficult. These principles shape user behavior through design.
Compare: Affordance vs. Error Prevention—affordance guides users toward correct actions by making them obvious, while error prevention blocks incorrect actions through constraints. Think of affordance as the carrot and error prevention as the guardrail.
Interfaces serve diverse populations with different abilities, experience levels, and contexts of use. These principles ensure no one gets left behind.
Compare: Accessibility vs. Flexibility—accessibility ensures users can use the interface regardless of ability, while flexibility ensures users can use it their preferred way. Accessibility is about removing barriers; flexibility is about offering choices. Both serve inclusion, but accessibility is non-negotiable while flexibility enhances satisfaction.
| Concept | Best Examples |
|---|---|
| Reducing cognitive load | Visibility, Simplicity, Hierarchy |
| Building trust through predictability | Consistency, Feedback |
| Empowering user agency | User Control, Flexibility and Efficiency |
| Guiding correct behavior | Affordance, Error Prevention |
| Inclusive design | Accessibility, Flexibility and Efficiency |
| Preventing frustration | Feedback, Error Prevention, User Control |
| Supporting novice users | Simplicity, Consistency, Affordance |
| Supporting expert users | Flexibility and Efficiency, User Control |
Which two principles both reduce user frustration but through opposite approaches—one by informing users and one by empowering them to act?
A user clicks a submit button but nothing visible happens for three seconds. Which principle has been violated, and what's the risk?
Compare and contrast affordance and consistency: how do both guide user behavior, and what's the key difference in how they achieve this?
You're designing a form that asks for a phone number. Explain how you would apply both error prevention and feedback to this single input field.
An FRQ asks you to evaluate a design that works well for sighted mouse users but fails for keyboard-only users. Which principles would you reference, and what specific fixes would you recommend?