Podcast appearances and mentions of dave zwieback

Best Safety Podcast, Safety Program, Safety Storytelling, Investigations, Human Performance, Safety Differently, Operational Excellence, Resilience Engineering, Safety and Resilience Incentives There is a new book in town.... and it is a good one.   Beyond Blame is a story about how one organization had to move past the old ways of viewing the world and start looking at new ways to learn and improve.    This podcast is a crossover between DevOps, High Reliability Computing, Safety, Human Performance, Operations, and pretty much any other process that is too risky to leave alone and too valuable to fail.  I love the fact that our worlds are colliding and combining.  You will really like this podcast no matter which world you operate within...he says, ending a sentence with a preposition.   Dave Zwieback has been working with complex, mission-critical I.T. services and teams for two decades. His career spans small high-tech startups, non-profits, and behemoth engineering, financial services, and pharmaceutical firms.  He is involved in the AWSOME POSTMORTEMS workshops!. Almost everything about Dave is cool.  Listen and find out more.  Thanks for being a part of the podcast.  You make the podcast go!!!

[from the archives] Our guest today is Dave Zwieback,  the author of Beyond Blame: Learning from Failure and Success and an engineering leader in various organizations in & around New York City.Dave does workshops for organizations looking to build People First cultures.  If you’re interested in hosting a highly-rated, practical, hands-on workshop based on the book at your company, please contact workshops@mindweather.com. You’ll learn the theory and, most important, get to practice conducting Learning Reviews, a critical new practice for building resilient, people-first learning organizations.This episode is for you if you’re interested in learning about soft-skills, career, or management.

Our guest today is Dave Zwieback,  the author of Beyond Blame: Learning from Failure and Success and an engineering leader in various organizations in & around New York City.Dave does workshops for organizations looking to build People First cultures.  If you’re interested in hosting a highly-rated, practical, hands-on workshop based on the book at your company, please contact workshops@mindweather.com. You’ll learn the theory and, most important, get to practice conducting Learning Reviews, a critical new practice for building resilient, people-first learning organizations.This episode is for you if you’re interested in learning about soft-skills, career, or management.

“The way to start would be, first, when we feel the tendency to blame, to try to get in touch with what it feels like to be holding on to ourselves so tightly. What does it feel like to blame? How does it feel to reject? What does it feel like to hate? What does it feel like to be righteously indignant?” - Pema Chodron There’s something calming about finding a target for our blame. It’s like in this moment of being lost in a rough sea of chaos and uncertainty, a person to assign the fault is like an unsinkable lifeboat to grasp. We climb aboard, take a deep breath, and relax. We do this as individuals, we do this in organizations, we do this as a society. But what incredibly valuable opportunities lie in resisting the urge to assign blame? What might we learn in what didn’t (or did) work if we explore a bit more? Jerry is joined today by author and CTO Dave Zwieback to talk about just that. Dave, in his book “Beyond Blame,” explores the fallacy of blame, how it fails to identify the immense complexity and interdependency of the world around us, and the real cost of rapidly assigning fault. If we pause and explore, we may just find that blame often prevents us from doing the very thing we want most - to learn and to grow. Links Dave Zwieback on Twitter - https://twitter.com/mindweather Beyond Blame by Dave Zwieback - http://www.amazon.com/Beyond-Blame-Learning-Failure-Success/dp/1491906413 The Five Dysfunctions of a Team by Patrick Lencioni - http://www.amazon.com/Five-Dysfunctions-Team-Leadership-Fable/dp/0787960756 Daniel Kahneman - https://en.wikipedia.org/wiki/Daniel_Kahneman John Allspaw - https://twitter.com/allspaw Truth and Reconciliation Movement - https://en.wikipedia.org/wiki/Truth_and_reconciliation_commission#The_South_African_TRC_and_after

