top of page

QBIT

Developer

HR Job Profile Platform: eJobDesign

Job architecture is critical to organisational clarity, yet the existing platform was complex, outdated, and frustrating to use. HR teams needed a system that could handle complex role structures without overwhelming users. The challenge was to redesign the experience from the ground up - simplifying workflows, improving clarity, and transforming a specialist tool into an intuitive, modern platform.

Timeline: 2017 - 2019

Platform: Web

Tester

Role: UX/UI, Front-end Developer

Designer

Context & Constraints

Context​

  • Legacy HR platform managing complex job families, profiles, competencies, and outputs.

  • Functionally powerful but visually outdated and difficult to navigate.

  • High learning curve even for experienced HR professionals.

  • Redesign aimed to modernise UI and introduce UX best practices without disrupting core workflows.

Goals

  • Modernise the UI to align with current design standards.

  • Simplify capturing and managing job profile data.

  • Improve navigation and information architecture.

  • Increase usability and satisfaction for experienced users.

  • Reduce onboarding and training time for new users.

  • Support development with a scalable design system.

Constraints

  • Legacy tech stack limited speed and scope of changes.

  • Fixed release schedule and tight deadlines.

  • Small, cross-functional team (3 people).

  • Stakeholders unfamiliar with UX processes and principles.

  • Complex, rule-heavy HR data structures.

  • Ongoing scope creep during the redesign process.

  • No existing UI standards or iconography system.

Users & Insights

The platform is used by highly skilled HR professionals responsible for managing job families, job profiles, competencies, and outputs. While deeply familiar with HR structures and terminology, they were increasingly frustrated by the limitations of an outdated and unintuitive system.

Disclaimer

The user images and personas shown are representations of the broader user group based on research insights. They are not real individuals, and any similarities to actual persons are purely coincidental.

Key User Needs

  • Faster, more intuitive workflows.

  • Logical information structure aligned to a job profile’s natural flow.

  • Clear distinction between editable and read-only content.

  • Reduced reliance on training and documentation.

  • Consistent, modern UI patterns to build confidence and efficiency.

Key Insights

  • Familiarity with HR concepts did not reduce friction caused by poor UX.

  • Inconsistent layouts and interactions increased cognitive load.

  • Visual clarity and structure were critical to preventing errors.

  • Consistency mattered more than feature expansion.

Design Process

Final Designs

  • Modernised UI aligned with current design standards.

  • Clear, consistent layouts across job profiles, families, and competencies.

  • Strong visual distinction between editable and read-only states.

  • Simplified forms with improved hierarchy and spacing.

  • Consistent iconography and UI patterns across the platform.

  • Design decisions optimised for experienced, high-frequency users.

  • Foundations laid for a scalable design system to support future growth.

Image 1/5
High-fidelity designs presenting the modernised UI, updated layout, and consistent visual language of the HR platform.
Image 2/5
High-fidelity designs presenting the modernised UI, updated layout, and consistent visual language of the HR platform.
Image 3/5
High-fidelity designs presenting the modernised UI, updated layout, and consistent visual language of the HR platform.
Image 4/5
High-fidelity designs presenting the modernised UI, updated layout, and consistent visual language of the HR platform.
Image 5/5
High-fidelity designs presenting the modernised UI, updated layout, and consistent visual language of the HR platform.

Reflection

What I Learned

  • Conducting user interviews and managing expectations in specialist domains.

  • Introducing UX thinking to stakeholders unfamiliar with the discipline.

  • Managing scope creep while protecting core user flows.

  • Bridging UX and development constraints in a small team.

  • Establishing UI best practices and icon systems from scratch.

  • Gaining confidence in presenting work and gathering actionable feedback.

© 2025 Blueprints by René du Plooy. All rights reserved.

bottom of page