Design in Practice
Design in practice is about how designers actually work: the brief, the client, the constraints, the team, and the tools. A candidate must understand the difference between a need (a problem or gap that exists) and a want (a preference the client expresses), and how a design brief translates both into a stated problem with success criteria. Know the roles of client, end user, designer, and stakeholder - they are not always the same person, and a recurring trap is a question that assumes the client is the user. Understand constraints (time, budget, materials, regulations, ergonomics, manufacturing capability) versus considerations (aesthetics, trends, sustainability), and be able to classify a given factor correctly.
Another core idea is intellectual property and professional conduct: original work, attribution, confidentiality, and safe and ethical use of resources. Questions often test whether you can identify the first practical step in a scenario - usually clarifying the brief with the client, not sketching solutions.
Worked example / rule of thumb: For any scenario question, run the P-C-C-U check: Problem (what need is stated?), Client (who commissions it?), Constraints (what limits exist?), Users (who actually uses it?). If the question asks what to do next, choose the option that gathers or confirms information before committing to a design decision. A rule of thumb: constraints limit, considerations guide - never label a legal requirement as a mere consideration.
Also revise documentation practices: design records, version control, and how evidence of process supports later evaluation. Examiners reward answers that link a practice to its purpose, not just its name.