Many organisations are working hard to become more data-driven. They invest heavily in strategies, advanced pipelines, extensive warehouses and building beautiful dashboards to support better decision-making. Yet even technically strong data products sometimes fail to deliver their full value. Not because the data is wrong or the design is poor, but because implementation isn’t considered early or thoroughly enough.
At its core, a data product creates value when it influences real decisions and behaviours. For example, it might help a team decide which marketing channel to cut, adjust inventory based on predictive demand, or allocate staff to peak-demand periods. Insights on a screen have limited impact if the intended users ignore them, don’t trust them, or don’t understand how the information connects to their daily work. A polished dashboard or a complex data pipeline may look impressive, but if the intended users do not trust the output or integrate it into their daily workflow, it fails to deliver real value.
This is why it is important to consider implementation when developing data products. From a change-management perspective, the value of a data product depends on the behaviour it enables and the decisions it improves. If implementation is weak or overlooked, even the best technical solution risks becoming an unused or misunderstood tool.
To bridge the gap between technical quality and practical impact, implementation should be considered from the very beginning of the development process. When the human, organisational, and behavioural aspects are considered early, data products have a greater chance of being adopted, understood, and ultimately used to drive meaningful change. Of course, making this happen is a complex challenge. It requires aligning technical development with human behaviour and the realities of everyday work. The next sections outline three key elements that can help: involving users early, empowering super users, and treating the rollout as a structured change process.
1. Involve Users Early to Build Products They Actually Use
The first step in successful implementation is to engage users from the very start of the project. This approach helps ensure the product reflects their workflows, priorities, and language, rather than the development team’s assumptions. Involving users early often has a positive effect on both satisfaction and adoption, which is essential if the product is going to drive behavioural change.
Early involvement helps uncover:
- How decisions are really made in practice
- What users struggle with today
- Which metrics and concepts matter most
- How terminology is understood across roles
- Where data can genuinely support workflows
In practice, involving users early can be done through a few concrete activities that help ground the data product in reality:
- Conduct short, focused interviews with key stakeholders and future users: The purpose is to understand how decisions are made today and what tools are currently used. This helps identify which behaviors need to change, what information people rely on, and where a data product can best support their work.
- Run lightweight workshops or co-creation sessions: This approach helps you better understand end-users and their actual needs, identify which metrics are meaningful to them, and align on terminology and interpretation. Such sessions might include co-creating simple mock-ups or reacting to early sketches of the product. This collaborative design not only yields a better tool but also signals to users that their input is valued.
Beyond shaping the product’s features and the product itself, early involvement can help foster psychological ownership among those who will use it. There is a well-documented effect in organisational psychology: when people help create a solution, they feel a sense of personal ownership that drives commitment (Source).
Furthermore, when the final product speaks the users’ language and addresses their real needs, they find it much easier to trust its output and act on its insights. Early involvement helps build that trust by demonstrating openness and shared ownership from the start
This early user focus also helps identify the right people to involve more deeply going forward, those who show engagement, and influence. These individuals are often well positioned to become advocates and super users, which leads to the next step in strengthening implementation.
2. Build and Empower Super Users to Anchor the Solution
Technical developers can’t (and shouldn’t) drive adoption alone. To turn a data product into a living part of the organization, identify a handful of early adopters and empower them as super users. Research shows that super users play an important role in technology implementation, as they can have a strong influence on how effectively a data product is adopted (Source).
Ideally, you involve these super users early in development and keep them engaged throughout. This way, by the time the product is ready to roll out, they have developed:
- Deep understanding of the data and logic: They know the numbers, calculations and definitions inside-out, which helps them trust the outputs.
- Insight into the design decisions: They understand why certain metrics or alerts were chosen and what the product is highlighting, so they can explain the rationale to others.
- Confidence to guide others: Because they’ve been on the journey, they feel prepared to support, train, and answer questions for their peers.
- A sense of responsibility for success: They feel some ownership of the product’s outcome and genuinely want the solution to succeed.
By the time of launch, super users essentially act as translators between the technical team and everyday users. They are the go-to colleagues who can answer “What does this number really mean?” or “Why does the dashboard show that?”. For many employees, a colleague’s endorsement carries far more weight than a consultant’s explanation. Their peer voice makes the solution credible in the eyes of others. When coworkers see someone, they respect using the new tool and vouching for it, it creates a positive pull to give it a try.
To anchor the solution in the organisation, it also helps to establish some simple routines and support structures with these super users at the center. For example:
- Hold weekly (or bi-weekly) “office hours” where users can bring questions and get quick answers
- Create short 2-minute video walkthroughs of new features, key metrics, or “how to read this” example
- Use super users as the first feedback loop: collect recurring questions and turn them into improvements or quick guides
All of these practices make support accessible and keep the product alive and evolving after go-live. Super users continue to act as long-term anchors well beyond the initial rollout. They gather feedback and surface new needs, helping ensure the product evolves rather than stagnates. Their ongoing involvement provides continuity, something external project teams or consultants usually cannot provide in the long run.
This peer-driven advocacy and support network can potentially increase the chances that the data product becomes part of the fabric of how the organisation operates. With engaged users and empowered super users in place, the final step is to treat the rollout not as a one-time IT deployment, but as an ongoing change process.
3. Treat Implementation as a Change Process – Because It Is One
With engaged users and empowered super users in place, the final step is to treat the rollout and implementation as an ongoing change-management process rather than a one-off IT deployment. This means having a thoughtful adoption plan that includes thorough training, strong communication, managerial support, and continued reinforcement over time, rather than simply handing over a dashboard and hoping for the best.
- Start with training and communication: Begin by equipping users with a comprehensive training programme and clear communication about the new data product from the outset. Effective training ensures employees know how to use the tool correctly and confidently, which reduces uncertainty and builds competence. Equally important is communicating why the product is being introduced and how it will benefit both the organisation and the individual’s work. When people understand the purpose and value of the change, they are more likely to embrace it. By starting with robust training and open communication, you establish a strong foundation for adoption, users feel prepared, informed, and motivated to incorporate the new system into their daily routine, driving the desired behavioural change from day one.
- Secure managerial and peer support: Visible support from leadership is crucial to drive adoption of a data product. When managers actively endorse the new product, allocate time for their teams to learn it, and even lead by example in using it, they send a clear signal that this change is a priority. This top-down commitment legitimises the new way of working and helps employees feel confident that adopting the tool is both safe and expected. Staff are much more likely to engage with a data product when they see their leaders championing its use as an integral part of achieving business objectives.
Peer support is an equally powerful force for encouraging behavioural change. Colleagues who are early enthusiasts or super users can act as champions. Sharing tips and offering hands-on help, with the new tool. Their enthusiasm is infectious: when people see their peers succeeding and benefiting from the product, it normalises the change and inspires others to follow suit. This kind of advocacy creates a supportive environment where asking questions and learning from each other is encouraged. In combination, strong managerial backing and active peer champions foster a culture that encourages adoption from every angle, making it more likely that the data product will be widely used and valued across the organisation. - Plan for ongoing reinforcement and improvement: Adoption isn’t a one-off event, it’s an ongoing process. After the initial rollout, organisations should reinforce the desired new behaviours to ensure they stick. This can include refresher training sessions, regular reminders or tips, and recognizing teams or individuals who use the data product effectively. Such reinforcement helps to prevent people from slipping back into old habits by keeping the new data solution front-of-mind.
Continuous improvement of both the product and the support around it is the other key to sustained adoption. As employees work with the data product, gather their feedback and be prepared to refine features or workflows to better fit their needs. When users see that their input leads to tangible enhancements or smoother performance, it boosts their sense of ownership and commitment to using the tool. Moreover, updating training materials and usage guidelines as the system evolves ensures that knowledge stays current and relevant. By planning for ongoing improvement, you demonstrate that the data product will keep delivering value over time.
Conclusion
Ultimately, the way a data product is implemented helps determine whether it becomes a driver of growth or just another piece of shelfware. Data delivers value only when it influences real decisions, so implementation should never be an afterthought, it works best when planned from day one. By involving users early to build ownership, empowering super users to anchor the solution, and treating the rollout as a structured change process, you move beyond mere technical delivery. This approach enables the behaviour change that helps ensure your data products are not just seen, but trusted and used to drive the organisation forward.