Decide Whether the Result Is Done

I was sitting in a Netrix sales review on Park Avenue in New York, looking at a dashboard that could not tell me what we had committed to do next week. Over thirty metrics on it. Bookings, revenue, deal status, every opportunity color coded red, green, or yellow. A dashboard is what you look at while you drive. This one told us where the car had been and where it was sitting. It did not tell us what we had to do to move.

Every week the reviews returned to explanations. Someone in marketing did not deliver. Someone in technology is still working on their piece. The prospect went quiet. Much of that context mattered. But we kept ending reviews without an owner, a next step, or a date. A rep carrying 20 active deals and 50 more in the pipeline cannot hold every next step in memory. That is not a lack of desire. It is a gap in practice and process. The dashboard changed when every meaningful opportunity gained three fields: a next customer step, an owner, and a due date. Follow-up moved from a rep's memory to the record. Explanations now led to commitments someone could follow up on.

The same gap at OVH cost us customers. The promise I remember making was direct: don't go to AWS, Azure, or Google. Stay with us, and we'll migrate you to a new data center in three months. Three months passed. Then another three. Then another. The migration process did not end until December 2019. Along the way, internal milestones were closing. Construction progressed while customer migration dates slipped. Every week, the teams reported their activity without showing which customer commitments they had completed. Many customers did not wait. They migrated out, and that result only became visible in the rearview mirror. When OVH's founder took control of the data center builds, the customer commitment stayed with us; control of the work did not. When authority over a dependency changes, reopen the affected commitment immediately. Keeping the old date requires evidence that the new arrangement can still deliver it.

Boeing shows the same gap at a scale where the cost was measured in lives. Lion Air Flight 610 crashed on October 29, 2018. Ethiopian Airlines Flight 302 crashed on March 10, 2019. 346 people died. The aircraft had been certified. Safe performance was not assured. The House Transportation Committee report in September 2020 identified production pressure, faulty technical assumptions, withheld information, and failures in FAA oversight. A signoff records an approval. It does not replace the evidence behind that approval. Done is the system outcome demonstrated under the conditions it has to meet. The operating question is who tests the interaction between the parts. When a design or an operating assumption changes, the review has to cover the changed conditions before the approval carries forward. Who can stop release when the evidence does not support it?

Back in our data center, the distinction between components and the whole still applied. We could build racks. We could turn on electricity. If the cooling system was not ready, we could not deliver. Component completion was not enough. Done meant a service the customer could use at the promised level.

Four views of one review, not four meetings. The Done Test defines completion from the customer backward. The Forward Commitment Dashboard pairs the lagging result with the next observable commitment. The Outcome Closure Agenda runs every review. The System Outcome Verification Gate tests the seams, where a result can fail between departments. For example, a sales review might record that the account lead and sales engineer will demonstrate the customer's agreed recovery scenario on Thursday. Done means the customer's technical owner confirms that the test met the agreed requirements and records any gaps. Sending the invitation or finishing the demonstration does not provide that evidence.

If you run the review, start with the commitment already in the record: what happened, what evidence establishes completion, and what remains for the customer to decide. End it with a next step, an owner, a date, and the evidence that will establish completion on every material item, and name who accepts that evidence. Keep activity, acceptance, and outcome visible as three separate things. If you manage a team that calls work done, ask what the customer can now do and who besides the builders says so. If you are the person whose head holds the next step on every deal or project, write those details beside your own work where a colleague can act, and confirm the acceptance conditions with the person who depends on it. Documentation is not a judgment of your contribution. It is the system that lets the team honor that contribution and keep serving the customer when you are not there.

Done on paper is not done in reality.