This past year, I led an effort to redesign the staff Intranet site for the National Center for Complementary and Integrative Health (NCCIH), at the National Institutes of Health (NIH). After months of surveying, planning, and testing (see the part 1 blog post, How Do You Redesign a ‘Dinosaur’? Redesigning an Intranet Site: the Beginning Stages), the site was launched in Fall 2017. I learned several helpful lessons along the way that I wanted to share:
Many content managers in the digital world understand the irrepressible desire to improve, fix, edit, add, and move things around. It’s our job, after all, to nurture the ongoing process of creating, updating, and testing. But, there are those sites or pages that never seem to make it to the high-priority list. For our Web team, this was our Center’s staff Intranet site. Our Web team recognized that the Intranet was in need of attention.
The Smithsonian’s mission statement is wonderfully simple: “The increase and diffusion of knowledge.” The “increasing” is arguably the straightforward part – the Smithsonian has amassed a collection of over 138 million objects and specimens, and the Institution’s curators and scientists obsessively add to the world’s knowledge base, publishing papers, creating exhibitions, and sharing their expertise. But how can all this informational goodness get passed along to teachers, our nation’s most powerful “diffusers” of knowledge?
What Makes a Native App Successful? There are over 200 native applications in the federal government with various download numbers. Are the ones with the most downloads the most successful? Is the one with fewer users who are more engaged more successful? It depends on what you are trying to accomplish. David Cooper, the Mobile Application Development Lead with the National Center for Telehealth and Technology (T2) and member of the MobileGov Community of Practice, said during a recent DigitalGov University (DGU) webinar, that while vanity metrics such as page views for websites and downloads for apps make you feel good, they don’t tell you anything about how users like your app or site.
Summary: How the U.S. Digital Service worked with students, families, schools, developers and teams across the federal government to rebuild the new College Scorecard tool. My niece is a smart kid. I’m biased, but I swear she is. And just as I started working on the College Scorecard project as the U.S. Digital Service’s new Chief Digital Service Officer at the Department of Education, I got a call from her—she was trying to decide where to go to school.
User Experience (UX) is the comprehensive experience a person has when using a product or application, and usability is the ease of use (or lack thereof) when using it. Many of us have discovered the vast advantages of evaluating usability on our own; however, getting others to jump on board is often a different story. The most difficult part of integrating an effective UX program in your organization is getting the initial buy-in from developers and stakeholders.
So, you have some systems or tools your customers or employees access. Maybe you want to put together a robust capability to conduct usability testing. How do you start formalizing user experience (UX) into your organization? Brad Ludlow at GSA tossed this topic out on the User Experience community listserv, and I’ve encapsulated the superb discussion that followed below. Here, then, are four easy steps to building User Experience into your office:
They say that necessity is the mother of invention. For me, the necessity resulted from long product development cycles paired with short windows for user testing and little room for iteration. The “invention” was the discovery of a powerful set of tools for prototyping that are available on just about every office computer. I found that you can use “Developer Tools” in Microsoft Office’s Excel, Powerpoint and Word to not only draw the basic outlines of a wireframe but also build a functioning prototype that simulates many of the features you want in your final product.
The PTSD Coach mobile app from the Department of Veterans Affairs, provides veterans and users with information about PTSD and professional care, along with self-assessment tools and aid in finding support opportunities. The app has been downloaded over 100,000 times in 74 countries around the world, received numerous accolades and has spawned versions in both Australia and Canada. Designed for users that are both in treatment and not, this application is a poster-child for the benefits of user testing and paper prototyping.
When it comes to Web and software design, the pen(cil) is often mightier than the Design Suite. What I mean is: Tech is cool, but don’t fall under its spell. It’s often when you remove the technological layers between you and your thoughts that the best ideas sprout. You’ve heard of great ideas that started on bar napkins, right? One way that low-tech beats high-tech is when it comes to conceptualizing early-stage design ideas.
What if a single piece of paper could make your mobile app work 20% better? It’s hard to imagine something as unimpressive as paper influencing our 21st century smartphones, but it’s true. Well before we get into the design and coding phases, we can show customers a mockup of an idea of what our product might look like. It’s called a prototype (or a wireframe)—it’s a model of a design that’s still in development.
For a children’s site, Kids.gov is pretty old—it was launched back in 2001. And it has the unenviable task of trying to keep pace with the rapidly changing online habits of youngsters. So in 2012, Kids.gov Director Arlene Hernandez thought her site was due a usability test with its two main audiences: kids and their parents. Hernandez already had a good deal of data on the current design based on Web traffic and emailed feedback.