Absento
Absento
(2024)
(2024)
Simplify HR Processes and Maximize Team Efficiency with a Smart, User-Friendly Approach
Simplify HR Processes and Maximize Team Efficiency with a Smart, User-Friendly Approach
Research-Driven
Research-Driven
UX Strategy
UX Strategy
Design System
Design System




New dimension of personnel management with Absento - a Web-based internal service for all company employees.
New dimension of personnel management with Absento - a Web-based internal service for all company employees.
🧭
Introduction
I designed Absento, a web-based HR platform that streamlines internal processes such as leave requests, absence tracking, and employee scheduling. The main goal was to improve the daily experience of employees while reducing friction for HR teams and decision-makers. My responsibilities included discovery, wireframing, design system creation, user testing, and close collaboration with developers to ensure accurate implementation. I leveraged Fluent UI, a React-based component library, to build a consistent and scalable interface that enabled rapid MVP delivery without compromising usability or visual quality.
I designed Absento, a web-based HR platform that streamlines internal processes such as leave requests, absence tracking, and employee scheduling. The main goal was to improve the daily experience of employees while reducing friction for HR teams and decision-makers. My responsibilities included discovery, wireframing, design system creation, user testing, and close collaboration with developers to ensure accurate implementation. I leveraged Fluent UI, a React-based component library, to build a consistent and scalable interface that enabled rapid MVP delivery without compromising usability or visual quality.
Role:
Role:
Product Designer
Product Designer
Project Type:
Project Type:
B2B Web App
B2B Web App
Collaboration:
Collaboration:
Cross-functional with developers and stakeholders
Cross-functional with developers and stakeholders
🔍
Understanding the Users
To design a solution that worked across departments, I developed proto-personas representing two core user types: office-based managers and on-site shift workers. This helped align the UX with real-world contexts.
To design a solution that worked across departments, I developed proto-personas representing two core user types: office-based managers and on-site shift workers. This helped align the UX with real-world contexts.

Evelyn, a mobile sales manager, needed a centralized overview of her team’s absences and scheduling, with quick, frictionless ways to approve requests.
Evelyn, a mobile sales manager, needed a centralized overview of her team’s absences and scheduling, with quick, frictionless ways to approve requests.

Adam, a factory worker, interacted with the system only occasionally, often via a kiosk. His priorities were clarity, simplicity, and SMS-based communication.
Adam, a factory worker, interacted with the system only occasionally, often via a kiosk. His priorities were clarity, simplicity, and SMS-based communication.






💡
Key Pain Points
From workshops and persona mapping, we defined and addressed several core issues:
From workshops and persona mapping, we defined and addressed several core issues:
❌
❌
Delays and confusion in leave approvals
Delays and confusion in leave approvals
Employees and managers often faced bottlenecks due to unclear approval chains and lack of real-time updates, causing scheduling conflicts and frustration.
Employees and managers often faced bottlenecks due to unclear approval chains and lack of real-time updates, causing scheduling conflicts and frustration.
❌
❌
Lack of calendar visibility across teams
Lack of calendar visibility across teams
Managers couldn’t easily see who was on leave or available, leading to miscommunication and difficulty in planning workloads or approving requests.
Managers couldn’t easily see who was on leave or available, leading to miscommunication and difficulty in planning workloads or approving requests.
❌
❌
Inflexible and outdated substitution and notification workflows
Inflexible and outdated substitution and notification workflows
The process of assigning replacements and receiving status updates was rigid, manual, and inconsistent - especially problematic in time-sensitive environments.
The process of assigning replacements and receiving status updates was rigid, manual, and inconsistent - especially problematic in time-sensitive environments.
❌
❌
Low accessibility for non-desk workers
Low accessibility for non-desk workers
Employees on the factory floor had limited access to tools and relied on kiosks or SMS, which weren’t well integrated with the broader system.
Employees on the factory floor had limited access to tools and relied on kiosks or SMS, which weren’t well integrated with the broader system.
🧠
Designing for Efficiency
My approach was focused on reducing friction and improving clarity at every touchpoint. I restructured the information architecture to provide a dashboard-first experience tailored to each user’s context. Managers could now view team availability, approve requests, and assign overtime all from one central location. Meanwhile, factory workers could easily submit requests and review their schedules without needing to navigate complex menus or external platforms. By reducing the number of steps it took to complete common actions, I helped improve task completion speed and user confidence.
My approach was focused on reducing friction and improving clarity at every touchpoint. I restructured the information architecture to provide a dashboard-first experience tailored to each user’s context. Managers could now view team availability, approve requests, and assign overtime all from one central location. Meanwhile, factory workers could easily submit requests and review their schedules without needing to navigate complex menus or external platforms. By reducing the number of steps it took to complete common actions, I helped improve task completion speed and user confidence.






📐
Building a Scalable Design System
To keep development agile and the design consistent, I built the product UI using Fluent UI. Its component-based structure allowed me to maintain scalability and accessibility while aligning with engineering workflows. This enabled our team to focus on the unique interactions and flows of Absento without reinventing basic interface elements. The result was a product that felt cohesive, responsive, and ready for enterprise use - while still being highly adaptable to future iterations.
To keep development agile and the design consistent, I built the product UI using Fluent UI. Its component-based structure allowed me to maintain scalability and accessibility while aligning with engineering workflows. This enabled our team to focus on the unique interactions and flows of Absento without reinventing basic interface elements. The result was a product that felt cohesive, responsive, and ready for enterprise use - while still being highly adaptable to future iterations.




✅
Outcome
Absento delivered a smarter, more human-centered HR experience. It addressed real workflow pain points while supporting the varied needs of both administrative and field workers. By grounding the design in real user behavior and streamlining it through scalable design systems, I helped build a product that was efficient for developers and delightful for users. The result is a platform that not only simplifies HR processes but also enhances productivity and team harmony across the entire organization.
Absento delivered a smarter, more human-centered HR experience. It addressed real workflow pain points while supporting the varied needs of both administrative and field workers. By grounding the design in real user behavior and streamlining it through scalable design systems, I helped build a product that was efficient for developers and delightful for users. The result is a platform that not only simplifies HR processes but also enhances productivity and team harmony across the entire organization.
Don't hesitate.
Let’s talk.
Don't hesitate.
Let’s talk.