Recording coming soon

In high performing teams, individuals understand what is expected of them, and take ownership of their work.

Sounds simple enough, right?

Not always. Especially in fast paced orgs, a lot of developer time is spent either trying to prevent things from breaking, or trying to fix things after they break - which can easily lead to silos, decreased visibility, and a lack of trust between team members. 

In this panel, we’ll discuss what  a culture of accountability actually looks like in practice, and the role of the engineering leader in encouraging a culture of accountability, not blame, in busy developer teams.

Register today to learn:

  • How to help your engineers to feel in control of their workload
  • How to encourage accountability without straying into micromanagement
  • The role of accountability in DevOps culture
  • How tools and processes such as feature flags can increase visibility and foster a sense of shared ownership

Moderator

Sarah
Milstein
Sarah Milstein
Sarah
Milstein
@sarahm

Panelists

Lesley
Cordero
Lesley Cordero
Lesley
Cordero
@clesleycode

Lesley Cordero is currently a Staff Engineer at The New York Times.

Nick
Smyth
Nick Smyth - Harness
Nick
Smyth

Nick Smyth is the VP of Engineering at Harness

Abby
Bangser
Abby Bangser
Abby
Bangser

Abby is a Principal Engineer at Syntasso