§ 2 · FIELD NOTES
Notes from teams
who actually run retros.
The blog is on the way. We're collecting facilitator stories, anti-patterns, and the things we've learned building Nudgile. Drop a line if you want to be the first to know when posts go live.
Fig. 2.0— Email signup wires up at GA. Until then, send us a note and we'll add you to the list.
2.AIn draft
The first batch of posts we're working on.
A rough sketch of what's queued. Topics will shift as we hear what teams actually need.
§ 2.A.1
Why your retro is full of stickies but light on action
Facilitation — The most common pattern we see: brainstorm goes great, action follow-through dies. What to change.
§ 2.A.2
When to swap Classic for Sailboat (and back again)
Templates — Different sprints surface different signals. A facilitator's guide to picking the structure that fits.
§ 2.A.3
How we built the Retro Coach
Behind the scenes — What it took to make AI useful inside a retro — and the patterns we threw away getting there.
§ 2.A.4
Five retro habits that quietly kill team trust
Anti-patterns — The micro-decisions facilitators make that determine whether a retro is safe or theatre.
§ 2 — Field notes · In draft
In the meantime, run your next retro on Nudgile.
Free during beta. The blog can wait — your team can't.