What Does it Mean to Lead IT?
summary
Argues IT must stop acting like an arm’s-length contractor and become part of the business by owning technical strategy, building cross-functional DevOps teams, and measuring outcomes. Describes an E-Verify program that sets concrete targets (70 cases per day per adjudicator), raises automation from 98.6% toward 100%, and fixes a 60% shopping cart abandonment by iterating in two-week cycles, using cloud provisioning, a DevOps pipeline, and monthly metric-driven oversight that lets leadership reallocate funding when experiments plateau.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 2:28What does it mean to lead IT
- 6:50Fuzzy front end
- 8:37Running IT as a business
- 12:36Digital Era
- 13:58DevOps
- 15:15Changing the working model
- 16:26Creating a new model
- 17:28What a CFO does
- 19:04Lean Startup and DevOps
- 20:00Experimentation
- 20:53Scaling
- 22:44Goals
- 23:47Teams
- 24:55Measuring Progress
- 27:03Every Month
- 27:33Four Pieces of Information
- 29:04Shopping Cart Abandonment Rate
- 30:43What is a CIO responsible for
- 32:38Enterprise Architect
related talks
27mWhat Does it Mean to Lead IT?
24mWhat Does it Mean to Lead IT?
29mDevops Lead IT Transformation
46mLeadership in IT
47mWhy We Need DevOps Now: A Fourteen Year Study Of High Performing IT Organizations
30m3 Practices for Effective DevOps Adoption
37mWant to do the DevOps? Change Everything
37mShaping What's Next: The Transformative Power of Engineers and Organization
