Roleplay Scenario
Scenario Overview
Your team needs to decide whether to tackle technical debt or focus on new features for an upcoming release. Some team members are pushing to address tech debt to maintain system stability, while others emphasize delivering features to meet business targets.
The goal is to reach a consensus that considers both immediate needs and long-term technical health.
Roles & Setup
Role A – Technical Lead (You)
Guide the team toward a decision, ensuring everyone's voice is heard.
Your goal: Facilitate discussion, weigh pros and cons, and help the team reach consensus.
Role B – Senior Engineer
Advocate for addressing tech debt, focusing on long-term stability.
Your goal: Persuade the team to prioritize tech debt without derailing immediate business goals.
Role C – Product Manager
Focus on timely feature delivery to meet business objectives.
Your goal: Make a case for feature delivery while being open to addressing tech debt.
Role D – Junior Engineer (Optional)
Observe team dynamics and contribute your insights.
Your goal: Offer fresh perspectives and learn from the discussion.
Suggested Openers
Technical Lead:
- “Let’s talk about how to balance our tech debt with our feature goals. What’s everyone thinking?”
- “I’d love to get your thoughts on handling tech debt without jeopardizing our delivery schedule.”
Senior Engineer:
- “If we don’t tackle some of this tech debt soon, it could really slow us down later.”
- “Can we focus on the most pressing tech debt and see what fits alongside our current work?”
Product Manager:
- “I get the tech debt concerns, but we have important features to deliver this quarter.”
- “Let's see if there are any tech debt items we can handle quickly without delaying our timeline.”
Junior Engineer:
- “How have we handled tech debt versus features in the past? What worked well?”
- “I see both sides. Could we integrate some small tech debt tasks into our current sprint?”
Sample Roleplay in Action
Technical Lead:
“Thanks for joining, everyone. We need to figure out how to balance tech debt with our feature commitments. Let’s start by identifying the biggest tech debt concerns and how they might affect our timelines.”
Senior Engineer:
“We have some outdated dependencies that are a pain. If we don’t fix them, they’ll slow us down more in the future.”
Product Manager:
“I hear you. But we’re under pressure to get these new features out. Can we focus on tech debt items that align with what we’re working on now?”
Junior Engineer:
“Maybe we can address some tech debt if we spot tasks that overlap with our feature work. Could we split our focus?”
Technical Lead:
“That’s a solid suggestion. Let’s prioritize tech debt items that fit with our current plan and push others to the next cycle. Does that work for everyone?”
Senior Engineer:
“I’m okay with that. Tackling some big tech debt now will help us keep moving at a good pace.”
Product Manager:
“Agreed. I’ll adjust our backlog so we tackle critical tech debt without affecting feature delivery.”
Junior Engineer:
“I’ll help review tasks to see where we can fit in tech debt fixes.”
Technical Lead:
“Great. Let’s regroup soon to review progress and adjust if needed. Appreciate the teamwork!”
Post-Scenario Tools
Curveball Mode (Optional)
Throw in one of these mid-roleplay to keep it interesting:
- A last-minute business request increases pressure on feature delivery.
- New info shows tech debt is causing frequent small production issues.
- A team member strongly opposes the consensus and needs reassurance.
Reflection Checklist
As the Technical Lead:
- Did you facilitate an inclusive discussion?
- Did you ensure all perspectives were considered?
- Did you guide the team toward a balanced decision?
As the Senior Engineer:
- Did you communicate the long-term risks clearly?
- Did you stay open to compromise?
As the Product Manager:
- Did you articulate business priorities effectively?
- Did you remain flexible in finding solutions?
As the Junior Engineer:
- Did you contribute constructively?
- Did you learn from the discussion dynamics?
Common Mistakes to Avoid
- Ignoring the long-term impact of tech debt
- Prioritizing short-term gains over sustainable development
- Allowing the discussion to become polarized
Pro Tip
Balancing tech debt and feature work requires strategic prioritization and team alignment. Use this roleplay to practice finding a middle ground that supports both immediate and future objectives.