Case Studies/Time Tracker

Product Design Case Study · Enterprise Platform · Mobile-first

People Portal & Time Tracker — every business module, one platform

How I turned scattered legacy links and third-party tools into one mobile-first platform, giving managers a single point of control and employees a single place for their working day.

My role
Lead Product Designer / UX Architect
Team
4 members, led by me
Timeline
Jan 2024 – 2025
Platform
Mobile-first · Mobile & web

Developed screens

Mobile self-service and desktop manager views · hover to pause, click to enlarge

Desktop · Employee dashboard
Desktop · Employee dashboard
Desktop · Add activity
Desktop · Add activity
Mobile · Secure login
Mobile · Secure login
Mobile · Employee overview
Mobile · Employee overview
Desktop · Manager dashboard
Desktop · Manager dashboard
Mobile · Password recovery
Mobile · Password recovery
Mobile · Dashboard
Mobile · Dashboard
Desktop · Employee view
Desktop · Employee view
5Departments researched
50People interviewed, employees & managers
2Audiences served by one platform
4Team members I led

One platform where managers run the business and employees run their day

Employees depended on a third-party business application and a trail of separate links for everyday needs: leave, timesheets, documents, policies, insurance and HR services. Data sat in different tables, and every department had its own way of working.

I initiated and led the redesign of this into a single, mobile-first People Portal, bringing every business module into one place, with compliance, procurement and HR operations built in. My brief to myself was simple: solve for the stakeholders who run the business and the employees who use it every day.

My role: I led a 4-member team and owned the work end to end: research, information and application architecture, interaction design, the design system, usability testing and developer handover.

A single point of contact for everything that affects the business.

  • Performance tracking
  • Attendance
  • Approvals
  • History
  • Teams & hierarchy
  • Billing
  • Projects
  • Task tracking
  • Tickets

The problem wasn’t missing data. It was fragmented structure and experience.

The company already had employee data, processes and content. But it was spread across legacy tables, external links and department-specific workflows. Employees had to remember where to go for each task, and managers had no single place to review requests, monitor time and act.

01

Fragmented employee journeys

Leave, timesheets, documents, policies and insurance lived behind different links instead of one predictable navigation model.

02

No view of who works on what

Managers couldn’t easily see which project each employee was on, or how time and effort were being spent.

03

Unstructured, siloed records

Data from separate tables and separate project trackers made information hard to trust, report on and maintain.

04

High cognitive load

People had to understand the system’s structure before they could complete ordinary workplace tasks.

05

Slow approvals

One-by-one approvals and time reviews with no bulk actions or consolidated views cost managers hours every week.

06

No single point of contact

Approvals, tickets, billing and HR questions had no one home, so issues moved through emails and follow-ups.

I started with where people were, not with screens

Before designing anything, I needed the real picture of how work got done. These were the questions I set out to answer:

  • Which system does the company use to capture time entries?
  • Where do people apply for leave, and how do they enter timesheets?
  • How do managers know which project an employee is working on?
  • How are records and project tracking maintained today?
  • Why does the business want this platform, and what does success look like?

I audited the existing methods, reviewed research documents, and used the findings to set the product vision and roadmap.

How the research ran

  1. Quantitative research & data gatheringAudited current tools and processes and gathered data on how time, leave, timesheets and projects were managed.
  2. Two lenses, two templatesOne template captured employee needs; the other captured how managers and stakeholders wanted to see the business.
  3. Interviews across five departmentsTen people from each of Development, Support, Finance, HR and Procurement, covering employees and managers.
  4. Affinity mappingGrouped what people said and how they felt into common themes, then mapped user needs against stakeholders’ business pain points.
  • Development
  • Support
  • Finance
  • HR
  • Procurement

What the synthesis revealed

01

User data spread across platforms

The core business pain point: employee and project data had to be brought together from many systems into one.

02

Data people can trust

Managers needed accurate, up-to-date records to act on, not numbers reconciled by hand.

03

KPIs for dashboards

Leadership needed clear KPIs defined up front so dashboards show performance, attendance, projects and billing at a glance.

04

User needs matched to business goals

Every employee need was mapped to a stakeholder pain point, so each feature serves both.

Understand, structure and unify what already existed

We didn’t need to invent HR processes from nothing. The work was to understand the ecosystem, define the right problem, reorganise how processes fit together, and deliver a coherent system that improved through phased releases.

01

Discover

Audited legacy links, data sources, tasks, stakeholder expectations and department workflows, then interviewed 50 people.

02

Define

Synthesised findings into affinity maps, set the vision and roadmap, and defined KPIs and requirements for both audiences.

03

Develop

Explored module structures, employee and manager flows, role-based dashboards, bulk actions and mobile-first patterns.

04

Deliver

Released module by module, tested each version with users, and refined before the next release.

The key decision: stop exposing the old system’s structure to users. Group information into recognisable modules, design each one around a task, and show every role only what matters to them.

From insight to a tested, accessible architecture

Between 2 February and 15 March 2025, I turned the research into structure: an architecture, flows and wireframes the whole team could build on. Because users already knew their flows, the design built on that familiarity instead of forcing new habits.

01

Information architecture

Organised every module into one structure with role-based views for managers and employees.

02

User flows & wireframes

Mapped key journeys and built wireframes with real components and data, so layouts reflected actual content from day one.

03

Accessibility (WCAG)

Applied WCAG guidelines across components and flows, covering contrast, readable type, clear focus states and keyboard access.

04

Application architecture

Defined how modules, data and services connect, giving developers a clear blueprint for the platform.

Usability testing, release by release

Rather than waiting for the whole platform to be finished, every completed module shipped as its own version and was tested with real users. Each round showed us what was missing and what was still unsolved, before it could become expensive to fix.

ReleaseShip each completed module as its own version.
TestRun usability testing to find missing features and unsolved issues.
RefineFeed findings into the design and the next release.

Repeated for every module, so the product got better with every version.

Mobile-first, then scaled to desktop

Employee self-service was designed for the phone first; manager dashboards scale up to desktop for deeper review and bulk actions. Explore the live Figma files.

Mobile — employee self-service

Desktop — manager & employee dashboards

Consistency across modules, roles and releases

I built the design system in parallel with the research, so every new module launched consistent. It started with the branding theme, typography and a custom icon set based on the flows users already knew, then grew into foundations for colour, spacing, forms, feedback and status, and components for navigation, cards, tables, filters, approvals, calendars and alerts, across mobile and web.

Design system — foundations & components

A clearer working day for everyone

01

One place for employees

Daily tasks, leave, timesheets, payslips, trainings and tickets in one app, on mobile or web.

02

One view for managers

Performance, attendance, approvals, projects, billing and teams in one place, with bulk actions for faster decisions.

03

Built-in compliance

Compliance, procurement and HR operations run inside the same platform, with history and records in one place.

04

Familiar from day one

Flows and icons based on how people already work made the platform easy to adopt across departments.

Reviewed by

  • CTO
  • Delivery Heads
  • HR Heads
  • Managers

Built for

Every employee in the company

Self-service, time tracking and approvals in one place, on mobile and desktop.

10 · Conclusion

One connected platform that serves the business and the people who run it

Starting from research rather than screens let us replace scattered tools with a single mobile-first platform. Managers got one point of control for the business, employees got one place for their day, and a shared design system kept every module consistent as the platform grew.

This is how I like to work: learn the domain first, architect for every role, test early and often, and lead the team through to delivery.