top of page

Hire to Retire

Reframing skills from a feature into a foundational capability across the employee lifecycle.

Product Strategy · Enterprise Systems · Cross-Product UX

I created a shared experience model spanning Talent and HCM, connecting worker incentives, AI-assisted profile maintenance, skill trust, and workforce intelligence.
AT A GLANCE
ROLE

Senior UX Design Engineer

TOOLS

Figma

TIMELINE

April 2024–June 2025

PARTNERS

Design leadership · Product teams · Research contributors · Talent and HCM stakeholders

SCOPE

Skills · Career Development · Learning · Internal Opportunities · Feedback · Performance · Mobility · Workforce Planning

WHAT I OWNED

Experience strategy · Systems mapping · Interaction model · Worker lifecycle · AI/automation concepts · Cross-product consistency

CHALLENGE

Skills had become increasingly important across Workday, but the experience had evolved unevenly across products. Workers encountered skills in Career Hub, Learning, internal opportunities, job profiles, feedback, performance conversations, and their Skills Profile, without those interactions consistently feeling like one system.


At the same time, organizations depended on current skills data to make workforce decisions—but workers had little incentive to keep that data updated.

STRATEGIC SHIFT

The key reframing was to stop treating skills primarily as a data-collection problem.


Design incentives, not just interfaces.


If an organization wants better workforce intelligence, it first has to make maintaining skills valuable and effortless for the worker. Better organizational data should become a byproduct of a better individual experience.

MY ROLE

Organizational intelligence starts with individual experience

A workforce-planning system can only be as useful as the data underneath it. Improving the worker experience became a prerequisite to improving business decision-making.


Automation should remove effort without removing agency

The system can do more of the maintenance work while still leaving people in control of their professional identity.


A shared mental model matters more than a shared component

The goal was not merely to standardize the visual representation of skills, but to make the concept behave consistently wherever a worker encountered it.

KEY DECISIONS

Decision 1 — Who needs to benefit first?

The organization needed accurate skills data, but demanding more manual updates from workers would not solve the problem. I reframed the strategy around giving workers direct value through growth, opportunities, feedback, and development so maintenance became worthwhile.


Decision 2 — Should skill maintenance be an explicit task?

I explored making maintenance more ambient. Existing work signals—learning, projects, goals, feedback, job history—could help pre-seed or suggest profile changes rather than forcing workers to repeatedly rebuild their skills manually.


Decision 3 — How much automation is appropriate?

Automation could reduce effort, but professional identity is personal and consequential. The model therefore kept the worker in control: the system could suggest changes, while the person confirmed, declined, or corrected them.


Decision 4 — What makes a skill rating trustworthy?

A level without provenance is difficult to trust. I explored models that made recency, evidence, relevance, duration, and source more visible so users could understand where proficiency assessments came from.

HOW I WORKED

The work helped establish a broader product model for skills across Workday, shifting the conversation from metadata attached to individual products toward a foundational capability spanning Talent and adjacent HCM experiences.


It also established a principle that carried into later AI work: the system should build useful context through the natural course of work instead of repeatedly asking the user to reconstruct it manually.

WHAT CHANGED

The work helped establish a broader product model for skills across Workday, shifting the conversation from metadata attached to individual products toward a foundational capability spanning Talent and adjacent HCM experiences.


It also established a principle that carried into later AI work: the system should build useful context through the natural course of work instead of repeatedly asking the user to reconstruct it manually.

LEARNINGS

Organizational intelligence starts with individual experience

A workforce-planning system can only be as useful as the data underneath it. Improving the worker experience became a prerequisite to improving business decision-making.


Automation should remove effort without removing agency

The system can do more of the maintenance work while still leaving people in control of their professional identity.


A shared mental model matters more than a shared component

The goal was not merely to standardize the visual representation of skills, but to make the concept behave consistently wherever a worker encountered it.

CONTRIBUTIONS

Product Strategy
Skills Strategy · Skills as an Approach · Workforce Intelligence · Product Vision · Opportunity Identification


Systems Thinking
Hire-to-Retire Lifecycle · Cross-Product Experiences · Talent + HCM · Skills Inventory · Historical Data · Portability


Product Design
Unified Skills Experience · Interaction Models · Worker Experience · Career Development · Complex Enterprise Workflows


AI & Automation
Automated Skill Maintenance · Generative AI · Machine Learning · Human-in-the-Loop Patterns · Evidence-Based Skill Levels


Research & Synthesis
Journey Mapping · Problem Framing · Research Synthesis · Worker Needs · Business Needs


Leadership
Cross-Functional Alignment · Strategic Influence · Design Advocacy · Product/Engineering Partnership · Navigating Ambiguity

port·fo·li·o| pôrtˈfōlēō | noun (plural portfolios) - a large, thin, flat case

​

© 2026 by Michael L. Olivier | thinflatcase.com

  • Medium
  • GitHub
  • LinkedIn
bottom of page