You’re doing culture wrong

Send us Fan Mail

DevOps “culture” gets blamed for everything—so what is it, really? Pinja and Eficode consultant Dan Khurram cut through the buzzwords to define culture in practical terms: how decisions get made, what behaviors are acceptable, and how teams talk about uncertainty and failure. They compare textbook “DevOps culture” to actual corporate culture, then borrow lessons from high-stakes domains like aviation and healthcare on learning from incidents instead of hiding them. Along the way: onboarding as your first culture signal, Microsoft’s “learn-it-all” shift, and three takeaways you can apply now—don’t call it a culture change, define your “why” for your context, and start locally so good habits spread. If your transformation feels like more ceremonies than substance (hello, Jira), this episode gives you a clearer map.