Project summary
Scope
Redesign the Employee page in People Portal, AlphaSights' internal HR platform. HR uses it to record employee changes, run progression and onboard new joiners.
Challenge
The employee record was hard to read and easy to get wrong. The old system accepted any data and saved every change as a new role. Eligibility rules lived in spreadsheets and emails, not in the product. In London alone, about 8 HR people look after about 600 employees.
Solution
I worked with HR and Product to separate real role changes from everyday updates, brought eligibility checks into the product, and kept improving it after launch as HR used it at scale.
5×
Faster load time
73%
Fewer roles records
~47%
Faster to create an employee
Position history
Make a career read like a timeline
In the old system, every change created a new role, even a manager change or a position break. Role lists grew long, with the current role buried at the bottom.
Decision
Product decided which changes create a new role. That fixed the data, but not the reading problem: HR still had to dig through a long list to find the current role.
Shadowing showed HR almost always start from the current position, so I put every position on one page as a timeline, with the current one open and the rest collapsed. An audit trail keeps every smaller change on record, which HR loved.
Outcome
One employee's role list went from 15 roles to 4. HR sees a whole career on one page, without the long scroll.
Editing a position
Design the edit, don't just reuse the create form
Product wanted to reuse the create form for editing. But editing is different: only flexible attributes can change, and HR can schedule several changes at once, which a reused form would hide. Separate team and whiteboard fields also led HR to make team changes they didn’t need.
Decision
I pushed back and designed a separate edit flow. Fixed fields are read-only with a short reason, and each scheduled change shows a “Change upcoming” tag. HR only edits the whiteboard, and the system works out whether the team has changed.
Outcome
HR can only make changes that keep the record correct, and sees every upcoming change in one place.
Progression
Put the check where the decision happens
Promotions happened outside the product. A manager emailed HR, and nothing in the system told HR whether the person was eligible.
Decision
A promotion is really a new position, so rather than add a separate promotion flow, I built it into the form HR already uses to create one. Choosing Promotion fills in what carries over, and the system checks eligibility when HR submits. If a rule isn't met, a modal says which one, but HR can still go ahead. Strong performers sometimes get exceptions, so the system advises and HR decides.
Outcome
Eligibility is now checked inside the product, at the moment HR decides, and HR loved seeing it there. Level changes, which follow fixed rules, went the other way: we automated them, and about 80 a month now only need HR to confirm.
Integration period
Design for the busiest day, not the average one
Every new joiner has a 6-month integration period, and at the end HR logs Passed, Failed or Extend. Logging one person worked fine. The trouble came when a whole joiner class finished at once: HR couldn't easily see who was due, and had to log about 50 outcomes one by one.
Decision
The hard part was the busy days, so I designed for those. A Needs action filter works as a reminder, showing everyone past 6 months with no outcome, and HR can select them and set the status in one go. I kept bulk to Passed and Failed. Extend is rare and needs a reason for each person, so it stays a one-by-one decision. Choosing Failed asks for an offboard date, which HR can apply to everyone at once.
Outcome
Setting outcomes for a joiner class used to take HR half a day. Now it takes about 5 minutes, and the sensitive cases still get individual attention.
Automated emails
Design where the work starts
The system emails HR every month about progression and every day about integration. Product and Engineering saw these as an engineering task. The first version shipped without design, and HR said it looked like phishing.
Decision
For HR, the email is often the first screen of the task, so I argued it should be designed like one. Before, HR had to download a spreadsheet just to see who needed action. I put that list in the email itself, with a direct link to each person in the portal.
Outcome
Far fewer spreadsheet downloads. HR reads what needs attention in the email and goes straight to the right place in the portal, without searching again.
Reflection
What I learned
Many of the UX problems started in the data. Every change created a new role, so the history was long and nothing could be automated. Once Product defined which changes create a new role, I could design a clear timeline. The same structure laid the foundation for automating 38% of HR's operational work.
Then we let HR show us what to improve. Integration outcomes started as a single action on each details page. HR told us 90% of joiners pass, so they were making the same decision one person at a time. We added bulk Pass and Fail, and kept Extend individual because it needs a reason for each person. A class now takes about 5 minutes instead of half a day.
