Accountability circles: review a build and leave with owned work

An accountability circle needs something its members can inspect. A build, a changed asset in the game, or a failed check is a better starting point than a percentage-complete report.

Clowdr requires weekly project updates and scoped, owned contributions. This circle format applies those requirements to a small recurring review. It is an operating model, not a report of successful Clowdr cohorts.

Give each commitment an owner and an artifact

Start with three to six people. Each person brings one owned area of work and one commitment for the next review. Contributors still agree task scope, handoff, and timing with the Project Lead. A circle helps expose problems; it cannot approve a Project or replace the Lead.

Write the commitment so another person can check it: “The controller can restart the approved encounter without losing input focus” gives the group a behavior to inspect. “Work on combat” does not.

Keep commitments within the current production gate. During the Slice Phase, only work needed to build, integrate, and evaluate the Vertical Slice is claimable. Encouragement from a circle does not open the wider roadmap.

Run a 45-minute review with four columns

Use one shared agenda with four columns: last commitment, evidence, blocker, next commitment. Before the call, link the build or artifact and record what actually changed.

During the call:

1. Check each previous commitment against its artifact. Record incomplete work plainly.
2. Show the change in context. For a build, demonstrate the behavior the task promised.
3. Identify the blocker and the person who can resolve it. If scope or rights are unclear, take that decision back to the Lead.
4. Agree the next small commitment and its handoff. Keep longer craft discussions outside the review.

A missed commitment calls for a useful adjustment. Reduce the work, ask for help, or communicate with the Lead before unclaiming it. Do not turn the meeting into a defense of time spent.

Review the format after four weeks

Look back at the agenda. Which commitments produced inspectable changes? Which blockers repeated? Did review time displace integration work? Change the cadence or group size based on those observations.

Keep local notes about what changed and why. A later Field Note can report that evidence with its project context and limits. Until then, this format makes no claim about completion rates.

Use How We Ship for the production gates and the Friday build review for a repeatable demo format. Publication still depends on the complete game and the Five Proofs of Release.