So, what is an MVP? And what can you realistically achieve in 60 days?
What does MVP mean?
A minimum viable product is just that. Minimal. It’s not fully-fledged. There will be compromises. It may not include all third-party data sources, it may only cover a single data domain, or it may lack some automation or integration that will come later. Despite these compromises it’s crucial that an MVP is not something disposable.
A successful minimum viable product should be the foundation for something bigger. Rather than a trial run or a throwaway project, it’s the starting point that you can build on, one that will evolve and grow as it becomes a core part of the business.
MVP is not synonymous with a short time frame. What is ‘viable’ for one organisation and achievable in three months may look entirely different for another, requiring 18 months. It’s not about getting something live quickly to say you can. The key is in the name, it needs to be viable for its intended purpose. This means considering who will use it and how.
- Business Users: Can they use it effectively in their daily operations?
- Analytics Teams: Does it provide the necessary data for reporting and analysis?
- Suppliers: Is it fit for their requirements and interactions?
Adopting a lean approach
A lean approach to master data management prioritises the most impactful data, delivering real business value without tackling everything at once.
- Focus on master data that drives key outcomes.
- Identify the smallest, most valuable data set influencing those outcomes.
Don’t aim to cover every requirement immediately. Focus on the "most valuable fruit", i.e. the data that will deliver the greatest business impact first.
Defining the right MVP for your organisation
Understanding what you’re trying to solve with your master data management solution is key to forming your MVP. The scope of an MVP should align with these answers:
- What’s the minimum needed to prove the solution’s value?
- What are you not willing to compromise on?
- What challenges does it need to resolve?
- What business case justifies the investment?
- What’s the least complex version that will be approved?
- What changes will this MVP drive, and what impact will they have?
The scope and timing will depend on your business goals, the challenges you’re facing and what needs to be demonstrated before scaling. There’s no fixed timeline for an MDM MVP, as each one is bespoke to your organisation. We’ve delivered well-scoped MVPs quickly, some in full in three months, others in phased implementations over several months.
While speed is impressive, quality matters more. An MVP must prove value, but that doesn’t mean rushing at the expense of substance. It must be functional and have solid foundations so that the MVP can evolve into what your business need it to be.
What is a full MDM implementation?
The key difference between a minimum viable product and a full implementation is scope and flexibility:
Feature | Minimum Viable Product (MVP) | Full Implementation |
Scope | | Defined, limited to key priorities | | Expansive, evolving over time |
Domains | | Usually 1-2 critical domains | | Need not be limited to 1-2 data domains |
Integrations | | Essential systems only (if any) | | Full integration across enterprise |
Governance | | Basic controls to ensure usability | | Comprehensive policies and automation |
Phasing | | Delivered within a single phase | | Delivered in multiple phases |
Flexibility | | Rigid scope to maintain viability | | Solution may adapt with business needs |
Business Value | | Proves concept and initial value | | Delivers long-term transformation |
With a minimum viable product, you must constantly challenge the scope to ensure it remains viable and delivers value within defined constraints. In contrast, a full implementation allows for a broader, more adaptable roadmap, making room for new priorities and requirements as they emerge but still making sure that incremental phases are clearly scoped to ensure continued delivery.
What can you realistically achieve within 60 days?
Referring back to the 60-day delivery time, it’s essential to define where that clock starts. Are we saying its:
- 60 days to build a solution?
- 60 days to design and build a solution?
- 60 days starting from scratch, with no existing requirements or understanding of value?
Each scenario is vastly different, and without clear scope expectations can become misaligned.
Clearing up misconceptions
There’s no single “60-day fix” for an MDM MVP because every organisation starts from a different place. Some have strong foundations, while others need time for data preparation, governance, or stakeholder alignment. Every business moves at its own pace, and that’s okay.
An MVP is about proving value efficiently, not delivering everything at once. The best approach is the one that balances speed with substance, ensuring the result is meaningful and sets the stage for future growth.
Case studies: what’s possible in a limited timeframe?
Here are two different projects which show how scope influences what can be delivered within a short timeframe:
