Evolving your data capabilities in a rapid and pragmatic way.
Our previous blog outlined three strategies to follow when considering a legacy data platform migration project.
- Take the time to understand your business needs and priorities first.
- Deliver value quickly, think agile and business-centric.
- Build a team that can execute.
So you’ve decided to migrate your data to the cloud. Now what? Where do you start? What approach do you adopt to mitigate risks, drive faster time to value in a predictable and scalable way? We’ve often heard our clients ask these similar questions.
So, we decided to share our four-step process to a successful data platform migration project.
1. Strategy & Roadmap
Building out a roadmap is your strategic game plan or blueprint to success. Your first step is defining your future state.
Define your future state
Start with your end goal in mind and use that to identify the changes to be made.
What does that journey look like?
Where are the gaps?
An example of an end goal or business outcome could be reducing IT spend by only paying for the computing you need.
To help forge a path forward and identify your priorities, your assessment should include people, process and technology gaps.
Determining if you have the right skills and knowledge, processes and technology to adopt a whole new paradigm shift from an on-premise to cloud-based is a critical step to building a successful roadmap.
Once your gaps are identified, next is determining how you go about closing that gap. Your gap plan should be based on your business priorities or needs. One of the simplest ways is to tackle the low-effort, high-value items first.
In a complicated or dynamic environment, there are several different methodologies that you can use, such as RICE. Still, often something as simple as effort and value is an easy way to help prioritize.
2. Design & Validate
Step two is taking the business priorities and designing a minimum viable product that will unlock business outcomes from your key priorities quickly and in a repeatable way.
In comparison to a proof of concept, an MVP is not a throwaway.
It helps validate patterns and establish a foundation for your program or product to grow and expand.
3. Learn & Expand
Use the MVP learnings to remove blockers to gaining the alignment, trust, and buy-in you need in order to expand to the next phase. Focus on establishing a pattern that’s repeatable, scalable and trustworthy that will meet the business needs today and in the future.
This is how you will onboard new stakeholders and expand your MPV into an enterprise-wide solution.
4. Review & Communicate
The final step to a successful legacy platform migration project is to adopt a transparent process by involving the business at every stage along the way.
Typically we use three different touchpoints with our clients.
- When working directly with the stakeholder, having bi-weekly touchpoints is a great way to maintain a pulse on the business needs through granular feedback and an opportunity to demonstrate your progress.
- Monthly touchpoints are used to discuss overall project progress and quarterly targets. Broader business unit stakeholders are often involved and often use this as an opportunity to share status updates, results and knowledge transfer.
- And finally, quarterly updates allow for the opportunity to validate project value, share learnings and focus on the quarter ahead. It also provides a forum for transparency and accountability.
All these touchpoints working together at different granularity levels ensure all stakeholders are engaged and invested in the outcomes.
The success of your legacy data platform migration boils down to these four steps.
- Understand the business needs and align around a shared vision of success.
- Don’t build something that only gets thrown away. Build an MVP to validate, establish trust and credibility.
- Use the learnings to adjust and move forward with a broader scope.
- And finally, continuously meet and adjust your plans accordingly.
Want to see what it looks like in action?