Rebuilding trust after a difficult programme.

Trust in a delivery team is not a feeling. It is a record: of decisions made, of commitments kept, of problems named and resolved. Rebuild the record and the trust follows.

After a difficult programme (one that overran, underdelivered, or left the team depleted), trust is usually in one of two states. Either it has been stretched and held, in which case people are still in the room but running on fumes. Or it has broken, in which case people are in the room physically and somewhere else entirely.

The response to both is the same: you cannot rebuild trust by talking about trust. You rebuild it through a sequence of small, kept commitments.

This is uncomfortable because the instinct after a difficult programme is to do the large, visible thing. A team offsite. A new way of working. A statement of intent from leadership. These are not useless, but they are not the work. They are the context for the work.

The work is: what was agreed this week, and did it happen? Who said they would do something, and did they? Where a problem was visible, was it named in the room where it needed to be named?

Each instance of a commitment kept adds to the record. Each instance of a problem named without punishment adds to it. Each decision made and communicated clearly adds to it.

Over time (and it takes time, there is no shortcut), the record becomes the basis for a new operating assumption: this team does what it says. That is trust. It is not a feeling. It is evidence.

Start with the small commitments. Keep them. Let the record build.