EP 4 Managing Conflict in a Major Incident — Transcript

Full transcript

1. 0:00Hey, welcome back. So, we've already
2. 0:02laid the groundwork for major incident
3. 0:04management, but let's be real. In
4. 0:06today's world of tangled microservices
5. 0:08and super complex cloud systems, just
6. 0:11following a process, well, it's not
7. 0:13going to cut it. When one little service
8. 0:15fails, it can set off this massive
9. 0:16ripple effect, right? And that makes
10. 0:18finding the root cause incredibly hard.
11. 0:21All that complexity, it breeds chaos.
12. 0:23And that chaos, it leads straight to the
13. 0:25toughest, most frustrating part of the
14. 0:27job, the cross-functional blame game.
15. 0:30And learning how to navigate that,
16. 0:32that's what separates a simple
17. 0:33coordinator from a true incident leader.
18. 0:35Oh, we've all been there, haven't we?
19. 0:37You can just feel this quote. This is
20. 0:39the heat of the moment. You've got a
21. 0:41critical service down, tensions are
22. 0:43through the roof, and all progress has
23. 0:45just hit a brick wall. As a major
24. 0:47incident manager, you're not there to
25. 0:49just referee this debate. Your job is to
26. 0:52break it. This right here, this is the
27. 0:55exact moment where you prove your worth.
28. 0:57I like to call this the technical
29. 0:59tug-of-war. It's really the central
30. 1:01conflict in almost every single
31. 1:03high-pressure incident you'll ever run.
32. 1:05You've got these brilliant teams, but
33. 1:06they're pulling hard in opposite
34. 1:08directions. So, today, we're going to
35. 1:10walk through the playbook to manage this
36. 1:12friction, to turn all that conflict into
37. 1:14focus, and get you to a resolution way,
38. 1:17way faster. Let's dive in. To make this
39. 1:20really hit home, let's jump into a super
40. 1:22common scenario, what we call a live
41. 1:24incident bridge. Now, if you're not
42. 1:26familiar, that's basically the virtual
43. 1:28war room, right? The conference call or
44. 1:30the video chat where you get all the key
45. 1:32teams together to solve the problem.
46. 1:34We're about to break down a classic
47. 1:36situation that I promise you, you will
48. 1:38run into. Okay, picture this. It's 2:00
49. 1:41on a Friday afternoon. Of course, it is.
50. 1:43It's peak traffic time, and your
51. 1:44company's main e-commerce site is
52. 1:47failing at the absolute worst spot, the
53. 1:49checkout page. Every single minute that
54. 1:51ticks by is just money pouring down the
55. 1:53drain, and even worse, customers
56. 1:55bouncing to your competitors. You are
57. 1:58the MIM on that bridge call, and every
58. 2:00single person is looking at you for
59. 2:01answers. The pressure is on.
60. 2:04And there it is. The database team
61. 2:06points a finger at the network, and the
62. 2:08network team points it right back. Look
63. 2:10at this slide for a second. You see how
64. 2:12the arrows of blame are pointing at each
65. 2:14other? They're not pointing at the
66. 2:15problem. Right now, in this moment, all
67. 2:18troubleshooting has stopped. They're not
68. 2:19collaborating anymore. They're defending
69. 2:21their turf.
70. 2:2210 minutes go by, then 20.
71. 2:24And you're just burning through time and
72. 2:26money while the entire investigation is
73. 2:27completely stalled. This is exactly why
74. 2:30you need a strategy. The strategy we're
75. 2:32going to use to break this deadlock is
76. 2:34called the data-driven reset. It's a
77. 2:37really simple three-step framework that
78. 2:39lets you take control of the
79. 2:40conversation.
80. 2:42The whole goal here is to shift the
81. 2:44entire team's focus away from who did it
82. 2:47and onto what does the data show.
83. 2:49And you know what the best part is? You
84. 2:51don't have to be the top technical
85. 2:52expert on databases or networks. You
86. 2:55just need to know how to lead the logic
87. 2:56of the investigation.
88. 2:58So, here they are, the three steps. Take
89. 3:00a quick look. First, you're going to
90. 3:02stop the blame. Second, you'll enforce
91. 3:04something called the show me rule. And
92. 3:05third, you're going to order a parallel
93. 3:07path. Don't worry, we're about to break
94. 3:09down each one, but just think of this as
95. 3:11your personal toolkit for turning that
96. 3:13chaos into clarity.
97. 3:15Step one is all about a verbal hard
98. 3:17reset. Your job is to interrupt that
99. 3:20blame cycle, and you got to do it
100. 3:21firmly, but also calmly. You just step
101. 3:23in with a clear, authoritative phrase,
102. 3:25just like the one you see here.
103. 3:27Team, we are losing time. Let's stop
104. 3:29speculating and focus on where the data
105. 3:31stops. See what that does? That one
106. 3:34statement validates the urgency
107. 3:35everyone's feeling, and it immediately
108. 3:37gives the entire group a new shared
109. 3:39mission. You've just reframed the entire
110. 3:42goal from finding fault to finding
111. 3:43facts.
112. 3:45All right. Next up, you enforce what I
113. 3:47call the show me rule. This is where all
114. 3:50the speculation just goes to die. You
115. 3:52ask each team for objective, undeniable
116. 3:55proof, not theories, data. So, you say
117. 3:57to the network team, "Can you show me a
118. 3:59trace log that shows the packet actually
119. 4:01reaching the DB server?" And the
120. 4:03database team, "Can you show me the
121. 4:05timestamp of the last successful
122. 4:07connection?" This simple request forces
123. 4:10this really powerful shift from, "Well,
124. 4:12I think." to, "Here's the proof." But,
125. 4:14what if they still disagree? Or maybe
126. 4:17the data just isn't clear. You can't
127. 4:19just sit there and wait for some
128. 4:20breakthrough. That brings us to step
129. 4:22three, ordering the parallel path. You
130. 4:25assign simultaneous actions to both
131. 4:28teams. You're not trying to guess the
132. 4:29solution here. You are simply creating
133. 4:31forward momentum. You say something
134. 4:33like, "Okay, network, I need you to
135. 4:35check the ACLs. DB team, you restart the
136. 4:37listener service. Let's all check back
137. 4:39in 5 minutes." By doing this, you're
138. 4:41proving that action is always better
139. 4:43than argument. Okay, so mastering these
140. 4:46steps, it does way more than just solve
141. 4:49the incident faster.
142. 4:51It actually fundamentally changes how
143. 4:52the technical teams and your leadership
144. 4:54see you.
145. 4:56This is the real pivot point, the moment
146. 4:58you move from just being an incident
147. 4:59coordinator to becoming an actual
148. 5:01incident leader.
149. 5:02And that leads us to a really critical
150. 5:04question. What is it that truly
151. 5:06separates a coordinator from a leader?
152. 5:09What's the one thing that separates
153. 5:11someone who just runs through a
154. 5:12checklist from someone who genuinely
155. 5:14leads a team to a resolution?
156. 5:17The answer, and honestly, this is the
157. 5:19most important take away from this, is
158. 5:21psychological safety.
159. 5:23Think about it. Under all that pressure,
160. 5:25technical teams are often terrified of
161. 5:27being blamed for huge outage.
162. 5:29A great leader consciously removes that
163. 5:31fear.
164. 5:32The moment you shift the entire
165. 5:34conversation from who did this to what
166. 5:36does the log say, you create this safe
167. 5:38environment where people can actually
168. 5:40investigate openly, they can share data
169. 5:42without fear of punishment, and they can
170. 5:44collaborate to find the real solution.
171. 5:46Mastering that skill, that is what tells
172. 5:48everyone you're ready for leadership.
173. 5:50So, here's the crucial thing I want you
174. 5:52to remember, especially if you're new to
175. 5:54this kind of role. Your job isn't to
176. 5:56have the deepest technical knowledge on
177. 5:57the call. You don't need to know how to
178. 5:59fix the code. Your job is to manage the
179. 6:01logic of the investigation and the
180. 6:03psychology of the people involved. Think
181. 6:05of it this way. You are the architect of
182. 6:07the solution, not the builder. So, I
183. 6:10want to leave you with a question to
184. 6:11chew on. What are some of the ways
185. 6:13you've seen this blame game play out in
186. 6:15your world? And what strategies have you
187. 6:18tried to break that cycle? I'm genuinely
188. 6:20curious to read about your experiences,
189. 6:22so please drop a comment below.
190. 6:24In our next explainer, we are going to
191. 6:25tackle data-driven post-incident
192. 6:27reviews. Basically, how you use them to
193. 6:29make sure an incident like this never
194. 6:30happens the same way twice. So, make
195. 6:32sure you subscribe so you don't miss
196. 6:34that one. Thanks so much for tuning in.