B Shifter
Fire command and leadership conversations for B Shifters and beyond (all shifts welcome)!
B Shifter
Standard Conditions, Standard Actions, Standard Outcomes
Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.
This episode features Chris Stewart, Steve Lester and John Vance
We unpack how clear size-ups, shared language, and realistic tactics turn a scene into a coordinated fireground. Standard conditions guide standard actions, which create standard outcomes—and the trust to avoid freelancing and prevent avoidable failures.
• defining standard conditions for typical occupancies in your district
• using precise radio language that sets tempo and expectations
• matching offensive or defensive strategy to true conditions
• aligning tactics with staffing, arrival order, and capabilities
• training chiefs in role to build trust and succession
• measuring outcomes by all-clear, fire control, loss control
• running hot washes that separate activity from results
• avoiding benchmark overload that hides core objectives
• embracing closed-loop communication and silence while work happens
Buy “Timeless Tactical Truths from Alan Brunacini” at bshifter.com in our store for only $10!
This episode was recorded at the Alan V. Brunacini Command Training Center in Phoenix on February 10, 2026.
For Waldorf University Blue Card credit and discounts: https://www.waldorf.edu/blue-card/
For free command and leadership support, check out bshifter.com
Sign up for the B Shifter Buckslip, our free weekly newsletter here: https://lp.constantcontactpages.com/su/fmgs92N/Buckslip
Shop B Shifter here: https://bshifter.myshopify.com
All of our links here: https://linktr.ee/BShifter
Thanks for listening - please subscribe and give us your support!
Welcome to the B Shifter Podcast. John Vance, Chris Stewart, and Steve Lester is with us today. Steve back in the studio. We're here teaching in Phoenix, Arizona at the AVBCTC with Steve, and we thought it'd be great to get him back on the podcast. How have you been lately, sir?
SPEAKER_00:Been good, been very good. Yeah, just uh this week will be my 30th anniversary with my organization. And yep, so you know, I'm I'm I've rounded third base, headed for home plate in my career, and looking forward to maybe another chapter here pretty soon. So who knows? But great to be here, great to be teaching here in this facility. Love this place, love the people. Oh man, this is great here this time of year. I've never the last time I was here in Phoenix was it was 109. So uh I think we're in the 70s today. So uh a big big a great much needed change.
SPEAKER_02:It's going to be so hard to get back on that plane in Minneapolis on uh Friday because it is lovely here right now. So I'm with it. How are you doing, Chris?
SPEAKER_01:I'm good. I'm glad to be back in Phoenix as well because I've spent the better part of three weeks in Michigan and Ohio during snow and a lot of wind and cold temperatures. And yeah, that's now I'm very clear why I actually do live here.
SPEAKER_02:Chris has been traveling for Blue Card and was in Benton Harbor, Michigan, on the shores of Lake Michigan, where like Gordon Lightfoot songs just emanate from the lake because of the weather and the gales and the frozen, and and it it is it is very, very cold. So I'm sure you're happy to be thawing out. Uh today we are going to talk about something that we say a lot in our classes and and in our media, and it's been part of the blue card program forever. I and I know seen Chief Bernicini classes with it, and it's standard actions, standard condition, standard outcome. Or sorry, I should say that the other way, standard condition, standard actions, standard outcomes. And we want to break each one down and talk about it because it is worth breaking down. I don't think a lot of times we get a great explanation of what that means, or sometimes that gets lost. So we wanted to dig more into that today and really talk about what those standard incident conditions starting off with look like. And when we say standard incident conditions, and I'll start with Chris on this one, what are we really talking about? And and why is it that some departments or individuals have struggles trying to define that?
SPEAKER_01:Yeah, so I think a lot of times with with many things in in in life and in incident command, right, is uh we take the words very literally and then we try and break them down into, all right, this is this is exactly what it means in a very, very narrow fashion. Well, if anybody knows anything about Alan Brunicini, he was the man of being able to take very very complicated uh things and complicated systems and processes and breaking them down into incredibly simple explanations. So that's, you know, if you want to look at, you know, Albert Einstein's, you know, one of his favorite quotes is if you if you can't under or if you can't explain a complex problem simply, you truly don't understand the problem, right? So that's kind of a little bit what we're talking about here when we when we get into these kind of subjects. So I think what the, you know, what I was taught and what I understand about this idea of standard conditions, standard action, standard outcomes is we have to find the commonality and we have to be able to define the standard elements of what we typically respond to in our response areas. So that may look different for me in the city of Phoenix than it does for Steve and in the Atlanta area, and it does for JV in the Minneapolis area, right? So we need to be able to establish what are our standard conditions typically when we show up on the on the on the on the more common types of fires that we go to. So what are the typical standard conditions that we would experience at a as a residence or at an apartment building in any one of our given response areas or jurisdictions, and then be able to communicate and train our folks on these are the things you need to be looking for that are typically standard with regards to critical factors. And then then that helps us then be able to identify when we have things present that are not normal or not common or maybe are even uh more dangerous or problematic for us to be able to more readily recognize that and be able to say, oh, this is different now because of this. I have a clear idea in my head what the standard conditions are when I show up on a on a two-story apartment complex in my first do, and now I'm showing up and things are different. Oh, I've got, I do a 360 and I've got, you know, three stories from the Charlie side. And maybe I have a fire down below, which is much different than a lot of the other places that I tend to go to. So it gives you that when we when we know and understand the idea of standard conditions, it gives us the ability to start to train people, help people understand that. And then it gives us the ability to recognize when things aren't normal, when things aren't as if they they usually are, and then we should should respond appropriately and make the the necessary changes, you know, when we talk about our action and and and our outcome. So it's a it's a way of well, well, we're balancing a couple things here. We're balancing that out of, well, all fires are the same. Well, no, they really aren't. We should be evaluating each one independently. We can find some commonality in them, and we can find some, you know, what we again, standard conditions that we may experience at these, but then we need to evaluate it for what it is in the moment to be able to figure out, okay, what what is important right now? What is what is critical, and what do I need to build my incident action plan around to either mitigate or avoid so something bad doesn't happen to us. So that idea of standard conditions as well as the actions and the outcomes really was meant to how do we start to train our folks on looking and sizing things up and measuring things that are more normal and and we're comfortable dealing with versus things that we show up and like, ooh, that's bad. We need to, we need to do something markedly different here to keep ourselves out of harm's way, to protect the community and maybe solve this problem. So it's we're definitely talking about the art rather than the science of incident command and knowing understanding this when we talk about these things.
SPEAKER_00:You know, and unfortunately, a lot of times, you know, a lot of what we interpret as standard conditions comes with experience. And the only way to be able to understand some of those standard conditions is to go to fires and see it yourself and sometimes even have to make some critical mistakes from time to time where we have lessons learned. We just had a fire recently in my organization where a basement fire was missed. A walk around was completed and they stated the basement on the walk around, but they didn't force the rear door to ensure that the fire wasn't in the basement. And in fact, it was, and the second do company, when they went in to do a search, uh, found a hole in the floor, and we were able to determine at that point that the basement the fire was in the indeed in the basement. Uh so yeah, those things are are definitely learning points. Luckily, nobody got hurt, and we had a nice critique and an after action review, and you know, we made something good out of it, but a lot of that just comes with experience, you know, and you have to go to fires in order to do that.
SPEAKER_01:So that so Steve is bringing up a fantastic point and about that experience because we do, you know, in a general term lack experience, right? Because of the age of our the service. I I'm not sure that that's a new problem, but we're definitely feeling it today. And when we're able to define standard conditions and and use examples like Steve's talking about, then we're able to actually share some experience that they may not have gotten individually, but hey, we're we're gonna we're gonna try and package this experience so you can take at least a little bit away from it, even though you weren't there and you're and and and hopefully you make a a better decision or a different decision when when you're you know faced with that.
SPEAKER_02:We we talk about how different people size that up, the conditions, you know, what famously worked with a guy that would arrive and just say, we've got a fire, you know, without any other explanation or size up. How does standard condition recognition and reporting those conditions reduce chaos and make us better on the scene? And you know, what uh because the transverse of that is it does create chaos if we don't recognize it. So let's let's spend some time with how does that reduce chaos and what can we do to uh better recognize those conditions, other than just experience.
SPEAKER_00:Well, you know, uh, JV, I think that starts with the first do and the initial radio report. You know, that's why we we are so mindful of that uh through this blue card program and how we teach how we want to be as descriptive as possible in our initial radio report to try to paint the clearest picture for all those units that are coming in. You know, one thing we still struggle with in my organization is stating the strategy. That is for some reason still a stumbling block for us as we transition into the blue card system for now, our seventh year. We still struggle with that on a daily basis. So, yeah, I think that's something you know we have to concentrate on that initial ready report and make sure that we're hitting all those points to be as descriptive as possible. Just like we talk about the difference between smoke showing and working fire. Smoke showing may not necessarily mean we're pulling a handline from our from our apparatus. We may go and investigate first, because if it's a pot of beans on the stove or or whatever that looks like, we may not need to deploy a hand line. But when we say the term working fire, that means we are deploying hand lines from our apparatus and we're going interior for fire attack. So I think those just those words matter. You know, we say that often in these trainers and when we go teach cert labs and and all the things that we do here at B Shifter, words matter. And so I think it's very important that we paint that clear picture.
SPEAKER_01:Yeah, that's huge, right? So you can in in a system where we're training new firefighters, hell, even old firefighters, doesn't really matter. But when we can define and demonstrate standard conditions and then define, demonstrate, and have them practice communicating using standard language that we all know and understand. That when we show up and we say we have nothing showing, smoke showing, working fire, defensive fire conditions, I know exactly what all those mean and what really the kind of the consequences or the actions that are going to be based on those, but that when the IC starts assigning people. That's that's a huge part of actually having an effective training system and and helping people better, you know, process and then communicate that stuff. Because to your point, when when an initial radio report and a follow-up report is done in a pretty thorough manner, in a in a calm, confident type way, that tends to set the stage and permeate an incident throughout, right? And people will try and match that when they communicate on the radio. So, so the ability to create this environment based on some knowledge and then based on how we're going to communicate drastically impacts the overall system or it can just impact the overall system. Conversely, if we show up and we're screaming and we're not making sense, that tends to ramp everybody else up and they start screaming and not making sense. And and and then we're not going off of any clear standard or process or you know, something that's very it's easily relatable for everybody.
SPEAKER_00:You know, I go back to strategy. I mention this a lot when I teach cert labs, you know, just a simple statement of the strategy. You know, if if Timmy and Johnny are riding in the back of a ladder truck on the way to a fire, and they may be going non-emergency because the first dude's not there yet, whatever the response model looks like. And they're back there, you know, and they're shooting the bull, they're talking about, you know, the ball game they watched last night or how many yards they got to go cut in the morning when they get off duty or whatever. And then that initial radio report comes in and they hear offensive strategy, well, that immediately sets the stage for what they're gonna be doing when they get there. They're gonna start putting on their SCBA if they have them still in their jump seats. They're gonna start thinking about what tools they're gonna be bringing off the apparatus, what their assignment's gonna be, whether it's search or ventilation or whatever that looks like. The other side of that is if they if that initial radio port calls for a defensive strategy, well, now they take a whole different mindset, right? Now it's gonna be, hey, we're gonna slow down, pump the brakes, we're probably gonna spot the apparatus where we need it for defensive operations, we're gonna get the jacks down, we're gonna prepare for uh bucket operations or whatever that looks like. So just that little term of strategy, offensive or defensive, can set the entire mindset of that first alarm that's coming in.
SPEAKER_02:What I can think of, uh, and it and it seems more in the past, I can't think of recent examples, but the failure to recognize that we've got defensive fire conditions and we end up with an offensive incident action plan. That's a that's probably the biggest failure in realizing what the conditions are and being able to identify them, right? Most definitely.
SPEAKER_01:Yeah. So so what can we do with that, right? Us as training folks with our with our with our members, we need to be able to define for them, all right, when we show up on these occupancy types, whatever it is we're talking about, commercial or residential, and we have these conditions and and they appear to be that, you know, well involved in the space. And then we do a more thorough evaluation of a 360, and then maybe we confirm, yeah, we've got fire throughout this thing, or we have fire through the roof. Well, that's a standard condition for defensive fire conditions. And so then the system should respond and move that way to a defensive fire condition rather than having this mindset of well, always show up and be offensive. The vast majority of time you will, but we tend to stumble a little bit oftentimes when we show up with defensive fire conditions, which are like, oh, we we constantly perpetually train for being in the offensive strategy. No, we need to set this up and and and implement a defensive IAP from the very beginning. So that can help people start to understand and better recognize you know these conditions on the fire ground.
SPEAKER_02:Anything else on conditions before we get into actions?
unknown:All right.
SPEAKER_02:I think we I think we pretty well define that. Beat that up. Talking about standard actions, then the actions that we take that address the conditions that we observe. Why do standard actions really speed things up instead of slow things down and and give the company officers tools to deal with the problem?
SPEAKER_00:Well, I mean, I think that starts with uh we have to ensure that our actions are matching those conditions, right? So we go back to step one and we talk about the conditions like heavy fire upon arrival, you know, fire coming from two windows of residential structure. You know, you know then you've got at least probably two rooms of involvement. Might be a good idea to do a quick hit before you go in and apply some exterior water, right? I mean, there's studies after studies after studies that show that that is prudent. That's a prudent tactic to do. So I those, you know, the big thing about the actions are it is that they have to match the conditions that you have. You know, we go back to the NIOS reporting and everything else that we see, you know, a lot of times you f you look, you read through these NIOS reports, and it's offensive tactics or offensive actions during defensive fire conditions.
SPEAKER_01:Yeah, the the the way the idea of standard conditions was best explained to me throughout my career was the fact that when we show up, we don't tend to do very well when we're making up new operations, when we're making up new tactics because we either know, don't know or understand, or we haven't practiced, or we're not, you know, we're not sure what to do here. Well, so when we talk about standard actions, is all right, when we show up at a res on a residential occupancy with fire conditions like Steve described, is okay, what is standard for us? Standard for us is evaluating this, the both the officer and the firefighters evaluating this incident and making decision, all right, is the is do I have the opportunity to flow water from the exterior to control this fire prior to me making the entry to the inside? Is that a standard expectation for us, right? So if we talk about standard actions based on the conditions, then that should become no, that's normal for us to do it. I I'm not worried about getting in trouble if I actually do that, right? Because we've talked about it, we've trained on it. That's what I want you to do. And then, and then when you'd move to the inside, what are the standard expectations for us with regards to advancing hose lines and advanced and searching, right? Is it done in combination with one another? Is it done independently of one another? It's all dependent on the standard conditions and the resources that you actually have to execute that. Absolutely, right? And tying those, the resources, the number of people, the number of companies you have to what that standard action looks like. Because if your standard action is to deploy and initiate fire attack and search operations in the same exact way as, say, the FDNY does, except for you're in, you know, middle town USA with three people uh showing up on the first apparatus and two more dudes showing up on another truck in 10 minutes, you're you you're out of balance. That's right. You you are not doing, you're not gonna be able to execute that in any real way. So your standard actions have to be built and based on the not only the conditions, but your response, resources, personnel, and capability of those people. And and make it very, very clear to everybody when we show up with three engine, a three-person engine, and nobody else is gonna be there for five or ten minutes, this is what is reasonable for us to get done.
SPEAKER_00:And I I think that's a that's why we have we do a resource determination at least uh three times on a working incident using the blue card system, right? We determine our resources on our initial walk around, our initial ray report. Then once we get our 360 in and we take in more information, we do another resource determination. And then when the chief gets there and evaluates and does a command transfer, we do a third resource determination because we have to determine what's coming behind us and do we have the resources coming to do what we need to do.
SPEAKER_02:How how does standard actions protect us from having emotionally driven actions on the scene? Because it seems like if if it's uh if there are plays that we've practiced, it there's gonna be a lot of trust and security with that versus people doing their own thing, ergo freelancing, really, right?
SPEAKER_01:Yeah, I it the comfort and safety that I think it provides us is I know and understand what my capabilities are, and I know and and as a firefighter, I know and understand what you want me to do, right? Based on what we have going on here, the conditions, and based on what kind of rig I'm showing up and what kind of how I'm equipped and how I'm staffed, right? And and then that is driven by the IC's plan, right? It gets communicated, we get assigned. And so when you show up, it's not just me looking at this, taking my best guess on what I think I should be doing right now, and and then just doing it without without a lack of communication, without a level of accountability, and without any any connection to an organized, well-communicated plan. So as an IC, standard actions help me to be able to, when I say, okay, I want you to stretch a line to this location, knock that fire down and get an all-clear on the first floor of this house, that I have a good idea how that's gonna happen. And we're not gonna invent a new hose stretch doing it, and we're not going to if the conditions allow us to go in the front door to get to where we need to go, that's what we're gonna do. We're not going to ignore the simple and obvious things that we can be able to do, and all of a sudden, all the firefighters are bailing in windows because hey man, that's what we that's what we did at our last hot training. So we we gotta pay attention to that a little bit and no one understand. Now, there's time and place to go in windows. I'm I'm not saying not, but but when it's straightforward, we should do straightforward things.
SPEAKER_00:Yeah. And I and as as the chief of training from our organization, I'll get on my training soapbox here. You know, firefighters don't know what they don't know, right? And it's up, it's up to the battalion chief or whoever's over those firefighters at a at the larger level, outside the company level, to let them to let those firefighters know what the expectation is and what the standard actions are. And the only way to do that, well, there's two ways. Number one is drilling. You gotta get the you got to get the crews down at the training academy or wherever your your organization trains, and you have to show them what the action is, what the expectation is from that level. And also it it boils down to kitchen table conversations, you know. It's it's that battalion chief making his rounds to his stations and sitting down with those crews and says, hey, if we have this, this is what the expectation is and this is what you should do.
SPEAKER_02:Doesn't that build a level of trust then between the crews and that IC or that BC, the response chief, whoever it is, they have a level of trust that those actions that are going to be carried out are the appropriate actions. The IC, when they they ask for it or they, you know, have that order, they know exactly the way it's going to work out rather than some either freelancing or new technique or something. That they've never even talked about.
SPEAKER_00:Right. And some people may say, well, Lester's getting into an SOP-based command system. That's not even close to being an SOP-based command system. Setting expectations has nothing to do with that. The incident commander is still going to give the order. We're talking about the how, you know, the how to accomplish that order. The how the expectation that uh this is what you're expected to do when you receive this order or assignment.
SPEAKER_01:Yeah. That that trust comes from clear communication expectations. So this is a great place to talk about like accountability model stuff, establishing the expectation, training to those expectations, monitor how they're doing in the real world and give them feedback. And then if something needs to be fixed, take some responsibility for it and go, all right, that didn't the the last couple of times that didn't go the way we wanted it to go. Let's get back down there and kind of re-establish our what it is that we want. And so, and then the trust also comes from when it appears like I should be doing whatever the standard evolution is here, and I as a company officer recognize something different that's going to cause us to do something different. I'm going to communicate it. I'm going to say, hey, I've got an issue here. Here's what we're doing. Right. And then there's no surprises to anybody. And that that keeps the IC informed. The IC is not going, I don't understand why they're doing that and try and try and get in the way of it. And so that that's a that's a really is a two-way street. And I do like the idea of that trust, but it has to be built on the things that you guys talked about.
SPEAKER_00:And and to me, those have to be that can't be something for my organization, it can't be completely organizational at the organizational level. And I'll give you a good example of that. So years past before I took over the chief of training position, we used to have what we would call a spring drill and a fall drill. That's where the entire department would come down and do one particular drill, right? And it was up to the training division to design that drill. When I became the training chief, I did away with that. Reason being is our particular our jurisdiction, our county is so diverse. We have on one side of our county, we have a 28-story high-rise building. On the other end of the county, we have 50 acre horse farms. So those we need to be training on everything from standpipe operations to doing long distance split lays, relay pumping, things like that. Being so geographically diverse, we cannot design a drill that fits our entire department. So instead, I handed that down to the battalion level. And so the battalion chiefs and their captains are expected to determine the strengths and weaknesses of their particular battalion and design drills that are going to improve their weaknesses and increase their strengths. And they come down to the training academy and we support them logistically, however, whatever their needs are. If that's live fire, we support them with 14 with N FPA 1403 standard. We do whatever we we can or whatever we have to do to make sure that they're training what they need to be training on. And that their training and their drilling is tailored for them in their geographic area and their response.
SPEAKER_02:Part of that, too, is having that chief train with them. And we talk to a lot of departments that will tell us, hey, this would work for us, but our chiefs don't train with us. And I'm talking response level chiefs, battalion chiefs, district chiefs. That's a crucial part of this. And and when we say train with your crews, at least from my definition, I'm interested in what you guys have that defined in. I don't mean getting on the end of the hose line. So often this is like showing people how great of a firefighter you were. And I'm not scared to get dirty. So I'm gonna go roll hoes and climb ladders, and that's all well and good, but that's purely recreational. I think as a chief, and I'm interested in your opinion on this, as a chief level officer, you go train in the role that you're going to do on the fire ground. So whether you're a division boss, you're an IC, you're a support officer, however that looks for your organization, play that role. So your folks get used to you being in that command position on the training ground. So it's that much easier on the actual fire ground. And it also exercises the entire system. So you know how those things are going to go in real life outside of a simulation lab. What do you guys think of that?
SPEAKER_00:I can give you an example of when I was a battalion chief, I would design a multi-company drill, battalion level drill. And just like you said, JV, I would, I would, I would come in as that I see number two. I expected the first due officer. Well, first around, let me back up a minute. I didn't give them the scenario, right? Because that to me, that takes away from the drill. That's that's not a drill if you if you know exactly what you're gonna do, right, when you get there. So it's basically three, two, one, go, you know, and then you give them the scenario when they arrive on the scene, or they go by what conditions they see if you're using theatrical smokes with machines or if you're using live fire. And then that that first two officer would start out as IC one, just like we do here in the SimLab. And then I would serve in that IC2 role. I would come in, give them the unit rundown, expect the command transfer to go, and then I would pick up the incident, go on. Typically, when I do those battalion drills, we would do at least two scenarios. And then the the second scenario, I would step back and allow one of my captains to step into that IC2 role because they're the ones that are going to be riding up in my place when I'm when I'm not there. So I want to make sure that they get experience and exposure. Not only them, but I want the guys working under them to be exposed to working with them as IC2, right? So I thought that was very important. So I would step into the role first, and then for the second scenario, I would step back and allow those captains to ride up in my place.
SPEAKER_01:Yeah, I think, I think the frustration that we're hearing from, you know, from a decent amount of folks across the country is is that lack of participation by their boss demonstrates indifference and value to the system and what the work they're doing. And so I think that's a huge problem. In fact, it's a gigantic failure on those bosses and those leaders that are are that are that are not participating to the degree that like you and Steve are describing now. And the there's the physical training part of getting used to the operational, how things are going to go with the the chief officer playing their role in position, whether it's whether it's IC uh stuff or division boss stuff, right? Because that both they both need to be exercised. And then, but it's also oftentimes I feel and I've seen where the chiefs aren't engaged because the chiefs are probably the least informed person there, right? With with regards to how things should happen on the fire ground today, with regards to information about building construction or or modern fire behavior, or maybe our more recent tools and adaptation of our tools and how we actually do things, you know, search techniques, when to search, how to search, access points, and and when we should default to search and when we should when when we really need to deal with fire control beforehand. And so that often is a lack of their comfort in doing that. So they're going to elect, say, oh, you guys just go do what you think you need to do, or I'll I'll tell you if I like what you're doing. And that's that's that that is a huge problem. And when something bad occurs on their fire ground, there isn't a single person in that organization that should be surprised because that clearly was set up due to the lack of participation, the connection that the bosses or what, you know, whatever level those bosses had. And and and and much like Steve, Steve's being super deliberate about no, I'm gonna be the IC here, and then I'm gonna move somebody up and I'm gonna, I'm gonna mentor and help and coach somebody in that position because that's that's a likely thing for them to have to do versus the guy that just showed up that I experienced in my career is no, no, we're gonna let the let the young guys move up here and do this because I've just done this so many times.
SPEAKER_00:That's also a big buzzword these days, is succession planning. Yeah. Yes, it is. That is that is what that is, is succession planning.
SPEAKER_01:Yeah, yeah. And and succession planning gets used very positively and it gets very misused, you know, significantly for those who want to misuse it.
SPEAKER_02:So go train. Go train with the crews, understand what their capabilities are, what they're working on. Doesn't mean you have to be an expert at everything either. I think when you're the jack of all trades, you're really the master of none. Uh during my career, I wasn't a big tech rescue guy, even though I spent a little bit of time on the tech rescue team. It just wasn't my forte. There were other things, you know. I'm I'm not a ladder guy. There's uh I'm not I'm not good at that stuff. So I'm I'm gonna lean heavily on the phone. That's right. Well sorry, ladder guys. Okay, let's uh segue over to standard outcomes. Because that's really where we we want to end up. And it's that success, really. I mean, we're looking for success. So how how do we define success with our standard outcomes?
SPEAKER_01:Well, there the success or the outcome is predicated by the conditions that we showed up to and the effectiveness of our actions. And so if we show up to defensive fire conditions and we employ the right stuff on the outside, we shouldn't expect us to miraculously turn deadly defensive fire conditions into survivable offensive fire conditions. That doesn't happen very just about never, I guess would be the best way to say that. So, so our outcomes and our expectation for our outcomes have to be aligned with the the conditions on the front end, what we experienced, how effective we are at our actions. And then the officers need to have a reasonable expectation of what should be occurring based on those two things. And that may change a little bit, right? And then that that helps us number one define what success looks like. Hey, based on what we showed up today, this is what I would have expected. Essentially, you can ask the question, how'd we do, right? Did we did did did this end the way we wanted it to end, or didn't it? And if it didn't, why? And was it something we did or something that was unforeseen we didn't necessarily weren't able to plan for? And and so we can make adjustments there. So that that standard outcome is yes, we want to win every time, we want to be able to get it effectively, get in all clear, locate victims, control the fire, do all of these things, but oftentimes the conditions and our effectiveness at the actions will dictate that. And then we as ICs need to know what's a reasonable outcome for us based on what we have going on right now.
SPEAKER_00:Yeah, and I I'll take all three elements of what we're talking about here: conditions, standard conditions, standard actions, and standard outcomes. I look at that as like an equation, right? Think of it as a like an addition problem. You know, conditions plus actions should equal outcomes. Plug numbers into that. Two plus two equals four. Two plus two doesn't equal three. So if I get there and I look and I'm thinking, okay, here's one problem, my conditions, here are the actions that are going on. Are these equaling my outcomes? Is two plus two equal equaling four or is it equaling three? If it's equaling three, then I need to make a change so that it equals four. I hope that makes sense. It does. It does, yeah.
SPEAKER_01:So, you know, to me, you're the first guy to do math on here, by the way, boys. So you know.
SPEAKER_00:You heard last week. We were not a number of math last week. Sorry, I'm a number two. No, I like it. But that's kind of the way, you know, that to me, that is strategic evaluation, uh specifically on the behalf of IC number two. IC number two pulls up, you know, three, four assignments have been made. He has to be able to look at that building, evaluate the conditions of the building, look at what actions are going on, visually not only visually, but via his tactical worksheet that hopefully he's been keeping up with on the way to the scene, if you're in that kind of system. And then looking, are we getting the outcome? Is the sum of the problem equaling those factors, right? And if they're not, then changes have to be made and they have to be made immediately so that they do.
SPEAKER_01:Yeah, I think that's actually a great way because whether it's too much or too little on that on that equation or the the the the sum part is all right, you need to adjust and adjust it correctly. So I thought that's a good comparison.
SPEAKER_02:What's the danger of celebrating activity versus outcome? You know what I mean by that? Like, oh wow, we got an interior fire attack on this, and they're high-fiving. Meanwhile, we just trash the place because we opened doors we shouldn't have, or we uh you know ended up accessing or firing up the PPV too early and causing a fire spread. So let's talk about the difference because what we're looking for is positive outcome, not just activity.
SPEAKER_00:I think that goes back to after action review. It goes back to hot wash, specifically hot wash. I think a lot of that is taken care of in the driveway uh of the of the residents after the fire, you know, being you know, that IC number two gathers everyone in the in the on the driveway and they take it from step one from hey, engine one, what did you do? Let's talk through it. Engine two, what did you guys have going on? Ladder one, what were you guys doing? Here's how how I thought the command transfer went. And you just walk through the steps of that and you talk it out and just say, next time, let's think differently and let's do it this way. And that there may not be a problem. It may be a high fiver. And everybody and hey, I I love those where I could just really, you know, gloat to my guys about how great of a job they did and and high five and and all go back to the house and have a nice supper, you know, but sometimes that's not always the case, and we have to hash that out. And, you know, I I I I used to tell my guys when when we would do these, hey, this none of this is personal, it's all constructive, right? And so don't bring your feelings and take it constructively and we'll move on.
SPEAKER_01:Yeah, I'll take I'll look at it from a different perspective is should we automatically assume we failed because we had to go defensive? I I I not necessarily, right? Sometimes the conditions, the situation is set up against us, period, from the get-go. And in spite of our best efforts, that's the way this thing was going to go. So, what is the outcome? What it what could we actually save here? Did we do a good job at saving the things that were actually sable and and not get ourselves jammed up in the process of actually doing that, right? And so I don't look at that as a failure, right? In in a lot of cases. Now, if we showed up and and we went defensive because we couldn't hit our ass with either hand, well, then that's a that's gonna be a different conversation, just like you said. And uh please leave your feelings at the station. And but we need to know and understand based on the conditions and how well we did, what's a reasonable outcome. And you're right, it's not we're not gonna celebrate necessarily the outcome and the or the actions in the same way that we celebrate the outcome, but we should define what we did as a good job and what we need to improve.
SPEAKER_00:I I'll give you a great example of that. Uh, the three of us sitting here at this table probably have a hundred years worth of fire service experience, all three of us combined. Could you can you think of a wind-driven fire that was vented upon arrival that you didn't have to go defensive on? Sometimes you can pour all the hand lines in the world on that fire, and you can't control the wind, and you can't control the ventilation opening that was established before you got there. And so sometimes, no matter how good things go, sometimes we just lose a game, right? Even the best ball team in the world is gonna lose a game eventually. And so that's just how it goes, you know. And you're right. Yeah, I I can't think of one.
SPEAKER_02:You know, that's a loser, right? Right. Exactly. It's gonna be a pretty standard outcome for those conditions that we exactly in spite of how awesome we think we are. Yeah, yeah. So how how do we measure positive success without getting lost in too many benchmarks? Because we we we talk to departments from all over, and you know, there's guys this week that they're they're adding in a bunch of different benchmarks that their agency wants. So, and that's how I see number two is measuring the outcome from the outside is all these benchmarks. Can we get lost in too many benchmarks? I guess that's the question.
SPEAKER_01:Yeah, I I think we can, really. Because when it comes down to it, regardless of whatever else we want to put in and around it, we're looking at the true tactical objectives. How effective were we at getting an all-clear? How effective were we at fire control and how effective were we at loss control? Right. And so we can put things in that maybe help us describe or communicate or or or or you know, give us intermediate steps to getting to those things. But in the end, they should the incident should be evaluated on our effectiveness at achieving those three things. Now, again, it's got to be reasonable, like we were talking about. We got to be set up for success or the con the situation has to allow us to be successful, but we are the ones that have to actually show up and do it. And so evaluate that action as it relates to the true fundamental tactical objectives, not you know, these intermediate benchmarks that we may put in place, you know, trying to get there.
SPEAKER_00:Right. And I I think the new NERS system that's uh gone into effect has has thrown an extra some of those extra benchmarks in there for knockdown, water, while run the fire, yeah, things like that. So yeah, I would agree. I think you can you can benchmark something, an incident to death at some point.
SPEAKER_02:But how does connecting standard action, standard uh condition, standard action, standard outcome? I keep mixing that up, change the way that then that dovetails into our after action review, especially the system that we're using now.
SPEAKER_01:Well, uh, we definitely have standard process. That's the strength of this incident command system is standard process. We're gonna begin the incident command system the same way every time. We're gonna communicate the same in the same manner based on the conditions that we have there. And there we're we are working to the best possible outcome based on those conditions and our effectiveness or our capability or our resources, you know, what we can actually accomplish. And so I think it, you know, if you take our after-action system, and and I'll even throw in our evaluation forms that we use for IC1, IC2 support officers and seniors advisors, is there is they're measuring a couple different things. The AAR system is really good at objectively looking at how did we do from a communication standpoint of effectively utilizing the system, when, how, and what we communicated. And then the evaluation sheets look at, all right, what kind of decisions did we make? Did we actually understand what was going on, come up with a decent plan, get companies in place to be able to do that? And how did that relate to the outcome? So I think the two of those together create a really strong system for being able to measure and say that we did a good job. And and it also doesn't let us just become, you know, enamored with, man, this whole overall incident didn't go didn't go great, but I don't know, I'll pick something like, man, we cut we cut a whole hell of a hole in the roof. And then so the incident becomes about that hole, not about the not about the outcome or the tactical objectives. And that's that ain't that's not a good thing either.
SPEAKER_00:Right. Yeah, you have to look at the overall incident, the overall outcome.
SPEAKER_02:You guys have anything else on this topic before we I I think it's good that we dove into it and really broke each one down because we talk about it a lot. So it it really merits that conversation.
SPEAKER_00:Aaron Powell I say all the time, you know, that I I think that that particular slide in the day one PowerPoint presentation is probably one of the most important slides in the entire program, you know. And there again, it's all about strategic evaluation for that IC number two, pulling up and looking at here's the conditions of the building that I see, here's the actions, the the assignments that have been made. Do are these matching up to produce the outcome that we're looking for? And if not, we've got to make immediate changes to that. Whether that's pulling the trigger on a strategic shift immediately or making more assignments in order to correct the the actions and to overall to it to improve the outcome.
SPEAKER_01:I just want to say it's about the system.
SPEAKER_00:The system.
SPEAKER_02:It's about what? The system. Yeah, that's what our boss says. It's the system, guys. Hey, you ready for a timeless tactical truth from Allen Bernardino? Let's do it. All right, here we go. Timeless Tactical Truth from AVB, and this is available at the B Shifter store. If you want to get this book for 10 bucks, it's well worth it. Do not think you are communicating just because you are talking. There must be some information exchange sign that the message got through.
SPEAKER_00:How do we how do we ensure that the message got through in our with our communication model? I mean, that's the order model, right? First thing we got to do is contact the senders, got to contact the receiver and get their attention. We push that a lot, you know. Even even if a crew just went level one, you know, you got to get their attention and make sure they're ready to get for that assignment. You know, I'm I was bad about it as a company officer. As soon as I went level one, first thing I want to do is jump out the truck and finish, finish turning out and grabbing my tools and telling my crew what my expectations were and things like that. And you have to you have to be ready for that assignment. And then you got to communicate properly, right? You got to give that, once you get their attention, then you have to give them the assignment and then expect that assignment to be repeated back so that you know that that that assignment has been received, right? It's closed loop communication.
SPEAKER_01:Yeah, so when when we experience, and we probably all have experienced it and hell, and we may have even done it, you know, uh unconsciously. But when we're communicating as ICs on the fire ground based on how we feel, or based on, you know. I'm gonna I'm gonna demonstrate how often. On my Amazon I see by how I'm gonna communicate, and I'm gonna communicate a lot, and I'm gonna tell people what to do, and I'm gonna I'm gonna micromanage and I'm gonna get in their business. Like we've seen that. And we all know, we all hated it too, right? And so we all know that typically it created division amongst the folks doing the work and it didn't do anything to make the incident better, right? And so that that idea of no, we have a system in process, we're gonna follow when we communicate, and I don't have to, I don't have to communicate all the time to uh ensure that we're doing the right thing. Like I we're gonna train and provide expectations, and then I'm actually gonna have the opportunity to shut up when I should and allow those things to happen because then I'm gonna expect that information to come back to me to be able to start to answer the and and solve the objectives that we're looking for. And and if somebody needs help, then I can put plug help in to help them, you know, accomplish whatever is they need to do. So it's a it's a that's one of those things where when we start to experience it outside of just the order model itself, is uh we got to get a mirror and say, okay, how are we actually communicating here?
SPEAKER_00:You know, we take a lot of flack with the blue card system about tying up radio traffic, too much radio traffic, too much talking. And yeah, I when we give assignments and we and we do our initial radio report, those things are lengthy, but they're lengthy for a reason, so that you only have to give that order one time. You only have to transmit that report one time, right? Because you know it's understood the first time. And in essence, uh it may seem longer, but it's really saving time in the long run. Because when the work starts getting done, the radio becomes silent. And I can tell you from a battalion chief perspective, when I was a battalion chief, that's at be in the beginning, that can be a very eerie feeling when that radio goes silent and you're when you're first experiencing the blue card system, and it's like, oh well now what do I do? You know, because the radio is quiet. And so you you try then to you wanna you want to fill the air, right? So then you start asking for canned reports and you know, and then eventually if you if you're critiquing yourself and you're listening to your incident audio, you're realizing, hey, I'm talking too much. I need to shut up and let and let my folks work, you know.
SPEAKER_02:And that that's the beauty of being a senior support officer as I have been in the past, is I'll look at an IC and say, embrace the silence. Because I could see they've got the microphone in their hand and they want to talk so bad, but what there's nothing bad going on. We we've got great conversion, the smoke velocity is changing. It looks like we've got success on the fire ground. Don't get on the radio just to get on the radio. And then back to you know, practicing our communication, our words mean something. That's what we do in Blue Card. So whether it's at the command training center or in the field, we're using the same process with command and the same words. So those words mean something. Right. You know, a non-Blue card department uh gave an order and got an order of come on up and assist. Well, that's a wide open door to do whatever they wanted.
SPEAKER_00:You might as well just say freelance.
SPEAKER_02:Yeah, and that created a lot of other radio traffic and confusion. So being prescriptive right away and being exact and precise and those words meaning something really lessens the communication overall, allowing the airtime to be open for priority traffic or God forbid a May Day.
SPEAKER_01:Yeah, it's highly entertaining. You can listen to the people that are critical about it, and it's not hard to figure out where they work. And then it's not hard to go find incident audio for their departments and listen to the complete, utter nonsensical drivel that comes out of people's mouths on the fire ground. And it does not make the incident any better. So it's uh I I find it entertaining.
SPEAKER_00:And it's that and it's those types of organizations, those types of incidents where Maydays are missed. Yep, yep. Fact. Yep, that's the truth.
SPEAKER_02:Well, any final thoughts, guys?
SPEAKER_00:Glad to be here, JV. Well, it's good to see you. Yeah. And you you we're gonna be in your place next week. Yep. Uh 17th and 18th. 17th and 18th, Cobb County Fire Training Center. We've got uh a Mayday workshop coming. I think we may have just a couple of seats left. Are we in that big fancy auditorium? Absolutely. Right on. Yeah, yeah. We're uh we're looking forward to hosting you guys. So yeah, it's gonna be a good time. And then we've actually got a trainer there as well coming up in June. Any seats for that, or is that just a I think there might be a couple of seats open left in that one as well. Great, great.
SPEAKER_02:You can go to uh b shifter.com, click on blue card, and then go to our events to check all those out and get the dates and sign up for them. So there's still availability if you're listening to this podcast. And let's see, it's you know, before the 17th and 18th of February, you have an opportunity to go to that May Day workshop if you're around Cobb County, Georgia. Yep.
SPEAKER_00:Also, I'm gonna be uh next month, I'll be down in O'Cala, Florida, helping uh Shane Ray do the big box workshop down there. I think we've still got a few seats open in that one as well. So uh if you're interested in the big box, that's one of the few opportunities this year to listen to Shane Ray give his speech on the big box. And man, that guy is something.
SPEAKER_02:Yeah, and and people, the last uh big box class we did, we did one in Minnesota in November, and there were guys I was talking to going to the class. They said, when I saw on the syllabus, we're spending a whole day talking about fire protection systems. I'm going, boy, you know, this is gonna and Shane does not make it boring. I'm telling you right now, it is totally relatable to firefighters, company officers, chief level officers. You don't have to be a fire prevention person to get into this. It's actually made me geek out. And I used to talk, I had a neighboring fire chief who who could look at a sprinkler head and tell me exactly how many GPMs came out of it from eight feet away. And it's I can't, I don't know that. I couldn't tell that. And that's not what we're talking about here. It's it's talking about basic operations of these systems, the difference between residential, commercial, uh, areas that are industrial, ESFR heads, all of that. Oh, yeah. It is such a knowledge base that we need to have in the fire service because we make so many mistakes when we don't know how those fire protection systems work. Did you have anything to plug? I feel like we're on the hot wing show right now.
SPEAKER_01:I don't think so. Uh yeah, no, I'm I'm very good.
SPEAKER_02:You're gonna remain warm in Phoenix, at least. Uh yeah, yeah, you can't make me go anywhere now. All right. Well, guys, thanks for being here. I really appreciate you spending some time with us on the B Shifter Podcast. And thanks to everyone for listening today. Remember to subscribe and tell your friends. And until next week, we'll talk to you later. Thanks for listening.