Design Strategies and Avoiding Design Fixation
What Is a Design Strategy?
A design strategy is the deliberate approach a designer or team takes to move from understanding a problem to finding a solution. Different strategies suit different types of problem. Some projects need deep collaboration between specialists; others require the designer to sit with users for days to understand their experience. Knowing which strategy to apply — and when to switch strategies — is a core professional skill.
User-Centred Design
User-centred design (UCD) treats the end user’s needs, behaviours, and limitations as the primary driver of every decision. Rather than starting from what can be manufactured or what the designer finds interesting, UCD begins with deep investigation of who will use the product and how they actually behave — not how the designer assumes they behave.
UCD relies on direct engagement with users throughout the process — not just at the start during research, but during prototyping and testing too. When a mobility-aid manufacturer involves wheelchair users in repeated rounds of testing, those users will consistently identify problems that engineers working from desk-based specifications would never anticipate. This is the core argument for UCD: it replaces assumption with evidence.
User-centred design keeps the end user’s real needs at the centre of every stage. It uses evidence gathered from direct contact with users — not assumptions — to drive design decisions, making it especially powerful for products used by vulnerable or specialist groups.
Collaborative Design
Collaborative design recognises that complex products cannot be designed by a single specialist. An aircraft requires aeronautical engineers, materials scientists, human factors specialists, software developers, and industrial designers. A medical device needs clinicians, regulatory experts, and manufacturing engineers. Collaboration means these specialists work together from the outset rather than handing a design from one department to the next.
The benefit of genuine collaboration (as opposed to sequential handover) is that conflicts between disciplines are identified and resolved early, when changes are cheap. If a software engineer only sees the hardware design after it is finalised, any interface conflict is expensive to fix. If both are in the room from the start, the interface is designed jointly.
Systems Thinking
Systems thinking treats a product not as an isolated object but as a component in a larger system. A smart thermostat is not just a device — it is part of a heating system, a home energy network, a user’s daily routine, a broadband connection, a smartphone app, and a supplier of data to an energy company. Designing the thermostat without considering these relationships will produce a product that works mechanically but fails in use.
Systems thinking also applies to sustainability. Designing a product in isolation from its supply chain, use context, and end-of-life disposal produces incomplete solutions. A packaging designer who considers only the structural brief — “protect the contents during transit” — without considering recycling infrastructure will design packaging that meets the brief but creates waste at scale.
The Double Diamond
The Double Diamond is a widely used model of the design process. It was developed by the Design Council and structures design into four phases: Discover, Define, Develop, Deliver. Each diamond represents a cycle of divergent thinking (opening up possibilities) followed by convergent thinking (narrowing down to a decision).
- Discover — explore the problem widely. Conduct user research, observe contexts, gather evidence without filtering. The goal is breadth, not answers.
- Define — analyse the research and synthesise a clear problem statement. This is where a design brief and specification emerge. The goal is to narrow understanding to the real problem.
- Develop — generate a wide range of ideas and prototype solutions. Iteration happens here. The goal is breadth of potential solutions, tested against the specification.
- Deliver — refine and test a chosen solution until it meets the specification. The goal is a final product or solution ready for production or use.
The Double Diamond has four phases: Discover (explore the problem), Define (clarify the real problem), Develop (generate and test solutions), Deliver (finalise and produce). Each pair of phases follows a diverge-then-converge pattern.
Design Fixation and How to Avoid It
Design fixation occurs when a designer becomes locked onto an early idea — their own or an existing product — and stops genuinely exploring alternatives. It is one of the most common barriers to creative design work. A designer who has seen a particular type of lamp will unconsciously replicate its form even when asked to design something completely new. The early idea becomes an invisible constraint.
Strategies designers use to break fixation include:
- Random input — introducing an unrelated object or concept and forcing connections between it and the design problem. A lamp design session that starts with the random word “river” might generate forms based on flow, reflection, and meanders rather than conventional lamp shapes.
- Reverse brainstorming — asking “how could we make this product worse?” or “what would cause this to fail?” and then reversing those answers to generate genuine improvements.
- Analogous inspiration — looking at how a completely different sector has solved a similar problem. Hospital designers studying how Formula 1 pit stops achieve rapid, error-free team coordination found applications in surgical team handover processes.
Iterative design is the practice of repeatedly making, testing, and refining a product based on what testing reveals. Each cycle produces a better-informed design decision. James Dyson’s reported 5,000+ prototypes for the bagless vacuum cleaner is the most famous example: each failed version revealed a specific reason for failure that informed the next attempt.
A strong extended response on iterative design shows how user feedback informs decisions throughout the process — not just at the end. A response that says “we tested the prototype and improved it” is weaker than one that says “user testing revealed that the grip diameter was too large for users with small hands, so the handle was reduced from 45 mm to 32 mm before the next prototype was built.”
Students often list design strategy names without explaining what they involve or why they are appropriate for a given scenario. Writing “the designer used user-centred design” names the strategy but explains nothing. Writing “the designer used user-centred design because the product was intended for elderly users with limited mobility — assumptions about grip strength and reading distance would have led to design errors that only direct testing with the target group could prevent” applies the strategy to the scenario, which is what the question asks for.