IT Landscape - control vs. scaling
summary
Rapidly scaling orgs double yearly or even triple in under two years, forcing a tech stack from a few clusters to over 100 apps with organic data flows and ad-hoc integrations. Practical controls are mapped: department workflows, ownership, SSO/password managers, data privacy separation, and retiring duplicate tools. Scaling tactics are concrete: identify single points of failure, track incident history, measure health checks and 3–5 performance KPIs, define SLAs/escalation and on‑call, prepare backups/fallbacks — one API limit once created a day‑long backlog at financial close.
AI-written summary · about
chapters (17)
- 0:00Start
- 0:20It Landscape
- 15:07Single Source of Truth
- 16:31Clear Separation between Privacy Data and Analytics Data
- 16:57Communications Security
- 17:19Manual Processes
- 17:54Access Management
- 18:39Password Management
- 19:33Access Retention
- 20:23Check Ownership
- 21:44A Single Point of Failure
- 24:39Define Your Service Level Agreement
- 25:13Escalation Plan
- 26:12Recovering Strategies
- 27:16Monitoring
- 28:20Performance Metrics
- 32:16Questions
related talks
31mScaling
26mScaling engineering organizations
35mThe elements of scaling
18mScaling DevOps in Complex Environments: Challenges, Failures, and Successes
31mScaling Tech Organizations
24mHow to design your team for scale
47mScaling Design Orgs Rapidly for Long Term Success
46mDigital scale-up architectural patterns