A flight trial doesn’t wait for a purchase order.
In the early 1980s, I worked in supply at the RAAF’s Aircraft Research and Development Unit, on one project: the F-111 flight-test programme.
The engineers needed things that weren’t in any catalogue, and the normal procurement system was often too slow.
My job was to get them what they needed, when they needed it. Through the normal system where it worked. By another authorised route where it didn’t.
The limit was the useful part
I had delegated purchasing limits. Above them sat the Wing Commander’s authority, and above that the CO’s.
It would be easy to see those limits as the obstacle. They were the part that made the job work. Inside them, I could move quickly without asking anyone. At the edge of them, I knew exactly whose decision it became.
Knowing where your authority ends tells you when to take the decision upward, and to whom.
Seeing the stall early
I also built a system that tracked each request from the engineers’ first ask to delivery. Its real value was that a stalled order showed early.
Seen early, there was time to find out why. I could talk to the supplier here in Australia and understand what the supply constraint was. Then I could either work with them, or contact suppliers in America through the normal channels and see whether they had stock that wasn’t seen in Australia.
The earlier I knew there was a problem, the more options I had to resolve it.
The same pattern, years later
When I was brought in to rescue projects, I often found a meeting of ten people where nobody in the room could decide.
On one, I replaced it with a steering committee of three: the IT assistant secretary, the business area’s director and me. Between us we had the authority to deal with issues as they came up.
We also set up an issues process, so each issue was identified quickly, given an owner and managed through to a resolution.
The committee wasn’t smaller for the sake of it. It put the decision at the level that could actually make it.
Still my responsibility
Just because a decision was outside my authority didn’t mean I was no longer responsible for managing the issue.
My responsibility was to identify who had the authority to make the decision and ensure they had the information they needed to make it.
In both environments, the ability to see a problem early was coupled with the authority to act.
Visibility without authority produces a report. Visibility that reaches authority produces a decision.
What a reviewer can ask
When a business case, a plan or a project report reaches you:
Whose decision is this, really?
Is it within the authority of the people who appear to have made it?
When something stalled, how early did it show, and did anyone find out why?
When it did reach you, did it come with enough to decide?
Good management is knowing what you can decide, recognising early what you cannot, and ensuring the decision is made at the right level.
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