Cairo
•
IST
home
home
2024 – present · Enterprise UX · azure execution & adoption
Cloud Accelerate Factory: Microsoft
The internal portal and the executive reporting system behind Microsoft's Cloud Accelerate Factory: where thousands of in-flight Azure migrations are tracked, aligned to one process, and reported up to leadership.
The client
Microsoft
Owns every Azure migration initiative — the global ecosystem and primary stakeholder.
The partner
LTIMindtree
Authorized by Microsoft to conduct migrations on its behalf.
The engine
MCAF
A 1000+ person unit inside LTIMindtree built for high-volume migration. FDO lives here.
The beneficiary
Azure customers
Global enterprises receiving direct migration support from the Factory.
Duration
2 years +
TEAM
Sole designer. I owned the UX end to end, working directly with the Program Director and the program's SME, Lead Solution Architects and migration engineers.
Partnered with
Internal tracking portal (FDO) · Information architecture · Hi-fi UI · Executive dashboard design library · Data visualization · Reporting system
Some details are withheld under NDA to protect company information. Everything shown here is shared with permission — figures are redacted, screenshots are cleared. The focus is the design process.
The ecosystem
LTIMindtree is Microsoft's Cloud Migration execution partner.
Every Azure customer modernizing the infrastructure they run on Azure, across 14 workloads, submits their migration request to LTIMindtree, where our migration engineers and workload experts carry it out at par with Microsoft's own delivery and best-practice standards.
PART 1
FDO · FACTORY DASHBOARD & OPERATIONS
Goal
A consolidated platform to track, report and unblock Azure migrations carried across14+ workloads as parallel workstreams for 1,000+ Azure customers.
How it started
The partnership was new and scaling quickly.
The Cloud Accelerate Factory kept expanding the workloads it supported for Azure migrations, and the volume of migrations rose with it.
When the program started, the team tracked and reported the process to leadership in Azure DevOps. Past a certain scale, that tool became too cumbersome, too manual and too rigid to track on. The team needed a robust source of truth — one that would minimize manual errors and reporting delays.
The Problem
Three things the old setup made hard.
PAIN 1
Manual ACR forecasting
Revenue was calculated manually individually for each workpiece — slow and error-prone
PAIN 2
Fragmented information
Workflows were in Azure DevOps, blockers handled in Teams, and progress in spreadsheets - fragmenting information and reducing ownership visibility.
PAIN 3
A generic tool, a specific job
Azure DevOps treats every item the same so urgency (blockers) and value (ACR) never rose to the surface.
How it started
The partnership was new and scaling quickly. The Cloud Accelerate Factory kept expanding the workloads it supported for Azure migrations, and the volume of migrations rose with it.
When the program started, the team tracked and reported the process to leadership in Azure DevOps. Past a certain scale, that tool became too cumbersome, too manual and too rigid to track on. The team needed a robust source of truth — one that would minimize manual errors and reporting delays.