Skip to main content
Steady at the Top
← All articles

How to involve respected skeptics in a company change

Involve respected skeptics by asking them to test implementation assumptions and report evidence, without requiring endorsement. Give them a genuine question, access to the work, and a clear route for findings. Leadership still owns the decision and must explain how criticism affects it.

Psychological safety is a shared team belief that interpersonal risk taking is safe. Edmondson introduced the construct in her 1999 study, Psychological Safety and Learning Behavior in Work Teams. Inviting a critic concerns that risk of speaking up. It differs from asking whether the critic personally trusts you, and does not establish that they support the change itself.

A private moment that makes the issue visible

Composite scenario, not a client case: You replay a skeptical manager’s comments while walking with someone close to you. The manager is difficult to dismiss because colleagues trust their account of the work. You consider inviting them into the project, but only if they will support the launch.

Notice the condition you placed on the invitation during that walk: support for the launch. Remove it before approaching the manager. Write down the particular implementation question you want examined and what you are prepared to change. If the answer is nothing, describe the meeting as an explanation of a decision, rather than consultation.

Use the research within its limits

Levitt and March’s 1988 review describes lessons from experience becoming organizational routines; see Levitt and March (1988): Organizational Learning. Give the skeptical manager a routine to inspect, such as how an exception reaches an approver. Asking whether the launch message sounds convincing examines a different question. The proposed invitation below uses scrutiny of work, without claiming the review validated a skeptic-engagement technique.

For industrial/organizational psychology, the psychology of work and organizations, the relevant issue is how the role permits useful scrutiny. Design this contribution as a test of an implementation assumption. Do not convert the manager into an informal morale monitor or require a psychological assessment of colleagues.

State the decision before discussing personalities

The purpose is better implementation evidence. Participation should not turn a critic into a symbol of approval before their findings are known.

Choose a claim with a consequence leadership controls: whether the training covers late-shift cases, whether a supervisor can approve an exception, or whether the proposed staffing covers practice time. State which part of the rollout could change after the test. Keep the final business decision with its accountable executive instead of outsourcing it to the critic.

Quote the specific objection before describing the manager as resistant. A statement that the training excludes a shift is testable against the materials and schedule. An assertion that the manager dislikes progress is a judgment about motive. Start with the former and ask what example would demonstrate that the implementation concern has been resolved.

Use the skeptic implementation-test invitation

  1. Choose the assumption to test. Name a practical claim the rollout depends on. Ask what would show that the claim fails. Write the assumption as an observable claim about the rollout. Include the conditions under which it should hold and the decision it affects. If leadership has already fixed the launch date, say so. Ask the reviewer to assess the mitigation required, without implying they can reopen a date that is outside this assignment.

  2. Invite relevant scrutiny. Select someone with direct knowledge and peer credibility. Explain the question rather than asking them to become positive. Choose the person for knowledge of the relevant shift or task. Explain privately why that experience matters. Ask whether they can take on the work and how their normal duties will be covered. Do not publish their name as a champion or use their attendance in a launch announcement without their agreement.

  3. Provide access and boundaries. Agree what work they can inspect and who can answer questions. Protect sensitive information and participation capacity. Provide the training examples, operating instructions, and people needed to check the assumption. Separate materials they may inspect from information they may circulate. Agree where a sensitive finding goes. If the reviewer cannot see a required process, record the access gap rather than treating an incomplete review as reassuring evidence.

  4. Hear findings without loyalty tests. Review supporting and contrary examples. Preserve the critic’s ability to disagree with the final choice. Ask for examples that worked as well as exceptions. Have the implementation owner answer each finding in terms of the task it affects. Preserve disagreement about the launch timetable after a training repair. Useful scrutiny does not require the manager to adopt the sponsor’s overall judgment about the project.

  5. Show the decision consequence. Explain what changed, what did not, and why. Assign unresolved implementation issues to owners rather than treating participation as closure. Return a finding-by-finding response: accepted repair, different solution, or an explained decision to proceed with the risk. Give each remaining problem an owner. Ask permission before attributing comments in wider communications. Participation should create an inspectable decision record, rather than a photograph suggesting the critic has joined the campaign.

