Introduction

Designing software for government agencies across emerging markets presents a unique web of structural, technical, and political challenges. When enterprise Business-to-Government (B2G) software relies on decade-old internal platforms and multi-tiered intermediary channels, establishing modern user-centric design practices requires far more than creating sleek interfaces. It demands navigating entrenched engineering mindsets, overcoming indirect user access, and actively advocating for the value of UX across all levels of an organization.

As the former Lead UX Researcher and Product Designer at a B2G SaaS provider servicing road agencies, tollgate management authorities, and licensing departments, I stepped into an environment dominated by legacy mental models, an Agile-Waterfall hybrid structure, and severe research gatekeeping. Over my tenure, as I grew the design function from a solo role into a dedicated UX team, we developed strategies to work ahead of engineering backlogs, execute creative qualitative research workarounds, and demonstrate tangible proofs-of-concept that transformed how leadership and clients viewed product design. This article explores the core lessons learned, structural breakthroughs, and practical frameworks for driving UX renewal within a legacy enterprise environment.

1. Project Overview & Scope

1.1 Anonymised Project Brief

The organisation operated as a Business-to-Government (B2G) SaaS enterprise, developing complex operational software primarily for government bodies, road authorities, tollgate management agencies, and vehicle licensing departments across Africa. Additionally, the company developed modular software assets aimed at expanding its footprint into international government markets globally.

Building software for public sector infrastructure carries distinct operational demands. Government-facing applications must handle high-stakes transactions, comply with strict regulatory guidelines, and support users with vast differences in technical proficiency. Designing effective UX within this ecosystem required balancing long delivery cycles with modern usability standards.

1.2 Role & Operational Scope

As the former Lead UX Researcher and Product Designer, I fulfilled a full-stack design role responsible for establishing the organisation's end-to-end design practice. The scope encompassed research, interaction design, system architecture, internal education, and team mentorship.

• UX Strategy and Research: Spearheaded user-centric design methodologies, established formal discovery processes, mapped complex user flows, and developed foundational user personas.
• Design Systems and UI Libraries: Built and maintained reusable UI component libraries to standardize interface patterns across internal development teams.
• Educational Platform Engineering: Configured, designed, and launched a dedicated Moodle e-learning platform with structured video and interactive courses. This platform educated government clients and internal staff on SaaS product adoption, addressing a critical onboarding bottleneck.
• Cross-Functional Collaboration: Partnered closely with Business Analysts (BAs), Product Owners (POs), and software development teams.
• Team Growth and Mentorship: Over eighteen months, expanded the design function from a solo role into a formal UX department by hiring and onboarding a former student intern into a full-time UX designer.

Operational Dimension	Initial Baseline	Evolved State
UX Headcount	1 Senior Designer (Solo)	2 Full-Time UX Designers (Dedicated Department)
Interface Standards	Ad-hoc, dated UI patterns	Standardized, reusable UI component libraries
Client Onboarding	Manual training sessions	Dedicated Moodle e-learning platform
Workflow Integration	Reactive UI support	Dual-track UX working ahead of backend sprints

 

1.3 User Ecosystem & Intermediary Dynamics

The operational user ecosystem consisted of three distinct user groups, each presenting unique research and design challenges:

1. Internal Developers and Configurators: Technical teams using a decade-old internal software builder to configure client applications. Their mental models were heavily shaped by legacy software constraints.
2. Third-Party Intermediary Partner Companies: Local partner organizations in target African nations acting as official liaisons between the SaaS company and government ministries due to regional political and contractual structures.
3. Frontline Government End-Users: Operators at tollgates, vehicle licensing offices, and border posts who executed daily administrative tasks using the software.

Because the company rarely interacted directly with government clients, direct user access was restricted. This multi-tiered structure created a communication feedback loop similar to a telephone game, where user needs were filtered through third parties before reaching the design team.

Figure 1: Navigating the multi-tiered communication channel separating UX research from frontline government operators.

 

2. Core Problems & Legacy Constraints

2.1 The Legacy Configuration Platform Trap

The company's software suite was built atop an internal low-code SaaS configuration platform developed roughly ten years prior. Functioning similarly to an enterprise SAP builder, it managed database connections, authentication servers, and business logic.

However, the internal platform was compiled without user-centric design principles. Its user interfaces were dated, configuration workflows were cumbersome, and system navigation created high cognitive load. This architectural debt severely slowed development velocity and made rapid prototyping difficult.

