<?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/georgia-gallavin/</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/georgia-gallavin/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>4 Tips on Great Survey Design</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2014/11/10/4-tips-on-great-survey-design/</link>
      <pubDate>Mon, 10 Nov 2014 10:00:40 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2014/11/10/4-tips-on-great-survey-design/</guid>
      <description>Whether they pop up while perusing an e-commerce site or land in your inbox after your bumpy flight in from Chicago, surveys are used in many different industries to gauge customer satisfaction and glean insight into user motivations. They are a useful tool in the kit of a user experience designer or anyone</description>
    </item>
    <item>
      <title>System Usability Scale (SUS): Improving Products Since 1986</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2014/08/29/system-usability-scale-improving-products-since-1986/</link>
      <pubDate>Fri, 29 Aug 2014 10:15:49 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2014/08/29/system-usability-scale-improving-products-since-1986/</guid>
      <description>Trying to measure usability can be a head scratcher. How easy something is to use depends on where you are, who you are, and a number of other factors. Luckily in the world of usability, there exists a post-test survey known as the System Usability Scale, introduced in 1986 by an engineer named John Brooke,</description>
    </item>
    <item>
      <title>API Usability Case Study: openFDA</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2014/08/22/api-usability-case-study-openfda/</link>
      <pubDate>Fri, 22 Aug 2014 09:32:53 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2014/08/22/api-usability-case-study-openfda/</guid>
      <description>The API Usability Program brings together developers from agency APIs and the private sector to evaluate how the API can be improved to be more user friendly. Sean Herron of 18F, who was a key member of the openFDA developer team, shared with us some of the major insights gained from this latest API usability session.</description>
    </item>
    <item>
      <title>Heat Mapping Case Study: Epa.gov Homepage</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2014/08/12/heat-mapping-case-study-epa-gov-homepage/</link>
      <pubDate>Tue, 12 Aug 2014 11:00:17 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2014/08/12/heat-mapping-case-study-epa-gov-homepage/</guid>
      <description>Most people relate the term “heat map” with something they see during the weather forecast on the nightly news, those colorful maps that vividly illustrate how hot it’s going to be during an impending heat wave. The word “heat map” may not usually however, conjure up images of a widely used Web usability tool; but for those</description>
    </item>
  </channel>
</rss>
