EDUCATION SUBJECT ATLAS · DESIGN
What Is Design?
Design is the disciplined process of shaping possible futures. Designers investigate needs, define problems, generate alternatives, build representations, test ideas and refine solutions so that products, services, spaces, interfaces and systems work better for the people and conditions they serve.
Design is not simply making something look attractive. Appearance can matter, but design also includes function, usability, accessibility, cost, reliability, sustainability, emotion, manufacturability and social consequence.
Design is the work of deciding what should exist, for whom, under which constraints and how we will know whether it is better.
Design begins with a problem—but the problem may be wrong
A client may ask for a faster checkout screen when the real problem is that customers do not trust the price. A school may ask for more revision worksheets when the real problem is weak feedback. A city may ask for wider roads when the real problem is unreliable public transport.
Designers therefore investigate the problem before accepting its first wording. Framing determines what solutions become visible.
Users
Design is grounded in people who will use, maintain, purchase, regulate or be affected by the outcome. The “user” is not always one person. A hospital system may serve patients, nurses, doctors, technicians, cleaners and administrators simultaneously.
Good design identifies whose needs matter, whose voices are missing and where goals conflict.
Research
Design research uses interviews, observation, diary studies, surveys, analytics, contextual inquiry and other methods to understand behaviour and needs.
What people say, what they do and what the system records may differ. Strong design research compares several evidence sources.
Observation
Observation reveals workarounds, habits and hidden constraints that users may not mention because they seem normal. A designer watching a receptionist use three spreadsheets may discover an integration problem invisible in a formal process map.
Needs and requirements
Needs describe outcomes users or systems require. Requirements translate those needs into testable conditions. Design quality improves when vague preferences become explicit criteria.
“Easy to use” becomes more useful when the team defines who must complete which task, under what conditions, within what time and with what acceptable error rate.
Constraints
Constraints include budget, time, regulation, technology, materials, accessibility, brand, maintenance and environmental conditions.
Constraints can stimulate creativity because they narrow the design space and make trade-offs concrete.
Problem framing
A problem frame defines what is included, excluded and prioritised. Different frames produce different solutions. “How do we reduce waiting time?” differs from “How do we make waiting feel predictable?”
Designers should be able to explain why a particular frame was chosen and what alternatives it leaves outside.
Ideation
Ideation generates multiple possible solutions before selection. Sketching, brainstorming, analogies, morphological charts and scenario building can widen the option set.
Premature commitment is dangerous because teams become emotionally attached to the first plausible idea.
Divergence and convergence
Divergence expands possibilities; convergence evaluates and selects. Effective design alternates between the two rather than remaining endlessly creative or becoming prematurely narrow.
Sketching
Sketches are thinking tools. They externalise ideas cheaply so relationships can be seen, criticised and changed.
A rough sketch can be more useful than a polished rendering early in the process because it invites revision rather than defending a finished appearance.
Prototyping
A prototype is a representation built to answer a question. It may be a paper interface, foam model, storyboard, mock service, clickable screen or working technical component.
Fidelity should match uncertainty. The cheapest prototype capable of answering the question is often best.
Testing
Testing observes how a design behaves when users or systems interact with it. The goal is not to prove the designer was right; it is to expose where assumptions fail.
Useful testing defines tasks, participants, success criteria and what evidence would trigger revision.
Iteration
Iteration means revising based on evidence. Design rarely moves cleanly from research to final answer. Testing creates new questions, and new questions change the design.
Iteration is productive only when the team learns. Repeated change without explicit evidence is churn.
Usability
Usability concerns whether intended users can complete intended tasks effectively, efficiently and satisfactorily. It includes learnability, error prevention, recovery and clarity.
A feature-rich product can be unusable if users cannot discover or understand the relevant features.
Affordances
Affordances are possibilities for action that a user perceives in an object or interface. A handle suggests pulling; a raised button suggests pressing.
Good design aligns visible cues with actual behaviour so users do not have to memorise hidden rules.
Feedback
Feedback tells users what happened after an action. A click, progress indicator, confirmation message or physical response reduces uncertainty.
Systems that accept input silently create anxiety and repeated actions because users cannot tell whether the action succeeded.
Error prevention and recovery
Good design prevents predictable mistakes and makes recovery straightforward. Confirmation is useful for destructive actions; undo is often better for reversible ones.
Blaming users for recurring errors can hide a design defect.
Accessibility
Accessible design supports people with varied visual, auditory, motor and cognitive needs. Accessibility includes contrast, keyboard control, captions, readable structure, input alternatives and clear language.
Accessibility works best as a design foundation rather than a final compliance patch.
Universal design
Universal design seeks solutions usable by the widest practical range of people. Curb cuts help wheelchair users but also parents with strollers and travellers with luggage.
Designing for edge cases can improve mainstream use because it reveals hidden assumptions.
Visual design
Visual design organises colour, typography, spacing, hierarchy, imagery and composition to support communication and action.
Visual polish should make structure clearer, not decorate confusion.
Typography
Typography shapes readability, hierarchy and tone. Typeface, size, line length, spacing and contrast influence how easily information can be scanned and understood.
Information hierarchy
Hierarchy tells users what to notice first, what belongs together and what is secondary. Size, position, weight, spacing and grouping create this structure.
When everything is emphasised, nothing is emphasised.
Interaction design
Interaction design defines how people act through interfaces over time. It includes navigation, states, transitions, feedback and error handling.
A static screen can look elegant while failing during real task sequences. Interaction design evaluates the flow.
User experience
User experience is the broader perception formed before, during and after interaction with a product or service. It includes expectations, usability, emotion, support and trust.
UX cannot be owned by one screen-design team when operations, policy and customer support shape the same experience.
Product design
Product design integrates user needs, technology, manufacturing, business model and lifecycle. Physical product design also deals with materials, ergonomics, tolerances and repair.
A product succeeds when these systems fit together, not when one feature is exceptional.
Service design
Service design coordinates people, processes, policies, information and touchpoints across a customer journey. Much of a service occurs backstage where customers never see it.
Service blueprints map frontstage experience against backstage operations and dependencies.
Systems design
Systems design considers interacting components and feedback loops. Improving one component can worsen the overall system if dependencies are ignored.
Complex social systems require humility because interventions can produce unintended consequences.
Design systems
In digital products, a design system is a reusable set of components, patterns, tokens and guidelines. It supports consistency and faster development across teams.
A design system should encode principles, not merely accumulate components.
Industrial design
Industrial design shapes manufactured products through form, ergonomics, material, production and user experience. It sits closely beside engineering.
Industrial designers translate technical capability into objects people can understand and use.
Graphic design
Graphic design organises visual communication across print and digital media. It combines typography, image, grid, hierarchy and identity systems.
Its success is measured partly by whether intended audiences can perceive and act on the message.
Information design
Information design makes complex information understandable through structure, visualisation and language. Maps, forms, instructions, dashboards and signage are information-design problems.
Clarity depends on knowing what decision or task the information must support.
Design and architecture
Architecture is a design discipline operating through buildings and space. Both architecture and broader design use research, requirements, models, prototypes and iteration, but physical permanence and regulation give architecture distinctive constraints.
Design and engineering
Engineering emphasises technical performance, safety and feasibility; design emphasises human fit, framing and experience. Real products need both.
The strongest teams integrate these perspectives early rather than asking one discipline to decorate the work of the other.
Design thinking
Design thinking is a family of approaches that emphasises empathy, problem framing, ideation, prototyping and testing. It is useful as a process scaffold but should not be mistaken for all design practice.
Experienced designers often move non-linearly between research, making and evaluation.
Co-design
Co-design includes users and stakeholders in creating solutions rather than treating them only as research subjects. It can reveal priorities and constraints outsiders would miss.
Participation should be meaningful; inviting users to choose colours after all important decisions are fixed is not genuine co-design.
Design strategy
Design strategy connects design choices to organisational goals, brand, capability and market position. It determines where design effort will create meaningful advantage or public value.
Design operations
Design operations builds the systems through which design teams work: research repositories, tools, governance, workflows and measurement.
As organisations scale, good design depends on coordination as much as individual creativity.
Sustainability
Sustainable design considers materials, energy, durability, repair, reuse and end-of-life. A disposable solution may create hidden costs beyond the point of sale.
Circular design asks how products can remain useful through maintenance, reuse, remanufacture or recycling.
Ethics
Design shapes behaviour, so designers hold power. Dark patterns can manipulate users into choices they would not make with clear information. Exclusion can be encoded into forms, algorithms or environments.
Ethical design asks who benefits, who bears risk, what assumptions are embedded and whether consent is meaningful.
Persuasive design
Persuasive design intentionally influences behaviour. Reminders, defaults and social proof can help users, but the same mechanisms can exploit attention or asymmetry.
The ethical boundary depends on transparency, user interest and ability to opt out.
AI and design
AI can generate concepts, analyse patterns, personalise interfaces and accelerate prototyping. It can widen option space, but generated outputs still inherit training data and prompt assumptions.
The design task shifts toward framing, selection, evaluation and accountability rather than disappearing.
Metrics and design
Design can be evaluated through task completion, error, satisfaction, conversion, retention, accessibility, support demand and other measures.
No single metric captures all design value. A highly converting interface can still be manipulative or difficult to understand.
A systems model of design
- ENTITY: users, stakeholders, products, services, interfaces and environments.
- STATE: needs, constraints, prototypes, usability conditions and system performance.
- OCCURRENCE: research, ideation, testing, use, failure and revision.
- RELATIONSHIP: interaction, dependency, accessibility, ownership and feedback.
- INTENT: problem frame, design goals, value proposition and desired behaviour.
- OBSERVATION: interviews, behavioural data, usability tests and operational evidence.
- ARTIFACT: sketches, prototypes, components, products and service blueprints.
- CLAIM: propositions about usefulness, usability, desirability and impact.
- VOID: unobserved users, future contexts, unintended consequences and hidden constraints.
structured systems analysis design keeps the user problem, design intention, prototype evidence, operational constraints and unintended effects connected before an idea is declared successful.
How to think like a designer
- Observe the real situation.
- Define whose problem matters.
- Reframe the problem if evidence requires it.
- Make constraints explicit.
- Generate more than one solution.
- Prototype the riskiest assumption cheaply.
- Test with representative users.
- Measure both success and failure.
- Revise from evidence.
- Ask what unintended behaviour the design may create.
Common misconceptions
- “Design means making things pretty.” Design coordinates function, use, meaning and constraint.
- “Users always know the solution they need.” Users are experts in their experience, not necessarily in solution design.
- “More features improve a product.” Additional features can increase complexity and reduce clarity.
- “Testing happens at the end.” Early testing reduces the cost of wrong assumptions.
- “A successful metric proves a good design.” Metrics must be interpreted with ethics and system effects.
Mini case: a door people keep pushing instead of pulling
If many people make the same mistake, the problem may not be careless users. The handle, plate or hinge cues may suggest the wrong action. Design diagnosis changes the object rather than repeatedly blaming behaviour.
Mini case: an online form with high abandonment
The form may ask unnecessary questions, hide progress, reject valid formats or fail on mobile. Design research traces where users stop and why before adding more reminders.
Design across the learning journey
Young learners can begin with making, observation, sketching and simple design challenges. Secondary learners can study visual communication, product design, prototyping and user needs. Advanced study adds specialised interaction, service, industrial, strategic and systems design.
The progression is from making objects to designing evidence-based systems of use.
Why design belongs inside education
Design teaches learners to move between empathy and evidence, imagination and constraint, idea and test. It develops the habit of treating failure as information rather than embarrassment.
Design education matters because the world is full of systems someone chose—and those systems can be redesigned.