The Publican’s Risk Appetite
Bryan Whitefield
I empower leaders to cultivate high-performance teams making faster and better decisions | Recognised expert in strategy and risk | Expert facilitator and trainer and sought-after mentor | MAICD, MRMIA & CCRO
I was “up the coast” this summer. A term well understood for those who live in Sydney and covers anywhere from the Central Coast to the Queensland border. As with most holidays you get a good story or three. One of mine is the quintessential Aussie story as well as a wonderful depiction of why leaders in organisations need to know staff are operating within the bounds of the leadership team’s appetite for risk.
My friend (let’s call him Mike) and I were walking towards a pub. A few people were taking interest in an old Valiant (an Aussie made car by Chrysler until 1981) outside the pub. Soon Mike and I were looking at a snake poking its head out from under the wheel well on the back left of the car. Mike decided to take a closer look and I was ready with the camera in case I was able to capture a spectacular moment.
(Un)Fortunately nothing happened to my friend and we went inside for a beer. A while later I heard a patron speaking to the publican.?
Patron: ”Did you hear Frankie from up whoop whoop way came into town with a python wrapped up in his wheel well?”?
Publican: “You don’t say.”?
Patron: “Yeh. Bazza grabbed it and has let it out back in the bushes.”?
Publican: “Where in the bushes?”?
Patron: “In the beer garden.” (A beer garden is an outside area for food and drinks at an Aussie pub).?
领英推荐
Publican: “You can’t let a bloody snake loose in the beer garden! It’s irresponsible!”?
Mike and I had to get moving. I ducked around the corner to a shop while he headed to the car. By the time I met him in the car he was laughing his head off. Apparently, the publican had just walked past with the snake in a pillow case. My friend explained what had transpired.
The publican had gone and found Bazza. Called him irresponsible along with a few other names. And Bazza had then done the right thing (as far as he was concerned) and grabbed the snake and put it in the pillow case. Presumably the Publican called the wildlife rescue service for the safe relocation of the snake. As they walk past Mike’s car he hears:?
Bazza: “Well I got the snake for you. How about a free beer!”?
Publican: “A free beer? No way. You’re bloody-well irresponsible!”?
My take-away from this story for you is that depending on our?personal biases that stem from our VEG (values, environment and genes)?we all have different perceptions of risk. Obviously Bazza thought nothing of dealing with a python while the publican knew that people in the beer garden would more than likely freak out if they saw a snake. Even if the snake was relatively harmless (pythons are non-venomous and very rarely attack humans as they swallow their prey whole).?
Given we all have different perceptions of risk, as leaders in organisations it is an imperative that staff know your tolerances for risk taking. Just ask the leaders of the Finance Sector Royal Commission here in Australia.
You can read more on my thoughts on?Risk Appetite in this paper?and if you are interested in having a conversation on how to bring value to an organisation through a risk appetite statement, please reach out to me by replying here or email me on?[email protected]. I’d love to chat!
Ensuring risk management adds value to your business
1 年Bryan, An interesting paper - but I suspect the application of a risk appetite statement is quite problematic. Indeed I query its value althogether as there are too many variables involved. Here is a link to a video that discusses "non-essential" items. The first addressed in the video is Risk Appetite. Although this is project focussed it applies to any initiative where someone is trying to manage the risks that may affect their particular objective. https://www.risktools.com.au/non-essential-data/ In addition to what is in the video on appetite there is also the question of how an appetite statement is used at different management levels each of whom may be undertaking an initiative. (For example how does a high level appetite statement apply (and help) a programme v project v sub-project.) My view that as risk professionals we are in danger of making risk management much too complicated. Risk management fails due to two aspects - risks are not identified or treatments are not undertaken. I suggest once we have systems that address those two key failings it may then be appropriate to look at whether items such as risk appetite really add value.