Roleplay Scenario
Scenario Overview
You're knee-deep in a project that needs a new data processing feature for [Specific Product]. Your manager picked [Current Technology], but you’re worried it might not cut it once we hit higher data volumes. You need to talk this over, suggest [Alternative Technology], and keep the chat positive and productive. The aim is to find a path that’s technically sound and works with our project goals.
Roles & Setup
Role A – Engineer (You)
You think there’s a smarter technical path than the one your manager picked.
Your goal: Share your concerns clearly, suggest a different route, and find a solution together.
Role B – Manager
You chose a technical direction based on your experience and project needs. You’re open to feedback but confident in your decision.
Your goal: Listen to your engineer’s point of view and make sure the choice supports the project.
Suggested Openers
Engineer:
- “Hey, can we chat about our approach for the data processing feature? I’ve got some thoughts on potential issues and maybe a better way to go.”
- “I’ve been thinking about our plan, and I wonder if there’s a more efficient way to handle the expected data surge.”
Manager:
- “Sure, I’m all ears. What’s on your mind?”
- “I’d love to hear your thoughts. Let’s see if we can make this work better.”
Sample Roleplay in Action
Engineer:
“Hey, I’ve been thinking about the tech stack we’re using for the new data processing feature. I’m concerned that [Current Technology] might struggle as our user base grows.”
Manager:
“Okay, what are you seeing as the potential issues?”
Engineer:
“I’m worried about how it’ll perform under heavy data loads. I’ve been looking into [Alternative Technology], which could handle large data sets more efficiently.”
Manager:
“Interesting. Can you explain how this alternative compares in terms of implementation time and resources?”
Engineer:
“Sure thing. [Alternative Technology] is known for scaling well with large data sets. There’s a bit of a learning curve, but I think the long-term benefits, like better performance, make it worthwhile. I suggest we do a quick trial to see if it fits.”
Manager:
“That makes sense. I picked [Current Technology] because [Reason], but I’m open to your suggestion. How do you think this will impact our timeline?”
Engineer:
“The trial might stretch our timeline a bit, but I believe it’s worth it for the future benefits. How about we set a timebox for this and then review the results together?”
Manager:
“Sounds good. I appreciate you bringing this up. Let’s run the trial and see what we learn.”
Engineer:
“Great, I’ll put together a plan for the trial and keep you posted.”
Manager:
“Thanks for taking the initiative. Let’s aim for a decision that supports both our current goals and future scalability.”
Post-Scenario Tools
Curveball Mode (Optional)
Introduce one of these mid-roleplay to add complexity:
- Manager initially resists any changes.
- A new requirement pops up that affects the decision.
- Time constraints get tighter, adding pressure to the decision.
Reflection Checklist
As the Engineer:
- Did you share your points clearly and constructively?
- Did you focus on facts and potential impacts rather than personal preferences?
- Did you propose feasible alternatives?
As the Manager:
- Did you listen openly without dismissing the feedback?
- Did you provide clear reasoning for your initial choice?
- Did you facilitate a path to explore the alternative?
Common Mistakes to Avoid
- Turning the discussion into a debate instead of a collaborative talk.
- Focusing too much on personal preferences without objective reasoning.
- Dismissing feedback without consideration.
Pro Tip
Approach these conversations with a focus on learning and collaboration. Keeping the project’s success in mind can help steer the discussion away from personal biases and toward productive outcomes.