Blockers, Risks, and Keeping Projects Honest

Projects rarely die of surprise. They die of things everyone half-knew: the blocker nobody wrote down, the risk nobody owned, the decision nobody made, the drift nobody measured. The hub runs the four honesty habits that prevent this - automatically, and in plain language.

Name the blocker while everyone is calm

When a task cannot move, it gets a Blocked By link (what it waits on) and a Blocker Note in plain words ("waiting on ASADA letter", "needs Ky's sign-off on the quote"). Written calmly at the moment of blocking, it is information; reconstructed three weeks later in a tense meeting, it is an argument. The Blocked & Waiting view is the daily unblocking list - the shortest route to momentum is usually there, not in starting something new.

Gate work on real decisions

Some work must not start until something is genuinely decided - a legal structure, a budget approval, a consent process. Linking the task as Gated By that decision does two kind things at once: it stops eager work from jumping the gun, and it makes visible that the delay is institutional, not personal. When the decision lands, the gate opens and the work shows up ready.

Keep a live list of what could go wrong

A Risk is a record: what could happen, how bad (severity), who is watching it (owner). Sera extracts risks from your meetings automatically - when someone says "my worry is the well permit slips past September", that worry becomes a record instead of evaporating. Reviewing the risk list occasionally is how projects fail politely - small, early, and cheaply - instead of catastrophically. The regenerative addition: for each risk, ask who is affected and whether they know. Care is a risk control.

Let the rhythm tell the truth

The weekly project status email reports each project's position - budget line, blocked work, movement - straight from the records. Nobody compiles it, so nobody polishes it. Drift shows up while it is still a conversation, not a crisis.

For the standards-minded

If a funder or partner asks: these four habits are the RAID discipline (Risks, Actions, Issues, Decisions) that ISO-style project governance expects, plus a standing status cadence. The hub maintains all of it as a side effect of your normal meetings and email. That is the honest pitch: internationally standard project governance, practiced automatically.

Key points

A blocked task carries who or what it waits on (Blocked By + a plain Blocker Note) - the Blocked & Waiting view is the daily unblocking list. Work that must not proceed before a decision is Gated By that decision, which prevents both jumping the gun and blaming individuals for institutional slowness. Risks are records with a severity and an owner - naming what could go wrong is how projects fail politely instead of catastrophically, and Sera extracts risks from meetings automatically. The weekly status email is the honesty rhythm: position against budget, blocked work, and drift, reported from records rather than optimism. Together these are the RAID discipline (Risks, Actions, Issues, Decisions) that international standards expect - running without anyone maintaining it.