The Role of an Executive Individual Contributor in Large Transformations
summary
An executive individual contributor leads a 2‑year internal move from one data center to four, consolidating thousands of individually managed systems (including hundreds of z/OS instances) into a standardized, automated platform for ~6,000 developers. The program builds a developer experience team, the largest internal GitHub, OpenShift and z/OS pipelines using Tekton pipeline and Python, converts system programmers into SREs, implements zero touch operations and replaces DR testing by flipping workloads every six months; migration is near the Q4 2023 deadline and largely successful so far.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 2:04Executive IC role
- 3:11IBM Fellow transition
- 4:20IBM transformation scale
- 6:55Reducing complexity
- 8:21Hybrid cloud showcase
- 10:08Transformation team assembly
- 11:55Lift-and-shift vs modernization
- 12:59Leading teams
- 14:01Developer experience & security
- 15:27Automating DR testing
- 16:12System programmers to SREs
- 16:56Client-zero advantage
- 17:38Quantum & AI design
- 18:23Deadline & lessons
- 19:04Success factors
- 19:50Technical leadership & diversity
- 20:31Career growth
- 21:15Closing
related talks
50mGrowing Your Career: From Tactical to Strategic
39mMoving from Management to Individual Contributor, a journey
28mScaling DevOps Talent in a Large Enterprise
45mGrowing into new roles beyond the cloud
23mTech leadership for everyone
06mIgnites - Zero to DevOps in less than a year...
32mLessons in Leadership
29mImpact Beyond Code: A Guide to Technical Leadership