Hilltop Partner Network

This blog post draws on lessons from a provincial IT  enterprise architecture modernization initiative led by Hilltop Partner Network consultants. They worked in collaboration with the public sector client’s centralized Information Technology team and line-of-business departments.

Disparate systems.

Project silos.

Years of accumulated technical debt.

Public sector IT leaders know this pattern. For many CIOs and Chief Architects, this is the legacy they’ve inherited, and the one they are expected to modernize.

But conventional modernization efforts often start in the wrong place: selecting technology solutions before defining the business problems.

On a recent consulting engagement, Hilltop Partner Network (HPN) worked with a provincial government client to reframe this challenge by beginning not with procurement, but with capabilities.

We demonstrated how enterprise architecture (EA), when applied pragmatically, can drive clarity, collaboration, and transformation across government organizations.

Start with capabilities, not with catalogues

Rather than inventory the existing client systems, the transformation initiative began by asking:

“What do government departments need to deliver on their mandates?”

“What does technology need to enable for them?”

This shift in framing (starting with business capabilities instead of technical realities) allowed stakeholders to define modernization in terms that mattered to both their central IT team and to their individual departments. The result was a future-state architecture grounded in real-world delivery, not abstract theory.

The team held structured engagement workshops across the different departments, and some key insights surfaced:

• They identified recurrent patterns of duplication across government programs
• They flagged integration pain points that stifled their overall service agility
• They found instances where common IT capabilities were being rebuilt in silos, previously unknown and unconnected to each other

What they ended up with wasn’t a one-size-fits-all blueprint.

It was a practical framework that let the province design shared solutions where they made sense, and allowed them to tailor other, individual solutions where they were needed.

Looking at enterprise architecture as a modernization strategy, not as compliance

Too often, enterprise architecture is seen as a gating function; something to work around. In this case, it became the connective tissue for their strategy. By translating department needs into a common architectural model, the team helped align funding requests, modernization priorities, and long-range planning.

Ultimately, it wasn’t really the EA diagrams that drove the largest value; it was the ongoing, cross-department dialogue they helped enable.

Moving from an enterprise architecture model to modernization roadmap

The engagement culminated in a phased transformation roadmap. The roadmap allowed the client to sequence their IT initiatives based on dependencies, impact, and cost.

Instead of having to pitch “modernization” as a single project, it gave decision-makers a rationale for what to fund next, and why.

Key outputs in the final roadmap included:

• Prioritized initiatives aligned to the teams’ shared capabilities
• A future-state EA model that served as a guiding north star for the client
• Budgeting guidance rooted in measurable outcomes, not technology fads

Key takeaways

This work underscores a broader shift many organizations (public and private) are now exploring:

1. That modernization doesn’t begin with the tools that are available; rather, it begins with intent.
2. That having a shared understanding unlocks more value than just having shared platforms.
3. That enterprise architecture is a leadership tool when it is used for insights, and not just for oversight.

Applying those lessons to your organization

If you lead IT strategy or enterprise architecture in government or a large public-sector organization, consider the following:

• What would shift if your planning started with capability maps instead of systems inventories?
• Could architecture become a bridge between central IT and service delivery leaders?
• Are you using EA to drive modernization, or simply document it?

Enterprise architecture doesn’t need a rebrand. It just needs to be used differently, treated less as a gatekeeper and more as a catalyst.

When done well, EA can bring clarity to chaos and helps governments move from reacting to planning. Not by dictating standards, but by shaping shared understanding.

Ready to rethink enterprise architecture?

The story above is just one example of how public sector organizations can use capability-led EA to break down silos, align modernization efforts, and make smarter funding decisions.

Download the full case study to see how Hilltop Partner Network helped a provincial government turn strategy into action:
Strategic Enterprise Architecture Advancements for a Provincial Government

Let’s talk

Are you navigating similar challenges in your organization? Or are you looking to reframe how your team approaches enterprise architecture?  We’d love to explore how we can help.

Written by

Hilltop Partner Network