Redesigning the SAP Fieldglass homepage from a one-size-fits-all solution to a governed template system

SAP Fieldglass is an enterprise SaaS platform that helps large organizations manage their external workforce and vendor relationships at scale. As a global B2B product, it supports complex workflows and compliance needs across different industries and markets.

However, despite its robust backend and business value, the homepage had become a source of confusion rather than clarity. There has been persistent user feedback that the homepage is hard to navigate and completely unintuitive.

In early 2024, I was tasked with redesigning this critical touchpoint. The project was one of SAP Fieldglass's strategic priorities for the year, supported by product and design leadership.

This redesign started with a clear but narrow executive mandate: adopt cards from the standard JavaScript framework SAP UI5 to modernize the homepage and enable future integrations across SAP platforms.

However, as the designer, I knew this visual upgrade would only scratch the surface. The redesign couldn't just be about better-looking cards, it needed to solve foundational UX and workflow issues.

Based on insights gathered from my domain observations, UX research findings, and ongoing cross-functional syncs, we translated broad platform pain points into clear, scalable design goals:

Translating our design strategies into a usable system meant resolving real design complexity. My focus was on reducing noise while enabling flexibility, and we approached it through parallel focused streams:

Working closely with our PM and UX researcher, we identified key personas: Hiring Manager (contingent and SOW), PMO, Financial Approver, and Admin. Each role required different widgets, layouts, and information priority, so we reverse-engineered user workflows into homepage actions, and then matched them to essential widgets.

I led a full audit of homepage widgets, worked with our PM and researcher to map core user actions (e.g., posting a job, reviewing SOWs) and determined what information truly needed to be surfaced. This reverse-mapping allowed us to cut noise and prioritize action, transforming the homepage from a wall of widgets into a focused control center.

We applied a flexible 4-column grid layout that allowed widgets to scale, supporting single, double, and full-width modules.

The template system answered "what should each role see." But when it came to who keeps this running, the working assumption was that admins would configure every user correctly. As a designer who has designed for admin users, I knew this assumption was not accurate: an admin overseeing hundreds of users cannot know what each person needs day to day, and users don't know exactly which widgets they could ask for.

I've seen a great amount of offline communication, including emails, Jira tickets, and hallway conversations between admins and other end users. The admins are end users too, and they are the last mile that decides whether the templates reach anyone. That's why I went ahead with my reasoning and got the stakeholders aligned on adding the widget request workflow to the roadmap.

The request loop replaces the offline back-and-forth between admin users and other end users. A user can request widgets from Homepage Settings, and the request lands in the admin's queue.

A modular, adaptive homepage now supports SAP UI5 cards and a scalable 4-column layout system. Our modular structure made it easy to adapt layouts when new needs emerged later in the roadmap.

Launched in November 2024, the redesigned SAP Fieldglass homepage became the default landing experience for thousands of enterprise companies. While full metrics are still being consolidated, early signals show strong adoption and alignment with SAP's long-term platform strategy.