Roleplay Scenario
Scenario Overview
Your development and design teams are working together on a new product feature. Recently, there have been misunderstandings regarding deliverables and timelines, causing delays and some frustration. You need to engage in a constructive feedback session to improve collaboration, address concerns without assigning blame, and establish a more effective workflow.
Roles & Setup
Role A – Engineer (You)
You’ve noticed recurring issues in the handoff from design to development, leading to rework and missed deadlines.
Your goal: Provide constructive feedback, understand the design team's challenges, and propose solutions for smoother collaboration.
Role B – Designer
You’ve experienced pushback on design changes and feel that your input is sometimes overlooked.
Your goal: Share your perspective on the challenges faced, listen to feedback from the engineering side, and work toward a collaborative solution.
Suggested Openers
Engineer:
- “Hey, do you have a few minutes to talk about our recent project handoffs? I think there are some ways we can improve our process.”
- “I’ve noticed some hiccups in our workflow lately, and I’d love to hear your thoughts on how we can address them together.”
Designer:
- “Sure, I’ve been noticing that too. Let’s talk about how we can better align our processes and expectations.”
- “Absolutely. I’d like to share some observations from the design side and hear your thoughts as well.”
Sample Roleplay in Action
Engineer:
“Hey, do you have a few minutes? I've been thinking about our recent project handoffs, and I noticed that some of the final designs we got were a bit different from earlier versions. It led to some rework on our side. How do you think we can make this better?”
Designer:
“Yeah, I’ve noticed that too. Sometimes we get late feedback from stakeholders, which can lead to those changes. I get how that could disrupt your timelines. What do you think would help us better manage these changes?”
Engineer:
“Maybe we can set up a consistent feedback loop where any changes post-initial approval are clearly documented and communicated. We could also have a joint review session before finalizing designs to catch potential issues early.”
Designer:
“That sounds like a solid plan. We could also create a shared document to track changes and decisions, so everyone stays informed. How does that sound to you?”
Engineer:
“Perfect. Let’s start by scheduling regular check-ins and setting up a shared space for documentation. I think this will help us stay aligned and avoid last-minute surprises.”
Designer:
“Great, I’ll draft a proposal for these changes and share it with the team for feedback. Thanks for bringing this up—it’s important that we streamline our workflow.”
Post-Scenario Tools
Curveball Mode (Optional)
Add one of these twists to increase complexity and test adaptability:
- A new design change is introduced mid-conversation, requiring immediate feedback.
- A stakeholder joins the conversation unexpectedly, offering conflicting priorities.
- One party misunderstands a key point, leading to potential misalignment.
Reflection Checklist
As the Engineer:
- Did you communicate feedback constructively and focus on solutions?
- Did you actively listen to the designer’s perspective?
- Did you propose actionable steps to improve collaboration?
As the Designer:
- Did you remain open to feedback and avoid defensiveness?
- Did you clearly communicate your challenges and needs?
- Did you contribute to developing a mutually agreeable solution?
Common Mistakes to Avoid
- Focusing on blame rather than solutions.
- Allowing the discussion to become defensive or adversarial.
- Concluding without clear, actionable next steps.
Pro Tip
When giving and receiving feedback, aim to build a feedback culture that emphasizes growth and collaboration. This approach fosters stronger inter-team relationships and more effective project outcomes.