Scaling Olympus Through Organizational Evolution
Given Olympus's current organizational complexity, implementing major structural changes quickly enough to impact v2.0/v3.0 is impossible.
"Building the House"
Platform teams build everything themselves
"Providing the Bricks"
Platform teams create tools for others to build
Build tools for streams and squads to develop end-to-end capabilities
Establish guidelines for how others should build
Enable the system to scale without bottlenecks
Product person leads the stream for release increments
Project person leads the squad for smaller increments
Engineering personnel report to the stream/squad leader for proper authority and decision-making
Alignment Principle: Engineering serves product development, with architects and technical leadership supporting product needsβor being replaced if unable to meet requirements.
Implement a single, actionable step that encompasses both organizational and process changes
Time from concept to deployment
End-to-end capability effectiveness
Cross-team dependency reduction
Maintaining high standards throughout transformation
Better understanding of cross-team relationships
Goal: Transition from waterfall to end-to-end agile delivery system
Visualize desired business outcomes and success metrics
Current and future state analysis of value delivery
Identify and visualize all cross-team dependencies
Organize insights, actions, and ownership into improvement plans
Our goal extends beyond mapping current interactions. We're fundamentally shifting the organizational approach to agile delivery, not reinforcing existing waterfall practices.
A dedicated product or project lead, depending on scope, ensures clear prioritization driven by product value and business objectives.
Not necessarily. Their role evolves to focus on guiding, supporting, and ensuring adherence to standards rather than directly building each component. They'll be measured on their ability to enable efficient delivery across teams.
Platform Technical Lead
Shift from direct builder to curator and reviewer; critical role in defining golden paths and architecture standards
Chief Architect
Evolving from centralized decision-making to mentoring, standard-setting, and enabling stream success
Platform/DevOps Lead
Leadership role standardizing CI/CD, infra-as-code, and developer workflows
Data Stream Lead
Increased autonomy consuming platform services; greater clarity on data contracts ownership
Security/Compliance
Policy curation and review; compliance frameworks embedded in automated templates
Stream Leadership
Clarified accountability for delivery outcomes and escalation responsibility
MTTR, uptime, SLOs/SLAs
Standards adoption rates
Platform NPS scores
Coordinating documentation, metrics baselining, training, and ensuring successful team onboarding
Benefiting from clear, frictionless platform onboarding and reduced dependency wait times
Improved clarity around data streaming tools, capabilities, and integration guidelines from guild
We're here to discuss the specific first step toward this transformation vision
β
Define the specific first step
β
Identify pilot team(s)
β
Establish success metrics
β
Begin transformation process