Balearic PAU Design common mistakes
Balearic PAU Design · Understand the traps and how to avoid them.
Describing a composition only by naming the elements present ('there is a red circle, a diagonal line and some text') without explaining how they relate through balance, hierarchy, contrast or rhythm.
Candidates learn element vocabulary (point, line, plane, colour, texture) as a checklist and treat identification as the answer, because naming is easier to revise than the relational reasoning examiners reward. The question asks for analysis, not inventory.
What to do instead
Force every element mention into a relational sentence: 'the diagonal line splits the field into two unequal triangles, which pushes visual weight to the lower right and makes the small red circle the focal point.' Practise with a fixed template: element, placement, effect on the viewer's eye, contribution to the stated intention.
Using colour terms loosely, saying 'warm colours attract attention' or 'blue is calming' without specifying hue, value, saturation, or the contrast relationship with adjacent colours.
Everyday colour psychology clichés are widely repeated and feel safe, so candidates default to them instead of analysing the actual colour relationships in front of them. They also confuse additive and subtractive mixing or cannot explain simultaneous contrast.
What to do instead
Describe colours by three attributes (hue, value, saturation) plus their relationship: complementary, analogous, triadic, or value contrast against the ground. Justify any psychological claim by the specific mechanism (high-saturation warm hue against desaturated cool ground creates figure-ground separation) rather than by association alone.
Writing the design brief as a wish list of features ('it should be modern, sustainable and easy to use') instead of extracting constraints, target user, context of use and measurable objectives from the scenario.
Candidates rush to draw. The brief feels like paperwork before the 'real' work, so they restate the prompt in vague adjectives and then have no criteria against which to judge their own proposals later.
What to do instead
Convert the scenario into a structured brief with four labelled blocks: user and context, problem statement, hard constraints (budget, materials, dimensions, regulations), and three to five testable requirements. Write each requirement so it could be checked with a yes/no or a measurement.
Jumping from the first idea straight to a polished final rendering, with no evidence of divergent sketching, no alternatives compared, and no record of rejected options.
Time pressure and the desire to produce something visually impressive lead candidates to commit early. Portfolios and social media reward finished artefacts, so the iterative middle of the process is undervalued even though examiners mark it heavily.
What to do instead
Reserve a fixed block for divergence: at least 8 to 12 quick thumbnails or annotated variants before selecting. Then show convergence explicitly, with two or three shortlisted options scored against the brief's requirements, and state in one line why the chosen one wins and the others were dropped.
Treating the prototype or mock-up as a final presentation model rather than a test, so no user feedback, no measurement and no resulting change is documented.
Candidates equate prototyping with craft. They build one model to look good in the exam and skip the evaluation loop, so the marker sees no evidence of learning from testing.
What to do instead
Plan the prototype around one question it must answer (legibility at distance, grip comfort, assembly sequence). Record who tested it, what was observed, and name at least one specific modification made in response. Even a paper mock-up with three annotated findings satisfies this.
Setting type by eye alone: mixing too many typefaces, using default tracking and leading, and choosing a display face for body text or a decorative face for a functional label.
Candidates select fonts by personality and mood, which is a legitimate instinct, but they lack the technical vocabulary (x-height, counter, ascender, measure, leading, tracking, hierarchy by weight and size) needed to control legibility and consistency.
What to do instead
Limit the system to two families with a stated role each (display and text) and justify the pairing by contrast or kinship. State measure in characters per line, leading as a ratio to type size, and build hierarchy through size, weight and space rather than through colour and decoration. Check a small-size proof for legibility.
Producing a layout with several competing focal points and no clear reading path, so the eye has no entry point and no sequence through the information.
Candidates fill available space because empty space feels like unfinished work. They also give every item emphasis to avoid deciding what matters, which flattens hierarchy instead of building it.
What to do instead
Decide the single primary message before laying out, then assign each element a rank (primary, secondary, supporting). Use one dominant contrast to create the entry point and align the rest to a grid so the sequence is deliberate. Remove or reduce anything that competes with the primary message.
Justifying a product's form aesthetically while ignoring ergonomic data, material behaviour or the end-of-life phase, and claiming 'sustainable' without naming a strategy.
Sustainability and ergonomics are easy to assert and hard to demonstrate, so candidates use them as adjectives. Many also assume a bio-based material is automatically better, without considering durability, repairability, transport or disassembly.
What to do instead
Attach numbers or named standards to every claim: grip diameter and hand anthropometry, load-bearing capacity, wall thickness, recycled content percentage, or a design-for-disassembly principle such as reversible fasteners and material separation. Choose one sustainability strategy (longevity, repair, mono-material, recycled feedstock) and show how the design embodies it.
Attributing works, dates or ideas to the wrong movement or author, or describing a movement only by its visual style with no account of its social, technological or ideological context.
Movements are often taught as image galleries, so candidates memorise looks and pair them with approximate dates. Names, schools and works blur together, especially where movements overlap or share a region.
What to do instead
Build a timeline card per movement with four fields: period and place, key authors and one canonical work, the technological or social condition that produced it, and what it reacted against. Learn each work through its context, and if a date or attribution is uncertain, say so rather than guessing.
Answering the practical exercise with a generic 'good design' solution that ignores the stated user, context and accessibility requirements, or running out of time and submitting an unfinished proposal.
Under exam conditions candidates reproduce a familiar solution they have practised rather than reading the specific constraints, and they spend too long on rendering. Accessibility and context are the first things dropped when time is short.
What to do instead
Spend the first minutes annotating the prompt to extract user, context, constraints and success criteria, and time-box the answer: brief and ideation, development, final proposal, and a short justification. Check the final proposal against each stated constraint and add one explicit accessibility decision (contrast ratio, type size, reach range, tactile cue) with its rationale.