Skip to content
Assessment · Data & Analytics Maturity

Data & Analytics Maturity Assessment

If two areas bring the same figure to a committee and the numbers do not match, the problem is not the report. We evaluate where your data comes from, what can be trusted and which decisions you could already be taking with what you have, and build the roadmap to close the gap.

What it is
A beautiful dashboard on bad data is a bad decision with a chart.

The assessment walks the full path of the data —origin, quality, governance, model, consumption and decision— and rates the maturity of each leg. It identifies which decisions currently lack support and what it would take to sustain them, and delivers the roadmap agreed with the areas that consume the information.

01

Know what you can trust

Which sources are reliable, which are not, and which decisions currently depend on the latter.

02

Order the data's path

Where it originates, who owns it and which version prevails when two disagree.

03

Use what you already have

Which decisions you could take today with the existing information, without investing in a platform.

Assessment or consulting

One surveys and maps the route. The other executes it.

These are two different services and it is worth knowing which one you need before contracting. The assessment does the first information-gathering exercise, builds the roadmap and aligns it with the business areas. The consulting practice executes that roadmap.

Data & Analytics Maturity Assessment — this page

Surveys, maps and aligns. It surveys the sources, measures quality, evaluates governance and model, identifies the decisions without support and builds the roadmap agreed with the areas that consume the data. It runs two to four weeks depending on the size of the organisation. It does not implement, does not configure and does not operate anything.

Analytics — execution

Executes the roadmap. It takes the roadmap and executes it: data engineering, modelling, building dashboards and reports, and continuous operation of the analytics platform. It works just as well if you already have a roadmap of your own.

What it covers

Eight legs of the data's path.

Trust in a figure is lost at the weakest leg of the journey. We review each one with the same depth and rate it by maturity level.

01

Sources and origin

Which systems each relevant figure comes from, how often it refreshes and how complete it arrives.

02

Quality

How accurate, complete and consistent what you have is — measured, not assumed.

03

Governance and ownership

Who answers for each data domain and who decides which version is true.

04

Model and definitions

Whether a single definition exists for the business concepts, or each area calculates its own.

05

Integration and flow

How data travels between systems, what transformations it undergoes and where traceability is lost.

06

Analytics platform

What tools the information is exploited with today and whether they sustain what the business asks for.

07

Consumption and adoption

Who uses the reports, how often, and whether they use them to decide or to justify.

08

Privacy and compliance

What personal or sensitive data exists, how it is protected and what the applicable regulation demands.

How we do it

Six phases, without interrupting your operation.

The assessment rests on interviews, source review and sample analysis. It never modifies data or systems.

01

Scope and preparation

We define which data domains and which decisions are in, and agree read-only access.

02

Business interviews

With the people who decide on the basis of data, to understand what they ask and what they cannot answer today.

03

Source review

Origin, frequency, completeness and transformations, checked against what the interviews said.

04

Quality analysis

Measurement on real samples: accuracy, completeness, consistency and duplicates.

05

Gap analysis

Comparison against DAMA-DMBOK and DCAM, leg by leg along the data's path.

06

Business alignment

Presentation of the roadmap with leadership and the areas, so priorities are agreed.

Method and frameworks

What your maturity is measured against.

The evaluation does not rest on the judgement of whichever consultant shows up, nor on a vendor catalogue, but on public and auditable frameworks your team can consult and your auditor will recognise. Data governance is also read against the law that applies to you —Habeas Data (Ley 1581) in Colombia, the LFPDPPP in Mexico— not only against a generic maturity model.

01

DAMA-DMBOK

Evaluation framework. The data management body of knowledge: governance, quality, architecture and lifecycle.

02

DCAM

Maturity framework. Data management capability model. It provides the scale that makes the result comparable.

03

ISO/IEC 25012

Quality guide. Defines the data quality dimensions that get measured: accuracy, completeness, consistency and the rest.

04

