Skip to main content

Engage Employees in Design to Build Buy-In and Surface Adoption Risks

Engage impacted employees early in design to shape solutions, surface barriers, and build adoption. Use clear boundaries, safe facilitation, real-work walkthroughs, and visible follow-up so feedback leads to decisions, actions, and stronger commitment.

Introduction: why this action matters for adoption

Engaging employees during design is a change-management intervention in the category of stakeholder engagement and commitment. Its purpose is not simply to “communicate early” or run a workshop. It gives the people who must adopt the change a structured way to shape the solution, identify barriers, raise concerns, and agree on practical next steps. Employee voice is most useful when people can express views, concerns, and suggestions that influence decisions at work [CIPD, 2026]. (cipd.org)

This matters because adoption is different from installation. A system, process, policy, or operating model may be launched, but value is realized only when people commit to and use the new way of working [PMI, 2015]. (pmi.org)

What this action is and when to use it

This action actively involves impacted employees in design conversations before all decisions are finalized. It may include listening sessions, workflow walkthroughs, prototype reviews, issue-resolution meetings, manager alignment sessions, or representative employee forums. Human-centered design principles support involving users throughout design and development, grounding design in users, tasks, and environments, and evaluating early [NIST, 2026]. (nist.gov)

Use this action when the change affects day-to-day work, roles, handoffs, tools, decision rights, customer experience, workload, compliance routines, or identity. It is especially valuable in discovery, solution design, pilot, and pre-go-live phases. After go-live, the same approach becomes adoption support: issue triage, refinement, and reinforcement. Do not use it as “fake participation” after decisions are closed; research on participatory change shows that controlled or symbolic participation can create frustration and resistance [Sahay & Goldthwaite, 2024]. (doi.org)

Preparation: inputs, stakeholders, materials, timing, and decisions needed

Before inviting employees, clarify the design questions. For example: “Which workflow steps create risk?”, “What support will managers need?”, or “Which policy options are workable in frontline conditions?” Separate fixed constraints from open design choices. This prevents a common failure: asking for input on matters the team cannot change.

Map the impacted groups, including high-volume users, edge-case users, supervisors, informal influencers, skeptics, and underrepresented groups. CIPD notes that voice can be direct or representative, formal or informal, and that a single channel is rarely sufficient [CIPD, 2026]. (cipd.org)

Prepare a simple impact summary, draft design, journey map or prototype, assumptions list, decision log, and concern tracker. Build psychological safety into the session design: Edmondson’s research defines team psychological safety as a shared belief that the team is safe for interpersonal risk-taking, which supports speaking up and learning behavior [Edmondson, 1999]. (web.mit.edu)

Step-by-step facilitation guide

  1. Open with purpose and boundaries. Explain why input is being gathered, what decisions are open, what is fixed, how feedback will be used, and when participants will hear back. This protects trust and reduces the risk of symbolic participation [Sahay & Goldthwaite, 2024]. (doi.org)

  2. Create safety and balance power. Ask leaders to listen before responding. Use small groups, anonymous pre-work, or neutral facilitation for high-resistance groups. Psychological safety is influenced by leader coaching, support, and non-defensive responses to challenge [Edmondson, 1999]. (web.mit.edu)

  3. Start with real work, not abstract opinions. Have employees walk through current tasks, exceptions, workarounds, customer impacts, and pain points. This aligns with human-centered design’s emphasis on understanding users, tasks, and environments [NIST, 2026]. (nist.gov)

  4. Test the proposed design. Present the future-state process, tool, policy, or role change. Ask: “Where will this fail?”, “What will slow adoption?”, “What would make this easier to use?”, and “What must managers reinforce?”

  5. Convert concerns into design decisions or adoption actions. Sort input into changes to the design, training needs, communication needs, manager actions, policy clarifications, and unresolved risks. Employee involvement is more effective when it connects to planning, implementation, and problem-solving, not just listening [Prosci, 2025]. (prosci.com)

  6. Agree on owners and follow-up. Assign each issue an owner, due date, decision path, and response message. Stakeholder engagement should inform realistic change plans and actions from the start of the project [PMI, 2015]. (pmi.org)

  7. Close the loop visibly. Share what changed, what did not change, and why. CIPD emphasizes that genuine two-way communication requires managers to listen and act on feedback [CIPD, 2026]. (cipd.org)

Example: how this could be applied in a real change initiative

A company is implementing a new scheduling and time-entry system for store employees. Instead of announcing the design after configuration, the change lead runs three 75-minute design input sessions: store associates, shift supervisors, and payroll administrators. Employees identify that the proposed approval flow breaks down during shift swaps and creates extra manager work on weekends. The project team changes the workflow, adds mobile approval guidance, and creates a manager exception script. When the pilot begins, the change team tracks fewer payroll errors, faster approvals, and higher manager confidence. This is employee engagement as adoption risk reduction, not just communication.

