Skip to content
This repository has been archived by the owner on Nov 10, 2020. It is now read-only.

Commit

Permalink
Merge pull request #3615 from ONRR/dev
Browse files Browse the repository at this point in the history
Dev-->Master
  • Loading branch information
jennmalcolm authored Feb 11, 2019
2 parents c8bf4e5 + 9b95fe6 commit 960d416
Show file tree
Hide file tree
Showing 4 changed files with 8 additions and 3 deletions.
2 changes: 1 addition & 1 deletion _config.yml
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ url: https://revenuedata.doi.gov

# app version number

version: v4.3.2
version: v4.3.3

exclude:
# top-level log
Expand Down
4 changes: 3 additions & 1 deletion blog-site/src/pages/usability-testing-training/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ date: "2019-02-07"

We have a small team: a product manager, one developer, one designer, one content strategist, and 3 program analysts. Our analysts are subject matter experts who know the site’s data, but they split their time between working on our website and managing a committee. To stretch our team further and make all of us better, we’re always looking for cross training opportunities.

Our user experience designer has been running the usability testing process – from recruiting participants to building prototypes – by herself. As the website grows in scope, it takes up an increasing amount of her time. As such, we decided it would be helpful to peer-train two of our program analysts to conduct usability testing. Prior to the training, both analysts had participated in usability testing by taking notes throughout user interviews and helping to summarize the interview sessions. Since the [Paperwork Reduction Act](https://github.com/ONRR/doi-extractives-data/wiki/What-you-need-to-know-about-doing-design-and-research-in-the-federal-government) prohibits us from recording user interviews, our team takes notes and debriefs right after the sessions to make sure we didn’t miss anything important.
Our user experience designer has been running the usability testing process – from recruiting participants to building prototypes – by herself. As the website grows in scope, it takes up an increasing amount of her time. As such, we decided it would be helpful to peer-train two of our program analysts to conduct usability testing. Prior to the training, both analysts had participated in usability testing by taking notes throughout user interviews and helping to summarize the interview sessions. Since [logistics](https://github.com/ONRR/doi-extractives-data/wiki/Research-norms-and-processes#make-a-consistent-usable-record-of-the-session) prohibit us from recording user interviews, our team takes notes and debriefs right after the sessions to make sure we didn’t miss anything important.

## Process

Expand Down Expand Up @@ -50,3 +50,5 @@ The analysts are already thinking about ways to apply design thinking to our oth
Now that the program analysts are becoming more familiar with the user research process, they have also provided good ideas for improving the process. For example, we will be exploring the use of a spreadsheet instead of documents to take notes, in order to cut out some of the work of copying and pasting from multiple docs into a consolidated spreadsheet when doing analysis. That will also allow us to start coding the findings into like issues as we go.

The next step is for the analysts to plan and conduct a study with real users. Increasing our capacity for user research will help us build bridges with other teams in our agency who are working on products that could benefit from user feedback. We hope to help introduce user-centered design practices to those teams.

*__Correction:__ This blog post originally stated that the [Paperwork Reduction Act](https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/inforeg/PRAPrimer_04072010.pdf) prohibited us from recording user research sessions, but we have since learned that the Act doesn't actually prohibit us from doing that. (Yay! Something we can look into doing in the future.)*
3 changes: 3 additions & 0 deletions blog-site/src/templates/blog-post.js
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,7 @@ import get from 'lodash/get'

import Layout from '../components/layout'
import { rhythm, scale } from '../utils/typography'
import favicon from '../../static/img/favicon.ico'

class BlogPostTemplate extends React.Component {
render() {
Expand All @@ -20,6 +21,8 @@ class BlogPostTemplate extends React.Component {
htmlAttributes={{ lang: 'en' }}
meta={[{ name: 'description', content: siteDescription }]}
title={`${post.frontmatter.title} | ${siteTitle}`}
link={[{ rel: 'shortcut icon', type: 'image/png', href: `${favicon}` }]}

>
{/* Digital Analytics Program roll-up, see the data at https://analytics.usa.gov */}
<script src="https://dap.digitalgov.gov/Universal-Federated-Analytics-Min.js" id="_fed_an_ua_tag"></script>
Expand Down
2 changes: 1 addition & 1 deletion gatsby-site/gatsby-config.js
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ module.exports = {
siteMetadata: {
title: 'Natural Resources Revenue Data',
description: 'This site provides open data about natural resource management on federal lands and waters in the United States, including oil, gas, coal, and other extractive industries.',
version: 'v4.3.2',
version: 'v4.3.3',
googleAnalyticsId: GOOGLE_ANALYTICS_ID,
},
plugins: [
Expand Down

0 comments on commit 960d416

Please sign in to comment.