Vanessa Sequeira, who goes by Ness, is an innovation strategist and business psychologist who heads People Design at Miro. Her team of agile coaches and learning experience designers co-design Miro’s culture with employees and open-source the solutions so other companies can build healthy cultures the same way. Her background sits at the intersection of agile business strategy, design, and systems thinking, with a particular interest in solutions for the circular economy.
This Reimagining Company Culture conversation explored what changes when a People team adopts the same posture a product team uses: customer needs first, multidisciplinary thinking, technology as a multiplier. Ness made a strong case that HR will be more useful to the business when it stops treating its work as policy and starts treating it as design.
The synthesis below pulls in research and field practice that backs the design-led approach to People work.
Why People Design Outperforms Traditional HR Process Maps
Traditional HR thinks in policy. Design thinks in user experience. The shift is not cosmetic. A policy assumes everyone in scope behaves the same way; a design starts from the actual user and works backward. The result is a People function that ships smaller, more usable interventions and learns faster.
McKinsey research on high-performing cultures found that 70 percent of transformations fail and 70 percent of those failures are culture-related. A meaningful chunk of that failure rate comes from policies designed for the average employee that fit none of them. Design-led People teams cut that risk by prototyping with real users before rolling out at scale.
The discipline is borrowed from product, but the materials are different. People designers iterate on rituals, onboarding flows, manager toolkits, and feedback systems. The cycle time is faster than most HR teams expect once they get used to working in increments.
What Design Thinking Looks Like Inside HR
How does design thinking apply to People programs?
Start with the employee, not the policy. Map the journey, find the friction, prototype small fixes, ship them, measure, iterate. The same loop product teams run on customer experience works on employee experience. Pair it with strong people analytics practices and the team learns from each iteration instead of guessing.
What does an MVP look like for an HR program?
An MVP for HR is the smallest version of a program that delivers real value to a real user. A new manager toolkit might launch as a five-page Notion doc plus a 30-minute peer coaching session, not a 12-module learning path. Ship the small version, learn what works, expand based on signal.
What Actually Works in People Design
Co-design with employees, not for them
The fastest way to make HR programs useful is to involve the people who will use them. Co-design sessions, employee research, and pilot groups produce programs that actually get adopted. Programs designed in isolation get launched and then ignored.
Treat managers as your highest-priority user
Employee engagement levels track tightly with manager quality. managers account for 70 percent of the variance in employee engagement, which means manager-facing programs deliver outsized returns. People designers who prioritize the manager experience above almost everything else get faster culture results than teams that aim broader.
Open-source what works
Sharing what works inside and outside the company is a Miro hallmark. Internally, it accelerates adoption across teams. Externally, it builds the employer brand and pressures the team to keep iterating because the work is visible. Companies that treat People work as proprietary IP move slower than they need to.
Where Employee Relations Fits in People Design
ER is one of the most under-designed parts of HR in most companies. The intake form is clunky, the workflow is opaque, and the employee on the receiving end has almost no visibility into what is happening with their case. Bringing design thinking to ER changes that posture entirely. Employee relations programs built around the employee experience look measurably different from the boilerplate version most companies inherit.
How design changes ER outcomes
The biggest design wins in ER come from intake, communication, and case routing. AI-powered employee relations workflows reduce intake friction, route cases to the right specialist faster, and keep employees informed without burning HRBP time. The user experience improvement compounds into better data and better outcomes.
Frequently Asked Questions About People Design
What is people design?
People design applies design thinking, systems thinking, and agile methods to People function work. Instead of writing policies and rolling them out, designers prototype interventions with real users, ship the smallest viable version, and iterate based on signal.
How is people design different from organizational design?
Organizational design focuses on structure (reporting lines, roles, levels). People design focuses on experience (rituals, programs, manager interactions). Both matter, and the best teams treat them as connected disciplines.
What skills does a people designer need?
Research methods, prototyping, facilitation, systems thinking, and basic data analysis. The unusual combination is what makes the role hard to hire for, but the impact compounds quickly once the team has the right people.
How do you measure the impact of design-led HR?
Adoption rates, employee NPS by program, time to resolution on cases, and qualitative signal from interviews. Design-led teams report on outcomes faster because they ship smaller and instrument their work from the start.
Can small companies practice people design?
Yes, and small companies often do it better. Smaller scope means tighter feedback loops. The hard part is convincing leadership that design takes time upfront and pays back in adoption later, instead of shipping a polished policy that no one uses.
One question that comes up often: how do you balance design rigor with the speed the business expects? The answer is to keep the prototype phase short and visible. A two-week design sprint that ends in a working prototype produces faster business signal than a three-month policy review that ends in a document no one reads. Stakeholders trust the team when they can see incremental progress. Skip the visibility step and the function gets pulled back into reactive work.
The other underrated discipline is retiring programs that do not deliver. Most People functions accumulate programs faster than they remove them, which leads to bloat and confusion for managers. Annual program audits with a real willingness to sunset underperformers free up capacity for the work that compounds. The teams that take this step are usually the same teams shipping new programs faster, because they have the bandwidth to design properly instead of patching what already exists.
The Bottom Line for HR Leaders
People design is not a rebrand of HR. It is a different posture: customer-centric, prototype-first, evidence-driven. Ness’s work at Miro shows what happens when a People team operates with the same discipline a product team would. Programs ship faster, adoption is higher, and the function earns more credibility with the rest of the business.
For HR leaders considering the shift, the practical move is to start with one program. Pick the highest-friction touchpoint (often onboarding, manager training, or ER intake), apply design methods to it, and measure the change. People team efficiency improvements compound from there, especially when the team gets disciplined about retiring programs that do not deliver.
See how AllVoices helps People teams turn workplace signals into action.
.avif)
.avif)