O'Reilly Radar Podcast: Learning from both failure and success to make our systems more resilient.O'Reilly's Jenn Webb chats with Dave Zwieback, head of engineering at Next Big Sound and CTO of Lotus Outreach. Zwieback is the author of a new book, Beyond Blame: Learning from Failure and Success, that outlines an approach to make postmortems not only blameless, but to turn them into a productive learning process. We talk about his book, the framework for conducting a "learning review," and how humans can keep pace with the growing complexity of the systems we're building.When you add scale to anything, it becomes sort of its own problem. Meaning, let's say you have a single computer, right? The mean time to failure of the hard drive or the computer is actually fairly lengthy. When you have 10,000 of them or 10 million of them, you're having tens if not hundreds of failures every single day. That certainly changes how you go about designing systems. Again, whenever I say systems, I also mean organizations. To me, they're not really separate. I spent a bunch of my time in fairly large-scale organizations, and I've witnessed and been part of a significant number of outages or issues. I've seen how dysfunctional organizations dealing with failure can be. By the way, when we mention failure, it's important for us not to forget about success. All the things that we find in the default ways that people and organizations deal with failure, we find in the default ways that they deal with success. It's just a mirror image of each other. We can learn from both failures and success. If we're only learning from failures, which is what the current practice of postmortem is focused on, then we're missing ... the other 99% of the time when they're not failing. The practice of learning reviews allows for learning from both failures and successes. In the practice of learning reviews—and of course, this is also present in the "blameless postmortems"—we don't focus on a single root cause, but we focus on a bunch of conditions. That comes not out of anything other than the realization of the complexity of the systems that we work with. In the current practice of postmortems, we talk about accountability, but really what that version of accountability means is, who's throat are we going to choke. Who are we going to punish? ... In a learning review, we go beyond blame to achieve real accountability. ... If there's blame, or there's punishment, then you're not going to get the full account. You really cannot fully hold people accountable. The other sort of lineage of removing blame and punishment actually comes from a normal non-restorative or punitive justice system, where in certain situations, we give people immunity. Why? So that they can give us the full account of what happened. We do that sometimes with people we know have done bad things. In mafia cases. In those cases, what we are saying or doing by giving people immunity is that we value the information they provide to us more than pushing them. Why do we want to go beyond blame, why do we want to go beyond bias? Those two are the short tickets to learning. ... More importantly, it's not a one time thing. We continually have to be learning about our systems and feeding that knowledge back into that system to make it more resilient. Subscribe to the O'Reilly Radar Podcast: Stitcher, TuneIn, iTunes, SoundCloud, RSS

O'Reilly Radar Podcast: Learning from both failure and success to make our systems more resilient.O'Reilly's Jenn Webb chats with Dave Zwieback, head of engineering at Next Big Sound and CTO of Lotus Outreach. Zwieback is the author of a new book, Beyond Blame: Learning from Failure and Success, that outlines an approach to make postmortems not only blameless, but to turn them into a productive learning process. We talk about his book, the framework for conducting a "learning review," and how humans can keep pace with the growing complexity of the systems we're building.When you add scale to anything, it becomes sort of its own problem. Meaning, let's say you have a single computer, right? The mean time to failure of the hard drive or the computer is actually fairly lengthy. When you have 10,000 of them or 10 million of them, you're having tens if not hundreds of failures every single day. That certainly changes how you go about designing systems. Again, whenever I say systems, I also mean organizations. To me, they're not really separate. I spent a bunch of my time in fairly large-scale organizations, and I've witnessed and been part of a significant number of outages or issues. I've seen how dysfunctional organizations dealing with failure can be. By the way, when we mention failure, it's important for us not to forget about success. All the things that we find in the default ways that people and organizations deal with failure, we find in the default ways that they deal with success. It's just a mirror image of each other. We can learn from both failures and success. If we're only learning from failures, which is what the current practice of postmortem is focused on, then we're missing ... the other 99% of the time when they're not failing. The practice of learning reviews allows for learning from both failures and successes. In the practice of learning reviews—and of course, this is also present in the "blameless postmortems"—we don't focus on a single root cause, but we focus on a bunch of conditions. That comes not out of anything other than the realization of the complexity of the systems that we work with. In the current practice of postmortems, we talk about accountability, but really what that version of accountability means is, who's throat are we going to choke. Who are we going to punish? ... In a learning review, we go beyond blame to achieve real accountability. ... If there's blame, or there's punishment, then you're not going to get the full account. You really cannot fully hold people accountable. The other sort of lineage of removing blame and punishment actually comes from a normal non-restorative or punitive justice system, where in certain situations, we give people immunity. Why? So that they can give us the full account of what happened. We do that sometimes with people we know have done bad things. In mafia cases. In those cases, what we are saying or doing by giving people immunity is that we value the information they provide to us more than pushing them. Why do we want to go beyond blame, why do we want to go beyond bias? Those two are the short tickets to learning. ... More importantly, it's not a one time thing. We continually have to be learning about our systems and feeding that knowledge back into that system to make it more resilient. Subscribe to the O'Reilly Radar Podcast: Stitcher, TuneIn, iTunes, SoundCloud, RSS