2.2 Agile-Waterfall Hybrid & Scope Creep

While the organization claimed to run Agile development, daily execution operated as a hybrid Waterfall-Agile process. This structural mismatch created significant product delivery friction:

• Weak Product Owner Integration: Product Owners lacked direct communication channels with end-users, relying on filtered requirements from third-party intermediaries.
• Chronic Scope Creep: Without clear user-validated requirements, projects suffered from constant requirement shifts, making it difficult to establish a Minimum Viable Product (MVP) or Proof of Concept (PoC).
• Development Waste: Engineering teams spent months configuring features that did not solve core user problems, leading to redundant work and delayed releases.

2.3 Technical Debt & Developer Resistance

Years of working within the legacy platform created a cultural barrier among engineering teams. Developers frequently cited legacy platform constraints as an excuse to reject proposed UI and UX improvements, assuming modern design patterns were technically impossible to implement.

Overcoming this mindset required months of persistent advocacy, demonstrating that modern interaction patterns could indeed be integrated into or built alongside the legacy engine.

2.4 Research Access & Gatekeeping

Political sensitivity, geographic distance, and contractual boundaries with third-party intermediaries severely restricted direct contact with frontline government staff.

To bypass this research gatekeeping, the UX team adopted rigorous secondary research strategies. We analyzed government regulatory documents, studied regional administrative guidelines, evaluated competitor systems, and reviewed academic papers to construct realistic user personas and workflow maps.

2.5 Business Consequences & Strategic Friction

Ignoring UX processes carried tangible financial and operational costs for the organization.

The Legacy Friction Loop:

1. Developer Assumptions: Engineering teams bypass UX processes to build outdated legacy interaction patterns.
2. Failed Prototypes: Management and third-party clients reject deliverables for poor usability and misalignment.
3. Rework and Delay: Emergency UX interventions are triggered to execute complete workflow redesigns.
4. Strategic Risk: Client frustration increases, leading to platform rejection and the loss of major public sector contracts.

In one notable instance, engineering teams bypassed UX input to rapidly build a prototype using legacy patterns. Upon presentation, executive management and the third-party client rejected the build, mandating that the team hand the project back to UX for a complete redesign. While our team applied lean UX methods to salvage the application, the delay cost substantial time and capital. Ultimately, failure to embed UX early led one major government client to reject the legacy configuration platform entirely, contributing to organizational retrenchments in late 2026.

 

3. Strategy, Research, and Execution

3.1 Research & Discovery Approach

Faced with restricted access to quantitative analytics and direct end-user pools, the UX team deployed a pragmatic, qualitative-first research framework based on multi-source triangulation:

• Desk Research (Primary Volume): Regulatory manuals, competitor analysis, industry documentation, and research papers.
• Intermediary Focus: Recorded qualitative interviews conducted via third-party partner contacts.
• On-Site Field Study (Breakthrough): Contextual inquiry and direct observation at active border posts.
• Guerrilla Testing: Internal usability checks, cognitive walkthroughs, and rapid card sorting exercises. 

Figure 2: Balancing secondary desk research with targeted primary contextual field studies.

A major breakthrough occurred when our team secured rare permission to conduct an on-site field study at an active border post. We observed border control officers using the system in real-time, conducted contextual interviews, and administered usability questionnaires. We synthesized these findings into a comprehensive executive report outlining critical usability bottlenecks, operational risks, and feature opportunities. This report provided empirical evidence that shifted management's perspective on user research.

3.2 Dual-Track Design Strategy

To prevent design from becoming a bottleneck and to protect UI quality from developer pushback, we established a dual-track design workflow:

Track	Timing	Primary Focus & Deliverables
UX Discovery Track	Sprint N - 1	Whiteboard sessions, rapid hi-fi wireframing, PO & client sign-off
Engineering Track	Sprint N	Database mapping, auth server setup, pre-approved UI construction

 

1. Working Ahead of Engineering: The UX team partnered with Product Managers to work one sprint ahead of development.
2. Rapid High-Fidelity Wireframing: Rather than spending time on rough hand sketches, we translated whiteboard concepts directly into high-fidelity interactive wireframes.
3. Pre-Development Alignment: While engineers configured databases and authentication servers, we workshopped high-fidelity wireframes with Product Owners and intermediaries. By the time backend setup was complete, the front-end layout and interaction flows were already approved.
4. Familiarity and Future-Proofing: We applied modern design standards that simplified complex administrative tasks while keeping interface patterns familiar enough to minimize user retraining. 
   
   

