Not long ago, a major housing association in the UK found itself under growing pressure.
At the heart of the problem was its resident services function, supported by a legacy on‑premises CRM system that had, over time, become more of a liability than an asset. The system was poorly designed, difficult to use, and unable to scale.
The impact was significant. Resident satisfaction scores had dropped, and poor feedback was publicly reflected on platforms like Trustpilot.
But the real story was unfolding internally.
Customer service advisors were struggling every day just to do their jobs. Capturing case information was inconsistent. The user interface made even simple tasks cumbersome. To resolve a single resident issue, advisors often had to navigate across multiple systems just to piece together the full picture.
It didn’t stop there.
The complexity of the system landscape made onboarding new staff particularly challenging. Teams were constantly requesting additional information from each other, leading to delays, missed handovers, and frustration on all sides.
And perhaps most critically, the system had reached a point where meaningful technical improvements were no longer possible. Its underlying design simply couldn’t support change.
The organisation knew something had to give.
A Decision to Change – But Not Repeat the Past
Faced with these challenges, the organisation made a bold decision to embark on a full digital transformation programme and move its technology stack to the cloud, including its CRM platform. After evaluating several SaaS solutions, Dynamics 365 Customer Service was selected as the most suitable option.
But there was a clear concern.
This organisation had attempted transformation efforts before, and they knew that simply replacing the system would not solve the problem. There was a real risk of repeating the same mistakes, just on a new platform.
They needed a different approach.
Starting with the Right Questions
To avoid a repeat of the past, the organisation engaged Flici Insights to apply its industry-proven Nexus Transformation Framework.
Rather than jumping straight into delivery, the focus shifted to something more fundamental: understanding why the transformation was needed, what value it should deliver, and how to approach it.
Over a focused 6-week engagement, a small team of a solution architect, a business analyst, and a delivery manager worked closely with stakeholders to answer these questions and shape a clear direction.
This wasn’t about technology first.
It was about creating clarity.
Bringing Everyone on the Journey
The first step was to bring key stakeholders together.
A structured kick-off session set out the activities, timelines, and expected deliverables. The work was organised into three clear phases: discover, design, and plan, giving stakeholders a transparent view of how the roadmap would be developed.
From the outset, the emphasis was on alignment.
Everyone needed to understand not just what was happening, but why.
Challenging the Past in the Discovery Phase
The discovery phase was where the real shift began.
Rather than documenting existing processes and replicating them, the team facilitated a process-driven “art of the possible” session, using Microsoft’s case-to-resolution model to demonstrate how modern CRM capabilities could transform the way services were delivered.
This was a crucial moment.
For many stakeholders, it was the first time they could see how things could work, not just how they currently did. It helped break away from ingrained habits and encouraged teams to think beyond the limitations of the legacy system.
This step played a key role in reducing the risk of a “lift-and-shift” transformation, one of the most common reasons digital programmes fail to deliver value.
Following this, a series of business and technical workshops were conducted to explore the existing case management processes, pain points, and the wider technology landscape in detail.
Designing Around Value, Not Features
In the design phase, the conversation shifted again, this time towards value.
Rather than focusing on system features, the team developed a business value assessment map, linking proposed changes to measurable outcomes and clearly defined KPIs.
For example, instead of highlighting capabilities like Outlook integration, the focus was on what that capability would achieve, such as reducing the number of untracked emails.
This subtle shift changed how decisions were made.
Alongside this, a solution blueprint was produced, outlining the future-state architecture required to address the organisation’s technical challenges. This included a detailed review of implementation strategy, ALM, licensing, security, and integration considerations.
By the end of this phase, the organisation had something it hadn’t had before:
a clear view of both the value and the technical foundation required to deliver it.
Turning Strategy into a Deliverable Roadmap
The final phase focused on building a roadmap that could actually be delivered.
A structured scoring approach was introduced to prioritise the rollout across 25 service teams. Each team was assessed across two dimensions:
- The value it would deliver (for example, improving resident experience)
- The complexity involved (such as system dependencies and cross-team interactions)
Each team contributed to the scoring, and the results were consolidated to create a value-driven roadmap.
The logic was simple but effective:
- High-value, low-complexity teams were prioritised first
- Lower-value, high-complexity areas were phased later
To ensure momentum, delivery was structured into 90-day packages, combining:
- Low to medium complexity teams (quick wins)
- One high-complexity, high-value team
- Cross-cutting technical foundations
In total, this resulted in nine structured delivery packages, each designed to maintain continuous progress while building towards the overall transformation.
The Outcome
At the end of just six weeks, the organisation had a clear, 24-month value-driven roadmap.
It provided a structured path to transition all 25 service teams from the legacy CRM system to a modern cloud platform. More importantly, it defined when and how value would be realised:
- Immediate benefits from go-live activities
- Short-term improvements within 3–6 months
- Long-term outcomes following full replacement of the legacy system
The roadmap also established a strong foundation for collaboration across a complex enterprise environment, enabling technical and business stakeholders to work in alignment from an early stage.
Why This Approach Made the Difference
What made this journey different wasn’t just the choice of technology.
It was the decision to stop, step back, and rethink the transformation before rushing into delivery.
The strength of the Nexus approach lies in its ability to bring stakeholders together, create clarity, and maintain alignment throughout the process, even within a tight 6-week timeline.
A Final Reflection
Many organisations recognise the need to modernise their technology.
Fewer take the time to ask the right questions before they begin.
This case study shows that transformation is not just about moving to the cloud,
It’s about designing a journey that delivers value, from day one to long after go-live.
Curious how this could apply to your organisation?
The Nexus transformation package is designed to help organisations define a clear, value-driven roadmap before committing to delivery.
If you’re facing similar challenges, it might be worth starting there.
If you found this useful, follow Finsights for the next article in the series.
Written by Adel Flici, Founder of Finsights Ltd, a Microsoft AI Business Solutions Partner.