Designing for Employees Without Employees: HR’s Blind Spot
“If it hasn’t been tested with real employees, it isn’t ready to launch.”
Why We Prototype at Home but Not at Work
How many of us have renovated a space at home, only to realize a design element didn’t quite work, whether in appearance or function?
Maybe a closet turned out too small. A doorway landed in the wrong place. Or two colors that looked great on the paint chip ended up clashing on the wall.
These things are hard to know for certain until they’re built and in use. That’s why prototypes are so useful: they let us test, adjust, and improve before committing to the final build.
Strangely, most workplaces don’t apply this same discipline. Corporate and HR policies, processes, and technologies are often designed, built, and launched at full scale without ever being tested in real-world conditions or with actual employee input. The result is frustrated employees and managers, wasted investment, and missed business outcomes.
The Cost of Skipping Testing
Think about the last time your organization rolled out a new tool or process. Did it truly work the way employees needed it to? Or did the launch lead to complaints, quick fixes, and rework?
One story from my own experience illustrates the risk. I helped launch a new global performance management system in a company of 70,000 employees. We were proud of the speed, just four months from start to rollout, and the rigor of our documentation: a 125-page master guide, complete with screenshots and step-by-step instructions.
But there was a problem: it had never been tested in the real world.
Employees struggled with usability. Adoption lagged. Leaders quickly realized that what looked good on paper did not translate into a positive experience at scale. The “big launch” came with an equally big set of issues to fix.
Lessons from Enterprises That Prototype
Contrast that with a story from one of our People Experience summits. A GE business unit tested three different performance management processes before choosing one to scale. They experimented with real managers and employees, captured feedback, and observed how the systems worked in practice.
The result was higher adoption, fewer surprises, and much stronger business alignment.
This isn’t just good human-centered design. It’s risk management. Prototyping allows organizations to:
Validate usability before major investment
Identify friction points early and cheaply
Build employee trust by involving them in the design process
Accelerate adoption once the final version launches
Where Prototyping Fits in People Experience
We often think of prototypes as physical, like cardboard mock-ups or wireframes, but in PX, prototypes can take many forms.
When to prototype in People Experience:
New policies (e.g., hybrid work guidelines tested with one function before enterprise rollout)
Digital tools (e.g., piloting intranet updates with a single business unit)
Physical spaces (e.g., testing flexible workspace layouts with one floor before redesigning an entire building)
Employee journeys (e.g., simulating onboarding steps with a small cohort to identify friction points)
Even small-scale usability testing or observation can reveal insights that surveys or planning sessions never uncover.
How to Prototype PX Initiatives
You don’t need a design lab or months of prep to prototype effectively. A simple, structured approach works:
Start small. Choose a team, function, or location as your test group.
Simulate the experience. Mock up the system, process, or policy as realistically as possible.
Observe behavior. Don’t just ask for opinions. Watch how people interact with it.
Capture feedback. Blend qualitative stories (“this step is confusing”) with quantitative measures (time on task, adoption rates).
Iterate quickly. Adjust based on insights before scaling.
This is exactly how product teams operate. And it’s how PX leaders can start treating the experience of work as a product: researched, designed, tested, and improved before “shipping” to the full organization.
The Business Case for Prototyping
Beyond better experiences, prototyping delivers measurable business value:
Reduced rework costs: Fixing a broken policy after rollout is 10x more expensive than adjusting in prototype phase.
Faster adoption: Employees embrace tools they helped shape.
Stronger outcomes: Design decisions are grounded in lived reality, not assumptions.
Lower change fatigue: Fewer painful missteps mean higher trust in future initiatives.
In short: if it’s worth building, it’s worth testing first.
In Summary
Before you launch the next HR system, policy, or process design, pause and ask: how might we prototype this first?
Prototyping isn’t an extra step. It’s the safeguard that ensures your investment delivers impact. By treating PX like a product, you reduce risk, accelerate adoption, and design experiences that truly work for people.
The question is simple:
Are we validating our experience with employees first, or fixing it after rollout?
At Impact PX, we help organizations shift from process-led HR to product-led People Experience. Our team of former global heads of People Experience has successfully built and led PX transformations in complex, enterprise organizations. If you’re exploring this shift or want to assess your current maturity, we can help you take the next step with clarity and confidence.
…about proven ways to integrate PX Prototyping into your HR strategy and operating model.