{
    "version" : "https://jsonfeed.org/version/1",
    "content" : "news",
    "type" : "single",
    "title" : "How to Use Remote Data Strategically in UX |Digital.gov",
    "description": "How to Use Remote Data Strategically in UX",
    "home_page_url" : "/preview/gsa/digitalgov.gov/cms/news/2024/07/2024-07-02-case-study-increasing-access-to-required-bankruptcy-meetings/","feed_url" : "/preview/gsa/digitalgov.gov/cms/news/2024/07/2024-07-02-case-study-increasing-access-to-required-bankruptcy-meetings/2015/11/17/how-to-use-remote-data-strategically-in-ux/index.json","item" : [
    {"title" :"How to Use Remote Data Strategically in UX","summary" : "One of the challenges UX practitioners can face is how to communicate much of the data that’s out there. The key word is “communicate.” Since many of us are used to qualitative findings, making the jump to “hard data” can be a challenge. There are tools out there that make this easier, but we still","date" : "2015-11-17T13:00:55-04:00","date_modified" : "2024-07-05T22:14:24-04:00","authors" : {"justin-dopke" : "Justin Dopke"},"topics" : {
        
            "analytics" : "Analytics",
            "user-experience" : "User Experience"
            },"branch" : "cms/news/2024/07/2024-07-02-case-study-increasing-access-to-required-bankruptcy-meetings",
      "filename" :"2015-11-17-how-to-use-remote-data-strategically-in-ux.md",
      
      "filepath" :"news/2015/11/2015-11-17-how-to-use-remote-data-strategically-in-ux.md",
      "filepathURL" :"https://github.com/GSA/digitalgov.gov/blob/cms/news/2024/07/2024-07-02-case-study-increasing-access-to-required-bankruptcy-meetings/content/news/2015/11/2015-11-17-how-to-use-remote-data-strategically-in-ux.md",
      "editpathURL" :"https://github.com/GSA/digitalgov.gov/edit/cms/news/2024/07/2024-07-02-case-study-increasing-access-to-required-bankruptcy-meetings/content/news/2015/11/2015-11-17-how-to-use-remote-data-strategically-in-ux.md","slug" : "how-to-use-remote-data-strategically-in-ux","url" : "/preview/gsa/digitalgov.gov/cms/news/2024/07/2024-07-02-case-study-increasing-access-to-required-bankruptcy-meetings/2015/11/17/how-to-use-remote-data-strategically-in-ux/","content" :"\u003cp\u003eOne of the challenges UX practitioners can face is how to communicate much of the data that’s out there. The key word is “communicate.” Since many of us are used to qualitative findings, making the jump to “hard data” can be a challenge. There are tools out there that make this easier, but we still need some explanations and/or translations. \u003cdiv class=\"image\"\u003e\n  \u003cimg\n    src=\"https://s3.amazonaws.com/digitalgov/_legacy-img/2015/04/600-x-400-Computer-keyboard-with-infographics-element-stevanovicigor-iStock-Thinkstock-478655615.jpg\"\n    alt=\"A keyboard key has a green button with a bar chart on it.\"/\u003e\u003c/div\u003e\n\n\u003c/p\u003e\n\u003cp\u003eFirst, let me be clear that I am not endorsing any product or technique. At our agency, we now use \u003ca href=\"/preview/gsa/digitalgov.gov/cms/news/2024/07/2024-07-02-case-study-increasing-access-to-required-bankruptcy-meetings/guides/dap/\"\u003eGoogle Analytics\u003c/a\u003e. We previously used WebTrends. In the past, this data had to be gathered through server logs, and it was up to the individual to make it understandable.\u003c/p\u003e\n\u003cp\u003eAs long as the data collection is set up for the site, the data should be there to be analyzed; if it hasn’t been set up, you will need to communicate to the client why it should be, and why you want to look at it. I have found this information useful in:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eStrategic planning (who to target, what to ask/what to focus on, when to look for data (date ranges)\u003c/li\u003e\n\u003cli\u003eWhere your users are located\u003c/li\u003e\n\u003cli\u003eHow they access your content (devices/operating systems). If this information has been collected you can use it to help you isolate areas of interest\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eSo, how can we as UX folks use this to our advantage? In my experience much of this information (the “how” and “where”) can be useful as up-front research (for existing, web-based services). It can be used to identify:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eWhere usability issues may exist (bottle necks, etc.)\u003c/li\u003e\n\u003cli\u003eOverly long processes (pathing, average times, drop-out pages)\u003c/li\u003e\n\u003cli\u003eMost popular pages/services (you don’t want to take anything away…)\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eNow, it still takes some speculation on our part to come up with the proper questions to ask, (the WHY questions) but at least we’re not flailing around in the dark. I’m not a marketing expert, nor do I claim to be, but by using this data we can at least identify what parts of the site to focus on (in terms of redesign), and what parts could be left alone (we don’t want to fix what isn’t broken!). It might be tempting to speculate about this to come up with the answers for the “how” questions, but remember: “Correlation does not equal causation.” We don’t know WHY until we ask the users.\u003c/p\u003e\n\u003cp\u003eIn order to make the most of this information, first, find out who “owns” it. If your organization is large—like mine is, you will need to request access to it. Building a relationship with that group or person can be helpful. Have some idea of what you are going to look for before you start. Since I work on EXISTING sites, entry/exit pages can give you an idea of what sections are the most popular/most used. Also, comparing returning visitors vs. new visitors can help you identify popular/most accessed content. If you are building a new site, or if this kind of information isn’t being collected yet—put it in as one of the recommendations. Think longer term here—this is a good way to stay involved with a project after you hand it off, and it will make future work easier. You may use this to inform redesign or back up recommendations. These tools collect a lot of information, so keeping your objectives clear is important: Who are your users, what are they looking for/are they accessing, where are they (geographically), how are they coming to you site (OS/device)—much of this info can be gathered through these tools. \u003cdiv class=\"image\"\u003e\n  \u003cimg\n    src=\"https://s3.amazonaws.com/digitalgov/_legacy-img/2015/11/600-x-450-Set-of-3D-infographic-elements-for-business-aqabiz-iStock-Thinkstock-477799640.jpg\"\n    alt=\"Set of 3D infographic elements\"/\u003e\u003c/div\u003e\n\n\u003c/p\u003e\n\u003cp\u003eOnce you have your info, these tools most often \u003ca href=\"/preview/gsa/digitalgov.gov/cms/news/2024/07/2024-07-02-case-study-increasing-access-to-required-bankruptcy-meetings/2014/03/04/creating-awesome-web-analytics-reports-and-presentations/\"\u003eput it into charts or graphics\u003c/a\u003e; if it doesn’t tailor to what you are trying to communicate, \u003ca href=\"/preview/gsa/digitalgov.gov/cms/news/2024/07/2024-07-02-case-study-increasing-access-to-required-bankruptcy-meetings/2014/05/22/visualizing-federal-data/\"\u003elook to your graphics department\u003c/a\u003e.\u003c/p\u003e\n\u003cp\u003eIn terms of what to do next, well, that is really up to you and your client. Remember—these are TOOLS, not solutions. The key here is to work smarter, not harder—but you still need to work…\u003c/p\u003e\n"}
  ]
}