Roles and responsibilities

The sponsor defines the purpose, decision rights, and non-negotiables, and removes barriers. PMI describes sponsors as accountable for enabling project success [PMI, 2015]. (pmi.org)

The change manager designs the engagement approach, facilitates sessions, protects psychological safety, synthesizes input, and manages the feedback loop. The project or product lead evaluates design implications and confirms what can change. People managers help employees understand local impacts and surface concerns; CIPD highlights the role of senior leaders and line managers in encouraging voice [CIPD, 2026]. (cipd.org)

Impacted employees contribute real workflow knowledge, identify risks, test assumptions, and help validate adoption support.

Common mistakes to avoid

The first mistake is asking for input when there is no real room for influence. If the decision is already made, be transparent and ask about implementation risks instead. The second is inviting only supporters. McKinsey distinguishes real ownership from merely attending meetings or making suggestions; broader ownership is associated with stronger transformation outcomes [McKinsey, 2021]. (mckinsey.com)

Another mistake is letting senior voices dominate. Use small groups, anonymous channels, or representative forums to hear from quieter employees. Finally, avoid collecting concerns without follow-up. Silence often increases when employees believe speaking up will not make a difference [CIPD, 2026]. (cipd.org)

Measures of success or adoption indicators

Measure whether engagement is changing the design and reducing adoption risk. Useful indicators include participation coverage across impacted groups, number of design assumptions tested, number of employee-raised issues resolved, cycle time from concern to decision, sentiment about “my concerns were heard,” manager confidence, pilot adoption, usage data, error rates, help-desk tickets, training confidence, and post-go-live workarounds. For transformations, ownership matters: McKinsey found that companies with at least 7% of employees owning transformation initiatives were twice as likely to outperform benchmark TRS, although this is correlational [McKinsey, 2021]. (mckinsey.com)

Checklist for the change manager

  • Define which design decisions are open, fixed, or constrained.

  • Identify impacted groups, managers, skeptics, and underrepresented voices.

  • Prepare an impact summary, prototype, process map, or decision draft.

  • Select the right format: workshop, interview, forum, pulse survey, or pilot review.

  • Set psychological safety norms and use neutral facilitation where needed.

  • Ask about real work, exceptions, barriers, and adoption support.

  • Capture input in a visible concern and decision log.

  • Assign owners and due dates for follow-up actions.

  • Communicate “you said, we did, we could not do” outcomes.

  • Track whether resolved concerns improve readiness and adoption.

Optional reusable session agenda

Employee design input session, 75 minutes

Purpose: Gather input on the proposed change design, identify adoption barriers, and agree on follow-up actions.

Opening script: “Today is not a general update. We are asking for your practical input on how this design will work in real conditions. Some items are fixed; others are open to influence. We will document every concern and report back on what changes, what does not, and why.”

Agenda: Begin with five minutes on purpose and decision boundaries. Spend 15 minutes mapping current pain points, 20 minutes reviewing the proposed design, 20 minutes identifying risks and improvements, 10 minutes prioritizing actions, and five minutes confirming next steps and follow-up timing.

References

Prosci. “The Link Between Change Management and Employee Engagement.” Published 3 Jul 2025; updated 30 Oct 2025. https://www.prosci.com/blog/change-management-employee-engagement

Project Management Institute. “Engaging Stakeholders for Project Success.” 1 Jan 2015. https://www.pmi.org/learning/library/engaging-stakeholders-project-success-11199

National Institute of Standards and Technology. “Human Centered Design.” Created 12 Apr 2021; updated 27 May 2026. https://www.nist.gov/itl/iad/human-centered-technologies/human-factors-human-centered-design

Edmondson, Amy. “Psychological Safety and Learning Behavior in Work Teams.” Administrative Science Quarterly, Vol. 44, No. 2, Jun 1999. https://web.mit.edu/curhan/www/docs/Articles/15341_Readings/Group_Performance/Edmondson%20Psychological%20safety.pdf

Sahay, Surabhi, and Christine Goldthwaite. “Participatory Practices During Organizational Change: Rethinking Participation and Resistance.” Management Communication Quarterly. First published online 11 Jul 2023; issue published May 2024. https://journals.sagepub.com/doi/10.1177/08933189231187883

McKinsey & Company. “How many people are really needed in a transformation?” 23 Sep 2021. https://www.mckinsey.com/capabilities/transformation/our-insights/how-many-people-are-really-needed-in-a-transformation

Did this answer your question?