{"id":10292,"date":"2022-01-26T09:36:17","date_gmt":"2022-01-26T09:36:17","guid":{"rendered":"https:\/\/ee.yelkdev.site\/?p=10292"},"modified":"2024-04-16T10:43:10","modified_gmt":"2024-04-16T09:43:10","slug":"7-pitfalls-to-avoid-with-you-build-it-you-run-it","status":"publish","type":"post","link":"https:\/\/www.equalexperts.com\/blog\/our-thinking\/7-pitfalls-to-avoid-with-you-build-it-you-run-it\/","title":{"rendered":"7 pitfalls to avoid with You Build It You Run It"},"content":{"rendered":"

You\u2019ve probably heard of <\/span>You Build It You Run It<\/span><\/a>. It\u2019s an operating model that empowers product teams to own every aspect of digital service management. When done well, it accelerates your time to market, increases your service reliability, and grows a learning culture. <\/span><\/p>\n

However, there are some pitfalls. These 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

In our recent <\/span>You Build It You Run It playbook<\/span><\/a>, my co-author Steve Smith and I take a deeper look at these pitfalls, and recommend how to avoid them. We believe you can proactively guard against them, and quickly escape if they do occur.\u00a0<\/span><\/p>\n

In no particular order, the pitfalls are:<\/span><\/p>\n

    \n
  1. Linear run cost<\/span><\/li>\n
  2. Responsible but unaccountable<\/span><\/li>\n
  3. Excessive BAU<\/span><\/li>\n
  4. Change management treacle<\/span><\/li>\n
  5. No major incident management<\/span><\/li>\n
  6. Embedded specialists in product teams<\/span><\/li>\n
  7. Limited on-call schedule<\/span><\/li>\n<\/ol>\n

    Linear Run Cost<\/h2>\n

    If you propose a move from a central operations team to You Build It You Run It, your senior leadership will no doubt worry about a linear run cost at scale. It\u2019s an easy trap to fall into. With central operations, you pay a daily rate for one analyst to be on-call for five digital services. So five on-call product team members for five digital services doesn\u2019t seem to make financial sense, does it? And what if you have 10 teams and 20 digital services, or more? You can see the concern.<\/span><\/p>\n

    To avoid this trap you need to:<\/strong><\/p>\n