Talent Intelligence Platform

Talent intelligence platforms helps HR assistants, recruiting specialists and hiring specialists make smarter hiring decisions by turning complex data into actionable insights to map internal career growth opportunities.

Goal

Build a two-sided, data-centric, transparent talent intelligence platform that helps organizations and candidates find through skill-aligned recommendations. The platform is designed to be scalable, flexible, and sold standalone or as part of a suite.

Problem Statement

Talent managers face inefficient workflows while managing a fragmented candidate pool across multiple systems due to lack the information.

Challenges

  • Data-Rich: Need at-a-glance information

  • Complex Matching & Transparency: Explain why a candidate matches a role

  • Two-Sided Experience: Balance needs of employers and candidates in one platform

  • Scalability: Large volume of job openings and candidates

  • Cross-System Integration: Ensure smooth interactions across existing systems

Result

Delivered a four-phase release which sold could be standalone or as part of a suite.

Release 1: Focused on transparency of reports.

Release 2: Added candidate portal and information input and output.

Release 3: Added Hiring Manager support and Appian.

Release 4: Enhanced assessments and Appian.

Role-Driven Design Process

Discover

Define Roles

Ideate

Design

Personas in the existing platform had similar overlaps we could support as part of a flexible system.

Requirements gathering easier by defining persona flows.

Existing System

Requirements Gathering Through UX

UX played a

The roles consisted of Hiring Assistants, Recruiting Specialists, Hiring Specialists and Candidates.

Data-Rich Pages

Each persona needed access to large amounts of data on one screen.

Scanability Difficult to Achieve

Competing data There’s a lot of information that is competing for attention

Daily Power Users

Scalability

With so much information, it was difficult. Each change would have a cascading effect

  • Information needed to be recognizable at a glance.

  • Efficiency was key for the daily power users.

  • Scalability

    • The UI needed to be scalable as the product grew in the four-phase release and beyond.

INFORMATION SUBSET

Integrated Platforms

New Platform

Although we reviewed the existing personas, we didn’t want to consider just yet how they’d fit into the user flows just yet. Our priority was to design the best possible experience for this product first. Each map defined the optimal experience independently, and by focusing on each persona in isolation, we designed experiences that addressed their unique needs and priorities. For this project, we designed individual workforce roles to optimize responsibilities and workflows, defining each role independently to provide clarity in tasks, goals, and priorities. Next, we examined how tasks and processes aligned across roles, helping define each role clearly while considering a scalable and consistent system.

The end-to-end experience of new and existing candidates acted as a foundation to drive cross-functional alignment and define the scalable product roadmap.

Early discovery mocks to visualize similar high-level flows for one persona

Support Existing Platform

With the foundation in place, we examined how the product could align with the existing platform. This approach allowed us to identify potential connection points, some of which didn’t have a UI, without impacting either product, creating a more cohesive and scalable suite.

MVP Hypothesis

We drafted a potential MVP flow based on the personas and priorities we defined. This hypothesis would serve as a starting point to guide discussions with stakeholders, highlight gaps, and inform decisions about which features to prioritize first. It was intended to evolve as we refined personas, validated assumptions, and gathered feedback, so the MVP addressed the core personas’ needs we defined earlier.

Wireframing

Touchpoints

Determine where multiple personas were seeking the same information or performing similar actions.

We developed micro flows for each persona to map the granular steps of their tasks. This level of detail was important because it allowed us to understand what each user actually needs and prioritize the most important elements of their workflow.

After identifying and prioritizing overlaps, we began designing shared interactions using wireframes. For each touchpoint, we examined where personas’ needs converged, assessed the priority of each overlapping need, and noted areas where there was no overlap at all. This approach allowed us to address the requirements of multiple personas simultaneously and create shared workflows that were coherent and aligned with the priorities of the overlaps.

Hypothesis for MVP

Hypothesis for MVP (validated and used above)

Discovered potential reusable components designed for variation

Defined the priorities for each persona and ideated components to support them.

Final Design & Delivery

Areas that had data-rich sections while keeping returning candidates engaged.

Early exploration of ways to surface and organize key information.

Initial work targeted the areas of the site visited most often

Scannable cards highlighted new information and allowed for deeper exploration