The majority of bid documents for fire sprinkler work is some form of delegated design. A consulting engineer frequently does not provide all of the detail about a system (pipe locations, size, hanging methods, hydraulic calculations, etc). Why is that? In other disciplines, the opposite is common. Mechanical Engineers regularly selects a system type and lays out ductwork in a one-line or two-line configuration on a plan before a contractor bids the system. Electrical Engineers commonly size up, calculate and provide power and lighting locations on plan with an overall one-line diagram. Even plumbing often has plans for domestic water feeds and sanitary waste. Why doesn’t that happen for fire protection? First, the biggest disclaimer today, I’m not advocating for all design to be upfront. Or even a majority of it. I do see many applications where a quality FPE consultant can provide a tremendous amount of value to a project. I explored this a bit with The Delegated Design Problem and in A Practical Design Spec Checklist. But I would like to start the conversation and get your ideas on why we are where we are today with why designs are not done upfront. Here is why I think all sprinkler design is not completed upfront, before bid time. #1 WE DON’T WANT EVERYTHING UPFRONT
Overwhelmingly, the sentiment I hear from sprinkler contractors about ‘full-design’ fire sprinkler drawings is that they wouldn’t want upfront designs for all projects. Why? Because in some (or many) cases, sprinkler contractors feel that upfront design either limits their flexibility or is of very poor quality, or both. A design that doesn’t coordinate with other systems, or ‘leaves coordination’ for the sprinkler contractor, is problematic. It’s difficult to bid and difficult to work with after a project has been awarded. How much needs to be ‘coordinated later’? How ‘real’ is the design? Is it less efficient than the contractor could have laid it out? Many who have designed on the contracting side feel that real-world “fit” and doing the sprinkler layout are one in the same. You can’t ‘rough-in’ a layout without thinking about conflicts and making it actually work in the real world. As an extreme example, I think most could agree that a basic NFPA 13D layout does not need upfront involvement by a consultant. Could they help? Perhaps. Could they provide value? Perhaps. But it does not need a high level of involvement. Now there’s a big counterpoint to this. Just because we don’t want upfront design on all projects doesn’t mean it wouldn’t be beneficial on some projects. Projects that have very specific needs, unique needs, high-visibility challenges, coordination challenges, or that require a specialized set of expertise could very much benefit from upfront involvement. Maybe it’s a retrofit in a high profile historic museum. Maybe it’s suppression for an automated storage retrieval system. Maybe it’s a unique storage configuration that is outside the bounds of NFPA 13. In these types of situations, involvement from a quality FPE consultant can address code concerns and clearly define the scope. It can help mitigate a lot of risk for contractors by doing so and help everyone bid apples-to-apples instead of a wide-open, ill-defined scope. #2 INADEQUATE WORKFORCE (INDIVIDUALS AND COMPANIES) Perhaps the alternative reason is the lack of expertise in the workforce. We simply don’t have enough people, nor expertise, to take on every project. Even if we wanted upfront involvement to a high-level of detail, we as an industry couldn’t pull it off. We don’t have enough bodies, nor enough qualified expertise. Is it an issue? Absolutely. Does the lack of people affect how well we advocate for fire protection itself? Absolutely. Could the construction experience for architects and owners and contractors actually benefit from more and better individuals working upfront on project? Absolutely. But until we catch up on the quantity of our own workforce, we simply can’t take on more involved work. #3 LOCATION OF THE EXPERTISE Another reason we don’t perform highly-detailed layout work upfront is the location of where expertise for layout technicians often falls – and that’s in contracting. Anecdotally I know far more layout technicians in contracting than I do in consulting. In our survey of nearly 500 industry professionals in 2022, of those who had roles as a designer or layout technician, 68% of them worked for contractors (another 4% were self-employed). That’s different than other disciplines where there is plenty of design and layout expertise embedded in consulting. #4 DOWNSIDES: COST, INFLEXIBILITY, & SCHEDULE Involving expertise upfront isn’t free. There’s a cost associated with it. We mentioned it before and stipulating a full layout upfront also set some parameters in place that can limit the creativity and efficiency of a contractor-provided layout. Lastly, there’s time needed to do that work upfront. Having a high-degree of involvement may not be a positive impact to overall project schedule. SO CAN WE KILL-OFF UPFRONT INVOLVEMENT? It sure feels like I’ve put out a hit piece on any upfront involvement in fire sprinkler design. The question is – does all design need to be done upfront? By an engineer or consultant, or someone other than a contractor? That answer is no. All design doesn’t need to be upfront. We couldn’t pull it off anyways, but it could also be costly and obstructive for many small or simple project applications. Is there value to having upfront involvement? Absolutely - when it’s done well. Consultants provide tremendous value, all-around, when:
Do consultants need to be doing fully-detailed layouts to accomplish this? Often no, though sometimes it could help. HOW DO WE RESHAPE THE WORK? In an SFPE Magazine Article in 2022, Thomas Gardner wrote “There is a happy medium between no delegation and full delegation of the fire protection system.” Count me in that camp. Many times when the subject of “Delegated Design” gets brought up, we instantly jump to extremes. Either all design should be by the EOR, or no design should ever be by the EOR. On one hand we have many military projects that specify the Qualified Fire Protection Engineer (QFPE) to be in direct charge of the layout upfront, if they don’t perform it themselves. On the other hand, we have an ever-growing amount of residential projects in North America that have no FPE or consulting involvement whatsoever. Both of these situations are not necessarily at odds. We can strike the balance between the two, and we can do “Delegated Design” better than what’s being done today. We can improve the quality of upfront documentation that defines scope and goes out for bid, and at the same time, still provide flexibility for the contractor and an overall lean project delivery. Part of solving that puzzle is looking realistically about what different approaches mean – how they look – seeing good and bad examples – and moving forward to introduce, educate and advocate on what better “Delegated Design” means in the future. For literally the past two decades there has been growing momentum to bring light to the issue. We’re not far from having more resources to define what “better” looks like and how we can easily get there. WHAT'S YOUR TAKE? We had a great dialogue about the problem of Delegated Design before, that's here. But what's your take on why work isn't provided upfront? Is it just tradition? Just the way things always have been? Is it any of the reasons I've cited? Why is our delivery method so different from Mechanical, Electrical, Plumbing or Structural? What separates us from other disciplines? Comment below - would be happy to hear your take. We tried out something new a couple months ago with a Detail Pick-Apart covering a dry sidewall sprinkler at a deck. We had a great response - healthy discussion from a wide variety of perspectives. Way back when we even talked about different parts and purposes for components of a wet riser. It's the dialogue that I often find the most helpful in seeing and understanding perspective that I simply just don't have. No detail is perfect, nor is it applicable in all situations. No way. It's one possible solution to some situations. That said, it can be really helpful to have open discord and learn from it. Quick rehash on ideas for critique and discord: USE CASES: What are good use cases for this? PROS: What benefits does an approach like this bring? CONS: What are the negatives with an approach like this? IMPROVE: What ways can this approach be improved? What critique would you offer here?
Thanks, as always, for being part of making the industry better. It's been quite the year! First - I'm thankful for you being a part of the community here. Whether it's reading a post here or there, downloading a cheatsheet, posting on the forum, using a tool or learning on the University platform - I couldn't be more thankful. You have helped make a dream of mine come to reality where I get to focus on ways to improve the industry I care so much about. Thank you for helping make that happen. Second - a lot has happened this year. We ramped up the learning experience with a load of new resources and 360-virtual simulations over at MeyerFire University. Perhaps just as impactful, we brought about an entirely new and improved site complete with an iOS and Android app. A lot has happened in that space over this year. In case you missed it, here are the top articles and resources of all time (as of 2023) at MeyerFire: #10 IS A POST INDICATOR VALVE REQUIRED FOR MY PROJECT? A code path study that looks at when post indicator valves are actually required. #9 A THRUST BLOCK CALCULATOR A calculator which helps size thrust blocks for underground pipe. #8 REQUIREMENTS FOR DRAINS IN FIRE SPRINKLER SYSTEMS A recap of when, where, and what size drains need to be in a fire sprinkler system. #7 FIRE HYDRANT FLOW TEST CHARTS A few pages for immediate flow translations for different fire hydrants. Useful for flow testing. #6 ARE FIRE SPRINKLERS REQUIRED FOR A CANOPY? A flowchart look at when sprinklers are required below a canopy, overhang, or porte-cochere. #5 A FIRE DEPARTMENT CONNECTION CHEATSHEET A PDF of all the biggest requirements & tips surrounding FDCs. #4 DETAILS AND REQUIREMENTS OF THE INSPECTOR'S TEST A breakout of the different requirements associated with an inspector's test. #3 SUMMARY OF DIFFERENCES IN NFPA 13, 13R, & 13D A breakout of the big differences between the three fire sprinkler standards. #2 BREAKING DOWN COMPONENTS OF A FIRE HYDRANT Types, components, and the "why" behind different parts of a fire hydrant. #1 COMPARE FLOW OF K-FACTORS WITH K-FACTOR CALCULATOR A tool (paid tool as part of the Toolkit) that optimizes flow and pressure across different available fire sprinkler k-factors. Thank you for another great year in helping improve the industry. I can't begin to tell you how excited and optimistic I am about what we'll be able to impact moving forward. Here's to 2023, and a bright year ahead. Cheers. - Joe Are you and others on your team looking for accredited professional development hours to wrap up 2023? Cash in and round-out unlimited continuing education requirements with MeyerFire University. We are a NICET Recognized Training provided and International Code Council Preferred Educational Provider, so all of our courses are NICET and ICC certified. With just one subscription you can get as many continuing education hours as you'd need, and still have the subscription active for your 2024 requirements next year as well!
Plus, you're in control of who uses your seat throughout the year - so you can remove yourself and add in others throughout the year for year-round learning. If you've been on the sidelines debating whether to join - now is a great time! Visit https://www.meyerfireuniversity.com to learn more today.
A couple weeks ago I was talking with a friend (shoutout to Chris Logan and his Fire Sprinkler Podcast) about different naming conventions for specific pipes in a sprinkler system.
What a great end result that chat started! We drew it up, labeled as best we knew, and posted it last week for your input. And boy did you not disappoint! ​Probably the term I knew least about was this one -
We got a wide range of names and input on how you describe the system. We can create a pretty kickin’ diagram today with your awesome input.
But I can't help but to take it one step further. We all have anecdotal experience, but what is the most common terms actually used in industry? If I’m talking to a colleague across the country – what term is most likely to strike home? I hate surveys, so I’m not going to do that. Instead, below we have simple poll questions where you can instantly see the results too. Vote on what term you usually call each part of the system, and afterwards we'll build a new (and more representative) diagram based on the most common terms. Keep in mind that each of these pieces don't have a defined name. The others we covered last week (riser, system riser, feed main, cross main, branch line, armover, sprig) are all defined terms in NFPA 13. If we do this well enough it just might be what the industry uses over the next few years, so thanks for taking part! TERM #1 ​TERM #2 ​TERM #3 ​TERM #4 ​TERM #5
Thanks for your input & being a part of the community here!​
You’re on a jobsite. On the phone with the boss back at the office. You’re looking up at a portion of the sprinkler system and have a question about that one piece of pipe. How do you describe that piece of pipe? What’s it called? It sounds silly, but up until Monday I’m not so sure that I knew the proper name for each segment within a sprinkler system. Like the true, proper terms that I should have learned way back when. There are a few things that can impact that – one is informal regional terms, which can cause some inconsistency. One is that up until Monday I’d never actually read all the definitions in NFPA 13 for each stick of pipe. One is that when I’d get cross-eyed looks when talking about a specific piece, I’d usually just point to it in conversation and move on. Well – as we do around here – it’s time to bring this topic out into the light and maybe we can all learn a bit from the discussion. Here’s a basic diagram of a sprinkler system, which each pipe path identified as best I understand it today: Is this consistent with the terms you use? What other names (maybe keep it PC?) or terms do you use? If not, what terms (even informal ones) do you use to describe each pipe? Take a look at the diagram above and some of these pictures and let us know here.
Last week I wrote on the Delegated Design Problem we have in the fire protection industry. The big ugly elephant that looms over us all. And wow – what a response! It’s a good thing (I guess) that so many others are as agitated as I am with the state of delegated design as I am. GOOD DELEGATED DESIGN ≠ FULL-LAYOUT One big and important point I’d like to make about the issues with what I’m calling delegated design; the answer is not full layout drawings by engineers. Some fire protection engineering firms can, and do, excellent detailed layout drawings for fire suppression systems. In some cases (unique, high-risk, location-sensitive clients), full-layout fire sprinkler documents can help convey exactly what the owner needs to all bidding contractors. It can be well done. But that’s not what we’re talking about when we’re talking about good delegated design. A set of engineering documents go by plenty of names:
I’m simply calling them “Engineering Documents” and that process being “Delegated Design”. A good set of high-quality of Engineering Documents is helpful to contractors, helpful for pricing, helpful to define and communicate the scope, and helpful to the owner as it conveys what the owner wants. In my opinion, that doesn’t have to mean a full-layout. In most contractors’ opinions (we’ll get data on this later), my guess is the far majority don’t believe that quality engineering documents means a full layout. If done poorly, they’re actually worse for a project. WHAT SHOULD ENGINEER DOCUMENTS INCLUDE? So what criteria exists today? We wrote on this a few years ago with a checklist for things to consider in a set of Engineering Documents. That’s our go-to on what to include. But what does everyone else say? Ten different leading organizations in the industry addressed just that. In a joint position statement originally created by SFPE and endorsed by everyone else (ABET, AFAA, AFSA, ASCET, FSSA, NCEES, NFSA, NICET, NSPE, SFPE), the paper identifies what it is that Engineering Documents should include. A link to the position statement is here: https://www.nspe.org/resources/issues-and-advocacy/professional-policies-and-position-statements/sfpenspenicetascetncees This is an important piece of information that (just my opinion) seems to be met by those who care about fire protection, and completely ignored by those who don’t. I would go so far as to think that most of the players who don’t meet the recommendations of the white paper probably don’t know it exists. There’s a major disconnect there. STATE MANDATES In some states, much of this same criteria is formally adopted into state law. Three that I’m personally familiar with (Florida, Illinois, and South Carolina) overlap much of what the joint position recommends. These state mandates have teeth. If an AHJ has installation drawings without upfront engineer involvement, they have the authority to reject and require upfront involvement (Illinois is slightly different in that the specific requirements are less defined). Other states have mandates too. If you have a tip you’d want us to add to this, comment below here. SO, WHAT IS REQUIRED FOR ENGINEERING DOCUMENTS? Below is a table to compare the main elements of the joint position paper and a sample of state mandates. Now, fire protection is not just fire suppression, but I wanted to start on the fire suppression side and look at this in detail since it’s the suppression side of delegated design that seems to be the most pervasive issue today. A comparison of the joint-position statement (ABET, AFAA, AFSA, ASCET, FSSA, NCEES, NFSA, NICET, NSPE, SFPE) and several state statues for minimum requirements of fire protection engineering documents. In this list we find a lot of should-be-obvious things. Identifying the scope of work. Ask your favorite contractor – how many drawings have you seen for a renovation or an addition that doesn’t cleanly identify what work is actually supposed to be done? Are we scrapping everything? Are we going in all-new? Are we just add and relocating sprinklers? Hazard Classifications & Design Criteria. This one is the hammer to the head. It’s the most-important decision for the design of a suppression system. What is the hazard? What design criteria do we need to protect it properly? Again going back to your favorite contractor – how many times have you had projects where hazard classifications weren’t even identified? Or, the only place it is addressed is with a paragraph about Light Hazard and Ordinary Hazard in the specification while completely ignoring the huge storage area that’s part of the project? Water Supply. Every state and the position statement all agree that water supply is an upfront, engineering document responsibility. Ask your contractor – how often do they see it? ASK YOUR FAVORITE CONTRACTOR As an industry – as a collective – we’re failing right now. And I don’t want to pretend that I’m above scrutiny. Ask someone who’s looked at my documentation. It’s not perfect. I’ve failed to meet this mark. But I can be better – we all can. This has to improve, and I think we can build up the support and resources around this topic to make it happen. YOUR TAKE This is the first look at simply “what should be in a set of fire protection engineering documents”. What should they be? If you have input – tips, comments, thoughts – join the discussion below. If you work in other areas – Louisiana, Arizona, wherever – that have state-level mandates for fire protection engineering documents – let us know below! Having a representative summary helps everyone. Thanks for reading – hope the research we’ve compiled this week helps you think about how we as a whole can improve the way we practice. If there’s one big hairy problem in the fire protection industry that everyone knows about, yet few take head-on, it’s the delegated design problem. The practice of delegating pieces of the fire protection design has been around forever. THE CURRENT REALITY Some harsh but perhaps true realities today as an industry:
Out of those realities has been “delegated design”, where a professional engineer stipulates (specifies) what they deem critical, and “leave” the details to the installing contractor. GOOD VS. BAD If done well, delegated design can:
If done poorly, delegated design can:
THE CENTRAL ISSUE At the risk of sounding highly dramatic, I see this as the central issue that plagues our industry in North America. It is awful. And if you haven’t seen it, then ask your local estimator. What do they see? Is the scope of work well-defined? Or are they seeing documents that are simply full of landmines? Where a quick note on plumbing plans or buried in a specification could mean tens of thousands of dollars of cost that the contractor is supposed to eat? A DISSERVICE We, as an industry, do a terrible disservice to everyone else in the way that we do delegated design. Terrible. This isn’t a regional issue, either. I didn’t know it was this bad until I started working for contractors and I saw what they saw. And good grief, it’s terrible. SO FULL-DESIGN? Now conversations about this usually then go to – fine – what would you have Joe? Full design, every time? What about a single-family home? We don’t have enough FPEs for complex projects, much less residential sprinkler design? And I’m with you there – I think the answer is more about reform than it is abolishment. If we simply do delegated design well, I don’t think we’d have the issues we’re seeing today. WHO'S TO BLAME? And, if I’m going to make gross generalizations; if you’re the kind of person who cares about the fire protection industry, or maybe you see your role as being “in” the fire protection industry (like this concept) … then you’re likely not the problem. I tend to find it’s not the people that are concerned about this being the biggest violators. It’s those who don’t care, don’t show up, don’t invest in fire protection. They just “also do” fire protection. That said, the issue needs fixing. CREATING CHANGE Two weeks ago I wrote about working towards change. If 2033 looks different, what is the reality we want to create by then? I think this problem is solvable, and it’s worth solving. A CARROT OR A STICK? Generally, we see fixing incentives as a carrot or a stick problem. Do we use the carrot, or the stick? The carrot entices, rewards, promotes and builds up those that are doing things well. We find ways as an industry to recognize and promote people who do it well. The stick simply beats the violators. It pushes-down, disciplines, penalizes. This might be reporting to state boards or reporting to certification bodies. Right now, we collectively don’t have much of a carrot or a stick.
NO REWARDS? NO PUNISHMENT? We don’t recognize who is doing it well, and we certainly don’t promote them. Heck – we really don’t even have a scorecard or a standard to even identify what “doing it well” looks like! And state boards? What if the people on the board are doing the same bad practices as the violators? Reporting someone to a state board is time-intensive, has little reward, and makes enemies. No wonder so few people go about trying it. And besides that – what do we even compare negligence against? What is our standard practice? If negligence is so widespread, then what really is our standard of care? So, the question becomes, how can we uplift the practice of engineering in our industry when we don’t clearly establish what it is that we should be doing? And even where we have established what that practice looks like – how many of those practicing in fire protection have read and understood it? How accessible is that guidance? WHAT'S THE ANSWER? These are questions and challenges I think we’re up for tackling. I think it can be done. As with all the other impact projects we look at – what is the fundamental answer?
I don’t know the answer, but I think it is within reach. Maybe it’s one or all these things. While some of the writing lately may sound grandiose (and it is my writing, thank you very much ChatGPT), we’re taking active measures to attack this core issue head-on. In the coming pieces over the next few months, I’ll talk about the issue from my vantagepoint, build and ask, and try to open up the dialogue on what a better engineering practice looks like. This is something we can affect, and something I hope you also want to see improved as well. Got ideas on this topic? Share them below. I'd love to hear your input. We can get this right. Thanks for being a part of our community – and as always – as an advocate for what we all do. - Joe I'm going to go out on a limb here and do something I'm a bit apprehensive about as an engineer. #1 FLAWS IN THE ARMOR First - my number one fear of writing when I first started was that I was going to be wrong, and I was going to expose it for the world to see. After all - Engineers are never allowed to be wrong. And when we are, we're not allowed to openly admit it, right!? Anyone? Ok now that I've offended my friends, I should say that I'm flawed. I don't mean that facetiously. I've mostly gotten over the fact that I don't know everything; I have gaps in my knowledge. And even the things I do feel pretty adamant about, I'm still learning ways in which even those areas need improvement. I'm learning all the time. So acknowledging first that I am flawed and make mistakes is piece number one. #2 OPEN DISCORD Second - it's better for the world to bring discussions out into the open - where we can all learn from it. That's the entire point of the Forum, the point of writing as part of this blog, the point of MeyerFire altogether. What conversations can we start that everyone benefits from? In that line of logic, today I'm posting this detail that is a sketch I put together for open critique. Hopefully, if this is something we all learn a little from and gain some useful knowledge, maybe it's something we can do again with different situations. #3 IDEAS FOR CRITIQUE Before we fire away, remember that any detail is simply an approach, a concept. It's one possible solution. It's not a cure-all for every situation. It's simply one approach of many. I'd like to propose a few prompts to help the discussion related to this specific approach: USE CASES: What are good use cases for this? PROS: What benefits does an approach like this bring? CONS: What are the negatives with an approach like this? IMPROVE: What ways can this approach be improved? Here's the concept: So - what critique would you offer here?
What are good and bad use cases? Pros and cons with the approach? How could it be improved? Thanks, as always, for being a part of making the industry better. Earlier this week I needed to copy a four-unit apartment where I designed the 13R sprinkler system and simply roll it over into a new job.
It was a complete duplicate building, just in a different location (new jurisdiction, different water supply). Slam dunk. Easy, done. Right? Well sure, except then I looked at my prior layout. I couldn’t stand it. I looked at my own set of plans from just three years ago (2020!) and they look terrible. Now, the actual layout was fine. The sprinkler, locations, pipe are fine. Plans are OK. They were not at a stage that I think the average person would look at them and puke – but when I look at them I want to. Why? There are so many different tweaks and improvements on the presentation in three years that the work I do today simply looks very little like the work I was doing just 36 months ago. The titleblock is hard to read. When you look at the coversheet, it’s a mess of schedules and details and sections seemingly thrown around wherever they would fit. There’s no big bold title at the top, nor any kind of easy recognition on whether this project is on Main Street or Mars. It’s disjointed, doesn’t flow, isn’t what I would choose to do today. I get little goosebumps now having to stare at it now. IMPROVEMENT We don’t all stand on the shoulders of giants when we start out. We don’t hit perfection right off the bat. In reality, we should acknowledge that we’re very clearly never operating in a state of perfection. There is always room for improvement. And even if tradition says that our organization has done something the same way for 25 years, we need to be adapting to the needs of today and making use of the tools of today. One single big overhaul that changes a whole organization’s work style and work output simply never happens. OK – maybe somewhere for somebody, a big, conscious overhaul of standardization and workflow is theoretically possible. But if it actually has happened somewhere, then it had to be exceptionally painful and surely not quick. Improvement doesn’t happen ‘when we have time to take that on’. It happens in very very small increments. Micro improvements. A tweak here on this job. A nudge here on this job. A lightbulb on this job. What worked better? What worked worse? Adapt and move the chains forward. It’s far better in our world to take the 4-yard gain every single play than it is to throw 3 Hail Mary’s, fail, and then punt on the idea. NO LIGHTNING-STRIKE CHANGES If we tinker and tweak (surely I’m using some kind of Gen-Z curse word here or something?) things constantly, find what works, and adapt over time – that’s when we do actually make change happen. We also don’t get this lightning-strike ideas all at once. We get lots of little ideas over time, that, when executed, add up. It’s only after implementing all the constant little improvements that the big differences can start to show. That’s why my gut sinks when I look at the presentation from a 2020 project. It’s not one thing – it’s the 30 things that have all improved since then. THANKS, JOE. Yes, I’m somewhat embarrassed of the work that happened not even that long ago. But no, I didn’t come here today to brag about my own self-improvement. SPINNING IT FORWARD What I’m really interested in – is taking that look back and spinning it around. Where do we want to be, as an organization, in the next three years? Where do I want to be, as a person, in three years? Where do we want to take the industry, in three years? 3-YEARS TO TEN? Where is it that we can take things? For me as a person, for my team, but also – what about all of us? Three years seems hard enough to imagine. But carry out that thought – where can we all be, as an industry, in ten years? Let’s set aside the news network hysteria and world ending predictions for just a second and assume that things are going to be mostly around in 2033. That the fire protection industry will be growing and adapting just as it has for the last 120+ years. What do we want the industry to be in 2033? OVERESTIMATING THE SHORT GAME, UNDERESTIMATING THE LONG A famous person once said, “Most people overestimate what they can do in one year and underestimate what they can do in ten years.” I find this to be slap-me-in-my-face true. And I find the evidence for that easily when I look back on the last ten years. What happened? Where was I? What did I know then? What did I not know then? (answer: it was much more than what I knew) What was I doing then? What am I doing now? 2033 In 2033, will we all be sitting around and griping about the same issues that we gripe about today? Are we going to fix the issues surrounding delegated design? The boilerplate specs from 1985? Bid drawings that themselves obstruct code? Or perhaps just as important, the apathy some people have towards fire protection? Is it still going to be a problem? If not – what must happen? How far away are we from changing the outcome? Even if it is big – or would take a lot of effort, or resources, or awareness – is it not something that we couldn’t completely change by 2033? THOUSAND SMALL INCREMENTS If we look back – see how all our small changes stack up – and then look back forward: it’s the thousand small increments that will make the big difference. What are the small actionable items, today, that move us all in the right direction? How do we break giant problems down so that we can hit the 4-yards of progress now instead of waiting for a Hail Mary in nine years? What is that? What does that look like? TIME + PRESSURE I’ve spoken with enough people I admire that I believe in my core that there are few things we can’t solve given enough pressure and enough time. I see a path where we can change the trajectory of the industry if we choose to do so, collectively. It all depends on what we choose to do today. What will we etch in a small way today that keeps us moving towards big change tomorrow? And without sounding like I’ve completely gone off the rails; I think about these things a lot. I feel extremely fortunate to be able to do so with the website and the content and community that hang around here. I am so thankful for that. I don’t mean taking on big challenges in a figurative sense – I mean it as an actionable challenge. If you’ve got a gripe with how our industry operates – what are you doing about it? What change can you make now that moves things in a better direction for all of us? Around here we’ve got “irons in the fire” so to speak to be making progress towards the areas we really care about. Some things maybe awareness. Others education. Maybe resources. Maybe advocacy. Maybe they’re slow burns – maybe they won’t come to life for some time – but after lots and lots and lots of little victories maybe they will make it out to the world and make some real tangible change. Ten years from now simply seems unfathomable for me to comprehend. Maybe it’s my age or my kids’ ages or that so much has changed in my world in the last decade. It’s difficult for me to picture it. I can only barely imagine what 2 years from now could look like. But if you assume that 2033 will happen, that it will hit us at some point: will we be looking back and be mildly embarrassed by how things used to be – because so much has changed? Or will we gripe about the same issues without doing anything about it? |
ALL-ACCESSSUBSCRIBEGet Free Articles via Email:
+ Get calculators, tools, resources and articles
+ Get our PDF Flowchart for Canopy & Overhang Requirements instantly + No spam
+ Unsubscribe anytime AUTHORJoe Meyer, PE, is a Fire Protection Engineer out of St. Louis, Missouri who writes & develops resources for Fire Protection Professionals. See bio here: About FILTERS
All
ARCHIVES
July 2024
|