Let the prototype be wrong in public
Early play sessions work best when teams protect observations from quick explanations. A useful test reveals the gap before it reveals the fix.
Offer a field note →Studio notes / practice
The working day is where the game changes.
Observations on the habits, limits and conversations that make a studio resilient enough to keep asking better questions.
Working principles
Keep the signal close to the work.
Every note begins with a simple question: what did this team make easier to notice? The answer can be a test habit, a tool constraint, or a clear shared language.
A boundary can become a design language
Constraints shape more than production. They can help a game find its rhythm, keep its attention clear and honour the work that is actually possible.
Offer a field note →Make room for the unfinished thought
Teams need language for ideas that are not ready to prove themselves. Naming uncertainty can make critique less defensive and more precise.
Offer a field note →Desk study / loose systems
For local practice
A note is more useful when it can travel.
If you are organising a thoughtful public conversation about games in New Zealand, tell us where it is taking shape. We review each message as an editorial lead, not an automated listing.
Send a local lead