Small operating systems

Course · 4 sessions

Build calmer rhythms for a small team that needs to stay close to users and move without a lot of ceremony.

Choose the loops that deserve to be visible

Most small teams need only a few dependable loops: deciding what matters, making the work, learning from users, and closing commitments. Name those loops before choosing a tool.

For each loop, write down:

• The signal that starts it.
• The person who carries it forward.
• The smallest artifact it should produce.
• The moment when it is genuinely complete.

Keep decisions close to the work

A short decision note beside the artifact is more durable than a decision remembered from a meeting. Record the context, choice, and what would cause you to revisit it.

Replace status theatre with useful artifacts

Prefer a working draft, user quote, test result, or changed checklist over a polished status summary. The artifact should help the next person act.

Review before adding

When work feels messy, first remove a stale ritual or unclear handoff. Add another meeting or dashboard only when you can name the decision it improves.