Main Content
Top Pain Points for Public Sector Website Stakeholders

Public Sector Sites: Top Pain Points and a Key Fix

Websites for state and local governments are being called upon to do more heavy lifting than ever before. 

Digital transformations and a wide range of initiatives in pursuit of greater efficiencies were well in the works at the start of 2020. Covid-19 took it up several notches -- driving home the imperative for modern and easy-to-navigate online interactions that engage the entire spectrum of constituents, while stepping up sites to serve as the virtual town square for connecting and conducting business. 

Fully 76 percent of local government officials indicated in a recent survey that Covid-19 has resulted in a sharpened focus on online community engagement. 

Within an environment of heightened expectations for rapid evolution and quick pivots, public sector sites are experiencing all kinds of growing pains.

  • Content editors need to be able to easily make updates, revise layouts, or spin up new pages without filling out a ticket with IT or making the case for why a particular revision is a priority.
  • Citizens have high expectations for quickly finding the information they need, with an efficient, value-added user journey that speaks their language.
  • A wide range of stakeholders are focused on the vast cost savings that can result from transferring administrative functions to the website whenever possible. A recent IRS study revealed that the cost for an in-person visit to a tax center amounted to $64 and the cost of a phone call amounted to $41 -- vs. $0.10 for a website visit.
  • Compliance officers face a range of issues. Even though compliance considerations can vary by state and municipality, The 21st Century Integrated Digital Experience Act (or 21st Century IDEA), which applies to Federal Government sites, can serve as a solid standards framework for modernization, accessibility, digitization of services and forms, and improved user experiences. 

Conversations with a wide range stakeholders for state and local government sites reveal one, overarching factor that can complicate efforts to ensure that public sector sites are positioned to meet current and future needs and expectations. 


Pain Point: Vendor Lock-In

An overarching pain point, and the issue from which many other challenges emerge concerns proprietary vs. open source CMS software. Flexibility is now an essential success factor, and stakeholders who have found themselves dependent upon the constraints of the licensing contract with the vendor that developed their CMS, are often a significant disadvantage.  

At Promet Source, we’re avid open source advocates, and for reasons that include the benefits of collective brainpower, tighter security, and cost efficiency. Our conviction is one that’s largely shared by the Federal Government

State and local governments that opt for proprietary CMS software solutions that were developed and are owned by individual companies, find themselves committed -- for the life of their website -- to a web developer that owns the code. That’s what’s called Vendor Lock-In and the the impact is far from optimal.


Advantages of Open Source

As constituent expectations evolve and needs change, stakeholders whose websites were built by web developers that deploy their in-house developed, specialized software, often find themselves in an uncertain spot -- hoping that the developer of their site will continue to invest in and maintain the software. It is also hoped that the company stays in business, that the level of support does not decline, and that the website’s features and functionality continue to evolve with the latest technology and trends. 

Hope does not tend to go very far as a business strategy, and the honeymoon that follows the build or launch of a new site can go in any number of unexpected directions. Private companies can radically shift directions. It happens every day.

And even if a proprietary CMS is developed by a team of tech geniuses who are committed for life to the success of the company and its clients, it is possible for a proprietary solution to come anywhere close to the level of innovation that’s fueled by an open source community such as Drupal.


What about Security?

The concept of open source can be counter intuitive, as the term, "open" is often not equated with "secure."  Fact is though, security is an essential advantage of open source.

Open source software allows for thorough auditing of the code for purposes of detecting potential security threats. Site owners can modify the code as they see fit -- whether to enhance security or customize a site to meet their specific needs. 

The Drupal community is constantly monitoring for and alerting Drupal support partners to security threats, and users are thoroughly empowered on their own to shore up any vulnerabilities that they detect. 

The Fix: Optimal Flexibility

The worldwide Drupal community exceeds 1 million members -- 100,000 of whom are are actively supporting each other, creating documentation, sharing networking opportunities, and building freely available modules in response to constantly evolving market needs and expectations. 

An essential difference when working with a Drupal developer vs. a proprietary developer is this: While there’s no guarantee that either will live up to expectations over the long haul, if a Drupal developer goes out of business or let’s a public sector client down the tooling and investment in the Drupal site remains intact. The client owns the code and there are countless of other Drupal developers willing and able to pick right up on the building or supporting the site. 

A final note on the inherent vendor lock-in that results from deployment of proprietary CMS software: many have pointed out subtle, but significant, cultural distinctions between  proprietary software developers and open source web development agencies. Proprietary agencies tend to be more invested in the sales pitch and messaging. Open source agencies are more developer driven with a focus on customization and support.

At Promet Source, our alignment with open source is both philosophical and practical. It turns out that freedom from the limitations of costly software licensing contracts while leveraging the innovative output and problem-solving skills of a vast global network of experts is a foundation for superior web design and development.

Interested in moving forward with web solutions that are focused on the big picture of current and future expectations for public sector sites? Let’s talk

How to subscribe to the Promet newsletter