Design Thinking Process

Five phases from user research to validated prototype, applied to every HR and SuccessFactors engagement we run. A discipline, not a workshop.

5 Design thinking phases
UX For HR & ERP projects
Workshops Empathy to prototype
Faster Adoption by design

Why design thinking

Solutions that fit
how people work.

Designed with people, not just for them — the discipline behind every system your workforce actually adopts.

Design thinking can be applied to practically any problem-solving situation. Traditionally used in ERP projects for user experience, we extend it across the full HR transformation lifecycle — so the systems we configure match how your people actually work.

The discipline is structured but not rigid: empathize with users, define the real problem, ideate broadly, prototype quickly, and test with real people before committing to build. It surfaces the requirements that traditional gathering misses — the unspoken workarounds, the moments of friction, the features nobody will use.

The cheapest moment to find a bad idea is before you build it.

That is what design thinking is for HR technology specifically. We bring it to every advisory engagement as a default, not an add-on.

The five phases, applied

From empathy to
validated prototype.

Design thinking moves through five phases, each with a clear purpose and a tangible outcome. For each, here is the concept first — then what it looks like when we run it on a SuccessFactors implementation.

01 Empathize

Shadowing, interviews, and journey mapping to understand how your people actually experience HR today — including the workarounds they have quietly built around the systems they have today.

In practice

We shadow an HR business partner through a Q3 performance cycle in the legacy system, sit with three line managers as they try to complete merit recommendations, and interview six recruiters about their ATS workarounds. We map the actual journey — including the shadow spreadsheet HR ops maintains because the standard report does not break down by cost center the way Finance needs it.

Outcome

A clear picture of what people actually do — not what the process document claims.

02 Define

Synthesise research into a sharp problem statement. The most common failure mode in HR projects is solving the wrong problem beautifully — this phase prevents it.

In practice

Research synthesises into something sharper than "we need SuccessFactors Performance." It becomes: "95% of managers skip mid-cycle check-ins because the legacy form has 7 mandatory fields, no mobile access, and asks for ratings that won't be used until calibration six months later." Now we know what Performance & Goals must actually solve for.

Outcome

SuccessFactors configuration that solves the actual problem — not the assumed one.

03 Ideate

Structured workshops that generate many options before converging on the right one. Quantity first, judgment later — the best ideas often start as the odd ones in the room.

In practice

In a 90-minute workshop with HR ops, three managers, payroll, and IT, we generate 20+ ways to handle the Employee Central transfer process — from the cleanest happy path to the messy multi-country transfer with mid-cycle effective dates and shared positions. We sketch, vote, combine, and prune until three viable designs emerge. Two go to prototype.

Outcome

Design choices made deliberately, with the trade-offs visible to everyone in the room.

04 Prototype

Low-fidelity prototypes — clickable mockups, process walk-throughs — that make the solution tangible before a single line of configuration is written.

In practice

Before anyone opens Provisioning, we build a clickable Figma walk-through of the proposed Open Enrollment flow — every screen the employee will see, every decision the system will ask them to make. We mock up the manager's "My Team" page before touching EC. The prototype lives somewhere lightweight stakeholders can click through on their phone during their commute.

Outcome

Stakeholders agree on the design before configuration cost is sunk.

05 Test

Put prototypes in front of real users, gather honest reactions, and iterate. By the time we build, the design is validated — not assumed.

In practice

Eight real managers attempt to complete a Compensation planning task on the prototype while we watch over Zoom with screen-share. We see exactly where they hesitate, where they ask "is this the right field?", and where they reach for the spreadsheet they swore they would give up. Three rounds of iteration later, the design is something they can use without a trainer sitting next to them.

Outcome

Validated SuccessFactors design ready for build — with the changes already made.

The reason it matters

HR technology projects rarely fail on the technology. They fail on the people side — the design that did not fit how the work is actually done. Design thinking is how we attack the root cause, before there is a platform to blame.

Design with us

Ready to design HR that
people actually use?

Most HR projects start with requirements. The best ones start with empathy. Book a discovery call and we'll show you how design thinking changes the outcome.

A
Athena
Online · Trained on Renew HR
Live demo
How long does a SuccessFactors implementation take?
A
With our SHARP SAP SuccessFactors Lighthouse package — Employee Central + Onboarding — you're in production in 12 weeks, fixed-scope. Full HCM suite (SHARP SAP SuccessFactors Plus) lands in 4-6 months. Both are signed off against SAP's own qualification criteria — 1 of 8 partners nationally with that accreditation.
Try asking
Powered by Claude · Built on SAP BTP