AI and Data are Business Strategy Experiments Now. How Far Are You Willing to Push the Curve?
Why Small Experiments Bend the Curve and Why Most Organizations Never Reach Zone C
In data products, people often use ‘data risk’ and ‘data experimentation’ as if they mean the same thing. They are different, though, and mixing them up is a big reason why many organisations struggle to achieve real results with AI or analytics.
The difference may seem small, but it separates teams that just keep data flowing from those that create lasting value with their data products.
Data Risk
Data risk means your assumptions, models, or understanding of the business could be off in ways you might not notice. This can lead to wrong decisions, mismatched metrics, or loss of trust.
However, risk also presents opportunities for disproportionate gains. Strategic decisions embedded within models (such as definitions, granularity, dimensions, and transformations) can later yield sustainable competitive advantages. Data risk is the necessary cost of developing enduring digital assets rather than temporary dashboards.
Data Experimentation
Data experimentation is about discovering new things. It means looking at real business behaviours instead of just trusting assumptions. This could involve trying new data transformations, testing different features, tracking data flows, watching how people use data, and exploring unusual data connections. Experimentation focuses on learning and finding benefits, not just avoiding risks or chasing quick results.
How do data risk and experimentation work together, and where does real impact come from?
Consider a graph with experimentation velocity on the x-axis and data risk exposure on the y-axis.
Zone A: The Data Product R&D Lab
Strong data teams start here, moving quickly, running experiments that are safe to fail, and learning a lot about their data. They map out data, improve metrics, test connections, and check how users behave.
At this stage, the rest of the company is not relying on your data definitions yet, which is helpful. You can learn freely without worrying about company politics. Here, it’s important to fail fast and cheaply, since each mistake helps you understand the business better.
As you experiment more, you start to see patterns. You find reliable ways to describe your data, set clear definitions, and notice which data stays consistent over time.
This is when the impact of data products starts to grow. As the experiments turn into real outcomes, more teams begin to use them almost instinctively, and the importance of the data team’s contributions increases by becoming more deeply connected to business lines.
Zone B: The High-Impact Data Product Frontier
In this zone, data experimentation and risk become mutually reinforcing. Data products begin to influence decision-making, automate processes, and, in some cases, impact customer-facing outcomes.
Even a small change to a metric or model can affect millions in revenue or disrupt how things work. Still, this is the most promising area for growth.
Now, teams like sales, finance, growth, operations, and engineering rely on your data. They care about your predictions and the information you provide. Experiments at this stage are not just for learning. They can change how the whole business sees itself.
In this stage, your impact grows quickly. Data products become self-reinforcing, and each experiment makes the organisation’s understanding stronger.
But risk also increases. The key is to keep moving quickly while making sure you understand and manage the consequences.
Zone C: The Mature Data Product Portfolio
By now, you have a steady process. You know which experiments are safe and where you need to set limits.
Your approach to risk is now based on experience, not fear. You use different models, definitions, and data layers to reduce risk. Tools like monitoring, tracking data history, and clear agreements help keep things stable, even as you move quickly.
Your goal is to get more value from each experiment. Every new test should give you bigger insights, more value, or better reliability compared to the effort you put in. At this stage, the organisation truly acts like a data-product company.
Exponential Thinking in Data Products
If Zones A, B, and C show how a data product grows from curiosity to impact and then to lasting value, exponential thinking is the mindset that helps this growth speed up instead of slowing down.
The World Economic Forum says exponential thinking means seeing how something small today can quickly become very important. This idea shapes data products: small changes and improvements add up to big advantages for the whole organisation.
What Does Exponential Thinking Mean for Data Products?
It starts with a basic idea: treat data as a key part of your business strategy.
When you view data products as strategic assets, you work backwards from your big goals. You think about what needs to be in place now (like certain features, behaviours, and structures) to make that future possible.
This is how exponential thinking links back to Zones A, B, and C:
Zone A provides the basics: experiments, new findings about your data, and early ideas for products.
Zone B is where growth speeds up. More teams depend on your work, more people benefit, and your experiments begin to shape the business.
Zone C is when growth becomes steady. Your data products are varied, strong, and keep adding value.
But to build products that last through this process, you need to address four key gaps.
The Strategic Gaps Every Data Product Must Close
These are not technical problems, but issues with how the organisation and design work. They decide if your growth continues or stops.
👁️🗨️ Vision Gap: Creating the Future That Doesn’t Exist Yet
In Zones A and early B, your data product is still small. Exponential thinking means you need to explain how things will come together: how definitions will settle, metrics will align, and insights will grow. You have to help others see the final goal before it’s clear to everyone.
👓 Confidence Gap: Sustaining Trust Through Linear Early Growth
At first, the value from data products grows slowly, not quickly. Still, you need others to stay interested until bigger benefits appear. The challenge is to show that steady progress now will lead to bigger results later.
🔮 Projection Gap: Identifying the Inflection Point
Every good data product reaches a point where more teams start using it, new processes are added, and trust grows. Knowing when this will happen helps you decide how much to experiment in Zone B.
🧞♂️ Resource Gap: Absorbing the Growth After the Curve Bends
Once your data product starts growing quickly, your teams need to manage the extra work:
new consumers, new use cases, higher SLAs, increased semantic commitments.
If you didn’t do the necessary prep work, rapid growth can overwhelm both your team and your systems.
Designing for the Exponential Big Picture: Two System Pillars
To fix these gaps, your data product setup needs two main systems, both closely tied to the Zone enablements.
1. Hyper-Independent Action Pods (Modularity as a Design Strategy)
This helps with fast experiments in Zone A and focused results in Zone B. Modularity is more than a technical idea, it also shapes your data culture and processes:
Hyper-independent Data Products for isolated, meaningful use cases (process-tech).
Hyper-independent pods within teams solving specific cases end-to-end (people/culture).
Modular infra resources enabling each pod without bottlenecks (tech).
Apple is a great example. Their design approach shapes everything from hardware to teams. The same applies to data. Modularity should be part of both your systems and culture, making operations leaner and more effective. This approach lets experiments in Zone A grow into real impact in Zone B without being slowed down by team dependencies.
2. Centralised Visibility & Support
If everything is decentralised, you get silos. If everything is centralised, you get bottlenecks. To grow quickly, you need a mix where teams work independently but share the same information.
The operations worth centralising are:
Orchestration
Governance
Global metadata modelling
Lineage visibility
Strategy alignment
This shared foundation keeps risks in early-stage data products from overwhelming the organisation and helps Zone C stay stable as more people use your data products. Without central visibility, growth stalls. With it, growth continues.
MD101 Support ☎️
If you have any queries about the piece, feel free to connect with the author(s). Or feel free to connect with the MD101 team directly at community@moderndata101.com 🧡
Author Connect
Find me on LinkedIn 🤝🏻
From MD101 team 🧡
🧡 The Data Product Playbook
Here’s your own copy of the Actionable Data Product Playbook. With 3000+ downloads so far and quality feedback, we are thrilled with the response to this 6-week guide we’ve built with industry experts and practitioners. Stay tuned to moderndata101.com for more actionable resources from us!
