9 ways to make your government website better (Part 1)
I spend a lot of time on government websites.
I probably hold the world record for number of government website visits.
Having recently gone on a whirlwind, marathon tour of the .gov web, I was a little more than taken aback by what I perceive to be standard web practices that are consistently not being used by government.
In an effort to help others, here’s a random, whimsical list of recommendations I have for government website designers, developers and social media managers to help make the web user experience better for citizens and journalists (I’m calling this “Part 1” because I may revisit this in the future with additional recommendations).
Be responsive. Any government that doesn’t incorporate responsive web design into their websites from now going forward is not thinking strategically. This is not a complicated request of your web team or vendor, especially if you’re launching a new site. Just tell them “we want responsive design.” Before you develop a mobile website or application, invest that effort and resources into integrating responsive web design into your web presence. This will save you time, money and the citizen experience will be seamless and much more enjoyable.
Don’t create separate websites for agencies and senior-level executives. I’ve often clicked on a link to an agency or executive-level official only to find myself in a completely different place on the Internet. The user experience is disjointed, and it’s a waste of money to develop an entire web project for what could be folded into a uniform interface and development environment.
Get a content management system. It’s clear many government websites still are using static pages. Adopting a content management system not only separates the design from the content, but it forces you into a different mindset with respect to delivering information to citizens. If money is an issue, there are a number of world-class, free content management systems you can use.
Create a /social page. Everyone is using Facebook, Twitter, Flickr, Instagram and other social media platforms. Government is no exception. Create a single page on your website (yourdomain.gov/social) that serves an agency/executive directory with all related social media accounts, including email subscriptions and RSS feeds. Give users one page to see all the ways they can connect with you. Make this accessible from every page of your website.
Incorporate reliable search. This is a little tougher, but in a world of Google, most web users these days are search-savvy, and it will be the first option used to find information (especially if you site isn’t well-organized). As with content management systems, there are freely-available search options to incorporate into your site relatively easy (and free).
URL/social media naming conventions for senior positions should be generic. When I see an elected official using a URL naming convention that incorporates his or her name, I see a lost opportunity for continuity. As a citizen, if I’ve bookmarked your page or followed your account on social media platforms, I lose a critical connection with government once you leave office or move to a different position. It’s fine for an official to have his or her own account, but there should always be an official, regularly updated companion.
Create an agency contact page. Similar to /social, an accessible /contact page that includes agency listings with email, phone, mail contact is critical, especially for journalists. As with /social, make this accessible from every page of your website.
Give Flickr photos some love. Photos are one of the most powerful ways government can communicate with citizens. They’re also a great resource for bloggers, journalists and online news outlets. When uploading to Flickr (or any other photo-sharing platform), make sure to flag as government work or no rights reserved so that others know they can freely repurpose (most government works are, but it’s confusing to see “All rights reserved”). Also, be sure to add titles and descriptions (including date and location) for context.
Make it easy to subscribe via email. Email is still a valuable way to connect with citizens. Create a simple subscription form and request just an email address. The more fields you add, the less likely someone will subscribe. One recent form required name, email, phone and address. You don’t need any of that.
I would love to hear from others on best practices or ideas not being leveraged but should be.
Every day I get to engage with entrepreneurs, public sector innovators and journalists on re-imagining and re-energizing how government works, what it means to be “civic,” and this year has been an incredible one for many friends and colleagues.
I’m always inspired talking and working with entrepreneurs trying to solve big civic problems, especially those who realize much of the challenge lies within modernizing and empowering internal government operations, so it was great to finally meet with Govtech Fund Founder and Managing Partner Ron Bouganim this week.
The 18F Delivery team released a “Partnership Playbook” that aims to help federal agencies understand what to expect when working with 18F, and the gem within is play number two, “We work with an empowered product owner.”
Citizens simply glaze over when they are confronted by a sea of large numbers with many zeros. These figures need to be relatable to the person reading the data. Otherwise, open data is just more data that dies on the vine.
The U.S. Department of Veterans Affairs released a beta version of Vets.gov, and it’s the future of federal government digital development.
The Welsh Government released a report of its findings on how local government in Wales can better leverage digital technologies and realize significant savings while still providing quality, scalable citizen services.
A California bipartisan oversight committee, the Little Hoover Commission, has issued recommendations on how the state can bring a more customer-centric government to residents and visitors.
Seneca Systems CEO Chris Maddox shares the inspiration behind the new constituent relationship management system, Romulus.
“No ugly, old IT” jumped out at me when I first reviewed DataSF’s strategic plan, “Data in San Francisco: Meeting supply, spurring demand,” and it still sticks, mostly because someone inside government was so bold as to make this a priority and openly communicate it and also because this should be a mantra for everyone building civic technology.
Enabling internal government tech shops to quickly stand up applications in a secure testing environment is fundamental to quick prototyping, and 18F’s new Cloud.gov is a major step in realizing ultimate IT flexibility.