Debugging Product Teams by Amy Newell Everyone knows that to build great software you need great teams. Experts are quick to offer principles and processes that are “the key” to greatness. But what if your team’s not “great”? It’s not “getting things done”. People don’t trust each other. There’s a lot of conflict. Low morale. Something is wrong. Now what? “Debugging” a team is a lot like caring for a complex distributed software system: it’s less about fixes, and more about observation, hypotheses, intervention, and more observation. Whatever your role, these are skills you can learn and apply right now, on your own teams.