Studio culture & creative process / DIJION
Small-studio retrospectives: turning discussion into action
An improvement plan connecting concrete events to small experiments, with ownership, review dates and outcome notes.
After a release, Improve communication is a reasonable intention but does not explain what should happen next week. In an illustrative small studio, a missing error state may have been discovered late. A retrospective should examine the working conditions behind the event and choose a small change rather than assigning personal blame.
Start from a concrete event
Record what happened, when it was discovered and which work was affected. Separate the sequence from interpretations. Replace Design is always late with the specific decision missing at a particular stage. Do not force conflicting accounts into an artificial shared story; uncertain parts can remain questions for investigation.
Examine conditions and feedback paths
Scroll the table horizontally to see all columns.
| Layer | Question | Possible output |
|---|---|---|
| Event | Which state was missing? | Concrete example |
| Condition | Why was it not visible earlier? | A review gap |
| Experiment | What changes in the next task? | A small review step |
Check that one action is practical
Adding a separate process for every problem can burden the team. Choose a small, plausible experiment; the example might add empty and error states to the handoff note. Define an owner, the first task where it will be used and a review point. Everyone should pay attention is not ownership; reduce scope when capacity is insufficient.
Separate completing an action from its usefulness
A checklist may exist without being used. At review, ask whether behavior changed and whether the action introduced new burden. One release without the problem does not establish definitive success. Record the evidence and limits behind keeping, changing or removing the practice rather than accumulating completed actions indefinitely.
Close with a follow-up note
- Separate the selected event from unexamined explanations.
- Define an owner, scope and review date for one action.
- Check whether it was actually applied in the next task.
- Preserve the outcome and continuation decision in a short record.
This is a working template, not an account of an actual Dijion team meeting. A useful retrospective leaves a traceable, revisitable improvement rather than a longer wish list.