What can we learn about working through and analyzing IT incidents from the high tempo, very high consequence world of medical emergency rooms? What does vulnerability have to do with psychological safety, creativity, and team collaboration? It turns out that we can learn quite a lot. We can all benefit from drawing connections across different fields of study and this panel will explore some of these connections.
SRE Architect, Blameless
Dr. Al'ai Alvarez
Clinical Assistant Professor, Emergency Medicine, Stanford Medicine
Thank you, Steve. So I've known Kurt Anderson for almost a decade back when he helped lead the SRE function at LinkedIn. And he's been a member of the dev ops enterprise community ever since. And I was so delighted and to be honest, astonished when he submitted a talk proposal with one of his colleagues at blameless, Christina tan, they wanted to share the learnings from Dr. LA Alvarez, who is clinical assistant professor of emergency medicine at Stanford medicine. And he will be talking about how it is sometimes surprisingly difficult to apply principles of blamelessness and compassion. In the context of medical professionals, there is so much about his experiences and expertise that defy easy explanation. And I am so excited about what he will be teaching us today. He'll be co-presenting what's Kurt Anderson, who is currently SRE architect and head of strategy at blameless, along with Christina tan, who facilitate strategy and executive alignment. Here's Dr. LA Kurt and Christina.
Imagine you're a neuro resuscitation and the emergency department. The ambulance brings in somebody gasping for air it's depend demic. You and your team are getting ready to resuscitate as a team leader. You're orchestrating medical interventions while also making sure about your staff safety. This is a very common scenario for us in the emergency department. We make high stakes decisions in high risk environments. Medicine is a Buka environment. It's volatile filled with uncertainty. We're not sure who's coming to us. And with what diagnoses it's complex, including their disease processes. Is this COVID or is this just a collapsed lung? Maybe both. And so we work with a lot of ambiguity. There's a saying in medicine that patients do not read our textbooks. They present with vague symptoms and it's on us to discern which symptom or physical findings are relevant. We don't always know whether interventions will work until implemented in my line of work. Mistakes can mean life or death. We do this several times a work shift one after another.
That sounds incredibly challenging and there's a relatable, but not equivalent parallel in it. Sometimes an incident could cost a company, millions of dollars, and the engineer who unintentionally triggers that Luca process would have challenging feelings that are very difficult to resolve
As John Allspaw who happens to also be on the program agenda for this conference has pointed out incidents are unplanned investments in our systems, and it would be a waste of that investment if we did not learn from it. So what can we learn about working through and analyzing it incidents from the high tempo, very high consequence world of the medical emergency departments,
And what does vulnerability have to do with team collaboration and creating a learning organization? These are the topics that we'll be exploring today with Dr. Alvarez and Kurt first, a round of intros. Hi everyone. I'm Christina. I'm on the strategy team at blameless strategizing for market positioning, executive team alignment and building a culture of high performance and connection. I'm passionate about showing how blameless culture can work for not only engineers, but also business leaders.
And hi, I'm Kurt Anderson. I've been an SRA since before the term was coined by Google working at a variety of organizations. Currently, my title is SRE architect and I'm the head of strategy at blameless.
My name is LA Alvarez. I'm the director of wellbeing at Stanford emergency medicine clinically. I'm an emergency physician at Stanford, also relevant to this talk. I serve as the associate residency program director focused on quality patient safety and process improvement. I also serve as a co-chair of the physician wellness forum at Stanford, William D by the way, we're among friends here. And so please feel free to call me by my first name.
So LA tell us how retrospectives are typically done in your emergency department.
Thanks Kurt. There are two main types of retrospectives for me. The first one is on shift immediately after the incident, which I'll refer to as debriefs. Then there's the case reviews for critical events. There's a team that meets twice monthly to review cases.
Well, let's come back to case reviews and a little bit. Tell me first a bit more about the on shift in the moment. Debriefs
For Lee briefs. I try to gather the team so we can reflect on how we did. This is very different from my training in the Bronx and New York city, where we rarely did debriefing after any incident as a resident. I remember we would talk about cases in subway. So on the way, home our gatherings now at Stanford, our nurses even ask for this, it's simply just part of our culture. So
Who all do pull in when you say the team?
Yeah. So for on-chip Steve reefs, uh, the whole team is invited the nurses, physicians, the tax, the respiratory therapists, pharmacists, really anyone who was in the room, including the social worker.
That seems like it would take quite a bit of time. How long do you dedicate to these events?
Yeah, this is the challenge. We often do not have the time to do this as there a constant influx of patients in the emergency department. However, we're very intentional about this and we would spend about five to 10 minutes, maybe 15 minutes max, if it's a challenging case,
Thank you for Shane overview of debriefs, LA let's dig in some more confronting a negative outcome can be very stressful, especially when a person feels some degree of personal responsibility. So LA, how do you alleviate the emotional trauma of post-incident debriefs?
I think it's important to preface debriefs during this gathering. I say something, Hey, I know we've done multiple debriefs. Here's the structure that I want us to use today. Let's comment on the individual. Then the team that the environment, because we are all showed up today with a goal of saving people's lives. Um, when we talk about the individual, please focus on yourself only so that we can avoid pointing fingers. The next key part is vulnerability. This creates psychological safety and provides a clean framework for the discussion. Before I did this, I would either get a lot of kumbaya or kudos. That's were very superficial, great job, what a team or the opposite where people blame each other. And so when we leave the debrief of you're feeling frustrated and angry. And so for example, I start with a mistake that I made, uh, there's always a mistake or opportunities for improvement.
So I pick one, everyone makes mistakes. Uh, because again, Buka environments, we're doing the best we can of the information that we have in the moment. I think something that I can normalize. So everybody, like, I'm not sure if you notice, but when the patient arrived, I was actually nervous. I was worried she was going to go into a cardiac arrest and I started taking over a procedure. Now, while I was able to successfully do the procedure, it distracted me from seeing the big picture and created a void in leadership in the room. By the way, this example is a very common mistake. So it's very easy to normalize this. This moment of vulnerability creates a psychologically safe space for my team. Okay. The team leader can own up to their mistake. Maybe I can as well. And it's actually very cathartic to admitting mistakes in a psychologically safe space.
It takes the uncertainty and ambiguity away. And also you get feedback from others. Whether the decision may actually be the right choice. Also I've learned to ask permission and for them to focus on the 1%, what is that 1% change that I can do to better the outcome or the experience for everyone? I think this takes away the pressure from somebody, especially when you're taking about, when you're talking about devastating events again at the get go, there's no naming, blaming or shaming. We're simply focusing on that 1% that we each can do better, which is more achievable. I think the next step is then leveling the team. Here's an example. Hey, I thought Dr. Christina did a great job in that resuscitation and I'd like her to lead the rest of the discussion. What people may not know is that I've already primed the senior resident about the structure. So she knows what she'll focus on in the debrief.
So it sounds like you've learned quite a lot about how to make these effective. Are there key takeaways that people should bear in mind about elements that make them particularly effective or might undermine them if they weren't done?
Yeah, that's right. Kurt for on-chip debrief. It really helps to do it immediately. That way it's, uh, everything is fresh and everyone is contained whether there's good or bad outcome. The goal of debriefing is to just unpack and come up with a shared mental model because my version is not always the version that's the nursing perspective may have, or from the trainee, the allows us to reflect and connect with each other instead of ruminating on the incident, on our own, as we drive home or for me right before we go to sleep. Right? So there's also the, the need for multiple touch points. Uh, this is very important. It's unrealistic to try to cover everything in one debrief, especially since we're talking about five to 10 minutes only. So for individual feedback, I would just pull them aside later on for something that I anticipate people will be perseverating with.
An example would be decision that many people will not agree with. I will quickly find time to pull aside the person who made the decision to give them a heads up. Hey, we're going to talk about this at the debrief. This is what I saw. I wonder what your thoughts are that way. Instead of hearing about it for the first time in front of everyone and processing the information to save face, they really have a few minutes to just collect their thoughts and not feel defensive. We never want someone to feel defensive during a debrief. This also allows them to talk through their thought process with me and I at night, I can coach them on some learning points. This is something that can be very powerful, especially for someone who's beating themselves up for a mistake.
So can you give us an example of how all these come together with maybe a case?
All right. So I recently had a pretty tough case. The patient died, which happens, but there was a lot of mixed emotions in the room immediately after the resuscitation, I can tell the head surgeon was very upset with how things went. So I pulled him aside. I said, I know you just came on to this and I can see that you're not happy. Let's talk this out because we, because I want us to be United in front of everybody. When we debrief, I'll share with you my perspective of why we did what we did and I want to hear from your perspective. And so when it just that I actually didn't get a chance to pull my senior ahead of time because of that meeting. And so, um, I didn't really get, give them a heads up or that's a, they're going to be leading the debrief.
And so I stood next to him during the entire debrief that showed that I support him because again, the case did not go so well, I'm sharing this because I want to highlight something that I did not expect the senior surgeon as we were going through this, uh, immediately share it. Hey, I screwed up, I should have done this instead. And I never would have expected trauma surgeons to say this in front of our nurses, the emergency medicine team, the tax, and acknowledged this. And we have a great team at Stanford, right? And so this is just not part of the norm. So for me, this was a signal that somehow we've established a safe space, enough for a surgeon, the surgical chief to acknowledge a mistake. And that was pretty cool because then with the leader openly owns their mistake. Everybody else starts sharing things like, oh, and I could have done this better. And next time I will this. And again, it's not focused on the screw up it's instead. Here's what I learned from this. So next time here's what I'm going to do in stat.
Yeah. And I think this is the forward-looking accountability that improves the team's ability to learn and adopt as a whole LA as a practitioner of mindfulness. How do you coach your students to deal with self-blame?
Uh, this is not as easy, uh, Christina, um, I think it's important to feel the negative experiences, but it's also important to put it in context that they're not alone in this experience, that everyone feels this way. And that there, we used to prove if they're willing to, if they're actually open to exploring that this is where mindfulness is important, it allows us to slow things down and process the experience, and also where self-compassion comes into play. Instead of focusing on the shame, we get to move past that and think about how we can improve better. This is very hard to train. Like I said, especially for positions, we've spent all our lives motivated by this fear of failure. I also don't like the notion of stripping away those negative feelings and just trying to be positive because that creates an internal conflict, just like you I'm allowed to feel crappy when I fail.
And I also do not need to identify with my own mistakes. So my goal in training is to help prepare them for when they are practicing independently. Hey, I'm letting you know that you'll have many mistakes and just like me, you'll also feel crappy when they, when you go through them. And this is where compassion comes in, just like me. When I make mistakes, I need to be able to be kind to myself in order to actually process what's happening as opposed to start blaming myself and focusing on the shooter could have water of the difficulty of that situation. Using the, just like me perspective, re able to see the possibility of being kind to yourself in order to not just do the job, but actually own our role and the privilege of being able to do the job and be accountable for the actions and decisions, and also being accountable to how we're going to iterate ourselves to change for the better. This is how we promote wellbeing and professional fulfillment.
So it sounds like this model you have of not only dealing with the team, but dealing with yourself is to be compassionate, to both taking care of both yourself and the team. So that instead of being a victim and feeling dumped upon, you're empowering everyone to understand that you have the capability to make an improvement. And then that fans out from there as you, uh, throw the rock into the pool, the ripples stretch out beyond. So how do you put mistakes into perspective when they are such high consequence? Potentially?
Yeah, that's right. Kurt, our goal is to empower rather than being fixated as victims, Ethan Cross in his book chatter about using time as a variable in five days and five months and five years, will it really matter? And at least it allows you to then think, okay, what can I do next, I suppose to, oh my gosh, I'm going to lose my job. And so, so far we focused on things that are going back. Debriefs can also be about celebrations and appreciation. Here's an example, after an incredible resuscitation, I pull a resident aside and share, Hey, I just want to pause and take this moment to let you know that this is what it feels like to save a life, right? I'm getting goosebumps just sharing this because oftentimes they're so focused on the inner critic and blaming things and focusing on the screw ups that we don't recognize when we're doing amazing things. We need to also bookmark positive feelings.
I love that bookmarking positive feelings now going from the individual to the leader, confronting the incident LA and Kurtz, should we, as leaders expect physicians and engineers to not make high-impact mistakes and our mistakes are reflection of lack of competence or skill.
Yeah. Thanks, Christina. This is very unrealistic. Um, I will acknowledge that in emergency medicine, when bad outcomes happen, people can end up with long-term complications or they die. And so how can you tell somebody to say that the mistake was okay? And I think that's very hard, but I think part of this is to also realize that there's only so much that we can do. We have to understand that what's really within our circle of influence and what's not what is actually part of the disease process and what are systems issues that led to the outcome. So for example, let's talk about the hypothetical scenario that I shared at the very beginning. What if that turns out to be a massive heart attack, the question then should not be, how can a smart doctor working in a top medical institution who went through four years of college, four years of medical school, and four years of residency training, miss a simple heart attack, it's inconceivable, right? And yet this actually happens that it happens not so infrequently across the country. And it's because of interruptions it's because maybe you're thinking about something else and then it was wrong. It's the wrong context in this scenario that I shared at the beginning, it's because it's the pandemic and imagined back in March of last year, when we didn't know a whole lot about COVID, everybody was scared and everybody had COVID until proven. Otherwise
We are all equally susceptible to the pressures of the systems that we operate within, whether they are in the moment or whether they are entrenched in the procedures that are around us. I think that's one of the things that is highlighted in the checklist manifesto, which is a book for people to look up if they haven't read it, because it highlights that even for well-trained extremely expert people having a basic pattern of steps to follow, uh, not necessarily to check off, but to check that it is done, helps to avoid these mistakes. And so that can be a countervailing pressure against the pressures of the system.
Yes. In situations of stress, we can all benefit from structure moving on from retrospectives. Let's talk about designing for wellbeing and performance through culture. This is a question for both of you, how can the leadership of our organization use language to build an adaptable, psychologically safe and learning organization
At Stanford? My medical director changed the name from peer review to case review. This is the second version of the retrospective we mentioned earlier, and it highlights how it's important, uh, to not focus on the peer. It's not about the peer anymore. I guarantee you that peer has learned a lesson and worse. They're in their shame spiral. By focusing on the case, we move past from the naming and blaming and shaming of this experience to really dissecting the case, understanding the systems driven factors that led to the outcome. This is how we advance patient safety discussions. And this is how we can also protect physicians and their frontline workers, Monica waterline, and Jane Dutton wrote the book, awakening compassion at work. If we look at events from the perspective of just like me, we can be kinder and have better empathy on how we would want to affect change
And highlighting the impact that language can have just a little word of why, if you change that in your questioning to a what or a help me understand, it makes a huge difference in the power or the forest that's coming across. In that question. Courtney Eckhart had an awesome talk, which is linked to, and the resources at the end of the talk that highlights that the word why asks for a judgemental or an agent of answer it's asking, who can we hang for this? Um, or, or blame frankly. And so avoiding why questions helps to open people up because it defangs that power.
Yes. I mentioned I trained in the east coast in the Bronx, so I've had to learn it the hard way in the Bronx. My attending would ask, why did you do this? And in California, I've learned reflective listening and appreciative inquiry. So, Hey, I noticed this, can you walk me through your thought process?
The other thing to do is to try to help keep me keep people from making counter-factual statements. I should have done X because that's not what happened, uh, regardless of what you think after the fact you're doing it with the benefit or the hindrance of hindsight bias, you're not doing it in the moment. And the decision-making in the moment is the key. And so you're trying to look back and understand retrospectively what happened. Don't try to bring the you from after the fact into that event. Be factual, not counterfactual with the, the hindrance of the pandemic. Now, uh, having been with us for almost two years, uh, the old term in the it field of PetSmart, um, is, uh, got a lot of weight to it now. And so generally we're seeing the industry shift to call it retrospectives because it doesn't have that, that negative connotation.
Yeah. And language is a powerful tool for shifting culture. Let's talk about the next tool rituals besides blameless and timely debriefs. What other rituals were programs have you created in service of building a learning organization?
Yes, I'm really excited about this. We brought, we brought back save of the months, uh, awards last year at the peak of the pandemic. It was important that we also here we're doing great. Instead of all the concept barrage of information about COVID also in medicine, there's this, uh, morbidity and mortality or M and M rounds in the east coast. This means me standing up in front of everyone and discussing the case and answering the questions from the audience of faculty and trainees. Talk about name, blame, and shame. And it was always humiliating because save of the months also acknowledges one person only this year, we've implemented the offshoot of M and M's, which is the amazing and awesome or Ana the recipient of the save of the month presents their case in front of faculty and trainees talking about the team and their efforts that led to that safe. We're highlighting positive variance in front of everyone, which is the opposite of the humiliating experience of MNF.
Andy is a very creative compliment to M and M LA. Uh, can you tell us how you conduct your biweekly case reviews and what objectives you're trying to accomplish there?
So for critical events, we look at contributing factors from the human level and the systems level. We then develop action plans for each and track incidents and interventions for patterns. For example, in the hypothetical case that I shared at the beginning, when you start seeing a couple of misses of heart attacks during the pandemic, you create a system that automatically checks for it. So no one forgets
And in the SRA world, we're seeing some similar evolutionary practices in retrospectives. Uh, first one of the developing practices is to interview the individuals beforehand. That's similar LA to what you do in terms of giving a heads up to your seniors before you go into the debrief. And then secondly, the other thing that's showing itself as being very valuable is to separate the identification of action items or fixes from the group meeting the group retrospective itself, because this allows the group conversation to focus on the things that can be learned and the things to be done. Everybody can come up with those, but doing it after you focus on the learnings and in a separate context, really helps to clear the mental space and people in the learning mode.
Yeah. And these rituals repeat it consistently create a new culture. LA you mentioned Monica and Jane's book earlier on, on awakening, compassion at work. They talk about role creation as a way of integrating compassion and fostering psychological safety at work. So how was your role as director of wellbeing created?
No, I am fortunate to work in a place where the chief wellness officer was first created this role. Uh, this opened up the role that I have now, which is the director of wellbeing. We have one for every department focusing on faculty and staff wellbeing. Before this role, I was one of the associate residency program directors in emergency medicine. Uh, my role was to help train future emergency positions and because of my background in quality and patient safety and clinical operations. And because of my experience with peer review, I created a role for myself. Focusing on providing trainees supports in the it's are involved in case reviews. I normalize with the residents how just like them, I still get palpitations. Whenever I get those secure emails about a case. This offers me the opportunity to share resources available, to debrief anonymously using our physician resource network.
So LA what kind of business case is there to justify the investment in wellbeing? What metrics of success can you point administrators or managers to?
So according to Stanford, well, MD on a survey of over a thousand physicians, physicians who practice self-compassion have low levels of burnout and vice-versa doctors who are burnt out, have low levels of self-compassion wellbeing and professional fulfillment leads to retention. In fact, the opposite is very costly. According to data, it costs the institution about 500,000 to $2 million, uh, per doctor who leaves the institution due to burnout. This includes recruitment efforts, loss of productivity onboarding. Um, it does not even include costs, attributed to medical errors and malpractice. There's also the cost of human lives. We have yet to see the cost of the pandemic and the mental health of frontline workers before the pandemic. It's estimated that about 400 physicians die of suicide per year beyond patient safety, we can do better to support mental health. This is why I do my work. There's a study showing that at time of matriculation medical students are less likely to be burnt out, have better quality of life and less depression than the general population would from their similar age groups. Then shortly after at every level of medical training from medical school to residency, to being a practicing physician, doctors are twice more likely to be burnt out than the general population from similar age groups. This is why psychological safety goes beyond team debriefing. It leads to better accountability and engagement and creates a more resilient workforce.
Yeah, absolutely language rituals and programs and role creation can all contribute to building a culture of psychological safety, which also means better wellbeing for the team. Now, as a concluding question to all of us, while we leave this talk summary up here for the audience, what measures of success matter most to you when you assess your progress towards building a learning organization and what principles of leadership do you carry with you?
Yeah. Uh, for me, whenever a resident comes up to me to talk about a challenging case, this tells me that we're creating as a more psychologically safe environment. My hope is that we can expand this to quality and patient safety discussions without fear or risk of losing our job. The pilots have figured this out. Also the humanizing aspect of our work requires us to see ourselves as followable. I believe that each one of us can play our part in awakening, compassion at work. And you can start with how we interact with each other when we discuss mistakes and bad outcomes.
When we're looking to create a learning organization and where we're looking for, how our retrospective practices feed into that, we need to look beyond the simple numeric quantitative data that has traditionally been looked at like time to respond or time to detect. Uh, we need to start looking at how many people are learning from this incident. How many people participated in the group meeting and learned there, how many people have improved their mental models. And after the fact, when there's a write up from your retrospective, how many people look at that afterwards? And over what duration of time
A measure of success that I care about is how responsive and adaptive of an organization is particularly to bad news. So let's say parts of your critical system needs a very costly and time-consuming rearchitecture and most of your engineers already know this. How long would it take for the company and management to prioritize this rearchitecture and support it with resources accordingly. It would be really unfortunate if management doesn't find out until months later and can react as quickly as competitors because the company lasts psychological safety. But imagine if the rearchitecture is planned and resourced because the engineers brought it up without fear in a timely manner, that's the type of organization I want to build. And it is possible if we, as leaders make time to listen to the team and always consider how they might be, right. Especially when they raise things that contradict with what we believe in.
So as a tradition at the DevOps enterprise summit, Jean has asked us all to leave you with something that we would like your help on. You can do it in the slack channel, or you can do it, uh, through Twitter, uh, to us. Uh, my question is, have you found specific and effective practices that help in socializing learnings from a retrospective, amongst a wider audience than those who were just directly involved? If so, please share,
Uh, please support initiatives to protect the mental health of physicians. The Dr. Lorna Breen healthcare provider protection act was unanimously passed by sent Senate on August 6th, 2021. The goal is to reduce and prevent suicide burnout and mental and behavioral health conditions among healthcare professionals. Also, thank you for those of you who are getting vaccinated. 18 months ago, doctors and healthcare workers were touted as heroes. Now there's the sentiment of betrayal from those who make decisions that put themselves into harm's way and also put us the frontline workers in harm's way by being vaccinated. You're protecting yourself and everyone else around you. So thank you.
Thank you, LA and Curt, the three of us would like to now invite you the audience to conclude our talk with a two minute mindfulness reflection LA and I actually met through a mindfulness community at Stanford, and I'll be guiding you through this reflection as you close your eyes. But before you do, I want to share the goal of this exercise. Really the intention is to give you some mental space to experience vulnerability and compassion yourself, because oftentimes we're so busy going from one task to another, without any time to think and reflect. Secondly, we want to give you the chance to consolidate some highlights from today's talk.
We now invite you to close your eyes, deep breath in and out, feel the loosening in your body with each out-breath now recall a mistake that you have made in the past that you're still holding against yourself. Bring that to your mind. Who do you see? What do you hear? What feelings are you experiencing and notice? How does your body feel? Is your throat tightened your eyebrows? Furled? Let that tension go with an out-breath recognize that being imperfect is a human condition. Just like you. I've made many mistakes and just like me. You make many mistakes in the future too.
Now put your hand on your heart and ask yourself for permission by repeating silently. May I be happy? May I be peaceful? May I be free from suffering? Feel free to continue resting your hand on your heart. Reflect on the talk today. What was the mental image you had during the talk that you want to commit to action? Make that image as clear and vivid as possible. Plant a seed of intention for the mental image to become a reality. Give thanks. Let go, and open your eyes when you're ready. Thank you very much for tuning into our talk until next time.
Unlimited users from organization
VendorDome: What does it mean to be a developer in the era of cyber crime?
Brian Fox, Sonatype; Stephen Magill, Sonatype; Sacha Labourey, CloudBees; Hope Lynch, CloudBees
VendorDome: Beyond the Buzzwords: Going Deep on DevOps with Dynatrace & LaunchDarkly
Dawn Parzych, LaunchDarkly; Rob Jahn, Dynatrace; Erin Jones, Dynatrace
Shifting Left on Production Excellence with Observability
Shelby Spees, Equinix Metal; Liz Fong-Jones, Honeycomb.io
Interview: Amanda Silver on Leadership and Remote Work
Amanda Silver, Microsoft; Gene Kim, IT Revolution
"She’s Not Dead Yet, Jim": Vulnerability and Retrospectives in Emergency Medicine
Dr. Al'ai Alvarez, Stanford Medicine; Kurt Andersen, Blameless; Christina Tan, Blameless
The Four Characteristics of Structure Needed to Get Great Dynamics
Gene Kim, IT Revolution; Dr. Steve Spear, The High Velocity Edge: How Market Leaders Leverage Operational Excellence to Beat the Competition
How Discover Financial Services Puts Engineering “Craftsmanship” at the Center of Our Digital Transformation
Dr. Angel Luis Diaz, Discover Financial Services; Sheila Lodhia, Discover Financial Services
Productizing the Network: Square Peg, Round Hole?
Girija Rao, Capital One; Denée Ferguson, Capital One; Jennifer Miles, Capital One
Continuous Delivery at Suncor's Digital Bay; Mining Maintenance Meets DevOps
John A. Hill, Suncor; Lindsey Deluca, Suncor; Joey Roa, Suncor
VendorDome: Software Supply Chain Attacks: Why They Matter and What DevOps Needs to Do
Daniel Nurmi, Anchore; Rory McCune, Aqua Security; Rani Osnat, Aqua Security
Interview: Kimberly Johnson and Christopher Porter on Leadership
Kimberly H. Johnson, Fannie Mae; Christopher Porter, Fannie Mae; Gene Kim, IT Revolution
Journey to Digitopia: The Government of Canada's Quest to Modernize Services
Marc Brouillard, Government of Canada; Denis Skinner, Government of Canada
A Radical Enterprise: Pioneering the Future of High Performance
Matt K. Parker, 'A Radical Enterprise'
Developer Productivity Engineering – The Next Big Thing in Software Development
Justin Reock, Gradle, Inc.
The Serverless Edge - Using Wardley Mapping with the Value Flywheel for combined business & technology evolution
David Anderson, 'The Serverless Edge'; Mark McCann, 'The Serverless Edge'
A DevNetOps Journey – How We Brought DevOps to Our Network Team
Hoda D Alshami, Nationwide Insurance; Mike Leuzinger, Nationwide Insurance
Chaos and Reliability: A Surprising Friendship in the Enterprise
Troy Koss, Capital One; Courtney Nash, Verica
Cloud-native DevSecOps at Supersonic Speeds (well...getting there)
Derek 'Eeyore' Bissinger, USAF; Michael Snyder, Oteemo, Inc.
Banking on Flow Metrics – Bank of New Zealand Transformation Journey
Paul Littlefair, Bank of New Zealand; BMK Lakshminarayanan, Bank of New Zealand
From Grass Roots to Brush Fire: Creating Massive Organizational Momentum Using Communities of Practice During a Global Pandemic
Jill Mead, U.S. Bank; Eric Kramlinger, Traive
A Force for Good: How TrueBlue is "Accelerating" Connecting People with Work
Jeff Dirks, TrueBlue; Carter McHugh, PeopleScout, a TrueBlue Company
The Shift to a DevOps Model While Building Our Cloud Platform - You Build it, You Run it!
Sakthi Kasiramalingam, Discover Financial Services; Bryan Payton, Discover Financial Services
Nationwide Building Society: Measure for Learning
Marc Price, Nationwide Building Society; Zsolt Berend, Nationwide Building Society
How William Hill uses PagerDuty and Rundeck to Deliver Full-Service Ownership in a Highly Regulated Environment
Rob King, William Hill; Matt Livermore, PagerDuty
Fear to Hope - How HCSC Became Nimble Through Experimentation During Peak Demand
Tashfeen Mahmood, HCSC; Dominica DeGrandis, Tasktop
Why the Dora Metrics and Feature Management are a Brilliant Combination
Michael Gillett, Betway Group
Cloud Data Journey: Story Of Adopting Cloud Technology and Modernization of Data Pipeline
Prajakta Yerpude, Discover Financial Services; Shivani Anand, Discover Financial Services
Tales From the DevOps Loop: 4 Teams Approach to 1 Common DevOps Framework
Denver Martin, Thread Research
ENSUCKLOPEDIA OF DevUps - An improvised glossary to help us for understanding of What DevOps should not be or become!!!
Jorge Luis Castro Toribio, ntt data
Governance, Compliance, and Risk in the SDLC Can Be a Fun Event!
Jeremy Castle, State Farm Insurance; Ryan Chambers, State Farm Insurance
Saving the Software Supply Chain: Critical Trends and 5 Must-Dos for DevOps
Daniel Nurmi, Anchore; Kim Weins, Anchore
Modern Test Automation, From Cloud to Mainframe
Keith Puzey, Broadcom Enterprise Software; Sujay Solomon, Broadcom Mainframe Software
Embedding Security: How We Use Automation to Reduce Time and Effort for Cisco Developers to Secure their Products
Chet Burgess, Cisco
Unlocking New Cloud-based Business Opportunities in an Industrial Company With a Novel Continuous Quality Assurance Approach
Klaus Baumgartner, Siemens AG; Dr. Peter Fassbinder, Siemens AG
DevOps and Internal Audit: A Great Partnership (Part 2)
Clarissa Lucas, Nationwide Insurance; Rusty Lewis, Nationwide Insurance; Ethan Culp, Nationwide Insurance
Making It Easier to do the Right Things: Govern, Measure and Audit DevSecOps
Dragan Pleskonjic, IGT; Colin Bell, HCL Software; Rob Cuddy, HCL Software
How's Your Bank Working From Home?
George Proorocu, ING Bank; Mihai Popa, ING Bank; Mihai Roman, ING Bank