The Folio That Ran Out of Time
A student has eight weeks to complete a major design project folio worth 40% of the final mark. By the end of week five she has a detailed needs analysis, three concept sketches, and a beautiful set of CAD renders, but no physical prototype and no test data. Her teacher notes the folio documents what she intends to make far more than what she has learned from making it. The project is a desk organiser made from bent plywood; the brief requires it to hold at least 3 kg and survive a 1 m drop. With three weeks left, she wants to spend two of them perfecting the renders and one week building a single prototype.
1. Critique her plan for the remaining three weeks and propose a revised plan that better satisfies the folio's purpose.
Read the worked answer
Critique: the plan inverts the value of the folio. Renders are low-information artefacts: they show intent, not evidence. With no prototype and no test data at week five, the folio cannot demonstrate the iterative design process the marking criteria reward. Spending two of the last three weeks on renders adds polish to the weakest evidence and leaves no time to act on test results. A single prototype built in the final week cannot be tested, revised, and retested, so it becomes a showpiece rather than a design experiment.
Revised plan:
- Week six: build a quick, low-fidelity prototype (card or thin ply) to check geometry and the 3 kg load path. Test it immediately. Record failures honestly.
- Week seven: build a second prototype informed by the first, using the real bent-plywood process. Test the 3 kg load and the 1 m drop. Photograph and measure. If time allows, make one targeted change and retest.
- Week eight: finalise the folio, presenting the test data, the changes made, and the reasoning. Use existing renders as supporting material, not the centrepiece.
Principle: the folio is a record of decisions and evidence, not a gallery. Two modest prototypes with documented iteration outscore one perfect render.
2. Explain what the folio should contain to demonstrate the design process, and why 'failure' evidence is valuable rather than damaging.
Read the worked answer
What the folio should show:
- The brief and constraints, with the needs analysis linked to specific requirements (3 kg load, 1 m drop).
- Concept development with reasons for rejecting options, not just the chosen one.
- Prototype iterations, each with what was tested, how, and the result.
- Test data: load applied, deflection measured, drop height, outcome, photographs.
- Design changes traced to test findings, showing cause and effect.
- A final evaluation against the brief, including remaining weaknesses.
Why failure evidence is valuable: a prototype that breaks under 3 kg tells the designer where the weak point is. Documenting that and changing the design demonstrates the iterative cycle in action, which is exactly what the process criteria assess. A folio with no failures usually means no real testing occurred, which is a weakness, not a strength. Honest recording of a failed test followed by a reasoned modification shows judgement, and judgement is what distinguishes a strong folio from a decorative one.