One of the topics of discussion at my office's winter workshop today was winter storm watches, warnings, and advisories (winter WWA, I'll call it). This isn't the first time we've talked about this as a group. I've always been big on products like that, but in the changing landscape of communication and messaging, I'm not so sure where I land now.
It's no secret that not all NWS products are understood correctly. I remember talking to my sister one time about a winter storm that was headed her way. I mentioned that she was under a Winter Storm Warning. She said something to the effect of, "Oh, but it's just a warning, so that's not too bad, right?" (she had always thought an advisory was worse than a warning). Who does she think she is not knowing that! I mean, how hard can it be to remember that??? The better question might be who am I to think that everyone fully comprehends that? In my mind, it seems like a simple concept. But, then again, I'M the one with the Meteorology degree...I'M the one regularly contemplating impacts and criteria. She has no idea what her local office's criteria are. Should she?
I don't think I've ever thought people should know our (the NWS') criteria. Heck, I don't even remember all of our criteria. I have an ops notebook dedicated to that very thing. If I'm being honest, though, there is probably a part of me that has expected people to at least understand the winter WWA difference. It seems like such a simple concept (says the Meteorologist). I don't know where the disconnect is, but something leads many people to repeatedly ask for clarification on the issue. Perhaps there's something important there.
With social media and SOOO many different ways to get information nowadays, there continues to be a push for improved and effective communication. One way to improve communication is to avoid confusion where possible. If the winter watch/warning/advisory distinction is causing confusion, maybe one solution is to avoid the mention of those products where possible. Think about the earlier conversation with my sister. What if I had just started the conversation with, "Hey, looks like ya'll are going to get 6-12" of snow tomorrow." Our conversation would have been shorter and less confusing.
My sister has three kids...all of which are in school. For her, 6-12" likely means no school and that someone needs to be home to watch the little rascals. THAT'S what matters to her. At the core, she probably could care less about whether she is under an advisory or warning...she just wants to know if the kids are staying home.
This is not an argument for, or against, the removal of winter WWA. As I understand the current state of the weather enterprise and how we communicate, there is still a place for those products. It just seems that our forward-facing message for the public, and likely even our partners, should be the potential or expected amounts, impacts, timing, etc. In time, maybe major changes to winter WWA will be more effective and is something the NWS Hazard simplification project is working hard to address going forward.
The challenge will still be how to best manage time spent on winter WWA
decisions vs other aspects of messaging in order to best set people up
for success as they contemplate important decisions with each winter
event. I'm still working through finding that balance. For now, I suppose I have landed on focusing most of my attention/effort on the science of the forecast and how that drives the forward-facing message (social media graphics, SitReps, briefings, etc) while at the same time not completely ignoring the role winter WWA have in the process. What about you? Where do you see winter WWA fitting in with messaging and how it is best utilized going forward?
P.S. My blog was never meant to be a let-me-tell-you-how-it-is kind of deal. I'm hoping any post I make starts conversations, whether I am ever involved in them or not. Writing these posts has helped me think through the challenges we face and I hope it does the same for others.
Just thinking my way through challenges faced in the field of Meteorology... Disclaimer: The views expressed in this blog are my own and do not necessarily reflect those of my employer.
Showing posts with label winter weather. Show all posts
Showing posts with label winter weather. Show all posts
Thursday, October 24, 2019
Sunday, December 9, 2018
Winter Storms and Flurries
High-impact weather events can either be annoyingly difficult to forecast...or a joy, depending on how you view it. While there is no right or wrong view on that, it can be an absolute nightmare when it is forecast and doesn't occur, or vice-versa. Several years ago, I wrote a post about the "Winter Storm that Never Was". The focus with that post was more about sharing (or not sharing) snowfall total maps from one model output. For this post, I wanted to look a bit more at the forecasting aspect.
7 to 10 days ago, model guidance was hinting at the potential of a significant snowfall for portions of the Central/Southern Plains. Snow lovers rejoice! And, haters...well, it's winter.
Fast-forward to present day and what was supposed to be a big snow ended up being scattered flurries, at least for parts of the Plains. Across parts of the Southern Plains, winter impacts were still felt, though (just ask the fine folks in Lubbock).
This wasn't a case of no snow occurring at all, but the actual swath of snow was quite a bit different compared to what many models were showing days in advance. The tough part with this forecast was that the models continued to suggest a higher-impact snow even up to 2-3 days or so in advance for areas that ended up seeing no flakes at all, or more of a wintry mix as opposed to all snow.
7 to 10 days ago, model guidance was hinting at the potential of a significant snowfall for portions of the Central/Southern Plains. Snow lovers rejoice! And, haters...well, it's winter.
![]() |
| One example of what some model guidance was suggesting (this was the GFS forecast from last Sunday) |
| NOHRSC Modeled Snow Depth for Dec 9, 2018 |
![]() |
| NAM Snowfall Forecast 2-3 Days Out |
I worked leading up to, and during, this event. Several things stuck out to me and/or came up in conversation within our office and with neighboring offices.
1) Trends are your friend, but know when to lock in. While not completely consistent, there was a noticeable trend further south with successive model runs. The trick here is knowing when to bite on a solution in the middle of a trend. This can be especially difficult when a certain trend continues well into the Watch/Warning/Advisory decision window. This is kind of like figuring out when to fill up on gas while prices are falling. You want to get the best price (forecast), but don't want to run out of gas (miss the forecast). From a messaging standpoint, you want to give people as much lead time as possible while still balancing out the potential crying wolf syndrome. The suggestion here is to be cautious with specific impacts if the models are in the middle of a consistent trend. If you can, try to wait until the guidance "levels off". This may be especially important when models show a drier, less snowy, less severe, etc type of trend for your particular area.
2) Consistency doesn't always equal higher confidence. There were several model runs in which the guidance were well-clustered on QPF / snowfall amounts. Typically, this would equate to higher confidence for the forecaster. The catch is that run-to-run consistency on where the heaviest snow would fall wasn't always there. Consistency in one model cycle is great, but make sure to look at it in context from previous runs.
3) I cannot stress this enough...don't let social media get to you. We can continue to educate folks and message events as best we can, but some things are simply misunderstood. Keep in mind, too, that the dreaded phrase, "They said...", while directed at us, likely includes non-Meteorologists as well. John Q posting a 400-hr snowfall map from some model is probably getting lumped into people's view of the error in the forecast. We didn't post those maps and yet we still get blamed. One suggestion is to take each event and, if you can, try to explain things to folks. I realize it won't always be received well, but don't give up trying. If this doesn't work, know when to just let it go.
4) Be honest with yourself. No matter how hard we try, we are going to bust at times. The models aren't perfect and neither are we. We all know this, but do we truly account for it in an honest post-event reflection? If you, personally, can do something better next time, then work at it. But, realize that even after considering all of the above suggestions on trends, messaging, science, and consistency...you will miss a forecast from time to time. Period. You are not alone...we all will miss forecasts. Richelle Goodrich said it well - “Many times what we perceive as an error or failure is actually a gift.
And eventually we find that lessons learned from that discouraging
experience prove to be of great worth.”
5) Postmortems! If you and/or your office do this already, great! If not, now is as good a time as any to start. It doesn't have to be a lengthy, detailed process. It could simply be an email pointing out which models did well or what stuck out to you during the event. Start a discussion. Figure out what went well and what didn't. Remember...be honest with yourself and as an office and learn from it. With each event, successful or not, we have an opportunity as individuals and as a team to improve. Make the most of each opportunity.
Forecasting the weather has its challenges, especially when high-impact events are at stake. What I'm learning is to implement change through lessons learned, figure out how to best interpret model guidance in various scenarios, and to be honest with myself. But, don't take my word for it...give it a try for yourself!
Note: if there are things you have learned from forecasting high-impact events, then let me know and add to the discussion!
Note: if there are things you have learned from forecasting high-impact events, then let me know and add to the discussion!
Thursday, April 26, 2018
Probabilistic vs Deterministic Messaging
This past Winter, our office (TFX) participated in the NWS' prob snow experiment. For those who might not be familiar with what that is or what it involved, it was a way to experiment with utilizing snowfall probability information within operations and decision-support activities. Perhaps in another post I'll ponder the good and the bad about the experiment, itself. But, for now, I wanted to take it a different direction.
Related to that experiment, a question was posed...is probabilistic or deterministic information better when it comes to messaging? At its core, this question is part of a larger and ongoing debate related to the effective communication of weather hazards. That debate is a fascinating and challenging one, but is probably too long for one post. For now, I'll just address the one piece of the puzzle that focuses on probabilistic vs deterministic messaging.
When it comes to snowfall amounts, what do we often see? Ranges. And, we seem to gravitate toward certain ranges at that. 1-3", 3-6", 6-12". If you are one of those rebel types, you might even use 2-5" or 3-7". Oh the humanity...
The interesting (note I said interesting and not necessarily bad) part about the end-user's use of ranges is the seemingly automatic focus on the high number. Knowing the worst-case scenario isn't a bad thing in of itself, but how it's used can be. Just before a winter storm a couple months ago, a friend of mine texted me and said, 'Hey! I heard we are supposed to get 7" of snow'. The winter product from our office said something to the effect of 2-4" with isolated amounts up to 7", if I remember correctly. My friend read that as we are getting 7" of snow. I doubt he was alone in that assessment.
I often give ranges when messaging upcoming snowfall events and I am not here to argue against that. My end-game is to think through the different possibilities. Recently, I decided to give the ole probability method a try. Prior to a winter event, a caller asked how much snow we expected for her area. With experimentation on the brain, I boldly informed her that there was an 80% chance of exceeding 4" at her house. To which she replied, 'So, do you think we might get a foot?'.
The sample size on my little experiment is incredibly small. But, how much would you be willing to wager against her response representing a large part of the population? One thing that stuck out to me in her response was the 12" amount. After talking with her more, I got the sense that 12" is when she starts having problems in her world. It's the point when her daily plans change. I believe that is why her mind immediately jumped to a foot. For her, my arbitrary percentage-greater-than-x-amount didn't help. Now, had I given her the probability of exceeding 12", well that could have been a different story. Would she have been able to interpret it effectively? I don't know.
When it comes to the general public, the thresholds for when action is taken is all over the place. That lady's threshold was 12". A recent transplant from the South would probably have a different response. So where does that leave us as Meteorologists? In a very challenging position. We have a responsibility to message hazardous weather, but to a group of people who don't even share a common breaking point.
On the flip side, we have individuals or groups (DOT, emergency managers, etc) that often DO have specific thresholds that we can know. I watched an enlightening presentation recently that looked at the potential effectiveness of probability information for decision-makers like the DOT. I get the sense that probability messaging works great for them. Honestly, I believe it could work great for the general public as well. The challenge is our inability to know each and every person's breaking point.
One part of the prob snow experiment that I really liked was that it gave probability information for several breaking points (2", 4", 6", 8", 12", 16"). We may not be able to know all thresholds, but we can certainly try to cover as many as possible in our messaging, within reason. But, that's just snow. What about rain, hail size, tornadoes, tornado strength, etc? Do we say "this storm will produce up to golf ball size hail" or "there is an 80% chance of exceeding quarter size hail?". I'm not sure a warning product is the place to put a lot of probability wording, if nothing else but for the sake of time/understanding. Imagine The Weather Channel scrolling the probability of multiple thresholds, or hearing those probabilities being read over Weather Radio broadcasts/statements?
My answer to the question of probabilistic or deterministic? The verdict is still out, but I imagine it involves some sort of a mix that relates to the known users, the product, and the event. I don't know if there will come a time when all of our messages are completely understood, used correctly, and heeded, but working through and experimenting with this piece of the puzzle is beneficial to the larger discussion regarding effective communication. In the spirit of probabilistic messaging, I will inform you that there is a 100% chance that I will blog more about effective communication down the road...
Related to that experiment, a question was posed...is probabilistic or deterministic information better when it comes to messaging? At its core, this question is part of a larger and ongoing debate related to the effective communication of weather hazards. That debate is a fascinating and challenging one, but is probably too long for one post. For now, I'll just address the one piece of the puzzle that focuses on probabilistic vs deterministic messaging.
When it comes to snowfall amounts, what do we often see? Ranges. And, we seem to gravitate toward certain ranges at that. 1-3", 3-6", 6-12". If you are one of those rebel types, you might even use 2-5" or 3-7". Oh the humanity...
The interesting (note I said interesting and not necessarily bad) part about the end-user's use of ranges is the seemingly automatic focus on the high number. Knowing the worst-case scenario isn't a bad thing in of itself, but how it's used can be. Just before a winter storm a couple months ago, a friend of mine texted me and said, 'Hey! I heard we are supposed to get 7" of snow'. The winter product from our office said something to the effect of 2-4" with isolated amounts up to 7", if I remember correctly. My friend read that as we are getting 7" of snow. I doubt he was alone in that assessment.
I often give ranges when messaging upcoming snowfall events and I am not here to argue against that. My end-game is to think through the different possibilities. Recently, I decided to give the ole probability method a try. Prior to a winter event, a caller asked how much snow we expected for her area. With experimentation on the brain, I boldly informed her that there was an 80% chance of exceeding 4" at her house. To which she replied, 'So, do you think we might get a foot?'.
The sample size on my little experiment is incredibly small. But, how much would you be willing to wager against her response representing a large part of the population? One thing that stuck out to me in her response was the 12" amount. After talking with her more, I got the sense that 12" is when she starts having problems in her world. It's the point when her daily plans change. I believe that is why her mind immediately jumped to a foot. For her, my arbitrary percentage-greater-than-x-amount didn't help. Now, had I given her the probability of exceeding 12", well that could have been a different story. Would she have been able to interpret it effectively? I don't know.
When it comes to the general public, the thresholds for when action is taken is all over the place. That lady's threshold was 12". A recent transplant from the South would probably have a different response. So where does that leave us as Meteorologists? In a very challenging position. We have a responsibility to message hazardous weather, but to a group of people who don't even share a common breaking point.
On the flip side, we have individuals or groups (DOT, emergency managers, etc) that often DO have specific thresholds that we can know. I watched an enlightening presentation recently that looked at the potential effectiveness of probability information for decision-makers like the DOT. I get the sense that probability messaging works great for them. Honestly, I believe it could work great for the general public as well. The challenge is our inability to know each and every person's breaking point.
One part of the prob snow experiment that I really liked was that it gave probability information for several breaking points (2", 4", 6", 8", 12", 16"). We may not be able to know all thresholds, but we can certainly try to cover as many as possible in our messaging, within reason. But, that's just snow. What about rain, hail size, tornadoes, tornado strength, etc? Do we say "this storm will produce up to golf ball size hail" or "there is an 80% chance of exceeding quarter size hail?". I'm not sure a warning product is the place to put a lot of probability wording, if nothing else but for the sake of time/understanding. Imagine The Weather Channel scrolling the probability of multiple thresholds, or hearing those probabilities being read over Weather Radio broadcasts/statements?
My answer to the question of probabilistic or deterministic? The verdict is still out, but I imagine it involves some sort of a mix that relates to the known users, the product, and the event. I don't know if there will come a time when all of our messages are completely understood, used correctly, and heeded, but working through and experimenting with this piece of the puzzle is beneficial to the larger discussion regarding effective communication. In the spirit of probabilistic messaging, I will inform you that there is a 100% chance that I will blog more about effective communication down the road...
Tuesday, February 7, 2017
Messaging Significant Events
Over the past few days, a part of our CWA (NWS Great Falls) has been pounded with heavy snow (here's a PDF from our office with some of the impressive snowfall amounts, records, and pictures). And, when I say pounded, I mean 30-50+" of snow, avalanches, roads nearly impassable or closed, roofs/buildings endanger of collapsing, emergency declarations, people stranded and/or unable to travel, etc. Perhaps pounded isn't a strong enough word, which brings me to the challenge of the day. How do we approach events like these from a forecasting and messaging standpoint?
I am a firm believer that a good message starts with a good forecast and good forecast starts with sound science. For me personally, my approach to forecasting (and this is by no means the only way to do it) has been to pour over the data, then build a forecast that best represents what I am seeing from model data, current observations, input from other forecasters, experience, etc. From there, I step back, look at the finished product, and then try to determine what, if anything, needs messaging. This is all well and good, but what happens when the finished product shows the potential, or even likelihood, of an anomalous event?
Perhaps more experienced forecasters than I don't struggle with this as much, but while working this recent event, stepping back and looking at the forecast prior to the event got me wondering if the ridiculous snowfall amounts I was coming up with were valid. So much so, as soon as I calculated my snowfall amounts, me and the other forecaster I was working with immediately picked up the phone and called a neighboring office that would also be impacted. When they answered, their response was the same. They also were, somewhat dumbfoundedly, looking at the amounts they were coming up with. In fact, in their words, they said, "We [the two forecasters at the other office] have been staring at our computers trying to figure out if these amounts are real."
Turns out, those amounts were real. But, hindsight is always 20/20 and, for many of us in the moment, I think there can be a hesitation to put out such a forecast. For me (and I assume I'm not alone in this), there is that concern of, well what happens if this doesn't actually pan out? This points to a larger question. What is more helpful/harmful? To see the potential and not put the forecast out, or to put it out? If you forecast the high-end event and it happens...awesome! If you forecast the high-end event and it doesn't happen...not so good. But, what if you don't forecast the high-end event and it does happen? Which is worse...forecasting the event and it not happening or not forecasting the event and it happening? Both have negative consequences and this is where the challenge comes in.
Sometimes, I think there is a tendency to back off from higher-end events. Let's face it, oftentimes at least one or two models show a worst-case scenario, only to back off as the event draws near. Or, maybe they never back off, only to be way off in the end. This isn't always the case, but it does happen. And, then, there is the issue of over-hyping an event or the boy who cried wolf syndrome.
But, at the same time, when even one model indicates the potential for a higher-end event, it probably isn't prudent to immediately write it off (outliers do verify at times). And, while never 100% perfect, I think this is where sound science, experience, and collaboration comes in. If after all of this, there is above average, or maybe even average, confidence, perhaps it is time to go ahead and pull the trigger on messaging the event as a higher-end event. Afterall, that is part of our job as Meteorologists. To inform people of the weather. If the weather is going to be really bad, people need to know so they can prepare. We can't make people prepare, but we can at least stress the expected magnitude of an event.
If there was a Messaging Hall of Fame, two statements/events come to mind to be included (and, of course, this is in now way an exhaustive list!) 1) The statement issued by NWS New Orleans prior to the landfall of Hurricane Katrina. That's not a statement any NWS office issues on a regular basis. 2) The higher-end wording by SPC, NWS offices, and the media during the April 27, 2011 tornado outbreak. Both of these events fell outside of the norm, in my opinion, and forecasters had to make the not-always-easy go/no go call on these higher-end watches, warnings, and statements. Should all events be messaged just as hard or do higher-end events need stronger wording?
At the moment, I would tend to lean towards higher-end events need to be messaged harder. A 40" snowfall in a non-mountainous area probably deserves higher-end wording/statements than a 10" snowfall. Winter Storm Warnings, for example, would likely be issued for both, but 40" has the potential to cause more significant impacts/disruptions to everyday life than a 10" snowfall. Both are significant, but again, the challenge is how to approach these higher-end events.
In our case, wind wasn't much of a concern for much of the hardest hit areas, so we felt that a Blizzard Watch/Warning wasn't warranted. Granted, it would certainly grab people's attention. I would imagine, and this is purely speculation, that a Tornado Watch also grabs a lot of attention and probably even more so than a Severe T-storm Watch. But, do you put out a Tornado Watch if you are not expecting any tornadoes? I hadn't thought of this before, but could it be that we approach winter storms like convective events and have PDS Winter Storm Warnings in addition to regular Winter Storm Warnings? For our CWA, I think this event would have justified such a warning. 10" of snow in a snow-prone area is definitely warning-worthy and causes significant issues. But, even here, 40" basically shuts everything down. The local DOT here mentioned in a statement that they are going to have to bring in heavy equipment to remove all the snow and that it would take multiple days to get through. Cars are buried, roads impassable, roofs are struggling to hold the amazing weight of the newly fallen snow. That's not your average winter storm. One of the shifts after mine added wording into the original warning, stating this is a dangerous situation. I thought this was a great idea and reminded me of the kind of enhanced wording SPC uses in PDS Tornado/Severe T-storm Watches.
I think it is always important to look back at an event as an office and as individuals to see how things played out and what, if anything, could be improved on. For me, I put out the higher-end forecast, but wasn't bold enough to go all in with the messaging, even after collaboration with national centers and a neighboring office. Basically, I used the process I mentioned above, but didn't fully apply it, unfortunately. I think the fear of being wrong and the fear of over-hyping or messaging too strongly got the best of me. It's important to make sure you're not missing something, but at the same time, if after a careful scientific/collaborative process, confidence is still above average, I think at a certain point you just have to pull the trigger. I think the lesser of two evils is people preparing for an event that doesn't happen as opposed to not being told of an event and it happening. The latter case, using a snow example, has the potential to leave people stranded with no food, water, power, etc, because who is going to prepare for an event they don't know is coming? Having extra food, water, candles, etc doesn't hurt anyone, but NOT having those things and then NOT having a way to get those things is much worse in my opinion. Perhaps these types of events only happen a few times in any of our careers, but when they do, don't fall into the trap I did of letting fear prevent a stronger-worded message from going out.
On a quick side-note, this event has reminded me that, no matter how good the models become in the future, I still hold firmly to the idea that an understanding of the science behind what the models spit out is vitally important to our messaging. Knowing WHY a model is showing something can help us explain HOW an event is going to play out and even know what to stress that even the best models might be missing out on.
I am a firm believer that a good message starts with a good forecast and good forecast starts with sound science. For me personally, my approach to forecasting (and this is by no means the only way to do it) has been to pour over the data, then build a forecast that best represents what I am seeing from model data, current observations, input from other forecasters, experience, etc. From there, I step back, look at the finished product, and then try to determine what, if anything, needs messaging. This is all well and good, but what happens when the finished product shows the potential, or even likelihood, of an anomalous event?
Perhaps more experienced forecasters than I don't struggle with this as much, but while working this recent event, stepping back and looking at the forecast prior to the event got me wondering if the ridiculous snowfall amounts I was coming up with were valid. So much so, as soon as I calculated my snowfall amounts, me and the other forecaster I was working with immediately picked up the phone and called a neighboring office that would also be impacted. When they answered, their response was the same. They also were, somewhat dumbfoundedly, looking at the amounts they were coming up with. In fact, in their words, they said, "We [the two forecasters at the other office] have been staring at our computers trying to figure out if these amounts are real."
Turns out, those amounts were real. But, hindsight is always 20/20 and, for many of us in the moment, I think there can be a hesitation to put out such a forecast. For me (and I assume I'm not alone in this), there is that concern of, well what happens if this doesn't actually pan out? This points to a larger question. What is more helpful/harmful? To see the potential and not put the forecast out, or to put it out? If you forecast the high-end event and it happens...awesome! If you forecast the high-end event and it doesn't happen...not so good. But, what if you don't forecast the high-end event and it does happen? Which is worse...forecasting the event and it not happening or not forecasting the event and it happening? Both have negative consequences and this is where the challenge comes in.
Sometimes, I think there is a tendency to back off from higher-end events. Let's face it, oftentimes at least one or two models show a worst-case scenario, only to back off as the event draws near. Or, maybe they never back off, only to be way off in the end. This isn't always the case, but it does happen. And, then, there is the issue of over-hyping an event or the boy who cried wolf syndrome.
But, at the same time, when even one model indicates the potential for a higher-end event, it probably isn't prudent to immediately write it off (outliers do verify at times). And, while never 100% perfect, I think this is where sound science, experience, and collaboration comes in. If after all of this, there is above average, or maybe even average, confidence, perhaps it is time to go ahead and pull the trigger on messaging the event as a higher-end event. Afterall, that is part of our job as Meteorologists. To inform people of the weather. If the weather is going to be really bad, people need to know so they can prepare. We can't make people prepare, but we can at least stress the expected magnitude of an event.
If there was a Messaging Hall of Fame, two statements/events come to mind to be included (and, of course, this is in now way an exhaustive list!) 1) The statement issued by NWS New Orleans prior to the landfall of Hurricane Katrina. That's not a statement any NWS office issues on a regular basis. 2) The higher-end wording by SPC, NWS offices, and the media during the April 27, 2011 tornado outbreak. Both of these events fell outside of the norm, in my opinion, and forecasters had to make the not-always-easy go/no go call on these higher-end watches, warnings, and statements. Should all events be messaged just as hard or do higher-end events need stronger wording?
At the moment, I would tend to lean towards higher-end events need to be messaged harder. A 40" snowfall in a non-mountainous area probably deserves higher-end wording/statements than a 10" snowfall. Winter Storm Warnings, for example, would likely be issued for both, but 40" has the potential to cause more significant impacts/disruptions to everyday life than a 10" snowfall. Both are significant, but again, the challenge is how to approach these higher-end events.
In our case, wind wasn't much of a concern for much of the hardest hit areas, so we felt that a Blizzard Watch/Warning wasn't warranted. Granted, it would certainly grab people's attention. I would imagine, and this is purely speculation, that a Tornado Watch also grabs a lot of attention and probably even more so than a Severe T-storm Watch. But, do you put out a Tornado Watch if you are not expecting any tornadoes? I hadn't thought of this before, but could it be that we approach winter storms like convective events and have PDS Winter Storm Warnings in addition to regular Winter Storm Warnings? For our CWA, I think this event would have justified such a warning. 10" of snow in a snow-prone area is definitely warning-worthy and causes significant issues. But, even here, 40" basically shuts everything down. The local DOT here mentioned in a statement that they are going to have to bring in heavy equipment to remove all the snow and that it would take multiple days to get through. Cars are buried, roads impassable, roofs are struggling to hold the amazing weight of the newly fallen snow. That's not your average winter storm. One of the shifts after mine added wording into the original warning, stating this is a dangerous situation. I thought this was a great idea and reminded me of the kind of enhanced wording SPC uses in PDS Tornado/Severe T-storm Watches.
I think it is always important to look back at an event as an office and as individuals to see how things played out and what, if anything, could be improved on. For me, I put out the higher-end forecast, but wasn't bold enough to go all in with the messaging, even after collaboration with national centers and a neighboring office. Basically, I used the process I mentioned above, but didn't fully apply it, unfortunately. I think the fear of being wrong and the fear of over-hyping or messaging too strongly got the best of me. It's important to make sure you're not missing something, but at the same time, if after a careful scientific/collaborative process, confidence is still above average, I think at a certain point you just have to pull the trigger. I think the lesser of two evils is people preparing for an event that doesn't happen as opposed to not being told of an event and it happening. The latter case, using a snow example, has the potential to leave people stranded with no food, water, power, etc, because who is going to prepare for an event they don't know is coming? Having extra food, water, candles, etc doesn't hurt anyone, but NOT having those things and then NOT having a way to get those things is much worse in my opinion. Perhaps these types of events only happen a few times in any of our careers, but when they do, don't fall into the trap I did of letting fear prevent a stronger-worded message from going out.
On a quick side-note, this event has reminded me that, no matter how good the models become in the future, I still hold firmly to the idea that an understanding of the science behind what the models spit out is vitally important to our messaging. Knowing WHY a model is showing something can help us explain HOW an event is going to play out and even know what to stress that even the best models might be missing out on.
Saturday, November 26, 2016
Hazards...Is Simpler Better?
The office I work for as of this writing (NWS Great Falls) has, in recent
years, taken steps to get feedback from partners and the public about how they
feel we did with various winter weather events and what steps, if any, they
took after various products were issued. A lot of responses were expected, but
something that caught my attention was how some viewed Winter Weather
Advisories compared to Winter Storm Warnings. Surprisingly, some thought an
advisory was worse than a warning. Speaking as someone who knows the
difference, I did not expect that confusion. But, at the same time, I still
have a hard time with people getting Tornado Watches and warnings confused. I know our products (as I should), but maybe the confusion is a sign of a bigger problem.
I love the idea of simplifying our hazards. When I look
at the difference between Canada’s “WWA” map and the US’ (see maps below), I feel like simpler is
probably better. The legends, alone, speak to the different approach.
But then again, part of me likes the array of colors. Maybe I’m
just used to it, but I do like how I can quickly look at the map and know
roughly what each hazard is without even having to click on it. That takes us
back to my perception, not only as a Meteorologist, but as a NWS employee who
has been used to this map and colors for years. The real question is, what does
my wife think of the colorful array of filled in counties? I guarantee she can’t
look at the map and say (without reading the legend), ‘Oohh…look at the
expansive fog advisory in Arkansas!’. I can, but I bet most of the public can’t.
The WWA map isn’t for me, it’s for the people I serve. Granted, the legend
clears things up some, but maybe multiple colors isn’t the best.
Then I go back to the products, themselves. Recently,
while contemplating with some colleagues on the best way to handle an incoming
winter system, I came to the realization that for me, personally, I couldn’t say
with complete confidence that one way to message the event was better
than another. Various products had their pros and cons, but initially it was
hard to say one product was the overwhelming favorite.
In this case, 1-3” of snow was expected for the southern
third of our CWA, but on the Wednesday before Thanksgiving. 1-3” of snow in this
part of Montana is not earth-shattering, but not only did it fall after a relatively mild and snow-free period, it also came during the middle of a very
busy holiday travel day and this presented an interesting messaging dilemma. It was
discussed whether an SPS or advisory was warranted (a warning seemed too much
given widespread, significant impacts were not expected). As mentioned earlier,
though, some consider an advisory worse than a warning, but maybe this and the watch vs
warning dilemma is an education/outreach issue??
While this wasn’t
expected to be a significant event, it seemed worth it to get people’s
attention, especially given the usually higher volume of traffic through the area. In the past, I would have leaned towards an SPS, but then I got to
thinking about reach. Which product is the most visible (which seemed to be a
motivating factor in this decision)? As far as I know, TWC still crawls SPS’ in
addition to advisories and watches/warnings (I haven’t had cable in several
years, though, so please correct me on this if I’m wrong). On social media, we
could post either (or just make a general post that doesn’t reference any
specific product), so that didn't seem to change the decision. But, what about the local TV media? Here, at least, I have
never seen a station show SPS’ on any of their watch/warning maps, but they
will show advisories. At the end of the day, I felt like an advisory had the
best chance of being the most visible between the two options. That is what our
office ended up doing. But, I’m not saying this is a right/wrong issue, it just
re-invigorated the messaging discussion in my mind.
But, what about a case where the decision is advisory vs
warning? Using the above arguments, both may get the same amount of visibility
and, frankly, it appears not everyone even understands the difference. So, we might say warning over advisory in a more widespread, higher-impact event, but would the correct message even be conveyed? In the wording, sure, but just getting the alert on a phone without seeing text...would people know the significance of a warning vs. advisory? I'm sure some would, but based on feedback here, not all would. Some have
proposed we get rid of one, namely the advisory. Honestly, I can’t argue
against that. But, do we keep the SPS? I know that this product will still go
to many phones via apps, even if it never shows up on TV stations. Plus, as it
stands now, it covers quite the array of hazards that fall in the potentially-less-impactful-than-a-warning
category.
And, of course, what would a good discussion be without a little
outside of the box thinking?! As much as I believe a simpler hazards approach
is best, is the risk of confusion worth it? We’ve had certain products for so
long and people, whether they understand them or not, have heard of these
products for many years. Is wiping out products and going with simply
Statement, Watch, Warning (ie. like Canada) the right approach? I’m not saying
it isn’t, I’m just asking the question. Do we keep the current system and work
harder at outreach/education or is the risk of further confusion worth what is
probably the best long-term solution? My gut says simplification is worth the
risk.
I feel like there isn’t a perfect solution that
adequately meets the needs of every single user, but I believe there is a solution
that is the most ideal. Personally, I’m still not sure what that is, but it seems some form of simpler is probably better. I’m
hoping through user feedback, we can come up with a best solution. I do believe
that the best solution cannot be figured out without user feedback. To this
point, it’s great to see the effort to get that feedback! I hope we get some
beneficial feedback along the way.
As I said before, I believe simplifying is the best
option, but I also believe there will be some growing pains along the way. I
think if we work together along with feedback from those we serve, we can come
up with a more ideal solution. It’s going to take patience and a concerted
effort, two tasks that aren’t always easy, but perhaps it will lead to a more
user-friendly product suite and maybe even an improved response to hazardous weather.
Friday, December 27, 2013
The Winter Storm that Never Was
Ah, winter. Cold weather, numerous holidays, and...weekly winter storms that never actually occur. Ok, so obviously winter storms do happen on some weeks. It's those storms-that-never-were that have been getting a lot of attention lately.
I would venture to say that come late November or early December and continuing through late-spring, a winter storm can be found at some point in any forecast cycle of the GFS. The problem is, it is often found beyond the 7-day / 180hr timeframe and it often doesn't play out like the GFS (or other models) claims it will. As Meteorologists, we know this. But, let's be honest, it is really fun to look at the GFS beyond 180 hrs to see the "eye candy" as I've heard many call it. I am not a doctor, but I hear that candy isn't always the best for you and yet it is still being passed out on a weekly basis.
My concern is that as Meteorologists we are doing a disservice to the ones it is our duty to serve. Can I go as far as saying that it is like a dentist passing out toothbrushes AND candy? Some great maps and charts ("toothbrushes") are spread around prior to an upcoming event, but then those end-of-the-world snow maps (ie. the candy) are mixed in. I am no authority in the weather community, but I just feel like we have to think of the potential consequences of passing that candy around.
In my opinion, one of our core responsibilities (regardless of sector) is to serve our clients, whether that be the public, a paying customer, or a business. When we post, share, or link to a model's "blizzard-of-the-year" output at 384 hours, what are we accomplishing?
I read a great blog post recently by Victor Gensini on this very issue. Check out his blog post HERE. He hit on a lot of the core issues with these posts, so I won't rehash that. But, a few thoughts to add...
1) If a model solution matches up closely with your own forecast, then fine. Maybe you don't have a fancy map-making tool and it is just easier to post a model's output with some sort of caption that clarifies the map shown is a model forecast, but that it matches closely with your thinking. But, how many of us actually make detailed forecasts for our clients 384 hours out? I know some do, but for the rest, maybe we should wait until the model's output is within our forecast period.
2) Post a map of your own, if possible. Many NWS offices, media outlets, and private sector company's do this. Right or wrong, it is their personalized forecast that incorporates analysis of many model solutions by the forecaster(s) on duty. I believe our clients are best-served when WE analyze each model's solution and come up with a best-guess forecast as opposed to posting all the solutions. And oftentimes, it seems like the worst-case-scenario maps are shown which just doesn't seem to be a good service (unless, of course, you believe the worst-case will happen with a particular event...and those DO happen).
3) I am not against looking at model output beyond 180 hrs. I think it does have some use. Personally, I like to look at longer-range output sometimes just to get an idea of what the weather pattern might be like beyond DY 7. Maybe the GFS and the ECMWF show a deep trough developing across the eastern US 10 days out...it may not happen exactly that way, but if a certain pattern is advertised consistently from run to run, maybe it will help with confidence in your forecast once that pattern comes into play within your forecast period.
4) The idea of posting images and explaining them or comparing with other model solutions is an interesting one. I have mixed feelings about this. I like the teaching motivation and I think it is a good one. But, even good intentions can go awry. I'm not sure yet if I am against this idea, but it might be an interesting case study to see whether a majority of the people reading the post focus on the learning aspect or whether they focus on the fact that one model is showing a huge storm.
5) I realize that a lot of hyped posts are done by those who are not actual Meteorologists. To be clear, I don't have something against people who make such posts. The internet and social media are great, but it does make all kinds of weather info available / shareable (for better or worse). Personally, I can't hold a non-Met responsible for those posts (although, I do wish they would stop). But, I believe that we, as Meteorologists (just like dentists with candy) should be held to a higher standard when it comes to passing around worst-case scenario posts that we don't actually believe will happen.
My desire is to see the weather community at large continue to serve others as effectively as possible. If posting certain model output isn't effective, maybe those posts should be as rare as the occurrence of those blizzards shown 2 weeks out...
I would venture to say that come late November or early December and continuing through late-spring, a winter storm can be found at some point in any forecast cycle of the GFS. The problem is, it is often found beyond the 7-day / 180hr timeframe and it often doesn't play out like the GFS (or other models) claims it will. As Meteorologists, we know this. But, let's be honest, it is really fun to look at the GFS beyond 180 hrs to see the "eye candy" as I've heard many call it. I am not a doctor, but I hear that candy isn't always the best for you and yet it is still being passed out on a weekly basis.
My concern is that as Meteorologists we are doing a disservice to the ones it is our duty to serve. Can I go as far as saying that it is like a dentist passing out toothbrushes AND candy? Some great maps and charts ("toothbrushes") are spread around prior to an upcoming event, but then those end-of-the-world snow maps (ie. the candy) are mixed in. I am no authority in the weather community, but I just feel like we have to think of the potential consequences of passing that candy around.
In my opinion, one of our core responsibilities (regardless of sector) is to serve our clients, whether that be the public, a paying customer, or a business. When we post, share, or link to a model's "blizzard-of-the-year" output at 384 hours, what are we accomplishing?
I read a great blog post recently by Victor Gensini on this very issue. Check out his blog post HERE. He hit on a lot of the core issues with these posts, so I won't rehash that. But, a few thoughts to add...
1) If a model solution matches up closely with your own forecast, then fine. Maybe you don't have a fancy map-making tool and it is just easier to post a model's output with some sort of caption that clarifies the map shown is a model forecast, but that it matches closely with your thinking. But, how many of us actually make detailed forecasts for our clients 384 hours out? I know some do, but for the rest, maybe we should wait until the model's output is within our forecast period.
2) Post a map of your own, if possible. Many NWS offices, media outlets, and private sector company's do this. Right or wrong, it is their personalized forecast that incorporates analysis of many model solutions by the forecaster(s) on duty. I believe our clients are best-served when WE analyze each model's solution and come up with a best-guess forecast as opposed to posting all the solutions. And oftentimes, it seems like the worst-case-scenario maps are shown which just doesn't seem to be a good service (unless, of course, you believe the worst-case will happen with a particular event...and those DO happen).
3) I am not against looking at model output beyond 180 hrs. I think it does have some use. Personally, I like to look at longer-range output sometimes just to get an idea of what the weather pattern might be like beyond DY 7. Maybe the GFS and the ECMWF show a deep trough developing across the eastern US 10 days out...it may not happen exactly that way, but if a certain pattern is advertised consistently from run to run, maybe it will help with confidence in your forecast once that pattern comes into play within your forecast period.
4) The idea of posting images and explaining them or comparing with other model solutions is an interesting one. I have mixed feelings about this. I like the teaching motivation and I think it is a good one. But, even good intentions can go awry. I'm not sure yet if I am against this idea, but it might be an interesting case study to see whether a majority of the people reading the post focus on the learning aspect or whether they focus on the fact that one model is showing a huge storm.
5) I realize that a lot of hyped posts are done by those who are not actual Meteorologists. To be clear, I don't have something against people who make such posts. The internet and social media are great, but it does make all kinds of weather info available / shareable (for better or worse). Personally, I can't hold a non-Met responsible for those posts (although, I do wish they would stop). But, I believe that we, as Meteorologists (just like dentists with candy) should be held to a higher standard when it comes to passing around worst-case scenario posts that we don't actually believe will happen.
My desire is to see the weather community at large continue to serve others as effectively as possible. If posting certain model output isn't effective, maybe those posts should be as rare as the occurrence of those blizzards shown 2 weeks out...
Subscribe to:
Posts (Atom)



