Coaching Peers Through Architectural Ambiguity

technical-leadershipSenior10–15 min
How to Use This: Run this roleplay with 2–3 people, or try it solo by embodying each role. Introduce curveballs to challenge adaptability. Reflect afterward to assess effectiveness and areas for improvement.

Roleplay Scenario

Scenario Overview

Your team is starting a new project, and the architectural path isn't clear yet. There are a few viable options, each with different benefits and drawbacks. As the senior engineer, your role is to guide the team in evaluating these options, encouraging input from everyone, and helping the team decide the best way forward.

Roles & Setup

Role A – Senior Engineer (You)
You’re the technical lead guiding the architectural discussion.
Your goal: Facilitate an open dialogue, clarify trade-offs, and help the team reach a consensus.

Role B – Mid-Level Engineer
You have some ideas but are unsure which direction to take.
Your goal: Share your thoughts, ask questions, and seek clarity.

Role C – Junior Engineer (Optional)
You’re eager to learn and contribute but feel a bit out of your depth.
Your goal: Understand the reasoning behind decisions and offer fresh ideas.

Suggested Openers

Senior Engineer:

  • “Thanks for coming together. We're deciding on the architecture for [Project], and I'd like to hear what you all think about the options.”
  • “Let’s go through the potential approaches, discuss their pros and cons, and see if we can align on a direction.”

Mid-Level Engineer:

  • “I’ve been thinking about option A, but I’m worried about how it scales. What do you think?”
  • “I’m not sure how option B fits with our current setup. Can we talk about that?”

Junior Engineer:

  • “I’m curious about how these options affect maintenance in the long run. Can we go over that?”
  • “I have some questions about option C’s implementation. Is this a good time to ask?”

Sample Roleplay in Action

Senior Engineer:
“Hey team, thanks for joining. We’ve got some decisions to make on the architecture for [Project]. Let’s talk about each option and figure out what makes the most sense.”

Mid-Level Engineer:
“I’m leaning towards option A because it’s straightforward, but I’m worried about how it handles scaling. What’s your take?”

Senior Engineer:
“Good point. Option A is simpler and could get us started quickly, but scaling might be an issue. Let’s also consider option B, which handles scaling better but is more complex. How do you feel about that?”

Junior Engineer:
“I’m not too familiar with option B, but it sounds like it might need more upkeep. Can we discuss what that would involve?”

Senior Engineer:
“Absolutely. Option B will take more setup and ongoing maintenance, but it might save us work as we grow. Let’s weigh these against our long-term goals. What do you all think?”

Mid-Level Engineer:
“Given that, option B seems like it might be worth the upfront effort. Should we outline some key areas to focus on if we choose it?”

Senior Engineer:
“Definitely. Let’s draft a roadmap to guide us, highlighting important milestones and potential challenges. By the end of this session, I’d like us to have a clear next step.”

Junior Engineer:
“I’d love to help with the roadmap. It’s a great way for me to learn more.”

Senior Engineer:
“Perfect. Let’s work on this together. I appreciate everyone’s input—it’s crucial for making a well-informed decision.”

Post-Scenario Tools

Curveball Mode (Optional)

Introduce one of these challenges to see how participants manage unexpected turns:

  • A new requirement comes in that could affect one of the options
  • A team member disagrees strongly with the chosen direction
  • Time constraints pressure a quick decision

Reflection Checklist

As the Senior Engineer:

  • Did you create an inclusive environment for sharing ideas?
  • Did you facilitate a balanced discussion on each option?
  • Did you help the team reach a consensus without dictating?

As a Participant:

  • Did you contribute your thoughts constructively?
  • Did you ask questions to deepen your understanding?
  • Did you stay open to different perspectives?

Common Mistakes to Avoid

  • Dominating the conversation without inviting input
  • Rushing to a decision without thorough discussion
  • Overlooking the long-term implications of each option

Pro Tip

Focus on fostering a collaborative atmosphere where everyone feels empowered to speak. Encourage questions and leverage diverse insights to guide your team through uncertainty.