I’m in the process of developing and formalizing the Risk Appetite Statement (RAS) for my organization, a public transport operator. Before we bring the draft to the Board, I’d appreciate your views on the best approach for engaging the Senior Leadership Team (SLT): Is 1:1 engagement more effective to gather candid input? Or would a group workshop be better to align perspectives and drive collective ownership? If anyone has experience developing a RAS specifically for a public transport or infrastructure-focused entity, I’d love to hear your lessons learned or key considerations. Appreciate any tips or tools!
Sort by:
Chief Information Officer in IT Servicesa month ago
I have not developed RAS for a transport operator, but for other industries like Banking, Services. Best approach to get what you want from SLT is a 1:1 engagement only. Once the inputs are in, then the driving force can be from the key leadership to the specific set of audience, in a workshop.
Developing a RAS(es) can be a tough gig. Taking a leaf out of Human Centred Design (HCD) approaches, I'd suggest 1-on-1 engagement is gold. Really taking the time to tease out the SLT's individual needs and how a RAS might address the same... until you gather that understanding you run a real risk of an otherwise great solution tackling the wrong problem.