top of page

Evolve HR

Turning an ambiguous enterprise concept into a product direction the organization believed was worth building.

0→1 Product Strategy · Prototyping · Executive Influence

I led the experience from loosely defined requirements to a cohesive product vision, using rapid design and prototyping to align Product, Engineering, Architecture, and senior leadership.
AT A GLANCE
ROLE

Senior UX Design Engineer

TOOLS

Figma

TIMELINE

March 2023–March 2024

PARTNERS

Multiple Product Managers · Functional Architecture · Engineering · UX leadership · Senior Product leadership

SCOPE

Flexible Teams · HCM · Talent · Cross-platform work experiences

WHAT I OWNED

Product vision · Experience model · Storyboarding · Interaction design · Rapid prototyping · Stakeholder alignment · Executive communication

CHALLENGE

Flexible Teams crossed organizational, technical, and product boundaries. Requirements were still evolving, there was no predetermined interface, and several teams brought different ideas about what the product should become.


The team had to define a new product model while designing it—and avoid allowing the constraints of the existing platform to define the future experience too early.

STRATEGIC SHIFT

First determine what the experience should be. Then determine how to build it.


Technical feasibility mattered, but using current platform limitations as the starting point risked reducing a new product vision to incremental improvements of the existing system.


I repeatedly redirected the conversation toward the desired customer experience first, then used that vision to make deliberate decisions about technology, feasibility, and investment.

MY ROLE

Get something tangible in front of people early

When requirements are ambiguous, waiting for certainty often creates more ambiguity.

An imperfect storyboard can generate more useful discussion than another meeting about requirements.


Technical constraints should inform a design—not define it prematurely

Feasibility matters. But if implementation constraints determine the product vision too early, teams risk optimizing the past instead of designing the future. Understanding the ideal experience first makes the tradeoffs intentional.


Staff-level design often means holding a point of view

Collaboration does not mean accepting every piece of feedback. My responsibility was to listen carefully, understand competing perspectives, and then make and defend a design recommendation.


Complexity is as much organizational as technical

Some of the hardest problems weren't on the screen. They involved aligning teams, navigating competing priorities, advocating for UX, and helping people see the problem from the user's perspective.


Speed creates leverage

Rapid iteration allowed me to turn conversations into tangible ideas quickly. That changed the role of design from downstream execution to an active part of product strategy.

KEY DECISIONS

Decision 1 — Design the ideal experience or optimize for the current platform?

I chose to define the desired product behavior first. That created a reference point for evaluating which constraints were unavoidable and which were artifacts of the current system.


Decision 2 — Wait for requirements or make ambiguity tangible?

I started storyboarding before the requirements were fully resolved. The purpose was not to create a perfect answer; it was to create something concrete enough for stakeholders to disagree with and improve.


Decision 3 — Incorporate every request or hold a coherent point of view?

With multiple Product Managers and stakeholders, the project could easily have become design-by-committee. I treated feedback as evidence to interpret rather than instructions to execute, then made and defended a design recommendation.


Decision 4 — Design for a screen or for the way people work?

I explored desktop, mobile, wearable, and natural-workspace contexts to shift the conversation from “What screens should we build?” to “How should this experience fit into the way this person actually works?”

HOW I WORKED

Flexible Teams progressed from an open-ended exploration into a cohesive application concept with organizational support behind it.


The design helped define the emerging product space, challenge premature technical assumptions, align competing stakeholders, accelerate decision-making, and give leadership enough confidence in the product direction to make a strong case for building it.

WHAT CHANGED

Flexible Teams progressed from an open-ended exploration into a cohesive application concept with organizational support behind it.


The design helped define the emerging product space, challenge premature technical assumptions, align competing stakeholders, accelerate decision-making, and give leadership enough confidence in the product direction to make a strong case for building it.

LEARNINGS

Get something tangible in front of people early

When requirements are ambiguous, waiting for certainty often creates more ambiguity.

An imperfect storyboard can generate more useful discussion than another meeting about requirements.


Technical constraints should inform a design—not define it prematurely

Feasibility matters. But if implementation constraints determine the product vision too early, teams risk optimizing the past instead of designing the future. Understanding the ideal experience first makes the tradeoffs intentional.


Staff-level design often means holding a point of view

Collaboration does not mean accepting every piece of feedback. My responsibility was to listen carefully, understand competing perspectives, and then make and defend a design recommendation.


Complexity is as much organizational as technical

Some of the hardest problems weren't on the screen. They involved aligning teams, navigating competing priorities, advocating for UX, and helping people see the problem from the user's perspective.


Speed creates leverage

Rapid iteration allowed me to turn conversations into tangible ideas quickly. That changed the role of design from downstream execution to an active part of product strategy.

CONTRIBUTIONS

Product Design
0→1 Product Design · Complex Workflows · Interaction Design · Cross-Platform Experiences · Visual Design


Product Strategy
Product Vision · Concept Development · Storyboarding · Experience Strategy · Design Advocacy


Prototyping
Rapid Iteration · High-Fidelity Prototyping · Multi-Form-Factor Exploration


Systems Thinking
Enterprise HCM · Cross-Product Workflows · Flexible Organizations · Platform Constraints


Leadership
Influence Without Authority · Stakeholder Alignment · Design Direction · Executive Presentations · Cross-Functional Collaboration · 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