Redesigning the SAP Time Entry App: From Tedious Tapping to Seamless Tracking

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, workers using the Fieldglass mobile app were struggling to get paid on time because submitting a timesheet on mobile was unnecessarily painful. The existing app carried ratings of 1.4 stars on the Apple App Store and 2.4 stars on Google Play, which is a clear signal that something needed to change!

If we categorize the problems into core pain points:

To ground our decisions in real behavior, I worked with our UX researcher to combine app store sentiment analysis, user research interviews, and data mining across the global worker base.

Workers ranged across a wide variety of roles, including Business Analysts, IT professionals, Machine Operators, Project Managers, Contract Specialists, and more. Despite their different contexts, their time entry needs shared common patterns.

That meant the common one-task day needed to be fast, while the product still had to support workers moving between many tasks.

Leadership initially asked us to improve the workflow already used by the old app. A worker would open a day, enter how long they spent on each task, separately enter when they started and finished work, then save everything. At the end of the week, they would submit the timesheet for manager approval.

However, based on my observation, this still solved the wrong problem. It made the worker responsible for acting as the recording device.

Based on the interviews we've conducted, many workers had to keep notes on paper or in other note apps throughout the day, then transcribe those notes into Fieldglass later. That is only slightly annoying for someone working at a desk, but much harder for a frontline worker moving through a job site such as an oil and gas worker.

I had also seen what happened downstream when those records did not agree. The hours entered for individual tasks often failed to match the separate clock-in and clock-out times. The manager could not resolve that discrepancy alone, so they had to contact the worker offline and ask them to correct it.

That's why instead of making that form easier to complete, I pushed for the product to capture the workday itself.

About 90 percent of the old mobile experience changed. I created a new information architecture, a new core interaction, and new screens rather than carrying the old workflow forward.

At the time documented here, the first version of the app is to be released soon!

Detailed usage data and performance benchmarks are confidential at this stage, however the team will be measuring success against the following key indicators post-launch:

Full performance results and usage data will be shared following the public launch post Sept 2026.

Due to confidentiality agreements, specific usage metrics and internal performance data cannot be disclosed at this time. Check back after launch for updated results! 🚀