Notice: Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the nfd_wpnavbar_setting handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /home1/scottich/public_html/wp-includes/functions.php on line 6078

Warning: Cannot modify header information - headers already sent by (output started at /home1/scottich/public_html/wp-includes/functions.php:6078) in /home1/scottich/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/scottich/public_html/wp-includes/functions.php:6078) in /home1/scottich/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/scottich/public_html/wp-includes/functions.php:6078) in /home1/scottich/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/scottich/public_html/wp-includes/functions.php:6078) in /home1/scottich/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/scottich/public_html/wp-includes/functions.php:6078) in /home1/scottich/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/scottich/public_html/wp-includes/functions.php:6078) in /home1/scottich/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/scottich/public_html/wp-includes/functions.php:6078) in /home1/scottich/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/scottich/public_html/wp-includes/functions.php:6078) in /home1/scottich/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831
{"id":3298,"date":"2018-09-10T22:12:12","date_gmt":"2018-09-10T22:12:12","guid":{"rendered":"http:\/\/scottdimmich.com\/?p=3298"},"modified":"2018-09-10T22:12:12","modified_gmt":"2018-09-10T22:12:12","slug":"weather-communications-has-a-problem-and-business-thinking-can-fix-it","status":"publish","type":"post","link":"https:\/\/scottdimmich.com\/2018\/09\/10\/weather-communications-has-a-problem-and-business-thinking-can-fix-it\/","title":{"rendered":"Weather Communications Has A Problem And Business Thinking Can Fix It"},"content":{"rendered":"

As a meteorologist, a weather communicator, and someone to aims to be humble, I’ve come to accept and respect that the weather community has a critical issue that needs to be addressed. As a businessperson, I see business problems being solved daily, but I also see a solution to the mounting weather communications problem.<\/p>\n

This problem is better shown than explained. It’s worth noting that there is a lot of great weather communication out there, and I’m not going to target specific people or companies as much as the product itself. To show this example, I will use New York City, a place I have never worked and with weather communications companies for which I have never worked.<\/p>\n

As I write this, Hurricane Florence is a major hurricane in the Atlantic Ocean. Here’s what the New York City NBC affiliate has to say recently:<\/p>\n

\n

Fresh from the weather center, here's your latest 4-Day Forecast. Watch News 4 at 4 pm for the complete breakdown. #NBC4NY<\/a> pic.twitter.com\/Df1uv7aICk<\/a><\/p>\n

— Storm Team 4 NY (@StormTeam4NY) September 10, 2018<\/a><\/p><\/blockquote>\n