The Mascot Request: Client Constraint in a Ten-Panel Design Folio
Priya is a Scholarship Design candidate building a ten-panel folio around a fictional public-health campaign, 'Slow the Flow', about household water use. Eight panels are locked: a wordmark, a colour system, three poster variants, a social-media grid, and two process pages. The local council's communications manager, acting as client, has seen the work and insists that panel nine become a cartoon mascot-a smiling water droplet-because 'ratepayers respond to mascots'. Priya's concept is a typographic system that treats water data as texture; a mascot would contradict the register and the assessment focus on extending a design position. There are six weeks left, two panels open, and a 1,500-word commentary to write. Priya has one week of school holidays and a part-time job. She has already tested two mascot sketches and found them visually clumsy, but she has not shown them to the client.
1. Explain how Priya should decide whether to accept, modify, or refuse the mascot request. What evidence should the decision rest on?
Read the worked answer
The decision should rest on three tests: audience function, system integrity, and assessment evidence. Function: if the campaign's goal is behaviour change among low-literacy ratepayers, a mascot may be a legitimate accessibility device; Priya should ask for the client's evidence, not assume taste. System integrity: a mascot can be admitted only if it is generated by the typographic system-for example, a droplet built from the same data glyphs-so it extends rather than abuts the concept. Assessment: Scholarship rewards a design position that is tested and refined, so a reasoned rejection can be stronger than compliance if Priya shows the test. She should produce one mascot test on panel nine, evaluate it against readability and register, and either refine or reject it on panel ten. The key is to make the client constraint visible as a design problem. Refusal without evidence is defiance; acceptance without testing is compliance. A documented negotiation with a clear criterion is design thinking.
2. How should the two remaining panels be used to show critical judgement rather than mere compliance or defiance?
Read the worked answer
Panel nine should be a controlled test, not a new direction. Priya could adapt the mascot into the data-glyph system: a droplet assembled from the same numerical marks used in the posters, then shown at three scales to test whether it reads as friendly without breaking the typographic register. Panel ten should show the decision: either a refined system that includes the device in one application, such as a bus-shelter poster, or a rejection sheet with the test, the criterion, and the revised alternative. The point is to evidence iteration: constraint, test, judgement, extension. She should avoid using both panels for a single polished outcome, because that hides the reasoning. One panel can be the test matrix; the other can be the applied consequence. This also protects against the examiner reading the folio as a client-service job rather than an authored design position.
3. What should Priya write in the commentary about the client negotiation so that it counts as design thinking rather than anecdote?
Read the worked answer
The commentary should frame the mascot request as a brief constraint, not a personal conflict. It should state the client's stated need, the evidence Priya had, the criteria she used-readability, register, campaign recall-the test she made, and the decision. For example: 'The client requested a mascot to increase recall. I tested a droplet built from the data glyphs against the existing poster at three viewing distances. At 2 m it read as a smudge; at 5 m it read as a droplet but lost the numerical texture. I retained the droplet only as a secondary mark in the social-media grid, where viewing distance is short.' This shows critical judgement because it connects form to context and admits a limit. It also shows extension: the system now has a rule for when a mascot-like device is permitted. The commentary should not say the client 'didn't get it'; it should show what the constraint revealed about the system.