Skip to main content
U.S. flag

An official website of the United States government

Dot gov

The .gov means it’s official.
Federal government websites often end in .gov or .mil. Before sharing sensitive information, make sure you're on a federal government site.

SSL

The site is secure.
The https:// ensures that you are connecting to the official website and that any information you provide is encrypted and transmitted securely.

The U.S. Web Design Standards team continues to sit down with various agencies who are using the Standards. In this fourth post in our series, we met with the team at the Lab@OPM and learned how they used the Standards to refresh USAJOBS.

Standards team: How did your team find out about the Web Design Standards?

USAJOBS Team: One of our team members learned about the Standards while interviewing for his job at the Lab in the Office of Personnel Management (OPM). After starting the job he went looking for the Standards and after seeing all the work that had been done, he knew the USAJOBS team could leverage them.

Standards team: What other frameworks did you consider?

USAJOBS Team: Bootstrap. Bootstrap was already in use so we had to do some work to modify the grid so elements from the Standards could be used without having to change the markup on the page. Once that was in place we were able to continue moving forward with our use of the Standards.

Standards team: Did you encounter any resistance in your adoption of the Standards?

USAJOBS Team: The development team we were working with was a little hesitant to change things up because they had already been using Bootstrap. However, we gave the pitch on why it’s good to establish your own design system and decided the Standards would be a good foundation for that work.

There were some struggles with how the developers were consuming the design system in their code – they were using compiled assets rather than the Sass files – but it was something we were able to work through. Some folks were less familiar with the idea of using a design system to help create designs and there was a bit of a learning curve, however, over time it was easy to see how using the Standards could speed things up.

Standards team: What were the benefits you gained? How much time or money did this save?

USAJOBS Team: There were so many benefits to switching to the Standards. A lot of time was saved initially just by having a system that’s already in place that we could adopt and adapt. Being able to point to the Standards and have that as a baseline for discussion when making design decisions took a lot of the chaos out of what was happening. Before we started using the Standards our color palette was exploding—and having a boutique style on every page was slowing us down whenever we wanted to change something.

The Standards also helped act as a catalyst for bringing along some user centered design thinking. Having a set of tools that were ready to use helped move things from “researching” to “doing.” We don’t use every component in the Standards—but just about—and the amount of time we saved by not having to build all those components from scratch is difficult to count.

Standards team: How do you plan to use the Standards on future projects?

USAJOBS Team: Outside of the USAJOBS work, the Standards have been used on a career field micro site for Data Science and our Agency Talent Portal product. The Standards will continue to be the starting point for our future digital design projects.

Standards team: What could we offer to make adoption easier?

USAJOBS Team: It would have been great to have more documentation to help developers using PCs with any build issues. The documentation has a Mac/Linux focus and it can be hard for Mac users to talk PC users through the issues they may be seeing.

At one point it wasn’t clear how to contribute back to the project. The barrier of entry was too high, especially for a small team without a lot of free time.

Standards team: What advice would you have for other agencies looking to adopt the Standards?

USAJOBS Team: First off, do it. Don’t delay. We hope folks realize that the potential upside is huge and there is no reason folks should feel they have to reinvent the wheel. In reality, we all have the same types of problems and there is a tipping point where adoption by a lot of groups and agencies within government will help everyone.

Also, start small. If you can only adopt the typeface or color palette, go for it. Do you really need a special typeface? If not, try it out. See if it helps your design discussions move forward and move a bit faster.

Apply the Standards, see if people like them better. Do a usability test. Pick the next thing and move on to that.


We’re looking to learn more from agencies that have used the Standards; if you’re interested in talking to us about your experience or have any feedback, feel free to send us an email at uswebdesignstandards@gsa.gov. You can also chat with the team in the new public Slack channel for the Standards!