Profile image forJonathan Rubin

Jonathan Rubin

News and Events

Data.gov – Usability Case Study

We all know listening to your customers is important. Not just reading their comments, but talking to them, actually getting in a room with them, and having them test your product. But if basing a whole-scale redesign around one series of user conversations makes you nervous – it should. That’s because sometimes when we listen,
Mar 18, 2014

Usability testers unite! Join our Community

I’m the kind of guy who loves tests. Not SATs, or BMI tests, but usability tests: connecting target customers with a government website and watching how they interact with it. Our DigitalGov User Experience Program (formerly known as First Fridays) has taught dozens of agencies how to conduct
Sep 17, 2013

Business.USA.gov – Usability Case Study

When redesigning a site, it’s easy to place menu items, text and other content wherever you can make them fit. It’s harder to take a step back and ask the strategic question: Is this the best place for this? A good rule of thumb is to never make any changes randomly—base your decisions on user
Jul 02, 2013

Fueleconomy.gov – Usability Case Study

Many technical websites have a hard time explaining information to the general public. This happens because users don’t understand the industry-specific or scientific terms. Fortunately, solutions to these problems are fairly easy—changing menu and navigation item text, or adding a line of explanatory text on key pages or complex graphics. The DigitalGov User Experience Program
Jul 02, 2013

Army.mil – Usability Case Study

If you want to make a website more efficient and user friendly, then it’s not enough just to have your most valuable information on the site. People are busy—they want to find what they’re looking for, and they want it fast. You don’t always need to redesign an entire site to make things easier to
Jun 19, 2013

ATF.gov – Usability Case Study

The Bureau of Alcohol, Tobacco, Firearms, and Explosives has some really valuable information for the public that a lot of people search for on ATF.gov. It’s important that the information is easily and quickly accessible. Government agencies reach a wide audience with their information, so making sure everyone can understand your content is important. The DigitalGov User
Apr 29, 2013

How to Do Usability Testing with Kids

What do kids know about Web design? As we found out, quite a lot. Recently our DigitalGov User Experience Program teamed up with the Kids.gov team to get some big time feedback from some pint-sized testers in a hallway test. We tested with almost 20 kids ages 6 to 14 at our GSA office,
Apr 26, 2013

Regulations.gov – Usability Case Study

More and more people use search as their primary means of finding what they are looking for. When users get confused by the search results, or can’t immediately find what they are looking for, they’re going to get frustrated. They may even leave the site for good. The DigitalGov User Experience Program helped test Regulations.gov on October 5, 2012, to
Mar 22, 2013

SaferBus Mobile App – Usability Case Study

When designing a site, remember that your terms and icons are like signposts that show people where your links and pages lead. Make sure that you use words and pictures that are easily understood or people will have trouble using your site. Small changes like underlining links or adding arrows to indicate expandable information can
Mar 21, 2013

Contractor Vehicle Navigator – Usability Case Study

When users interact with a website to find information, it is important that we help them find their way by using plain language, clear terminology and visible help text. On December 7, 2012, the DigitalGov User Experience Program helped test the U.S. General Services Administration’s Contract Vehicle Navigator website. This Navigator site helps contracting officers find
Feb 19, 2013

SAM.gov – Usability Case Study

One of the most vital parts of any website is its starting point. When a visitor arrives on the main page of your site, they should be able to quickly tell what the main tasks are and how to perform them. Visual cues and plain language are the best ways to accomplish this. The SAM.gov
Dec 17, 2012

IRS – Usability Case Study

Acronyms and jargon are fine when you want to communicate quickly to an internal audiences or to like-minded readers. Once the scope of your audience widens, however, these elements can make your pages harder to understand. The IRS recognized that its pages about tax planning for retirement were reaching an audience beyond tax professionals, and
Dec 14, 2012

Weather.gov – Usability Case Study

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
Dec 06, 2012

NSF.gov – Usability Case Study

Many government websites are informational in nature – you don’t sign up for things or buy anything. Instead, you look for something – a name, a ruling, some contact information. Informational sites – and scientific sites in particular – can be a challenge to design. With so much information, how do you make the important
Nov 05, 2012

GSA Intranet (Insite) – Usability Case Study

Not all usability changes are dramatic. Sometimes a few small tweaks can make a site significantly easier to navigate, or make important but hidden content pop off the page. The DigitalGov User Experience Program helped test Insite, GSA’s intranet, on September 21, 2011. GSA took the feedback from their usability test and made some changes to the
Oct 15, 2012

FedRAMP – Usability Case Study

Websites allow newer government programs to establish a visual identity that introduces them to users and conveys the importance of their work. On April 18, 2012, the DigitalGov User Experience Program helped test GSA’s Federal Risk and Authorization Management Program (FedRAMP) site, which at that point was less than six months old. Three immediate needs were
Oct 15, 2012