<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Digital.gov</title>
    <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/authors/troy-kitch/</link>
    <description>Recent content on Digital.gov</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="/preview/gsa/digitalgov.gov/bc-archive-content-3/authors/troy-kitch/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>NOAA National Ocean Service &amp;#8211; Usability Case Study</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2014/04/14/noaa-national-ocean-service-usability-case-study/</link>
      <pubDate>Mon, 14 Apr 2014 10:00:04 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2014/04/14/noaa-national-ocean-service-usability-case-study/</guid>
      <description>For a small shop with a small staff, limited time, and a small budget, redesigning a website (and testing that redesign for usability) can be daunting. At least it seemed so to us when we redesigned the National Oceanic and Atmospheric Administration (NOAA)’s National Ocean Service website in November of 2013. We met the challenge</description>
    </item>
  </channel>
</rss>