Do not route an immediate safety concern through an optional rollout workshop. Send it to the responsible safety owner and explain the temporary action to participants. Once that action is recorded, distinguish the urgent incident from the broader implementation questions the skeptical manager was invited to examine.

Put the boundary into words

Offer this draft invitation only if the reviewer’s access and freedom to disagree are real:

I am asking you to test whether this part of the plan can work. You do not need to endorse the decision to participate. Bring evidence and implementation risks. I will explain how we use the findings and where leadership retains the choice.

Ask the manager to identify a useful deliverable and an access requirement you may have missed. Confirm that their ordinary supervisor understands the time allocation. Then state how you will handle a finding that challenges your preferred plan. Answer that question before asking the reviewer to invest credibility in the assignment.

Work through a bounded example

Hypothetical application: A respected supervisor tests a training plan and finds that examples exclude the hardest shift conditions. The project revises the training. The supervisor continues to question the timetable, and leadership records that concern instead of presenting involvement as unanimous support.

In the hypothetical, retain the original training package beside the revision. Have someone from the excluded shift attempt the revised task. If the training improves but the timetable objection remains, report both outcomes. Do not combine them into a claim that the supervisor now supports the launch or that all implementation risks have disappeared.

Choose evidence that can change the decision

Use a short review log organized by assumption, observed exception, proposed repair, and executive response. Request a concrete work example when an objection is broad, but allow the reviewer to explain when confidentiality prevents sharing it widely. Give the operating owner the material they need through an appropriate route. Keep unresolved findings in the launch decision pack. A sponsor who disagrees should explain the tradeoff they accept, rather than editing the objection until it sounds supportive.

Keep an invitation record

Before sending the invitation, put the assignment on one page. Include the specific rollout assumption, the work available for inspection, and the boundary around the final decision. Add the person’s expected contribution and the normal duties that will be covered. Ask them to correct this description before accepting it. This gives both sides a reference if colleagues later treat participation as endorsement.

At the end, compare the invitation with what happened. If the manager was asked to inspect training but spent the meeting defending the launch to peers, the role changed. Discuss whether they want the expanded assignment and what it requires. Correct any announcement that exaggerated their support. Do not solve the discrepancy by asking the manager to keep quiet about it.

Check the failure mode before scaling

Do not recruit a critic to neutralize their voice. Avoid overloading the same trusted employees with unpaid advocacy expectations. Keep ordinary conduct standards separate from agreement with the plan.

Set conduct expectations for the review without banning criticism. Insults and unauthorized disclosure can be addressed separately from disagreement about timing. Consult employment or privacy advisers before using the review as a source of personnel information. Do not make an employee’s future opportunities depend on providing a favorable conclusion.

Review the work, then revise the arrangement

Review whether the invitation produced useful evidence and whether participants could report inconvenient findings. Check that actual communication describes their involvement accurately.

Check what happened to the first finding after the meeting. Did the training owner receive it, did someone make the promised change, and did the reviewer see the revision? Ask about that chain before measuring satisfaction with the invitation. If an access promise failed, repair the access and extend the review rather than marking the question answered.

Leave a separate field for the manager’s remaining view. They may agree that a particular training defect is repaired while still opposing the sequence. Publish the decision owner’s reason for proceeding without describing that difference as a failure of engagement. Allow a later work example to reopen a factual assumption without demanding a renewed declaration of loyalty.

APA’s 2018 entry on role ambiguity describes unclear expectations about a position; APA Dictionary of Psychology: role ambiguity. Use that distinction when specifying this temporary review role. State whether the manager advises, tests, approves, or implements. The invitation should not leave colleagues guessing whether the critic has acquired authority to halt the entire program.

Connect this decision to the next one

Write the purpose of the review into the broader change story. Use employee listening design when participation needs wider coverage. Examine status-loss conversations before assuming all objections concern implementation. For the decision meeting itself, use the dissenting-view process to give a minority account a hearing without transferring the final choice.

Begin with one assumption the skeptical manager is equipped to inspect and one decision you can change in response. Give the resulting finding a named recipient. The invitation earns its place when inconvenient evidence reaches the executive choice, even if the reviewer remains unconvinced by that choice.

Sources

Steady at the Top