
Work First, Names Last: A Practical Way to Redesign Your Engineering Org
A peer CTO described a team of four engineers responsible for roughly fifteen services: user management, marketing and transactional email, a handful of services nobody else wanted, and an integration that belonged with another team. The team's name no longer described anything it did, and the CEO wanted to know why it was slower than everyone else. Kevin Goldsmith calls the cause ownership drift. Over the years, work ends up with whoever built it, whoever was available, or whoever couldn't say no.
Kevin's earlier episode on org design covered why to reorganize. This one is about how to actually do it, starting from a blank whiteboard. He walks through a reorg he led as a new CTO, when ownership had followed people instead of missions and teams were spread across eight time zones. From that experience, he lays out an approach he calls work first, names last: inventory everything the organization does, group it into missions, give each mission a measure, deal with the leftovers, apply your constraints, and only then add people. He also covers when it makes more sense to start from strategy or from the flow of work, and why starting from a headcount target tends to carry the old problems into a smaller org.
The last third looks at why so many leaders are redrawing their teams right now. With agents writing more code, bottlenecks have shifted, team size is increasingly set by how much one person can supervise, and shared tooling needs a different kind of owner. Kevin shares patterns he's hearing from other CTOs, a cautionary story about a design system team at Spotify, and the parts he hasn't figured out yet.
It's a practical episode for engineering leaders planning a reorg, and for managers who've realized their team has become the junk drawer.
Show notes
- The Hidden Architecture of Engineering: Practical Lessons in Organizational Design: https://itdependspod.com/episodes/the-hidden-architecture-of-engineering-practical-lessons-in-organizational-design/
- Every Organization Is a System. Are You Designing It or Just Living in It?: https://itdependspod.com/episodes/every-organization-is-a-system-are-you-designing-it-or-just-living-in-it/
- Using Self-Selection to Create Journey Teams at Avvo: https://itdependspod.com/episodes/using-self-selection-to-create-journey-teams-at-avvo/
- The Role of QA When Agents Write the Tests: https://itdependspod.com/episodes/the-role-of-qa-when-agents-write-the-tests-why-quality-follows-context/
- DORA, 2025 State of AI-assisted Software Development: https://research.google/pubs/dora-2025-state-of-ai-assisted-software-development-report/
- Team Topologies by Matthew Skelton and Manuel Pais (Amazon link): https://link.amazon/B0hZh25LY
- Questions for the December Q&A episodes: [email protected]
- Listener Survey: https://forms.gle/JVeKHsHJKhEM3dvK6
- The book: It Depends: Writing on Technology 2012-2022 (https://itdependsbook.net)
- Your host: Kevin Goldsmith (https://kevingoldsmith.com)
D'autres épisodes de "It Depends: Lessons in Technology Leadership"



Ne ratez aucun épisode de “It Depends: Lessons in Technology Leadership” et abonnez-vous gratuitement à ce podcast dans l'application GetPodcast.