There is a new book in town.... and it is a good one.   Beyond Blame is a story about how one organization had to move past the old ways of viewing the world and start looking at new ways to learn and improve. This podcast is a crossover between DevOps, High Reliability Computing, Safety, Human Performance, Operations, and pretty much any other process that is too risky to leave alone and too valuable to fail.  I love the fact that our worlds are colliding and combining.  You will really like this podcast no matter which world you operate within...he says, ending a sentence with a preposition.Dave Zwieback has been working with complex, mission-critical I.T. services and teams for two decades. His career spans small high-tech startups, non-profits, and behemoth engineering, financial services, and pharmaceutical firms.  He is involved in the AWSOME POSTMORTEMS workshops!. Almost everything about Dave is cool.  Listen and find out more.  Thanks for being a part of the podcast.  You make the podcast go!!!

Brian talks with Dave Zwieback (@mindweather; Head of Engineering @NextBigSound) about his book “Beyond Blame”, the challenging cultures of web-scale and DevOps, understanding complex and chaotic systems and how to lead through problems. Check out O-Reilly's new initiative: Learning Paths. Show Links: "Beyond Blame" book Dave’s Blog - Simple Thoughts on Complex Systems Topic 1 - Tell us about your background and the things you’re doing at NextBigSound. Topic 2 - You’re at VelocityConf this week. What topics are you really interested in or focused on? Topic 3 - Let’s talk about your book “Beyond Blame”. What was the motivation to write it and why choose the storytelling model (similar to The Phoenix Project)? Topic 4 - Is there a “journey to better post-mortems”  or “learning review” model, or is this an all-or-nothing approach? Topic 5 - The book talks a lot about accountability, and there is an area where “accountability” is defined very differently than we tend to use it today (“blame”). It’s one thing to discuss empathy, because that’s not really taught in any formal courses or via team/group things (e.g. sports). How to you expand or redefine a well-understood concept?

Our guest on the podcast this week is Dave Zwieback, Author of Beyond Blame, Head of Engineering at Next Big Sound, and CTO at Lotus Outreach. We discuss how to reach a blame-free culture where outages are linked to multiple conditions instead of one person. Dave shares his framework for Learning Reviews and effective Postmortems. In an increasingly complex world, it is impossible to predict how a system will fail, but through these practices we can see emergent trends and understand how to continuously improve our systems.

Dave Zwieback, VP of Engineering at Next Big Sound and Mike Rembetsy, VP of Technical Operations at Etsy discuss learning from the unexpected and examining failure without blame. With practical tips about technical tools and philosophical insights into the human factors and cognitive biases in play, these industry experts offer useful guidance for the thorny questions around the topic of failure.

Dave Zwieback, VP of Engineering at Next Big Sound and Mike Rembetsy, VP of Technical Operations at Etsy discuss learning from the unexpected and examining failure without blame. With practical tips about technical tools and philosophical insights into the human factors and cognitive biases in play, these industry experts offer useful guidance for the thorny questions around the topic of failure.

John and Damon chat with Dave Zwieback (Knewton) about his excellent talk from DevOps Days New York and the most difficult part of DevOps... hiring.  Show notes at http://devopscafe.org