Deliver outcomes, not output
The unit of work is a delivery, a change with an outcome a person asked for. It is not a message, a session or a pull request.
At Blume, we count work in outcomes. An outcome is a sentence about the product that a person can check: “A person refunds an order from its page, fully or in part.” Messages, commits and pull requests are output. Output is how the work gets done. It is not what you asked for.
What goes wrong without it
Counting output
You ask an agent to add refunds. Two days later there are three conversations, two pull requests and about four hundred messages.
Are refunds done? The pull requests say “payment call merged” and “checks passing”, and both can be true while a customer still cannot refund an order. You are the only place where the whole change exists.
One delivery
One delivery, “Refund an order from its page”, holds the outcome, the checks, the tasks that are left, the conversations, both pull requests and the evidence.
Asked if refunds are done, it answers: in the merge review, one pull request merged, one waiting for you, release not started.
What to do
- Name the work by its outcome. “Customers can check out with a saved address”, not “Address work”.
- One delivery per outcome. A follow-up continues the same delivery. A different outcome gets its own.
- Do not confuse a part with the whole. A merged pull request is a step. The delivery is done when the outcome is live and checked.
- Let output be disposable. Conversations end and branches get rebased. The delivery stays.
In Blume
- The app lists deliveries, each with its outcome, its phase and what is left.
- The plugin has the agent resume an existing delivery with the same outcome.
- A delivery links every agent conversation and pull request, and ends in Release and Done.