ISO/IEC 38505

Governance guide. Corporate governance of data: who answers for it and to whom.

05

Applicable data protection law

Regulatory guide. The local personal-data framework, which determines what may be collected, retained and processed.

06

Kimball / dimensional modelling

Modelling guide. Reference for evaluating whether the analytical model sustains the questions the business asks.

Risks of going without

What it costs to decide on data nobody certified.

The cost of bad data does not show up on an invoice: it shows up in a decision taken badly that nobody connected back to its source.

01

Figures that contradict each other

Two areas present different numbers for the same thing and the committee argues about the source instead of the business.

02

Decisions without support

Choices get made on intuition because the data does not arrive in time or is not believed.

03

Reports nobody uses

Money goes into dashboards that do not answer the questions the business actually asks.

04

Invisible manual work

Hours every month consolidating spreadsheets by hand, an effort nobody counts as a cost.

05

Regulatory exposure

Personal data with no access control or retention policy, in a regulatory environment that keeps tightening.

06

Analytics that does not scale

Every new question demands development, because there is no model to sustain it.

What it asks of your team

What it costs you in time, said upfront.

An assessment that does not state the commitment it requires ends up delayed. This is what we need from your side to deliver on time.

01

Two to four weeks

Two weeks in organisations of up to 50 employees; four between 51 and 300. The timeline is agreed before starting.

02

Scheduled interviews

Sessions with the people who decide on the basis of data, with the owners of the source systems and with the technical team.

03

Read-only access

Queries against the platforms and existing documentation. At no point is a configuration modified.

04

A single point of contact

One person coordinating schedules and access. It is the factor that most affects hitting the deadline.

05

Whatever documentation exists

Data dictionaries, existing reports, indicator definitions and privacy policies, in whatever state they are in.

06

A closing session

The presentation of findings with leadership and the areas involved, where the roadmap priorities are agreed.

Who it is for

When it makes sense and when it does not.

It makes sense if…

Figures do not match across areas; there is monthly manual work to consolidate information; you are about to invest in an analytics platform and want to know whether the data supports it; or you want to use AI and need to know whether you have the foundation for it.

Probably not if…

You already have the data in order and want the dashboards built: go straight to Analytics. Or if your question is about artificial intelligence use cases, that is covered by the AI Readiness Assessment, for which this one is usually the prior step.

Benefits

What you gain from the assessment.

Trust, measured

Which sources are reliable and which are not, by measurement rather than perception.

A single version

Single definitions for the business concepts, and one owner per data domain.

Decisions unblocked

The questions that cannot be answered today, with what is missing to answer them.

Less manual work

The by-hand consolidations identified, with their cost in hours.

A backed investment

Whether it is worth investing in a platform or whether the origin has to be fixed first.

A foundation for AI

A diagnosis of whether your data sustains artificial intelligence use cases, before attempting them.

The SUMāTO approach

Why this evaluation and not a sample dashboard.

The difference is not in showing a good-looking chart: it is in saying whether the number feeding it can be trusted.

01

Evaluation, not demonstration

A sample dashboard proves the tool. This evaluates whether the data feeding it can sustain a decision.

02

Quality measured

Quality is measured on real samples of your sources, not estimated in conversation.

03

Recognised frameworks

The comparison is against DAMA-DMBOK and DCAM, with quality dimensions from ISO/IEC 25012.

04

Business language

Each gap tied to the decision it blocks, not to a technical attribute of the model.

05

Vendor independence

The roadmap is not shaped by whichever analytics platform would suit us to sell.

06

Continuity into execution

If you decide to proceed, it connects with Analytics without surveying the sources again.

The conclusion

As-Is, To-Be and the plan to get from one to the other.

Every assessment closes with the same structure, whatever the practice: where you stand today, where you need to be, what separates the two states and in what order that distance gets closed.

01

Current state — As-Is

