Recently, the Public Accounts Committee highlighted recurring issues in procurement processes and contract management, emphasising the need for stronger oversight in the public sector. The report, dated February 10, made it clear that the modernisation of government IT systems must be accelerated. This is further supported by statements from the public finance oversight committee, which stressed the importance of strengthening protection against cyber threats.

In terms of IT controls and cybersecurity governance, the committee found that weaknesses in privileged access management have recurred over the years. This system is intended to regulate and safeguard accounts with higher-level access than regular users.

One of the key reasons behind the slow pace of digital transformation within government is technical debt. The Ministry of Digital Development and Information (MDDI) and SNG explained that legacy systems make the implementation of modern security standards both costly and complex.

Read this article to learn more about the importance of a national enterprise architecture initiative and the technical debt. 

Why a national enterprise architecture initiative matters now

The urgency reflected in the Public Accounts Committee’s report shows structural vulnerability. This is another sign why a National Enterprise Architecture (EA) Initiative is crucial. 

A national EA initiative would not replace agency autonomy. Instead, it would provide a coherent framework within which that autonomy operates. It would establish shared principles, common standards, and visibility across the entire public sector digital estate.

More importantly, it would shift the conversation from “Which system should we fix?” to “How must our organisation evolve?”

The watchdog's findings actually present an opportunity. Not merely to correct weaknesses, but to establish an enduring architectural foundation that prevents those weaknesses from recurring. Because in a digital-first nation, architecture is a national strategy expressed in structure.

What is the technical debt?

 

Technical debt is the accumulated cost of outdated systems, shortcuts, and fragmented processes that slow down change, increase operational risk, and raise the cost of innovation. In the case of the Singapore government, this issue has become critical, as reliance on manual processes to manage privileged access accounts significantly increases the risk of human error.

So, how does technical debt actually begin within an organisation?

At first, stakeholders tend to overlook invisible structural risks. They often take refuge behind:

“The system still works.”
“We’ll fix it next budget cycle.”
“Migration is too risky.”
“Operational continuity comes first.”

Until, eventually, transformation becomes prohibitively expensive and security vulnerabilities become systemic.

This is exactly the pattern reflected in the public sector findings: legacy systems make even basic modern security controls complex and costly to implement.

How technical debt appears from an EA perspective

From EA viewpoint, technical debt is structural misalignment across four domains. 

Business Architecture

• • Capabilities duplicated across agencies.
  • Processes dependent on manual verification.
  • Inconsistent policy enforcement across departments.
  
  

  Data Architecture

  
  
  • • Fragmented data ownership.
    • Inconsistent standards.
    • Limited interoperability.
    • Difficulty in obtaining a single source of truth.
    
    

    Application Architecture

    
    
    • Redundant systems performing similar functions.
    • Custom integrations are no longer documented.
    • Limited scalability.
    
    

    Technology Architecture

    
    
    • Outdated infrastructure.
    • Security controls layered inconsistently.
    • Manual privileged access management.
    
    

    Enterprise architecture as a solution

    
    Outdated systems, lack of integration, manual processes, and high maintenance costs can all be addressed. The question is how? By adopting Enterprise architecture. EA provides a systemic, cross-domain blueprint aligned with national or organisational strategy. 
    
    Below is how EA systematically addresses technical debt.
    
    

    1. Current-State Visibility

    
    
    • Application Portfolio Assessment: EA provides a comprehensive inventory of applications across the organisation. 
    • Technical Lifecycle Tracking: EA tracks where each system sits in its lifecycle. 
    • Obsolescence and Risk Identification: EA helps prioritise modernisation based on enterprise risk exposure and strategic value.
    
    

    2. Target Architecture

    
    
    • The Desired Future-State Blueprint: The target architecture aligns directly with strategic objectives. 
    • Rationalisation Decisions: EA enables structured decisions and defines deliberate transformation waves.
    • Capability-Driven Modernisation: EA focuses on business capabilities, ensuring that modernisation improves enterprise performance. 
    
    

    3. Roadmap Planning

    
    
    • Phased Modernisation Waves: Quick wins, medium-term stabilisation, and long-term structural redesign. 
    • Alignment with Business Priorities: EA ensures modernisation aligns with budget cycles, regulatory timelines, and organisational readiness. 
    • Risk-Based Sequencing: Not all systems should be modernised simultaneously.
    
    

    4. Governance

    
    
    • Architecture Review Boards: Ensure new projects comply with enterprise standards before funding approval.
    • Standardised Platforms and Tools: Reduce proliferation of technologies by defining approved technology stacks.
    • Integration Principles: Promote API-first design, modular architecture, cloud governance standards, secure-by-design principles. 
    • Continuous Lifecycle Management: EA embeds lifecycle monitoring into operational governance. 
    
    

    Conclusion

    
    The recurring challenges highlighted in the report make one thing clear: modernisation cannot be treated as a series of isolated system upgrades. Technical debt, cybersecurity vulnerabilities, and fragmented governance are structural issues that require structural solutions; a National Enterprise Architecture (EA) Initiative. 
    
    As an industry expert, ATD Solution believes that implementing EA at a national level enables organisations to move from reactive fixes to sustainable evolution. Our work with multiple government agencies across Asia Pacific has demonstrated how structured EA drives long-term transformation.
    
    Ready to transform your organisation? Contact us here.