{
    "version" : "https://jsonfeed.org/version/1",
    "content" : "news",
    "type" : "single",
    "title" : "Weather.gov – Usability Case Study |Digital.gov",
    "description": "Weather.gov – Usability Case Study",
    "home_page_url" : "/preview/gsa/digitalgov.gov/bc-archive-content-3/","feed_url" : "/preview/gsa/digitalgov.gov/bc-archive-content-3/2012/12/06/weather-gov-usability-case-study/index.json","item" : [
    {"title" :"Weather.gov \u0026#8211; Usability Case Study","summary" : "After conducting a usability test and listening to customer feedback, the Weather.gov team and the DigitalGov User Experience Program identified these three issues as both important and quickly solvable. Problem 1: Terminology and Labels Confusing The terminology and labels used were either too technical or too abstract for users to understand—a far cry from the plain","date" : "2012-12-06T16:43:22-04:00","date_modified" : "2025-01-27T19:42:55-05:00","authors" : {"jonathan-rubin" : "Jonathan Rubin"},"topics" : {
        
            "research" : "Research",
            "usability" : "Usability",
            "user-experience" : "User experience"
            },"branch" : "bc-archive-content-3",
      "filename" :"2012-12-06-weather-gov-usability-case-study.md",
      
      "filepath" :"news/2012/12/2012-12-06-weather-gov-usability-case-study.md",
      "filepathURL" :"https://github.com/GSA/digitalgov.gov/blob/bc-archive-content-3/content/news/2012/12/2012-12-06-weather-gov-usability-case-study.md",
      "editpathURL" :"https://github.com/GSA/digitalgov.gov/edit/bc-archive-content-3/content/news/2012/12/2012-12-06-weather-gov-usability-case-study.md","slug" : "weather-gov-usability-case-study","url" : "/preview/gsa/digitalgov.gov/bc-archive-content-3/2012/12/06/weather-gov-usability-case-study/","content" :"\u003cp\u003eAfter conducting a usability test and listening to customer feedback, the \u003ca href=\"http://www.weather.gov/\"\u003eWeather.gov\u003c/a\u003e team and the DigitalGov User Experience Program identified these three issues as both important and quickly solvable.\u003c/p\u003e\n\u003ch2 id=\"problem-1-terminology-and-labels-confusing\"\u003eProblem 1: Terminology and Labels Confusing\u003c/h2\u003e\n\u003cp\u003eThe terminology and labels used were either too technical or too abstract for users to understand—a far cry from the plain language style required in government. On the homepage, users encountered map tabs for “Graphical Forecasts” and “National Maps”. While these terms have significance for power users, they mean little to casual users.\u003c/p\u003e\n\u003ch2 id=\"solution-1-simplify-language\"\u003eSolution 1: Simplify Language\u003c/h2\u003e\n\u003cp\u003eThe tabs on the top of the map were greatly simplified, using plain language to guide users while providing the same information as before.\u003c/p\u003e\n\u003ch2 id=\"problem-2-navigation-and-branding-inconsistent\"\u003eProblem 2: Navigation and Branding Inconsistent\u003c/h2\u003e\n\u003cp\u003e\u003ca href=\"https://s3.amazonaws.com/digitalgov/_legacy-img/2013/12/weather.gov-before_0.jpg\"\u003e\u003cdiv class=\"image\"\u003e\n  \u003cimg\n    src=\"https://s3.amazonaws.com/digitalgov/_legacy-img/2013/12/weather.gov-before%5c_0-237x250.jpg\"\n    alt=\"weather.gov-before\\_0\"/\u003e\u003c/div\u003e\n\n\u003c/a\u003eIn the example, we can see that a link to NOAA’s main site is provided in the prominent upper left position, while the link for the Weather.gov site is relegated to the far right. A user looking to navigate back to the Weather.gov homepage would more likely click on the link on the left and end up stranded on the NOAA main homepage.\u003c/p\u003e\n\u003ch2 id=\"solution-2-relocate-logos\"\u003eSolution 2: Relocate Logos\u003c/h2\u003e\n\u003cp\u003eA “Home” button was added to each page to ease navigation, and the logos of NOAA and Weather.gov were moved side-by-side to reduce confusion.\u003c/p\u003e\n\u003ch2 id=\"problem-3-too-much-information\"\u003eProblem 3: Too Much Information\u003c/h2\u003e\n\u003cp\u003eThere was simply too much text on the page. The casual user was confronted with a mass of technical wording and links, leaving them with little guidance as to how to find information that might be most useful to them.\u003c/p\u003e\n\u003ch2 id=\"solution-3-move-less-important-information-down\"\u003eSolution 3: Move Less Important Information Down\u003c/h2\u003e\n\u003cp\u003e\u003ca href=\"https://s3.amazonaws.com/digitalgov/_legacy-img/2013/12/weather.gov-after.jpg\"\u003e\u003cdiv class=\"image\"\u003e\n  \u003cimg\n    src=\"https://s3.amazonaws.com/digitalgov/_legacy-img/2013/12/weather.gov-after-156x250.jpg\"\n    alt=\"weather.gov-after\"/\u003e\u003c/div\u003e\n\n\u003c/a\u003eThe text on the original page was reorganized and moved to the bottom, and graphics were added for particularly timely and relevant information. The amount of information for both technical users and the general public remains the same, but the user experience is greatly improved.\u003c/p\u003e\n\u003cp\u003eAs a result of First Fridays testing, the Weather.gov team created a much more streamlined site, while still providing sufficient information to both casual users and weather professionals. The screen capture below is from August 28, 2012. Addressing the usability of your agency’s website is about more than just identifying aesthetic changes. It’s about making sure that every visitor to your website gets the information they need in a quick and clear manner.\u003c/p\u003e\n"}
  ]
}