Transparency Is Not Delivery
I committed a fixed block of consulting days to a client for the month. I delivered roughly a tenth of them.
I committed a fixed block of consulting days to a client for the month. I delivered roughly a tenth of them.
When I finally sat down to reckon with it, I wrote the client's operations lead and finance contact an email that said exactly that: here is what I promised, here is what I actually delivered, I am not billing you for this month, and here is the week-by-week plan to recover. Playbook first, then the systems kickoff, then an execution review.
Sending that email felt like closure. It was not.
What the email was good for
It was genuinely the right call, and I would send it again. Self-reporting a miss before the client discovers it converts a trust problem into a trust asset. Waiving the month's billing made the apology cost something, which is what separates an apology from an excuse. A client who watches you absorb the cost of your own failure learns something about you that no case study conveys.
So: the communication worked.
What the email did nothing about
It did not touch the reason the gap existed.
The gap existed because I had promised capacity I had already spent. I was building my own products with the same hours I had sold. No amount of honest reporting changes the arithmetic of a calendar. I could write that email every month, with perfect candour each time, and the client would still be receiving a tenth of what they were promised.
This is the trap: honest communication about failure feels so much like fixing the failure that it can substitute for it. It produces the emotional relief of resolution — the difficult thing was said, the discomfort was faced — without producing any change in the underlying system. And because transparency is genuinely a virtue, it's very hard to notice you're using it as a substitute rather than a supplement.
I could see the same pattern elsewhere in my own week, in a different costume. Six consecutive days of writing down that a set of compliance and receivables tasks were overdue. Six days of accurate, unflinching self-assessment. Zero days of actually doing them. The record-keeping was immaculate. The record was of nothing happening.
The test I use now
After any honest admission of a miss, one question: what changed in the system, not in the conversation?
If the only thing that changed is that the other party now knows, I haven't fixed anything — I've just distributed the knowledge of the problem more widely. For an over-commitment, the system change is a lower committed number next time, not a better email this time. For a repeated overdue task, the system change is a hard close mechanism — someone else's deadline, a booked call, an irreversible step — not another calendar block that will be honestly reported as missed.
Transparency is necessary. It's just not sufficient, and it's dangerous precisely because it feels like it is.