Postcards from the Edge of GBS: Why Have an Operating Model?
Add bookmark
We respect your privacy, by clicking "Download Your Copy" you agree to having your details passed onto the sponsor who may promote similar products and services related to your area of interest subject to their privacy policy. You have the right to object. In addition, you will receive our e-newsletter, including information on related online learning opportunities. For further information on how we process and monitor your personal data, and information about your privacy and opt-out rights, click here. Download PDF Attachment
This post starts a third series of postcards from the edge of GBS. I am going to be ambitious and tackle something complex. It’s something that every GBS needs, but not all are clear about, and there are many opinions on what it should look like. I am talking about an agreed and written down operating model.
I have helped design many operating models for GBS organizations. Some of them were effective, others not, and this series explores techniques for building operating models that become the way of working rather than shelf-ware. As before, my focus is on lessons learned from the front line and tools you can use.
Oh, and I am sorry that I took a pause in these postcards at the start of 2024, I have been consulting, working on designing operating models for some GBS organizations which got in the way of finishing this batch of posts! I intend to keep the column going, so please bear with me.
Tim Palmer, Basel, May 2024
