You are viewing content from a past/completed QCon

Presentation: Mistakes and Discoveries While Cultivating Ownership

Track: Building & Scaling High-Performing Teams

Location: Ballroom BC

Duration: 11:50am - 12:40pm

Day of week: Monday

Slides: Download Slides

Share this on:

This presentation is now available to view on InfoQ.com

Watch video with transcript

What You’ll Learn

  1. Hear how individual contributors at Netflix are allowed to take ownership of their projects, and how they empower their team to accomplish their tasks.
  2. Learn how to have smoother conversations within a team to cultivate a culture of ownership and create a team of independent leaders.

Abstract

At Netflix, we pair a strong sense of responsibility for outcomes with the freedom to choose how those outcomes are met to let people do their best and most-impactful work. My path to cultivating a culture of Ownership on our team was twisted and full of missteps. To help us talk about it and increase it routinely,  our team created a model of the five levels of Ownership: 

  • 0. Demonstration - Watch me do it. Ask good questions.
  • 1. Oversight - Run it by me. Expect a lot of revisions.
  • 2. Observation -  I’ll watch you do it with occasional high-level guidance.
  • 3. Execution - You do it independently, with random check-ins for me to stay aware.
  • 4. Vision - Tell me what we should do.

We also discovered necessary precursors - purpose, freedom, trust and safety. In this talk, I’ll share my well-intentioned mistakes and what we’ve learned so far.

Question: 

What's the motivation for your talk?

Answer: 

I've learned a lot as a manager about cultivating ownership on our team. I wish I could say that I learned it the easy way. I actually learned the hard way. I feel like I discovered the many different ways that creating ownership breaks down between a manager and their team and within people on the team. I want to share the mental framework that we use to think about a lot of different levels of ownership and also different failure modes. Being able to have that framework and terminology takes something that's you kind of aware of in the background and puts it right clear front and center and can be something you talk about in one on ones, or you can talk about even in larger team meetings depending on what kind of culture and flexibility you have on the team. This can be the kind of thing where I'm going to do it, you're going to watch and ask good questions all the way to the other end of the spectrum where you're taking the lead on this.

Within that spectrum is where the gray area happens, and I have experienced various levels of mismatch and understanding what level we were at. And even if we have been in agreement about what level we're at, being at the wrong level of ownership for the time. I'm sharing how we think about that and also the stories of those missteps along the way as a way of humanizing it, making also approachable.

Question: 

How would you describe the persona and the level of a target audience?

Answer: 

It's for anyone who is responsible for leading projects and tasks with other people. This talk would not really be for someone who's going to be heads down themselves. They may get some benefit with understanding their relationship with the people that are delegating work to them or figure out how to share in those responsibilities. But the real target audience for this talk is people who are in that leadership position, could be team lead, could be principal engineer, could be a manager, could be the most senior software engineer in a team. But if you're in that realm of being the default owner of something and need to transfer that ownership to various extents to others, this talk is there to help.

Question: 

What do you want this persona to walk away with?

Answer: 

Hopefully, new tools to have smoother conversations with different people on their team, and that smoother conversations will lead to healthier projects and also help that person to scale themselves as they can more rapidly transfer ownership when appropriate to other people.

Speaker: Aaron Blohowiak

Engineering Manager @Netflix in Cloud Infrastructure

Aaron is an Engineering Manager at Netflix in cloud infrastructure, where he learns and practices context-based leadership with a great team of engineers. Prior to Netflix he spent over a decade writing and operating software at various startups. Aaron occasionally rants on LinkedIn and is a hobbyist woodworker.

Find Aaron Blohowiak at

Last Year's Tracks

  • Monday, 16 November

  • Paths to Production: Deployment Pipelines as a Competitive Advantage

    Deployment pipelines allow us to push to production at ever increasing volume. Paths to production looks at how some of software's most well known shops continuous deliver code.

  • Java, The Platform

    Mobile, Micro, Modular: The platform continues to evolve and change. Discover how the platform continues to drive us forward.

  • Security for Engineers

    How to build secure, yet usable, systems from the engineer's perspective.

  • Modern Data Engineering

    The innovations necessary to build towards a fully automated decentralized data warehouse.

  • Machine Learning for the Software Engineer

    AI and machine learning are more approachable than ever. Discover how ML, deep learning, and other modern approaches are being used in practice by Software Engineers.

  • Inclusion & Diversity in Tech

    The road map to an inclusive and diverse tech organization. *Diversity & Inclusion defined as the inclusion of all individuals in an within tech, regardless of gender, religion, ethnicity, race, age, sexual orientation, and physical or mental fitness.

  • Tuesday, 17 November

  • Architectures You've Always Wondered About

    How do they do it? In QCon's marquee Architectures track, we learn what it takes to operate at large scale from well-known names in our industry. You will take away hard-earned architectural lessons on scalability, reliability, throughput, and performance.

  • Architecting for Confidence: Building Resilient Systems

    Your system will fail. Build systems with the confidence to know when they do and you won’t.

  • Remotely Productive: Remote Teams & Software

    More and more companies are moving to remote work. How do you build, work on, and lead teams remotely?

  • Operating Microservices

    Building and operating distributed systems is hard, and microservices are no different. Learn strategies for not just building a service but operating them at scale.

  • Distributed Systems for Developers

    Computer science in practice. An applied track that fuses together the human side of computer science with the technical choices that are made along the way

  • The Future of APIs

    Web-based API continue to evolve. The track provides the what, how, and why of future APIs, including GraphQL, Backend for Frontend, gRPC, & ReST

  • Wednesday, 18 November

  • Resurgence of Functional Programming

    What was once a paradigm shift in how we thought of programming languages is now main stream in nearly all modern languages. Hear how software shops are infusing concepts like pure functions and immutablity into their architectures and design choices.

  • Social Responsibility: Implications of Building Modern Software

    Software has an ever increasing impact on individuals and society. Understanding these implications helps build software that works for all users

  • Non-Technical Skills for Technical Folks

    To be an effective engineer, requires more than great coding skills. Learn the subtle arts of the tech lead, including empathy, communication, and organization.

  • Clientside: From WASM to Browser Applications

    Dive into some of the technologies that can be leveraged to ultimately deliver a more impactful interaction between the user and client.

  • Languages of Infra

    More than just Infrastructure as a Service, today we have libraries, languages, and platforms that help us define our infra. Languages of Infra explore languages and libraries being used today to build modern cloud native architectures.

  • Mechanical Sympathy: The Software/Hardware Divide

    Understanding the Hardware Makes You a Better Developer