FADA1010 Chap.6 Process Journals and Reflective Practice
Process Journals and Reflective Practice
A process journal becomes assessment evidence when it connects research, sketches, models, feedback and experiments to decisions. This chapter turns description into reflection through an evidence, interpretation, evaluation and action sequence.
It also shows how specific journal moments can support a concise reflective statement about skills growth, project management, collaboration, challenges and future design practice.
What this chapter covers
- 01
Dated and labelled process evidence
- 02
Purpose and result for each test
- 03
Observation, interpretation and action
- 04
Keeping failed work and unresolved questions
- 05
Skills growth and project management
- 06
Specific reflection on collaboration
Worked example · free
Upgrade a descriptive journal sentence
- 1Name the observed failure and the condition in which it occurred.
- 1Interpret what the failure reveals about material, geometry or intention.
- 1State the controlled next change and the evidence it should collect.
Key terms
- Process Journal
- A working record of the research, making, feedback and decisions that develop a design.
- Reflection
- Serious consideration of experience used to interpret learning and guide future action.
- Evidence Chain
- A documented link from an event or observation through interpretation to a design decision.
- Annotation
- A concise note that explains the purpose, result or significance of visual process evidence.
Process Journals and Reflective Practice FAQ
Is a process journal a portfolio?
No. It should be legible, but its primary role is to show investigation and development, including uncertainty and failed attempts. A portfolio selects resolved work, while a process journal preserves the evidence and reasoning that led there.
How can reflection avoid becoming descriptive?
Choose a specific event, identify evidence, explain why it mattered, evaluate what it reveals about your practice and state a future action. Words such as because and therefore help only when the causal relationship is supported.
How should collaboration appear in reflection?
Name the feedback, group activity or shared process, then show the decision it affected and what you learned. If advice was declined, explain why. Generic claims that collaboration was helpful do not demonstrate its impact.
Assessment move
Record work during the project rather than reconstructing it near submission. Date entries and label purpose, material, scale and conditions where relevant. After a test, write what happened, what it suggests and the next action. Photograph transient models and include unsuccessful attempts that produced learning.
Every few weeks, tag important moments under concept, iteration, execution, skills, project management, collaboration and future practice. These tags become a bank of specific evidence for the final reflective statement. When drafting, build paragraphs around contrasting moments rather than answering template questions mechanically. Include success and difficulty, and avoid turning every setback into a neat victory.
Proofread each claim by asking where the evidence appears in the journal. A clear causal chain makes reflection credible and also helps tutors see the development that a final outcome alone cannot communicate. Use the journal as an active decision instrument during studio, not a scrapbook completed afterward.
Open each work session with the question or risk being addressed, then capture enough process to reconstruct what happened. A useful entry includes the starting version, changed variable, observation and decision. Material names, dimensions, file versions and fabrication settings matter when they explain why a result changed.
Photograph fragile or temporary constructions immediately, with a scale cue and more than one view when spatial relationships are important. Distinguish evidence from retrospective interpretation through layout or labels. A photograph can show buckling; the claim that thickness caused it remains a hypothesis until comparison supports it. Beside an unexpected outcome, list other plausible causes and define a follow-up test.
This honesty makes the journal more persuasive because it reveals judgment rather than certainty performed after the event. Include failures selectively: keep the attempt when it changed understanding, challenged an assumption or redirected effort, and explain the consequence. A weekly review can convert raw entries into a navigable evidence bank.
Mark turning points, connect feedback to the affected version and link repeated problems across pages. Use tags consistently, but do not allow categories to replace explanation. Under collaboration, state what another person observed and how you responded. Under project management, compare the plan with what occurred and identify the effect on scope or quality.
Under skills, name the procedure learned and where it expanded or limited design choice. Draft the final reflection from specific contrasts. Pair an early assumption with later evidence, a weak iteration with the decision it provoked, or an optimistic schedule with the adjustment that followed. Analyse why the change mattered to your practice rather than narrating every week.
A balanced reflection can acknowledge a limitation that remains unresolved and state what a credible next step would be. Before submission, conduct a claim audit: underline each assertion about learning, locate the journal evidence and remove or qualify statements that rely only on memory. Then check chronology, image captions, attribution and legibility.
The final journal should let another reader follow how evidence, critique and making altered your decisions without needing a verbal reconstruction.
