Designing Key HR Services for an Internal Mobile App
Designing Key HR Services for an Internal Mobile App
Designing Key HR Services for an Internal Mobile App
Long story short
Long story short
Improved core HR services in a mobile app
Improved core HR services in a mobile app
Redesigned complex workflows (vacations and expert meetings), made them intuitive while preserving strict business rules and multi-role interactions.
Redesigned complex workflows (vacations and expert meetings), made them intuitive while preserving strict business rules and multi-role interactions.
Context
Context
JNP - internal mobile app with access to HR services.
JNP - internal mobile app with access to HR services.
I worked on an internal mobile app that provides employees with access to HR services, including:
vacation and business trip management,
internal tools,
professional development services.
The app already had an established visual language and structure, so my focus was on:
improving UX logic,
refining user flows,
designing new features within existing constraints.
I contributed across multiple areas, with two key directions highlighted below.
I worked on an internal mobile app that provides employees with access to HR services, including:
vacation and business trip management,
internal tools,
professional development services.
The app already had an established visual language and structure, so my focus was on:
improving UX logic,
refining user flows,
designing new features within existing constraints.
I contributed across multiple areas, with two key directions highlighted below.
Problem
Problem
The goal was to make these processes intuitive without simplifying or breaking the underlying logic.
The goal was to make these processes intuitive without simplifying or breaking the underlying logic.
The main challenge was designing user-friendly experiences within complex and constrained systems.
Across different features, common issues included:
disconnected workflows,
unclear system logic,
friction caused by business rules,
multiple user roles with different needs.
The main challenge was designing user-friendly experiences within complex and constrained systems.
Across different features, common issues included:
disconnected workflows,
unclear system logic,
friction caused by business rules,
multiple user roles with different needs.
My Role
My Role
I was responsible for:
UX logic and interaction design,
designing mobile user flows,
contributing to HR admin panel logic,
adapting and extending existing product patterns.
I collaborated with HR stakeholders and validated decisions through feedback from colleagues, who represented the actual user base.
I was responsible for:
UX logic and interaction design,
designing mobile user flows,
contributing to HR admin panel logic,
adapting and extending existing product patterns.
I collaborated with HR stakeholders and validated decisions through feedback from colleagues, who represented the actual user base.
Process: Understanding workflows and constraints
Process: Understanding workflows and constraints
I started by analyzing how HR processes actually work and where users experience friction.
I started by analyzing how HR processes actually work and where users experience friction.
Since formal research was not conducted, I validated assumptions through:
discussions with HR stakeholders,
testing flows with colleagues outside the project,
observing how users interpret scenarios without prior context.
Since formal research was not conducted, I validated assumptions through:
discussions with HR stakeholders,
testing flows with colleagues outside the project,
observing how users interpret scenarios without prior context.
Process: Pattern research
Process: Pattern research
I’ve explored commonly used products that share similar UX patterns.
I’ve explored commonly used products that share similar UX patterns.
To design intuitive interactions, I explored patterns from:
calendar and scheduling tools,
booking systems,
planning interfaces.
This helped create familiar user experiences even within complex internal logic.
To design intuitive interactions, I explored patterns from:
calendar and scheduling tools,
booking systems,
planning interfaces.
This helped create familiar user experiences even within complex internal logic.
Case #1
Case #1
Vacation flow redesign
Vacation flow redesign
Vacation flow redesign
Context
Context
Company uses two systems: vacation requests and a yearly vacation schedule.
Company uses two systems: vacation requests and a yearly vacation schedule.
In addition to submitting vacation requests, the company uses a vacation schedule — a yearly plan created in advance that defines when employees are expected to take time off.
This schedule is important for:
workforce planning,
workload distribution,
budget forecasting.
In addition to submitting vacation requests, the company uses a vacation schedule — a yearly plan created in advance that defines when employees are expected to take time off.
This schedule is important for:
workforce planning,
workload distribution,
budget forecasting.
Problem
Problem
Two systems exist but are not connected.
Two systems exist but are not connected.
Employees planned vacations in advance (schedule), but submitted requests separately with free date selection.
After a business change:
users could only select dates from the schedule,
but the connection between these flows was unclear.
This created confusion:
users didn’t understand why date selection was restricted,
navigation between flows was unclear,
users could get stuck without knowing what to do.
Employees planned vacations in advance (schedule), but submitted requests separately with free date selection.
After a business change:
users could only select dates from the schedule,
but the connection between these flows was unclear.
This created confusion:
users didn’t understand why date selection was restricted,
navigation between flows was unclear,
users could get stuck without knowing what to do.
Employees could submit vacation requests in the app, while the vacation schedule existed only within HR and wasn't part of the workflow.
Employees could submit vacation requests in the app, while the vacation schedule existed only within HR and wasn't part of the workflow.
Solution
Solution
I redesigned the experience to connect both processes into a single, coherent flow
I redesigned the experience to connect both processes into a single, coherent flow
Made constraints visible
Clearly explained why dates are restricted and where they come fromAdded cross-navigation
Users can seamlessly move between schedule and requestSupported planning logic
Clear sequence: plan → adjust → submit
Made constraints visible
Clearly explained why dates are restricted and where they come fromAdded cross-navigation
Users can seamlessly move between schedule and requestSupported planning logic
Clear sequence: plan → adjust → submit
Vacation planning service. Employees can see all planned vacation periods and the status of each one. When submitting a vacation request, they simply select one of the planned periods.
Vacation planning service. Employees can see all planned vacation periods and the status of each one. When submitting a vacation request, they simply select one of the planned periods.
Result
Result
Two disconnected processes became a single, understandable flow.
Two disconnected processes became a single, understandable flow.
Users now better understand:
why restrictions exist,
where to modify dates,
how to complete the process.
HR teams benefit from improved alignment between planning and actual vacation requests, making workforce and budget planning more predictable.
Users now better understand:
why restrictions exist,
where to modify dates,
how to complete the process.
HR teams benefit from improved alignment between planning and actual vacation requests, making workforce and budget planning more predictable.
Case #2
Case #2
Expert meeting service
Expert meeting service
Expert meeting service
(Top Dating / Ask Project)
(Top Dating / Ask Project)
(Top Dating / Ask Project)
Context
Context
One of the company's goals was to make internal expertise more accessible.
One of the company's goals was to make internal expertise more accessible.
To support this, we designed a service that enables employees to schedule one-on-one meetings with senior managers (Top Dating) or project managers (Ask Project), creating a simple way to ask questions, discuss career development, or share ideas.
To support this, we designed a service that enables employees to schedule one-on-one meetings with senior managers (Top Dating) or project managers (Ask Project), creating a simple way to ask questions, discuss career development, or share ideas.
While Top Dating and Ask Project are presented as separate features in different parts of the app, they share the same interaction model and solve the same user need — connecting employees with experts through one-on-one meetings.
While Top Dating and Ask Project are presented as separate features in different parts of the app, they share the same interaction model and solve the same user need — connecting employees with experts through one-on-one meetings.
Design challenge
Design challenge
Design a service that allows employees to book meetings with experts or managers.
Design a service that allows employees to book meetings with experts or managers.
Challenges included:
multiple roles (employee, expert, HR),
hybrid logic (automatic booking + manual coordination),
scenarios where no time slots are available.
Challenges included:
multiple roles (employee, expert, HR),
hybrid logic (automatic booking + manual coordination),
scenarios where no time slots are available.
Solution
Solution
I designed a flexible booking experience:
I designed a flexible booking experience:
Familiar scheduling model
Users select experts and available time slots, similar to booking systemsGraceful fallback scenario
If no slots are available:users can send a request,
HR coordinates manually
Role-based simplicity
Complex internal processes are hidden from the user
Familiar scheduling model
Users select experts and available time slots, similar to booking systemsGraceful fallback scenario
If no slots are available:users can send a request,
HR coordinates manually
Role-based simplicity
Complex internal processes are hidden from the user
The booking experience combines automated scheduling with a graceful fallback. Employees can book available time slots directly or submit a meeting request when no availability is shown, allowing HR to coordinate the meeting manually.
The booking experience combines automated scheduling with a graceful fallback. Employees can book available time slots directly or submit a meeting request when no availability is shown, allowing HR to coordinate the meeting manually.
Result
Result
The service:
simplified access to internal expertise,
reduced barriers to communication with managers,
successfully combined automated and manual workflows.
The service:
simplified access to internal expertise,
reduced barriers to communication with managers,
successfully combined automated and manual workflows.
Impact
Impact
The new features helped the mobile application better support both business goals and employees' everyday workflows.
The new features helped the mobile application better support both business goals and employees' everyday workflows.
In particular:
HR processes became more structured and easier to manage,
employees gained clearer and more intuitive user flows,
communication with managers and experts became more accessible,
planning and execution of HR activities became more closely connected.
In particular:
HR processes became more structured and easier to manage,
employees gained clearer and more intuitive user flows,
communication with managers and experts became more accessible,
planning and execution of HR activities became more closely connected.
Other Contributions
Other Contributions
In addition to key features, I also worked on:
employee referral service with status tracking,
internal currency balance and transaction history,
improvements to existing HR flows.
In addition to key features, I also worked on:
employee referral service with status tracking,
internal currency balance and transaction history,
improvements to existing HR flows.
These tasks were smaller in scope but helped maintain a consistent product experience.
These tasks were smaller in scope but helped maintain a consistent product experience.
