STRATEGIC GUIDE FOR SWISS ORGANISATIONS

A four-level assessment to identify priorities, build a roadmap and invest where it matters.

IN BRIEF  We assess maturity by how reliably your teams turn trustworthy data into decisions they can repeat.

Why assess data maturity?

When we assess an organisation’s data maturity, we look at what happens when a number is challenged, a source goes offline or a quick decision is needed. Maturity is the collective ability to explain, share and use data with confidence.

An organisation can be advanced in one area and still vulnerable in another. A strong architecture can coexist with poorly understood KPIs. Committed teams can still spend their days consolidating Excel files. The assessment shows where the next franc and the next hour will make the greatest difference.

Maturity progresses in stages, from manual consolidation to shared, well-governed use of data.

Assessing maturity helps you avoid investments disconnected from actual needs. It identifies strengths and vulnerabilities, gives executives, business teams and IT a common language, and helps sequence the work.

The Datavizin Data Strategy Toolkit provides a practical approach to governance, architecture, quality and making data available. Its purpose is to identify the next changes that will help.

Five dimensions to examine

Consider these dimensions together, since strengths in one rarely offset weaknesses in another. A new platform cannot fix an ambiguous definition, and good governance does little good if the data still arrives after the meeting. Look for the exact point where decision-making gets held up today.

A balanced assessment goes beyond infrastructure. It covers five dimensions that rarely advance at the same pace.

1. Vision and use cases

Do data initiatives support explicit business goals? Do you track expected benefits? A mature organisation can explain why each data product exists and which decision it improves.

2. Data and quality

Do teams know the authoritative sources? Do they use shared definitions? Do they measure and correct errors? Maturity shows in the ability to explain a figure and trace it back to its source.

3. Architecture and automation

Do workflows rely on copy and paste, isolated macros or documented and monitored integrations? The architecture should fit the need, be understandable and evolve without accumulating fragile dependencies.

4. Governance and compliance

Are responsibilities, access rights, retention rules and correction procedures clear? Mature governance speeds up decision-making because everyone knows their role.

5. Culture, skills and use

Can teams interpret indicators, challenge a figure constructively and act on the results? Have they made the tools part of regular management reviews? Real maturity shows in how people work.

The four levels of data maturity

LevelCharacteristicsPriority
1. ExploringSilos, scattered files, shifting definitions, manual reporting and decisions based mostly on experience.Choose a use case and map the sources.
2. InformedInitial shared KPIs, regular analysis and BI tools, with uneven data quality and ownership.Make data reliable and formalise ownership.
3. DrivenShared indicators, automated workflows, active governance and frequent use of data to inform decisions.Scale delivery, measure value and develop self-service skills.
4. TransformedData embedded in products, processes and business models, with continuous improvement and a strong culture of experimentation.Optimise, innovate and manage risk at scale.

Level 1 – Data Exploring: make the problem visible

Each team has its own files and methods. Reporting takes significant effort, people dispute the numbers and management gets a late view of the business. Prioritise one critical process and build a first shared version of the figures.

The Data Starter Pack works well when an organisation already has data in an ERP, Excel files or business tools but needs a reliable dashboard to use it quickly.

Map critical data sources and their owners. Define three to five unambiguous KPIs. Measure time spent consolidating information by hand. Deliver a focused first use case with a visible result.

Level 2 – Data Informed: improve reliability and organise

At this stage it is tempting to create more reports. Start by strengthening what exists. Name the owners, make the rules visible and monitor priority data flows. This work lets you expand usage without adding more versions of the same figure.

The organisation produces dashboards, but results still depend on manual fixes or specialists who are hard to replace. Teams consult the numbers without always understanding their limits. The next stage requires better quality, documentation and accountability.

Assign business data owners, document indicators, monitor data flows and put a simple process in place to handle anomalies. Compliance and access controls also become more important as more users work with the data.

Level 3 – Data Driven: scale decision-making

Data is reliable, available and frequently used in decisions. Business teams can explore shared information without making one-off requests to IT. Priorities shift to measuring value, managing the portfolio of data products and enabling self-service within clear rules.

At this level, the Datavizin BI infrastructure plans can support automated workflows, report sharing and hosting for Microsoft BI solutions based on capacity and user needs.

Level 4 – Data Transformed: reshape the business model

Data helps shape product design, customer relationships, planning and operational automation, as well as explaining past results. The organisation tests, learns and adjusts decisions quickly while maintaining strong control of risk.

This level is not a necessary goal for every SME. Aim for maturity that supports the strategy at an acceptable cost, level of complexity and risk. Trying to maximise maturity everywhere can be as ineffective as leaving all the data unstructured.

A 15-point self-assessment

Score each statement from 0 to 3. Use 0 for never, 1 for sometimes, 2 for often and 3 for consistently.

  • Our data projects support measurable business objectives.
  • Each important KPI has a shared definition.
  • We know the authoritative source for critical data.
  • We track and correct major data quality errors.
  • Our priority reports are refreshed without manual copying and pasting.
  • We document our architecture and data flows.
  • We test backups and business continuity measures.
  • Access rights match responsibilities.
  • We have a named business data owner for important domains.
  • We design with data protection requirements in mind.
  • Users understand the limitations of the indicators.
  • We use dashboards in regular decision-making.
  • Teams receive training suited to their roles.
  • We measure the benefits of data projects after delivery.
  • We prioritise requests for changes by value.
HOW TO READ YOUR SCORE  0–12 Exploring • 13–25 Informed • 26–37 Driven • 38–45 Transformed. The total offers a broad indication. Gaps between the five dimensions often tell you more than the overall score.

How we turn the assessment into a roadmap

We balance three kinds of work. One action quickly eases the burden on teams, one reduces a risk and one prepares for the next stage. This mix avoids disposable quick wins and lengthy foundational work with no visible benefits for months.

An assessment is useful when it leads to decisions. Group the findings by dimension, then choose three priorities. Select an action to reduce risk, an action that delivers value quickly and an action that strengthens the foundations over time.

Time frameType of actionExample
0–3 monthsDemonstrate valueFirst dashboard, KPI definitions, correction of a critical source.
3–12 monthsBuild the foundationsOwners, data quality, automation, lightweight catalogue, training.
12–24 monthsExpand usageSelf-service BI, new sources, value measurement, data products.

The ECSTAA method provides a guide for carrying out this roadmap. Explore systems, understand how data is produced, structure the foundations, analyse the information and act on the findings.

The right level of maturity supports your strategy

An SME can manage its operations well without automating and scaling everything. It needs to know which data matters, how much confidence it warrants, which decisions it supports and who owns it. Maturity grows as those answers become simpler, more widely understood and easier to apply consistently.

NEXT STEP  Use the questionnaire to identify your three biggest gaps. Then explore the Data Strategy Toolkit or ask Datavizin for an assessment to turn those findings into realistic priorities.