Last week I read a post about holding a decision when someone is disappointed in it. Its picture was water, which goes around whatever is in its way and keeps its direction.
Laozi used the same picture. Nothing is softer than water, and nothing is better at wearing down the hard.
Its distinction is the useful part. Accepting that someone is disappointed is one thing. Agreeing to what they expected of you is another.
I read it as a reviewer. For most of my career I assessed other people’s work and handed the finding back to the person who owned it. Most of those handovers had a moment when someone was disappointed, and what they had expected was nearly always a yes.
Two ways to get it wrong
The first is to treat the disappointment as an argument and dig in on everything. The owner stops listening, and the finding goes nowhere.
The second is to let the disappointment move the finding. You soften it, or leave it out of the summary. Everyone leaves the room happy, and the problem goes to the board unannounced.
Both feel reasonable at the time. The first feels like rigour and the second feels like kindness. Neither gets the finding acted on.
What I gave way on
Almost everything except the substance.
When the business case or board paper was mine, I walked senior managers through each draft, one at a time, and took their difficulties to the general manager while there was still time to deal with them. For board papers, the Chairman read the draft and suggested changes before it went in.
Their questions made the documents better, and their words went into them. It is very hard not to approve a document when your own words are in it.
When the case was someone else’s, I asked the hard questions early, while the draft could still change. The finding at the end was still mine to give.
Sometimes a question exposed something that needed reconsidering. A finding should change when the evidence does. Disappointment isn’t evidence.
The wording moved. The order of the argument moved. Sometimes the reasoning improved. But where the evidence still supported the finding, the finding stayed.
What I didn’t
I didn’t give away a finding simply to secure agreement.
My boss might give a business case a go, and the CEO might too. Then the Chairman and the Board would look at the same investment from a different angle and give it a no-go.
Nobody enjoyed that meeting. The no stood anyway.
I wrote about that chain in Your boss said yes. The board is reading a different case.
What I didn’t write about there is how the no felt to the people at the bottom of the chain. Most had worked hard on that business case for months, and disappointment was sometimes the least of what they felt. Some heard the no as a judgement of them. Others heard it as information about the case, went back to it and rewrote it. That work was theirs.
Early is kinder
The sign I trusted most on any project was simple. Were the key documents written on time, and approved by the people who had to approve them? When they were late, or sat unapproved, something underneath was wrong.
A finding delivered while the document is still a draft costs the owner a rewrite. The same finding delivered at the board can cost them the project.
I spent years as a firefighting project manager, brought in after things had gone wrong, and by then every finding was expensive.
The earliest version of this was sitting beside people while they wrote their first project documents. I found it nearly always worked better than marking up a finished draft.
The template was there to make them think: what is the business problem, and how do you explain it so someone else can decide?
When a question came up that the case couldn’t answer, the writer found it themselves, at the desk, with time to fix it. Nobody had to deliver that finding at all.
So most of the giving way happens early. You sit with the draft, you change the words, you let people put their own thinking into it. You keep the finding in plain sight the whole time, so nobody meets it for the first time in the room where it counts.
The same rule, built in
This week I started building that rule into The Assay, the independent review service I’m developing. It’s on a test version and isn’t live yet.
Before a report goes out, every concern the review raises has to be answered. The person releasing it can accept the suggested wording, edit it, or leave it as it is. Editing it or leaving it needs a reason.
The report as first written is kept. If the check still rates the report not fit, it can be released anyway, but the record shows it went out against the check.
The system has to keep that distinction. A review should be open to challenge, and pressure should leave a mark on the record.
Water gives way to the rock and still reaches the sea. A review can give way on almost everything. The finding is the part it can’t give away.
Source: Laozi, Tao Te Ching, chapter 78.
Want more like this? Rick writes about the go/no-go decision: for the people who assess business cases, and the founders who have to make them.
All writing