DDES9010 Chap.6 Documenting and Communicating Design Development
Documenting and Communicating Design Development
The visual diary and the final presentation have connected but distinct roles. The diary retains research, sketches, notation, photographs, experiments, abandoned ideas, feedback and reflection while work is developing. The submission curates that evidence into a professional sequence that communicates source, analysis, alternatives, selection and resolution.
Documentation should happen during making.
Date stages, capture several viewpoints and attach a short decision note to each important test. In presentation, give each page one communicative job and use captions that explain action and consequence.
A reviewer should be able to point from a resolved feature back to the observation and experiment that justified it.
The Task 1 rubric rewards visual research and analysis, originality and creative development, demonstrated skills and collaborative practice. These qualities are best communicated through visible evidence, not through claims that the work is original, researched or collaborative.
What this chapter covers
- 01
Visual diary as process evidence
- 02
Presentation as design argument
- 03
Source, test, feedback and decision links
- 04
Page purpose and information hierarchy
- 05
Decision captions and relational verbs
- 06
Rubric criteria as evidence questions
- 07
PDF quality and technical inspection
- 08
Reflection through changed judgment
Worked example · free
Planning a six-page reinterpretation sequence
- 1Open with the observed source, context and question, then pair photographs with a diagram of the selected relation.
- 1Compare several model trials under the same viewpoint and identify the relational consequence of each change.
- 1Show feedback beside the revision it caused, then state why one direction was selected over the strongest alternative.
- 1Close with the resolved model, scale, several views and a reflection that names how evidence changed the initial assumption.
Key terms
- Process evidence
- Dated visual and written material that shows how research, experiments, feedback and decisions changed a design.
- Decision caption
- A concise note that states what changed, why it changed and what consequence the test revealed.
- Presentation hierarchy
- The ranked arrangement of titles, images, captions and spacing that controls reading order and emphasis.
- Silent critique
- A review in which another reader follows the document without spoken explanation to test clarity and traceability.
- Reflective statement
- An account of how observation, testing or feedback changed judgment and influenced the resolved work.
- Submission trace
- A backward path from a resolved feature to its source observation, alternatives, comparison and selection reason.
Documenting and Communicating Design Development FAQ
How is a visual diary different from a final PDF?
The diary is expansive and records work while it happens, including uncertainty and abandoned directions. The final PDF is selective and controls hierarchy, sequence and scale for a reader. It should preserve enough process evidence to make decisions traceable without reproducing every diary page.
What makes a useful caption?
A useful caption identifies an action and its consequence. It tells the reader what to inspect and why the image matters to development. Replace labels that only name objects with statements about widening, aligning, compressing, separating, strengthening or weakening a relation.
How do I show response to feedback?
Place the relevant feedback beside the version it concerns, then show the specific revision and its result. Do not include names or unrelated discussion. The evidence should make clear what was considered, what changed and whether the change strengthened the design relation.
What should a reflection discuss?
Describe an initial assumption, the evidence that challenged it, the decision that followed and the effect on the work. Avoid a chronology of activities or a list of tools. Reflection is valuable when it shows learning through changed design judgment.
How should I inspect an exported submission?
Open the actual PDF at normal viewing size. Check page order, image sharpness, caption legibility, margins, colour contrast, scale labels and cropped context. Confirm that the live task requirements are met and verify the uploaded file and receipt rather than relying on the authoring file.
How can I use the rubric without making the document mechanical?
Turn each criterion into an evidence question. Ask where independent research is visible, which alternatives demonstrate experimentation, how weekly skills appear in the resolved work and where feedback changed a decision. Let the page sequence answer those questions instead of writing unsupported claims.
Assessment move
Treat documentation as part of making. Photograph stages before they disappear, date key pages and use short action-based notes while decisions are fresh. Once a week, pair source evidence with the experiments it prompted and place feedback beside the revision it caused. For presentation practice, give every page one job and conduct a silent critique with another reader.
Ask them to point to the question, relation, alternatives, selection and outcome. Repair missing links with genuine evidence rather than retrospective claims. Before submission, trace three resolved features backward, read captions aloud, inspect the exported PDF on another device and confirm the live Moodle conditions.
Finish by removing repetition while preserving the decisive fork that explains why the chosen direction survived. Use a final criterion map privately, but remove any page that only repeats rubric language. The submitted sequence should communicate evidence and judgment directly, not announce qualities that a reviewer must still search for.
Ask a peer to locate each claim without verbal help and revise any page whose evidence remains hidden.
