A Wing Commander I worked for at an RAAF flight test unit took me flying in Macchi jets. He flew each manoeuvre himself first. While he did, he wanted me to gently hold the controls.

“No force, just feel what was happening through the stick.”

Then he handed over the controls.

Now I was flying, but his hand remained lightly on the stick. Just as I’d felt his inputs, he could feel mine. He was there to take back control if I needed it.

It was a gradual transfer of responsibility, with someone experienced still beside me.

The same handover, years later

As an IT contractor, I set up the project management method for an organisation. Writing the method was the smaller job. What mattered was whether the organisation would still use it once I’d gone.

So I sat beside the people who would run it and helped them prepare their first documents. They did the work, made the decisions and learned why things needed to be done a particular way. I was there to guide them, question their reasoning and intervene when necessary.

Just as the Wing Commander had done, I kept my hand lightly on the controls while they learned to fly.

I’ve always believed it’s better to help people prepare their first documents rather than simply give them a template and instructions.

While we worked, we could talk about why something needed to be done a particular way. What was the business problem? What information mattered? What would someone else need to know to make a decision?

A template is a way of getting people to think. It should help them understand the business problem more fully and explain it clearly enough for others to make informed decisions.

A template is a way of getting people to think.

The method stuck. It became part of how the organisation worked because the people responsible for using it understood the process and made it their own.

The credit for that belongs to them.

A method only survives its author if the people left behind can run it.

Knowing when to let go

Good judgement includes knowing when to hand responsibility to someone else and making sure they can exercise it.

Both halves matter.

Hand over too early, without support, and the person is flying an aircraft they haven’t yet felt.

Hold on too long and nobody learns to fly at all. The organisation remains dependent on whoever happens to be in the room.

I’ve seen the same in projects and organisations. A method can appear to be working beautifully while its author is there to explain it, interpret it and resolve every uncertainty.

The real test comes after that person leaves.

What a reviewer can ask

When reviewing a project, a method or a plan that’s changing hands, the handover itself is worth examining.

Who wrote the documents: the people who will run the work, or the person who is leaving?

Did the people taking over have time with their hands on the controls while someone experienced was still beside them?

Do they understand why they’re doing things, or have they simply learned to follow instructions?

If the author left tomorrow, who could carry on?

A handover that happens on the last day is a hope.

The Wing Commander let me fly while keeping his hand lightly on the stick, ready to intervene if necessary.

Responsibility should transfer before support is withdrawn.

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