Figure 3: Operating a dual-track workflow to validate interactions before backend engineering begins.

 

3.3 Stakeholder Alignment & Advocacy

Winning over skeptical developers and traditional managers required strategic advocacy tailored to enterprise dynamics:

• Demonstrating Through Tangible Demos: Skeptical engineers were convinced not by design theory, but by working interactive prototypes that demonstrated how modern UI patterns functioned within legacy constraints.
• Partnering Directly with Product Owners: Recognizing that software engineers can build almost anything once required, we focused our alignment efforts on Product Owners. Securing PO and client sign-off on UX wireframes ensured design requirements were locked in before engineering commenced.
• Navigating Management Biases: When traditional managers remained resistant due to entrenched habits, we relied on user-backed evidence and executive management support to maintain design integrity.

3.4 Key Breakthrough Moment

The pivotal turning point in organizational design maturity occurred during a high-stakes product cycle. After a developer-driven prototype was rejected by leadership and external stakeholders for poor usability, management formally intervened.

Executive leadership mandated that all future product features must undergo complete UX discovery, high-fidelity wireframing, and stakeholder sign-off prior to engineering allocation. This directive transformed UX from an optional cosmetic service into an essential gateway for product development.

  

5. Impact, Lessons Learned, & Practitioner Takeaways

5.1 Outcomes & Qualitative Client Value

While full quantitative metrics were still being tracked upon my departure due to long public sector deployment timelines, the qualitative and organizational outcomes were significant:

• Established UX Infrastructure: Built standardized UX discovery processes, interaction frameworks, and reusable UI component libraries from scratch.
• Transformed Client Perception: Government stakeholders and third-party partners expressed clear satisfaction with UX-driven prototypes, recognizing a stark improvement over legacy interfaces.
• Internal Cultural Shift: Successfully shifted product development from an engineering-driven mindset to a collaborative model where Product Owners actively sought UX sign-off.

5.2 The UX Renewal Framework & Practitioner Principles

For UX leaders operating within legacy enterprise or B2G environments, driving design maturity requires a combination of tactical patience and strategic framework execution: 

Figure 4: A 4-step framework for driving UX renewal in legacy enterprise environments.

Core Principles for Legacy UX Practitioners:

1. Execute a Pilot Renewal Project: Audit legacy software and present side-by-side modern prototypes to demonstrate undeniable contrast.
2. Work Ahead via Dual-Track Workflows: Validate hi-fi wireframes one sprint early to lock in interaction patterns before engineering begins.
3. Empower Product Owners: Provide POs with lightweight discovery templates, user story frameworks, and intake checklists.
4. Leverage Creative Field Research: Combine secondary desk research with targeted site visits to build empirical evidence.
5. Execute a "UX Renewal Project" to Counter Bias: Direct arguments rarely change legacy mindsets. Instead, select an existing legacy tool, conduct a thorough heuristic evaluation, and build a side-by-side prototype demonstrating modern usability. Showing tangible contrast is the most effective way to break through stakeholder skepticism.
6. Work Ahead via Dual-Track Workflows: Never wait for backend development to finish before starting UI design. Partner with Product Managers to validate wireframes one sprint ahead, locking in interaction patterns before code is written.
7. Equip Product Owners with UX Tooling: Enable Product Owners by providing them with lightweight discovery templates, user story frameworks, and intake checklists. Empowered POs become strong advocates for UX requirements.
8. Embrace Qualitative Adaptability: When direct access to end-users is blocked by gatekeepers, combine secondary desk research with opportunistic field studies. Even limited real-world observation yields powerful evidence to guide design decisions.

Conclusion

Modernizing legacy software within a B2G environment is ultimately an exercise in strategic perseverance and institutional enablement. While architectural debt, indirect user access, and entrenched organizational biases can easily stall design efforts, meaningful change is achievable when UX practitioners move from passive service providers to proactive strategic partners.

By establishing dual-track workflows that stay ahead of technical backlogs, conducting targeted field studies despite gatekeeping, and equipping Product Owners with structured discovery tools, design teams can incrementally prove their value and win executive alignment. For UX leaders operating under similar legacy constraints, running a dedicated "UX renewal project", using heuristic evaluations and tangible side-by-side prototypes, offers a practical roadmap to overcome institutional resistance and deliver software that truly serves its end-users.