BizOps and you
summary
Argues that business units join DevOps processes to reduce costly surprises, with concrete examples: a Subversion-to-GitLab migration because GitHub violates customer legal constraints, a marketing CSS tweak that produces a 2.6% revenue lift in 24 hours, and a “bug” in a finance report that isn’t a bug but required running both reports for months. Recommends monitoring revenue and visitor metrics alongside APM, inviting business to post-mortems and planning, and using that context to change SLOs and prioritization.
AI-written summary · about
chapters (19)
- 0:00Start
- 0:25WHY BizOps?
- 2:04WHAT is BizOps?
- 2:39WHY should you care?
- 3:21your job is to empower business
- 3:32technology is useless unless it supports business
- 4:48marketing tech
- 7:51there's a grain of joke in every joke
- 9:17every technical decision should support a business need
- 9:29there is just one problem
- 12:38fail quickly fail often
- 13:53HOWdo we learn?
- 15:15what we've got here is a failure to communicate
- 16:30how does your decision impact business?
- 17:51judge on value not point of view
- 20:42different perspectives are extremely valuable
- 23:28context is important
- 24:50collect correlate
- 26:37assume everyone is trying to do good
related talks
22mBizOps and you
30mA Story of DevOps Transformations
43mDevOps – when doing the right thing hurts!
47mDevOps is for Product Engineers, too.
22mDevOps in Regulated Industries: What to do when Internal Audit says ‘No!’
25mDevOps for Pointy-Haired Bosses
55mDevOps isn't just about developing
36mDevOps in Outsource… Really!