{"id":10296,"date":"2022-02-02T09:10:10","date_gmt":"2022-02-02T09:10:10","guid":{"rendered":"https:\/\/ee.yelkdev.site\/?p=10296"},"modified":"2024-03-28T13:54:04","modified_gmt":"2024-03-28T13:54:04","slug":"5-ways-to-minimise-your-run-costs-with-you-build-it-you-run-it","status":"publish","type":"post","link":"https:\/\/www.equalexperts.com\/blog\/our-thinking\/5-ways-to-minimise-your-run-costs-with-you-build-it-you-run-it\/","title":{"rendered":"5 ways to minimise your run costs with You Build It You Run It"},"content":{"rendered":"

You\u2019ve probably heard of <\/span>You Build It You Run It<\/span><\/a> before. It\u2019s an operating model that empowers product teams to own every aspect of digital service management. <\/span><\/p>\n

When done well, it accelerates your time to market, increases your service reliability, and grows a learning culture. There are also some pitfalls, which can drain the confidence of your senior leadership, and ultimately put the success of You Build It You Run It at risk.<\/span><\/p>\n

Today I would like to focus on one of the pitfalls that often stops projects from getting off the ground. The <\/span>run cost pitfall<\/span><\/a>. This is part of our recent <\/span>You Build It You Run It playbook<\/span><\/a>, we take a deeper look at the risk of on-call costs becoming uncontrollable, and how y<\/span>ou can guard against it, and even escape it.<\/span><\/p>\n

If you\u2019re in a hurry, our ways to minimise run costs are:<\/span><\/p>\n

    \n
  1. Understand an operating model is multi-cost insurance for business outcomes<\/span><\/li>\n
  2. Make product team budget holders accountable for business outcomes<\/span><\/li>\n
  3. Fund on-call costs from product team budgets<\/span><\/li>\n
  4. Select availability targets on financial exposure<\/span><\/li>\n
  5. Select out of hours schedules on financial exposure<\/span><\/li>\n<\/ol>\n

    The run cost pitfall<\/h2>\n

    If you work in a large enterprise organisation, you\u2019re probably familiar with the traditional IT operating model. You\u2019ll have a multi-level support hierarchy, with an L1 operations bridge team for monitoring, and an L2 application support team for incident response. Each day, an application support analyst is on-call out of hours.\u00a0\u00a0<\/span><\/p>\n

    The names of these teams change, but the operating model doesn\u2019t. It\u2019s so ubiquitous, it doesn\u2019t really have a name of its own! In our playbook, we call it <\/span>Ops Run It<\/span><\/a>.\u00a0<\/span><\/p>\n\"\"\n

    This operating model has a clear benefit in run cost management, due to:<\/span><\/p>\n