Replacing technology that powers government services is a monumental decision. It requires thoughtful deliberation and strategic execution, given the significant impact these systems have on public welfare, compliance with laws, and operational efficiency. As the saying goes, “The pain of keeping a system has to be greater than the pain for replacing a system, or you should never replace what you have.” This principle underscores the critical elements to consider before initiating a technology replacement project.
Timing is everything in government technology projects. A rushed replacement can lead to implementation failures, while waiting too long might exacerbate the risks of outdated systems. Factors influencing timing include the system’s lifecycle, potential penalties for non-compliance with federal mandates, and the readiness of stakeholders to adapt to new technology. Strategic planning ensures that transitions occur during low-demand periods or before critical deadlines, minimizing disruptions to services.
Effective governance is the backbone of any successful technology replacement. A well-defined governance structure clarifies roles, responsibilities, and decision-making processes. This ensures that stakeholders—including IT staff, program administrators, and external partners—align on goals and priorities. A steering committee or governance board should oversee the project, mitigating risks and ensuring accountability at every stage.
The selection of a credible vendor can make or break a project. Governments must rigorously evaluate vendors for their track record, expertise, and ability to meet specific needs. This includes reviewing references, assessing financial stability, and conducting comprehensive evaluations of proposed solutions. An ideal vendor should demonstrate experience in delivering projects of similar scale and complexity, particularly in the public sector.
Securing legislative approval is a critical step, particularly for projects that require substantial funding or policy changes. Lawmakers need to understand the risks of maintaining the status quo and the benefits of the proposed replacement. Building a compelling case backed by data and aligning the project with broader policy goals can facilitate smoother approval processes.
Federal mandates often drive the need for system upgrades or replacements. Compliance with regulations such as those governing healthcare, cybersecurity, or data privacy is non-negotiable. Governments must ensure that new technology aligns with these mandates, avoiding penalties and ensuring continued access to federal funding.
End-of-life systems pose significant operational and security risks. Vendors may no longer provide updates, leaving the system vulnerable to cyber threats and performance degradation. Governments must weigh the costs of maintaining such systems against the potential fallout from their failure, ensuring timely replacement to mitigate risks.
Determining the right deployment model is a critical decision.
Offers full control over hardware and software but demands significant resources for maintenance and upgrades.
Involves hosting government systems in a secure third-party data center, balancing control with reduced infrastructure responsibilities.
Provides flexibility, scalability, and regular updates with lower upfront costs but may require relinquishing some control over data and processes.
Each model has its advantages and challenges, and the choice should align with the agency’s operational needs, budget, and long-term goals.
At the heart of this decision lies the balancing act between the pain of maintaining an outdated system and the pain of adopting a new one. Stakeholders must carefully analyze whether the costs, risks, and inefficiencies of the existing system outweigh the challenges of a replacement. If the current system still meets operational requirements and compliance standards, replacement may not be necessary.
Replacing technology for government services is not merely a technical decision—it’s a strategic one. Timing, governance, vendor credibility, legislative buy-in, compliance with mandates, end-of-life considerations, and deployment models all play critical roles in shaping the success of these projects. By approaching these elements with care and aligning them with the guiding principle of minimizing pain, governments can ensure that their technology transitions serve the best interests of the public.
SBA Certifications:
© 2024 Cross-Sector Consuting. All rights reserved. | design by: WoM
Cross-Sector Consulting
We firmly believe that the internet should be available and accessible to anyone, and are committed to providing a website that is accessible to the widest possible audience, regardless of circumstance and ability.
To fulfill this, we aim to adhere as strictly as possible to the World Wide Web Consortium’s (W3C) Web Content Accessibility Guidelines 2.1 (WCAG 2.1) at the AA level. These guidelines explain how to make web content accessible to people with a wide array of disabilities. Complying with those guidelines helps us ensure that the website is accessible to all people: blind people, people with motor impairments, visual impairment, cognitive disabilities, and more.
This website utilizes various technologies that are meant to make it as accessible as possible at all times. We utilize an accessibility interface that allows persons with specific disabilities to adjust the website’s UI (user interface) and design it to their personal needs.
Additionally, the website utilizes an AI-based application that runs in the background and optimizes its accessibility level constantly. This application remediates the website’s HTML, adapts Its functionality and behavior for screen-readers used by the blind users, and for keyboard functions used by individuals with motor impairments.
If you’ve found a malfunction or have ideas for improvement, we’ll be happy to hear from you. You can reach out to the website’s operators by using the following email
Our website implements the ARIA attributes (Accessible Rich Internet Applications) technique, alongside various different behavioral changes, to ensure blind users visiting with screen-readers are able to read, comprehend, and enjoy the website’s functions. As soon as a user with a screen-reader enters your site, they immediately receive a prompt to enter the Screen-Reader Profile so they can browse and operate your site effectively. Here’s how our website covers some of the most important screen-reader requirements, alongside console screenshots of code examples:
Screen-reader optimization: we run a background process that learns the website’s components from top to bottom, to ensure ongoing compliance even when updating the website. In this process, we provide screen-readers with meaningful data using the ARIA set of attributes. For example, we provide accurate form labels; descriptions for actionable icons (social media icons, search icons, cart icons, etc.); validation guidance for form inputs; element roles such as buttons, menus, modal dialogues (popups), and others. Additionally, the background process scans all the website’s images and provides an accurate and meaningful image-object-recognition-based description as an ALT (alternate text) tag for images that are not described. It will also extract texts that are embedded within the image, using an OCR (optical character recognition) technology. To turn on screen-reader adjustments at any time, users need only to press the Alt+1 keyboard combination. Screen-reader users also get automatic announcements to turn the Screen-reader mode on as soon as they enter the website.
These adjustments are compatible with all popular screen readers, including JAWS and NVDA.
Keyboard navigation optimization: The background process also adjusts the website’s HTML, and adds various behaviors using JavaScript code to make the website operable by the keyboard. This includes the ability to navigate the website using the Tab and Shift+Tab keys, operate dropdowns with the arrow keys, close them with Esc, trigger buttons and links using the Enter key, navigate between radio and checkbox elements using the arrow keys, and fill them in with the Spacebar or Enter key.Additionally, keyboard users will find quick-navigation and content-skip menus, available at any time by clicking Alt+1, or as the first elements of the site while navigating with the keyboard. The background process also handles triggered popups by moving the keyboard focus towards them as soon as they appear, and not allow the focus drift outside it.
Users can also use shortcuts such as “M” (menus), “H” (headings), “F” (forms), “B” (buttons), and “G” (graphics) to jump to specific elements.
We aim to support the widest array of browsers and assistive technologies as possible, so our users can choose the best fitting tools for them, with as few limitations as possible. Therefore, we have worked very hard to be able to support all major systems that comprise over 95% of the user market share including Google Chrome, Mozilla Firefox, Apple Safari, Opera and Microsoft Edge, JAWS and NVDA (screen readers).
Despite our very best efforts to allow anybody to adjust the website to their needs. There may still be pages or sections that are not fully accessible, are in the process of becoming accessible, or are lacking an adequate technological solution to make them accessible. Still, we are continually improving our accessibility, adding, updating and improving its options and features, and developing and adopting new technologies. All this is meant to reach the optimal level of accessibility, following technological advancements. For any assistance, please reach out to