In product design, how does a vision statement differ from a set of design principles, and when does a team reach for each?
answer
- destination versus rules of the road
- years ahead versus every review
- why we exist versus how we choose
- principles must be specific to the product
- vision sets direction, principles settle choices
basics
~20 sA vision statement describes the future the product aims to create for its users; design principles are short, product-specific rules for choosing between options. The vision sets direction and priorities; principles settle everyday design decisions and review debates.
solid answer
~40 sA **vision statement** is a picture of the change the product wants to make in its users' lives, looking a few years ahead - for a pharmacy refill app, something like 'every patient has their medication on time without having to think about the pharmacy'. It guides roadmap and priority decisions and rarely changes. **Design principles** are a handful of short rules that tell designers and engineers what to favour when options conflict, such as 'confirm the medicine, not just the order'. They are used every week: in critiques, design reviews and when two reasonable proposals disagree. A vision without principles leaves every decision to taste; principles without a vision can be internally consistent but aimed at nothing.
go deeper
Recall the difference: the vision is where the product is going for its users, principles are the rules for choosing between options. Be ready with one example of each.
Explain why a vision cannot settle a screen-level debate, why principles must be specific and opinionated, and how each principle should trace back to the vision.
Show how the pair works in practice: principles cited in reviews, decisions recorded as examples, and principles re-tested when the vision or the users change.
Discuss who owns the vision and the principles, how leadership behaviour makes them credible or hollow, and when a strategy shift should force a rewrite.
## Two artifacts with different jobs Product teams often keep several guiding documents, and interviewers check whether a candidate can tell them apart. The two in this question do different work: | Artifact | Answers | Time horizon | Used when | |---|---|---|---| | **Vision statement** | What future are we creating, and for whom? | Several years | Setting strategy, choosing what to build next, onboarding | | **Design principles** | When good options conflict, what do we favour? | Stable for a product generation, revised with evidence | Critiques, design reviews, trade-off debates | | **Brand values** | What does the company stand for? | Long | Identity and communication | | **Usability heuristics** | What makes any interface usable? | Timeless | Evaluating usability across any product | The last two rows are there to show what principles are **not**: they are neither the company's values nor general usability rules that apply to every product. ## What a vision statement contains A useful vision is short and concrete about the user and the outcome: - **Who** it serves - patients who take regular medication. - **What changes** for them - they never run out, and refilling takes no thought. - **Why it matters** - missed doses have real health consequences. It deliberately says little about screens or features. Its job is to make some roadmap items obviously more important than others and to give a team a shared destination. A vision that lists features is a plan, and it ages as soon as the plan changes. ## What design principles contain Design principles translate the vision into decision rules. Good ones share a shape: 1. **Short and memorable** - a team can recite them in a review without opening a document. 2. **Specific to this product** - they would not fit a food delivery app or a game unchanged. 3. **Opinionated** - each one favours something over something else that is also good. 4. **Explained** - each carries a sentence of rationale and an example of a decision it settled. A pharmacy refill app might hold principles like: - **Confirm the medicine, not just the order** - show the drug name, strength and prescriber before submission. - **Never ask for what the pharmacy already knows** - prefill insurance, address and prescriber. - **Refill is the default path** - anything else is one step away, never in the way. Common practice is a handful - roughly three to seven - because more cannot be remembered, and principles that cannot be remembered are not used in the moment of decision. ## How the two connect The vision is the reason the principles exist. 'Confirm the medicine' follows from 'on time and safely'; 'never ask for what we know' follows from 'without having to think about it'. When a principle cannot be traced to the vision, it is either a leftover from an older strategy or a personal preference dressed up as a rule. The flow in practice: 1. Leadership and the team agree on the **vision**. 2. The design team drafts **principles** that express how the vision shapes trade-offs. 3. Principles are used in **reviews**, and the decisions they settle become examples. 4. When the vision changes, the principles are **re-tested** against it. ## One debate, two artifacts Suppose the team disagrees about whether the refill screen should promote a paid home-delivery upgrade. The vision helps at the strategic level: delivery might serve 'on time' very well, so the feature belongs on the roadmap. It cannot say where the offer goes or how prominent it is. The principle 'refill is the default path; everything else is one step away' can: the offer may appear after the refill is confirmed, not as a gate before it. The vision justified building the feature; the principle decided its placement. Candidates who can walk through a case like this show they know which artifact answers which question. ## Common confusions in interviews - Treating the vision as a decision tool for a specific screen: it is too broad to say whether a confirmation step belongs in a refill flow. - Writing principles that are really values ('we care about patients') and therefore settle nothing. - Copying another company's principles; they encode someone else's users and trade-offs. - Confusing product principles with usability heuristics, which apply to any interface and do not express this product's priorities. A candidate who can say which artifact answers which kind of question - and give one example of each for a real product - has understood the distinction.
- Who should write a product's design principles, and who should sign them off?The design team usually drafts them, but engineers, product managers and people close to users should shape them, because the principles will be cited against their proposals too. Product leadership signs them off, since a principle that leadership overrules in the first real conflict stops working immediately.
- How often should a vision statement change compared with design principles?A vision changes rarely - when strategy or the target users change. Principles are revised more often, when reviews show that one fails to settle disputes, is never cited, or has been outgrown by the product. Both are revisited deliberately, not edited casually.
saying these in an interview costs you the question
- Vision and design principles are two names for the same document
- The company's values can serve as the product's design principles
- A vision statement should list the features to build next
- Generic usability heuristics are the product's design principles
- Another company's principles will fit our product just as well