Prefer a note over a block

Show what is missing and let the work continue. Stop only at the step a person must decide.

At Blume, we would rather tell you what is missing than refuse to move. A process that blocks at every gap trains people and agents to work around it. Then the record no longer shows what happened.

What goes wrong with blocks

Block and wait

You are in a meeting. An agent asks which of two labels a button should have, and waits. It has a sensible default, and it sits idle for two hours.

Elsewhere, a “changes requested” from an automated review on a replaced commit stops another piece of work. Neither block protected anything.

Note and go on

The agent asks the label question, marks its recommendation and builds with the recommended label. Your answer two hours later arrives as a correction, a one-line change.

The stale review is shown beside the pull request for you to judge. The delivery says in plain words what has no go-ahead yet.

What to do

  • Ask without stopping. A question blocks only when the agent cannot go on without the answer. Otherwise it states its assumption and continues.
  • Say what is missing where the decision is made. “Approving goes past: 1 check not run” is more useful than a disabled button.
  • Record what was skipped. A noted skip can be reviewed later.
  • Block only what a person must decide. Merging and releasing wait, when your team says they should.

The test for any block: does it protect a decision that belongs to a person? If not, it should be a note.

In Blume

  • Requests carry a recommended answer and say whether they block.
  • With optional review, work goes on and Blume says what has no go-ahead yet. With required review, agents pause before merging or releasing. See reviews and plan review.
  • Moving a phase is never refused for a skipped step. See Phases follow reality.