Welcome to yet another Ops Stories roundtable. Every now and then, we put our heads together to dive into an operational topic presented to us by one of our community members.
The format is simple and informal - the host presents the topic and shares a couple of questions, we split into small groups (3-5 people), and then we discuss. At the end of the session, we bring our learnings together so we can share them with the wider community.
We’ll be talking about how to (or if to?) future-proof operations.
As operations leaders, should we build for the now or for the future? Should we be building for and investing our budget into challenges which we don't yet have but might, or should we just "wait and see"? What does future-proofing mean, and within our operations context, is it desirable and is it possible?
"The Future of Proof" - what is a successful "future proof", and have we failed if we have to change later?
Why does everyone else run like clockwork and I feel like I'm playing whack-a-mole?
In the words of Michael Caine: "calm on the surface, but always paddling like the dickens underneath". Is future-proofing possible and desirable?
8:10 - 8:15 am - "arrive" online
8:15 - 8:25 am - kicking off with topic introduction
8:25 - 9:10 am - discussion in small groups
9:10 - 9:30 pm - regroup and align on session outputs
See you soon! ❤️