Most studios run Instant events back-to-back without writing down what they learned. A 30-minute retro turns a single event into a pattern the team can lean on — and stops the next event from repeating yesterday's pain.
How to do it
Pull the stage numbers in one line: total Imported, Uploaded, AI Edited, Exported, Shared.
Pull guest signal: support tickets, social DMs, on-site asks. Treat them as signal, not noise.
Cross-reference: where did the dashboard look fine but guests still complained? Usually a sharing or notification gap.
Decide one change for the next event of the same kind. One change, not five.
Update the project template inside Instant the same day so the next setup inherits the change automatically.
Try it
On the next branded activation, schedule a 30-minute retro for the same week. Bring the dashboard numbers, the guest feedback, and the one change you propose. Update the Instant template that day, while it is fresh.
Watch out for
Skipping the retro for the next pitch. You will rebuild every setting from scratch next time.
Tracking only technical metrics. A perfect dashboard with frustrated guests is still a failed event.