Visualisation and the communication of design proposals - the role of sketches, annotated drawings, models and prototypes in developing ideas, and the use of presentation visualisations, design language and justification to communicate and pitch a resolved proposal

What this dot point is asking

QCAA wants you to understand visualisation as both a thinking tool and a communication tool. Designers visualise to develop ideas (thinking on paper) and to communicate the resolved proposal to a client or audience (selling the idea). You need to know the range of visualisation types - from rough thumbnails to high-fidelity presentation renders and prototypes - and how to use them to develop, refine and justify a design. Communication and justification of the resolved proposal is the climax of the design process and a heavily weighted part of QCE Design assessment.

The answer

Two jobs of visualisation

Visualisation does two distinct jobs in the design process:

• Developing ideas (thinking) - quick sketches and rough models externalise ideas so the designer can compare, combine and improve them. Visualising is faster than describing and reveals problems an idea hides in words. This happens throughout develop.
• Communicating the proposal (selling) - polished presentation visualisations and high-fidelity models communicate the resolved design to a client or audience persuasively and clearly. This happens in resolve.

The fidelity ladder

Visualisation rises in fidelity as the design firms up. Matching fidelity to phase saves effort - polishing a render of an idea you might discard is wasted work.

• Thumbnails and rapid sketches - fast, rough, many to a page; used in early ideation to capture and compare concepts.
• Annotated design sketches - a chosen concept drawn with labels explaining materials, dimensions, function and intent; the workhorse of develop.
• Low-fidelity prototypes - cardboard, paper, foam or digital mock-ups built to test a specific question (does it fit the hand? is the flow clear?).
• High-fidelity models and renders - accurate, finished representations used in resolve to communicate the final proposal.

Drawing and presentation techniques

QCE Design expects fluency with a range of techniques: freehand sketching, isometric and perspective drawing, orthographic (plan, front, side) views for technical clarity, exploded views to show assembly, and rendering to convey material and form. Digital tools (vector and 3D software, CAD) are valid and increasingly expected. The point is always communication - the right technique is the one that makes the idea clearest to the audience.

Design language and annotation

Annotation turns a drawing into an argument. Good annotation explains what a feature is, how it works, what it is made of, and crucially why it answers a user need. The visual language - line weight, colour, labelling, layout - should be consistent and legible so the audience reads the proposal the way the designer intends. Clear design language signals professionalism and helps the marker follow the reasoning.

Communicating and justifying the resolved proposal

The resolve phase ends in a pitch: the designer communicates the final proposal to the client or audience and justifies it. Justification is the part QCE Design weights most heavily here - you must show how the resolved design meets the design criteria and the identified needs, and why your decisions are defensible. A pitch that only describes features, without linking them back to needs, scores poorly. The strongest proposals walk the audience from need to feature to evidence.

Worked example