Assessing your data ecosystem: Why it matters, when to do it, and why most organisations get it wrong

Julian Thomas, Principal Consultant at PBT Group

In most organisations, there is an implicit assumption that the data ecosystem has evolved according to some form of deliberate, overarching plan. In reality, that is rarely the case.

Data ecosystems tend to grow unevenly. Enterprise-level initiatives, line-of-business requirements, subsidiary decisions, and project-specific needs shape them. Each of these layers evolves at a different pace, influenced by both internal priorities and external pressures. Over time, this creates an environment that is far more complex than it appears on the surface.

This is why assessing the data ecosystem is not a once-off exercise but an ongoing requirement. The rate of change within organisations continues to increase, and data landscapes are evolving in ways that are not always coordinated. In many cases, this evolution is valid. New technologies are adopted, new capabilities are introduced, and teams respond to changing business demands. At the same time, complexity accumulates. Different parts of the organisation may move in different directions, and the overall ecosystem becomes more difficult to understand and manage.

Internally-focused

Without a structured way to evaluate what is actually happening, organisations risk losing sight of how their data environment is performing.

An effective way to approach this is to treat the assessment as an internal audit. It should provide an objective view of the current state of the ecosystem, highlighting strengths, identifying weaknesses, and exposing areas of risk. Importantly, it should also create visibility across the organisation.

That visibility is often where the real value lies. There is a tendency for assessments to remain within a specific team or function. When this happens, the outcome is limited. The findings do not influence broader decision-making, and the opportunity to align stakeholders is lost. For an assessment to have a real impact, it needs to be commissioned at the appropriate level within the organisation and supported by the right structures, including funding and executive sponsorship.

Strategic integration

It also needs to be seen. If the results do not “see the light of day”, the assessment becomes a tick-box exercise. It may document issues, but it does not create the conditions required to address them.

Assessments should not exist in isolation from strategy. In practice, the relationship works in both directions. An organisation does not define its data strategy without understanding its current state, and it cannot evaluate its ecosystem effectively without considering where it wants to go.

A useful approach is to align the assessment to a longer-term strategic horizon, typically around three years, supported by more frequent reviews or course corrections. This allows organisations to account for both stability and change. The long-term view provides direction, while shorter cycles ensure that the ecosystem remains aligned to evolving business needs.

Getting broader involvement

In this context, stakeholder engagement becomes critical. Understanding how different parts of the organisation interact with data, what they require, and where they experience friction provides a more complete view of the ecosystem. It also ensures that the assessment reflects operational realities rather than purely technical perspectives.

What often becomes clear through this process is that the biggest challenges are not always technical. While technology and skills are important, the complexity of the data ecosystem is frequently driven by organisational factors. These include governance structures, funding models, ways of work, and the dynamics between teams. In many cases, these elements have a greater influence on outcomes than the underlying technology.

If these factors are not considered in the assessment, the organisation risks focusing on symptoms rather than root causes.

Sharing the knowledge

This is where many assessments fall short. They focus narrowly on tools, platforms, or specific technical issues, without addressing the broader environment in which those technologies operate. As a result, improvements tend to be incremental and short-lived. The underlying complexity remains, and the same issues reappear over time.

A well-executed assessment provides a different outcome. It creates a shared understanding of the current state, establishes a baseline for improvement, and enables more informed decision-making across the organisation.

It also introduces a level of discipline. Rather than reacting to individual challenges as they arise, organisations can take a more structured approach to managing their data ecosystem. They can identify where investment is required, where efficiencies can be achieved, and where changes in operating model or governance may be necessary.

Ultimately, the purpose of assessing the data ecosystem is not to produce a report. It is to create clarity.

In an environment where data plays an increasingly central role in decision-making, that clarity is essential. It allows organisations to move beyond assumptions, understand the true state of their ecosystem, and take deliberate steps to improve how data supports the business.

Look out for my next piece, which will address what to evaluate, where inefficiencies hide, and how to optimise for change when assessing your data ecosystem.