This is the first in a series of blog posts on Human-Centered Government that we’re publishing in partnership with our friends at Apolitical: the social learning network for government.
“Why are so many government websites hard to use?” This is a question consistently asked by policymakers, government employees, and the public.
And it’s not just websites. All sorts of government tech projects have challenges. One report found that only 13% of large government software projects are successfully completed on time, on budget, and on target.
In our decade-plus of working with governments to deliver critical services to people that not only met their needs, but treated them with respect and dignity as well, we’ve found that there are three common factors that tend to complicate these projects:
- “Clunky” approaches and practices: project scopes that are too large and rigid, with too many upfront specifications and not enough iterative development.
- Not focusing on people-centered tech practices like user research, design, and product management.
- Insufficient technical capacity and expertise.
To be fair, these challenges are not unique to government. They’re common in the private and nonprofit sectors too. There are also many cases of well-functioning government websites that power services that are simple, accessible, and easy to use. Still, addressing these key issues can make a world of difference in delivering better public services. Let’s explore how:
1. “Clunky” approaches and practices
Government needs many goods and services to function, from bridges to fire trucks to pencils. Traditional budgeting and procurement treats digital technology as if it’s similar to a large physical item by requiring:
- A long timeline for planning, budgeting, procurement, and delivery—often measured in years.
- A precise understanding of how people will use it before it’s purchased or built.
- Long, detailed lists of requirements specified at the beginning of the process.
- A clear definition of when something is “done”.
This approach doesn’t work well for software. As our friends at 18F put it, “Technology changes, government policies change, regulations change, laws change, and leadership’s priorities change—any project that is planned in great detail up front will be unable to adapt to those changes, and will be at significant risk of failure, significant cost and deadline overruns, or costly ‘change orders.’”
Rather, treat software as a service that is constantly being improved rather than a big item bought once. “Fund product teams, not projects.” If work is being contracted out, break it up into small “modular” contracts.
Treat software as a service that is constantly being improved rather than a big item bought once.
2. Not focusing on people-centered tech practices
Often, government digital tools technically do what they’re supposed to do—but in a way that doesn’t work well for the people who use them. A big culprit can be inadequate user research, design, or product management. Governments may not employ people with these skill sets—or if they do, there might not be enough of them. Meanwhile, vendor contracts used to purchase technology may not have these practices included in their scope.
Each of these practices plays an important role in delivering effective, easy-to-use digital services digital services:
- User research is the process of learning about people’s “needs, behaviors, experience and motivations through various qualitative and quantitative methods to inform the process of solving for [their] problems.”
- Design covers several aspects, including user experience (UX), user interface (UI), content strategy, and service delivery. Designers are critical in blending product goals with user insights to create systems and technology that work well for the people who need to use them.
- Product management is the practice of strategic direction of a product throughout its lifecycle. Product managers “prioritize, communicate and align stakeholders and teams around: what needs to be built, why and for whom the product is being built, [and] how it will be built and delivered.” They are not the same as project managers. Though a staple of private-sector digital teams, they are uncommon in government.
When the needs and experiences of real people aren’t placed front and center throughout the development process, a lot of money and time may be spent on software that doesn’t deliver on what the people who are using it actually need.
3. Insufficient technical capacity and expertise
Despite digital technology being a key part of government operations, it’s common for governments to lack the tech knowledge and skills needed to plan, manage, and implement such projects and services. This creates challenges both for the large portion of government IT work that is contracted out to the private sector as well as for efforts to develop technology internally.
- At the administrative/leadership level, legislators, executives, and policy staff often lack appropriate knowledge that’s critical for strategy, policy, and budgeting.
- Staff in procurement offices and mission agencies sometimes lack the domain-specific knowledge needed to effectively write RFPs, evaluate vendors, and act as good product owners for digital technology; it’s hard to oversee the work if you don’t know how the work should be done.
- When it comes to the actual technology development and delivery, some work is contracted out that would actually be cheaper or more efficient to do in-house but can’t because of insufficient internal staff skills and/or expertise in key digital disciplines.
Common challenges that governments face in hiring certain types of digital specialists include: complex hiring processes, outdated job titles, below-market salaries, degree requirements, and bureaucratic work rules. By addressing some of these issues—as well as educating policymakers and upskilling existing employees—governments can greatly improve their digital capabilities.
Where do we go from here?
On top of these key issues, there are several others that further complicate matters: complex laws and policies about government programs; requirements related to security, privacy, and accessibility; and divisions between different departments and agencies as well as different levels of government.
As challenging as some of the issues in this post may seem, they can absolutely be addressed. We regularly see examples both in our work at Code for America and beyond.
This fall, we will publish a series of blog posts addressing each of these major issues presented above. By confronting these challenges head on, we can help make government work for the people, by the people, in the digital age.