Roleplay Scenario
Scenario Overview
You're in the middle of a project when leadership shifts priorities, asking your team to pivot to a new strategic initiative. The new direction is critical for meeting upcoming business objectives, but it's important to maintain team morale and avoid burnout. You'll need to communicate the change, manage expectations, and keep the team aligned.
Roles & Setup
Role A – Team Lead (You)
You’ve just received new directives from leadership and need to communicate this to your team.
Your goal: Clearly convey the change, address concerns, and keep the team motivated.
Role B – Software Engineer
You're focused on the current project and concerned about changing directions.
Your goal: Understand the rationale, voice any concerns, and find out how this affects your workload.
Role C – Project Manager (Optional)
You’re responsible for project timelines and deliverables.
Your goal: Help adjust plans, manage expectations, and ensure alignment with stakeholders.
Suggested Openers
Team Lead:
- “Hey team, leadership has asked us to shift focus to a new priority. Let’s talk about how we can incorporate this into our schedule effectively.”
- “I know changing gears can be challenging, but we’ve got an important new focus. Let’s figure out the best way to handle this transition.”
Software Engineer:
- “Can you share more about why this new priority is coming up now? I’d like to understand the overall strategy.”
- “I’m worried about how this will affect our current work. Can we discuss what this means for our workload?”
Project Manager:
- “Let’s outline what needs to change in our timelines to accommodate this new priority.”
- “I’ll reach out to stakeholders to ensure everyone is aware of the changes.”
Sample Roleplay in Action
Team Lead:
“Thanks for joining, everyone. Leadership has identified [New Initiative] as a top priority due to recent market developments. They believe this will give us a competitive edge.”
Software Engineer:
“Why the sudden shift? I thought our current project was critical.”
Team Lead:
“Good question. The new initiative aligns with some urgent market opportunities that have come up. It’s a shift, but leadership sees it as key to our success this quarter.”
Project Manager:
“Alright, let’s look at our current tasks and see which ones can be paused. I’ll draft a new timeline and communicate any changes to stakeholders.”
Software Engineer:
“I’m concerned about balancing both projects. Are there specific tasks we can deprioritize?”
Team Lead:
“Yes, we’ll focus on critical tasks for the new initiative first. Let’s meet later to go through the current workload and make the necessary adjustments.”
Project Manager:
“I’ll update our stakeholders to keep everyone in the loop. Let’s aim to make this transition as smooth as possible.”
Team Lead:
“Great. Let’s keep the lines of communication open and support each other through this change. I’m confident we can manage this effectively.”
Post-Scenario Tools
Curveball Mode (Optional)
Introduce these scenarios mid-roleplay to test adaptability:
- Leadership adds yet another priority shift.
- The team expresses concerns about potential burnout.
- Stakeholders demand updates on current projects that are put on hold.
Reflection Checklist
As the Team Lead:
- Did you communicate the change clearly and empathetically?
- Did you address team concerns and provide rationale?
- Did you outline clear next steps and support the team?
As a Participant:
- Did you express concerns constructively?
- Did you seek clarity on the new priorities?
- Did you contribute to finding solutions?
Common Mistakes to Avoid
- Failing to explain the rationale behind the shift
- Overloading the team with unrealistic expectations
- Neglecting to adjust timelines or communicate changes
Pro Tip
During times of shifting priorities, maintaining transparency and fostering an environment of collaboration is key. Engage the team in problem-solving to strengthen resilience and trust.