Truth 6 in Practice: Organizational Structure Determines Technical Outcomes
Making It Real
Truth 6 in Practice: Organizational Structure Determines Technical Outcomes
Before: Data science, engineering, and operations are separate departments. Job descriptions require narrow specialization. Models are "thrown over the wall" to engineering for deployment. Training is an HR benefit offered annually. Career ladders reward deep but narrow expertise.
After: Cross-functional teams own outcomes end-to-end. Job descriptions emphasize learning agility and cross-domain collaboration. The same team builds, deploys, and operates intelligent systems. Reskilling is a strategic program with dedicated time and executive accountability. Career ladders reward impact and the ability to bridge technical and business domains.
Application:
- Organize by outcome, not function. Have a fraud team, a recommendations team, and a search team. Each team has all the skills it needs.
- Co-locate skills. The people who need to collaborate should be in the same channel, the same meetings, and the same code review rotation.
- End-to-end ownership. The team that builds a system operates it.
- Hire for learning, not knowing.