Mapping your systems and platforms will help you understand your opportunities and constraints. This way, you can solve common problems, avoid silos, and ensure that any new solutions use open data standards.

You can capture:

  • how, and if, different systems interact with each other
  • the scope of your current systems
  • any existing workarounds and ‘shadow IT’ (systems created by teams to bypass the central IT department)
  • where you enter, store, and access data​
  • user journeys through the several systems, for both frontstage and backstage processes
  • any cyber resilience and security risks

The right technology stack will allow a modular approach and the use of data across different services.

When to map your technology ecosystem

It’s unlikely anyone has a full and accurate view of their entire technology stack. There is no set time for mapping it, but consider doing so when you’re:

How you can map your technology ecosystem

You could use one of the options below.

Ecosystem map

It can help you to understand how different stakeholders, teams, platforms, and products relate to each other in the problem space you aim to improve. Read more about ecosystem maps.

Service blueprint

It detail workflows, processes, and backstage procedures, showing how they relate to the user’s experience and journey. The Local Government Association’s guidance explains what a service blueprint is.

Current state map

With this map, you can focus on business functions, capabilities, applications, technology stack, and cloud architecture. Use tools like Lucidchart to map your current state before scaling. While this approach focuses more on business and technology needs, ensure other activities prioritise your users.

What you can do next

After you’ve mapped your current systems, consider your opportunities and constraints. Decide whether you should build, buy, or share solutions.