Roleplay Scenario
Scenario Overview
Two teams are working on a project with overlapping features, leading to confusion about ownership. You need to clarify responsibilities without disrupting workflow or team dynamics. The goal is to ensure everyone knows their role, maintain positive collaboration, and align on shared objectives.
Roles & Setup
Role A – Team Lead (You)
You’re leading one of the teams involved.
Your goal: Clarify roles and responsibilities constructively.
Role B – Counterpart Team Lead
You’re leading the other team. You value collaboration but want to maintain influence over critical parts of the project.
Your goal: Ensure a fair distribution of responsibilities.
Role C – Project Manager (Optional)
You oversee the project timeline and need both teams to work together efficiently.
Your goal: Facilitate alignment and maintain progress.
Suggested Openers
Team Lead:
- “Hey, can we touch base on the integration feature? I’ve noticed some overlap and want to ensure we’re aligned on our roles.”
- “Let's discuss how we can best divide the responsibilities for the new feature to avoid duplication.”
Counterpart Team Lead:
- “Sure, I’ve been meaning to align on this as well. Let’s make sure our efforts complement each other.”
- “Absolutely, I’m open to discussing how we can coordinate effectively.”
Project Manager:
- “I’m glad you’re both addressing this. Let’s outline responsibilities to keep the project on track.”
- “Thanks for bringing this up. Clarifying roles will help us avoid delays.”
Sample Roleplay in Action
Team Lead:
“I wanted to chat about the integration feature. It seems like both our teams are working on similar tasks, and I think we can benefit from clearer ownership. What’s your team focusing on?”
Counterpart Team Lead:
“Thanks for bringing this up. We’ve been handling the backend logic because it ties into our existing systems. What aspect is your team handling currently?”
Team Lead:
“We’re working on the API endpoints and data exchange. How about we continue with this focus while your team takes the lead on the UI components?”
Counterpart Team Lead:
“That division makes sense to me. We can set up weekly syncs to ensure everything aligns and address any issues early.”
Project Manager:
“Great collaboration! I’ll update the project plan with these roles. Let me know if any changes arise that impact the timeline.”
Team Lead:
“Agreed. I’ll draft a shared document to track our progress and dependencies. Let’s keep communication open.”
Counterpart Team Lead:
“Sounds good. I’ll inform my team about this new structure and ensure they’re clear on their responsibilities.”
Post-Scenario Tools
Curveball Mode (Optional)
Throw in one of these mid-roleplay to make it more interesting:
- A stakeholder requests additional features impacting both teams
- One team lead is hesitant to adjust roles due to previous commitments
- A misunderstanding about an earlier agreement surfaces
Reflection Checklist
As the Team Lead:
- Did you approach the conversation constructively and collaboratively?
- Did you encourage open communication without dictating outcomes?
- Did you propose a balanced solution?
As the Counterpart Team Lead:
- Did you remain open to adjustments and express your team’s needs clearly?
- Did you contribute to finding a balanced resolution?
As the Project Manager (if applicable):
- Did you facilitate alignment without taking sides?
- Did you ensure the conversation moved towards actionable outcomes?
Common Mistakes to Avoid
- Allowing the discussion to become adversarial or one-sided
- Neglecting to follow up on agreed actions and updates
- Ignoring potential scope changes or dependencies
Pro Tip
Frame the conversation around mutual goals and benefits. By focusing on how both teams can succeed together, you’ll foster a cooperative environment that enhances project outcomes.