The starting point surveyed with evidence, not declared in an interview: what exists, how it operates and how far it sits from what the business needs.

02

Target state — To-Be

Where the organisation needs to get to, defined with the business areas rather than imposed by the consultant. It is the benchmark everything else is measured against.

03

Gap analysis

Every difference between the As-Is and the To-Be, with everything required to close it: technology, processes, people, governance and budget. No gap is stated without what it demands.

04

Risk matrix

Each gap rated by probability and business impact, so priority does not depend on who pushes hardest but on what it costs to leave it open.

05

Work plan

The concrete sequence to reach the To-Be: what comes first, what it depends on, how much effort it takes and who should answer for each front.

06

Business alignment

The plan is presented and agreed with the areas involved. A roadmap signed only by IT does not survive the first quarter.

The report

How what you receive is structured.

The central deliverable is a report with a fixed structure, designed so leadership reads the first pages and the technical team works with the rest.

01

Executive summary

Two pages: maturity level, the three gaps that weigh most and which decisions currently lack support.

02

Maturity by leg

Rating of the eight legs with the gap made explicit against DAMA-DMBOK and DCAM.

03

Quality diagnosis

Measurement on real samples per source: accuracy, completeness, consistency and duplicates.

04

Data flow map

Where it originates, what it passes through and where it is transformed or loses traceability.

05

Roadmap

Gaps prioritised by decision unblocked against effort, with a suggested owner.

06

Immediate actions

What can be corrected or defined without a project or a new platform.

Deliverables

What you receive at the end.

  • Current state (As-Is): data and analytics maturity across each of the eight legs, with the data's flow from origin to consumption.
  • Quality measurement on real samples of the sources evaluated.
  • Inventory of sources with frequency, completeness and owner.
  • Diagnosis of definitions: where the business calculates the same thing differently.
  • Inventory of decisions that currently lack support in data.
  • Target state (To-Be): the level of quality, governance and availability those decisions demand, agreed with the areas.
  • Gap analysis between the As-Is and the To-Be, with each gap, its evidence and everything required to close it: sources, quality, definitions, governance and capabilities.
  • Risk matrix: quality, privacy and compliance, rated by probability and business impact.
  • Work plan to reach the To-Be, prioritised by decision unblocked against effort.
  • Executive presentation for committee and leadership.
  • Alignment session with the areas that consume the information.
Frequently asked questions

About the Data & Analytics Maturity Assessment.

What exactly do you evaluate?+
Eight legs of the data's path: sources and origin, quality, governance and ownership, model and definitions, integration and flow, analytics platform, consumption and adoption, and privacy and compliance.
How does it differ from analytics consulting?+
The assessment surveys the sources, measures quality, builds the roadmap and aligns it with the areas. Analytics executes that roadmap: data engineering, modelling, dashboard construction and continuous operation.
Do you really measure quality, or estimate it?+
We measure it on real samples of your sources: accuracy, completeness, consistency and duplicates. Anything estimated is marked as an estimate in the report.
Do we need to have a data platform?+
No. One frequent outcome is precisely that the origin should be put in order before investing in a platform, because a new tool does not fix bad data.
Do you modify our data during the assessment?+
No. Access is read-only and the analysis runs on samples. Nothing is written, nothing is transformed and no production system is touched.
Who should take part on our side?+
The people who decide with data, the owners of the source systems and the technical team. Without the business, the evaluation measures technology rather than usefulness.
Is it useful as a prior step for artificial intelligence?+
Yes, and it is the advisable order. Most AI projects that fail do so for lack of usable data, not because of the model. This assessment answers that question before you invest.
How often should we repeat it?+
Annually, or after a significant integration, a change of core system or a merger — the events that most degrade the traceability of data.
The first step

Know which data you can trust before deciding with it.

Book your Data & Analytics Maturity Assessment and get the quality measurement of your sources, the data flow map and a roadmap prioritised by decision unblocked.

Book my assessment See the Analytics