Register or log in to access this video
Learn the theory behind the operating systems of high-performing engineering teams. Leave with a practical idea of how to design a flexible team operating system with rhythms, tools, and feedback loops for your team.
More like this
Engineering teams of all size and complexity need a structured operating system. Without this set of rhythms, processes, and tools to guide how your team collaborates, communicates, and executes, silos emerge, context is lost, and priorities become muddled. In this talk, we’ll discuss the essential components of an effective system, digging into the theory of why some things you’ve tried before have worked and why some things fell flat. We’ll also examine how to design a system tailored to your team’s size, maturity, and unique goals, emphasizing that the best operating systems aren’t static—they grow and evolve alongside the team.
Attendees can expect to hear about collaboration norms, decision making frameworks, and feedback loops and to learn about effective cadence and rhythms for all of these things. And by the end of this talk, attendees will walk away with actionable insights to audit their current systems, implement meaningful changes, and drive alignment across their teams.
Join Meg Adams from the New York Times to learn how a well-designed team operating system can transform your engineering team.
Key takeaways
- What is an operating system and why does my team need it?
- What are the components of an operating system?
- What are the theories I should know to inform the design of my team operating system?
In short: By the end of this talk, attendees will walk away with actionable insights to audit their current systems, implement meaningful changes, and drive alignment across their teams.
