I once took charge of a project whose client had reached the end of their patience with us. Dates had been missed, quality had been poor and the communication they had received had done little to reassure them. They were prepared to end the engagement.
In the first call, they went through every grievance in detail. My instinct was to provide context. I had inherited the situation, and there were reasons behind some of what had happened. But I also knew that another explanation, however accurate, might sound like one more excuse.
So I did not begin with the recovery plan. I acknowledged that we had let them down, without adding a qualification. Then I asked them to take me through the specific pain points and describe what good would look like from their side.
That conversation gave us the basis for a plan they helped shape. We agreed priorities, made realistic commitments and were honest about what would take longer. The plan was important, but it did not restore trust by itself.
Trust returned through what happened afterwards. We did what we had said we would do. When something was at risk, we told the client early. The quality improved, but so did the predictability of the relationship. Over time, they no longer had to wonder what we were not telling them.
The experience left me with a question I still find useful in troubled projects. Are we creating the recovery plan because it addresses what the stakeholder has experienced, or because producing a plan makes us feel that we are back in control?
Both the work and the relationship need attention. A sound schedule can address the first. The second may require acknowledgement, participation and a period of consistent evidence before confidence begins to return.
For those who have led a project recovery, what helped you rebuild stakeholder trust beyond revising the milestones and actions?
