Skip to main content
Loading...
communication

Win Genuine Buy-In from a Skeptical Colleague

Practice a project-planning conversation with a skeptical colleague who thinks the new intake process will slow the team down. Learn how to acknowledge concerns, answer objections, and land on a concrete next step.

Every employee gets a seat — priced per employee in Performance & Learning, quoted with this template ready.

Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.

Built for: Technology · Operations · Customer support · Professional services · Education

Overview

This roleplay practice scenario helps the learner persuade a skeptical colleague in a project planning meeting. The setup is specific: the learner is proposing a new customer intake process, and Sam is resisting because they believe it will slow the team down and add work for their department.

Use this template when the goal is not to win an argument, but to earn real buy-in from a peer who has legitimate concerns. The learner practices acknowledging the objection, explaining the change in concrete terms, and proposing a realistic compromise such as a pilot, phased rollout, or revised handoff. The persona is direct, cautious, and fair-minded, so the conversation rewards calm reasoning and a specific next step rather than polished sales language.

Do not use this template when the issue is purely informational, when no one is blocking the decision, or when the conversation is about executive approval rather than peer alignment. It is also not the right fit if the learner needs to practice a formal presentation or a one-way update. The value of the template is in the back-and-forth: the learner must listen, respond to pushback, and close with an agreement Sam can actually support.

How to use this template

  1. Read the situation carefully so you understand the proposed intake change, Sam's concern, and the learner objective before starting the roleplay.
  2. Start the conversation with a clear opening line that names the proposal and invites Sam's perspective instead of pushing straight into persuasion.
  3. Talk to Sam in a realistic back-and-forth, acknowledging the concern, answering objections with concrete reasoning, and adjusting your proposal when needed.
  4. Complete the attempt against the scored rubric so you can see whether you earned buy-in, addressed objections, and closed on a specific next step.
  5. Review the feedback, identify where you became defensive or vague, and retry with a tighter compromise, clearer ask, or more specific pilot plan.

Best practices

  • Name Sam's concern before you explain your idea, or the persona will feel talked over.
  • Use concrete process language such as intake volume, handoff steps, ownership, and timing instead of abstract claims about efficiency.
  • Offer a small pilot or phased rollout when Sam pushes back on workload or risk.
  • Ask one clarifying question before defending the proposal so you can respond to the real objection, not the one you assumed.
  • Close with a specific ask, such as testing the process for one week or agreeing on a revised next step.
  • Keep your tone calm and collaborative even when Sam is skeptical, because defensiveness usually makes the persona harder.
  • If Sam raises a valid operational concern, acknowledge the tradeoff and show how the proposal protects their team's time.

What this template typically catches

Issues teams running this template most often surface in practice:

Jumps into selling the new process before acknowledging Sam's concern.
Responds defensively when Sam questions the workload impact.
Uses vague benefits like 'better alignment' without explaining what changes in practice.
Ignores the effect of the proposal on Sam's department and only talks about the learner's team.
Fails to offer a compromise, pilot, or phased next step when resistance appears.
Ends the conversation without a concrete agreement or specific ask.
Over-explains the proposal and loses sight of the main objection.

Common use cases

Project manager aligning a cross-functional peer
A project manager needs a colleague in another department to support a new intake workflow before rollout. The conversation focuses on workload concerns, ownership, and a practical pilot that both sides can accept.
Operations lead proposing a new request triage step
An operations lead is introducing a new intake step to reduce missed requests, but a peer worries it will create extra admin work. The learner must explain the tradeoff clearly and land on a trial that protects the team's time.
Customer support supervisor seeking team agreement
A support supervisor wants to change how incoming customer issues are routed, and a skeptical teammate believes the change will slow response times. The learner practices acknowledging the concern and proposing a limited rollout.
Product or service team planning a process change
A team is revising how requests enter the queue, and one colleague is blocking the direction because they expect more rework. The learner has to turn resistance into a workable next step without escalating the conflict.

Frequently asked questions

What kind of conversation is this template for?

This template is for a project-planning or team-alignment conversation where one colleague is blocking a proposed change. The specific scenario centers on a new customer intake process and a skeptical teammate named Sam. It is best used when you need genuine buy-in, not just polite agreement.

Who should use this roleplay?

It works well for individual contributors, project leads, managers, and cross-functional partners who need to persuade a peer. The learner is expected to explain a change clearly, respond to pushback, and close on a shared next step. It is especially useful for people who struggle to stay calm when a colleague is resistant.

How often should someone practice this scenario?

Use it before a real planning meeting, after a difficult stakeholder conversation, or as part of recurring communication practice. One attempt can surface the main objection, but a second or third attempt is often where the learner improves tone, clarity, and compromise. Repeating the scenario helps build the habit of acknowledging concerns before problem-solving.

What makes this different from an ad hoc discussion guide?

This is a scored roleplay with a defined situation, persona, learner objective, and rubric criteria. That structure gives the learner immediate feedback on whether they actually earned buy-in, rather than just sounding persuasive. It also makes the practice repeatable across different teams and managers.

Can this be customized for other departments or projects?

Yes. You can swap in a different process change, team function, or objection while keeping the same communication skill focus. For example, you could adapt it for operations, sales handoffs, support workflows, or approval steps. The persona can also be tuned to be more cautious, more analytical, or more time-pressed.

What should the learner do if the colleague keeps saying no?

The goal is not to force agreement in one turn. If the persona remains resistant, the learner should slow down, restate the concern accurately, and propose a smaller pilot or trial step. A good attempt ends with a concrete next move, even if full commitment is not yet available.

What are the most common mistakes this template surfaces?

Learners often jump straight to selling the idea, defend the proposal too hard, or ignore the practical impact on the colleague's work. Another common miss is failing to ask for a specific commitment at the end. The rubric is designed to reward acknowledgment, clarity, compromise, and a clear ask.

How does this fit into a communication training program?

It fits well alongside feedback conversations, stakeholder alignment, and conflict navigation practice. The scenario builds skills that overlap with Radical Candor and SBI-style communication because the learner must be direct without becoming combative. It also reinforces the deliberate-practice pattern of realistic reps with immediate, specific feedback.

Go deeper on the topic

Related concepts
  • Asynchronous communication is any exchange where the sender and receiver are not in the same moment — written messages, recorded video, shared docs, threaded...
  • Collaboration is the coordinated work of two or more people toward a shared outcome — arguing, deciding, producing, and shipping. It is not the same as...
  • Communication is the movement of information from one person or group to another — announcements, updates, instructions, questions, acknowledgements....
  • Interpersonal communication is the exchange of information between two people or a small group — distinct from broadcast communication (one-to-many) and from...

Ready to use this template?

Every employee gets a seat. Request pricing for Performance & Learning and we quote into a workspace with Win Genuine Buy-In from a Skeptical Colleague ready.

Request pricing

Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.