Conflict Resolution in Creative Projects

𝗖𝗼𝗻𝗳𝗹𝗶𝗰𝘁 𝗮𝘁 𝘄𝗼𝗿𝗸, 𝘄𝗵𝗲𝘁𝗵𝗲𝗿 𝗱𝗶𝗿𝗲𝗰𝘁 𝗼𝗿 𝗽𝗮𝘀𝘀𝗶𝘃𝗲-𝗮𝗴𝗴𝗿𝗲𝘀𝘀𝗶𝘃𝗲, 𝗶𝘀 𝘂𝗻𝗰𝗼𝗺𝗳𝗼𝗿𝘁𝗮𝗯𝗹𝗲, but it’s inevitable. Yet, many don't know how to handle it effectively. Once I got curious about what causes conflict, I realized most are rooted on 3 sources: 𝟭. 𝗜𝗻𝗳𝗼𝗿𝗺𝗮𝘁𝗶𝗼𝗻 𝗔𝘀𝘆𝗺𝗺𝗲𝘁𝗿𝘆: Conflict often happens when parties lack access to the same data. Their decisions clash because they’re not working with the same information. At Google Home, the e-commerce team and I didn't see eye to eye on a new service launch strategy. The economics impacted their channel performance, but after I shared the roadmap of future services that would offset the challenges, we aligned. With both teams accessing the same "data set", the conflict dissolved.     𝟮. 𝗣𝗵𝗶𝗹𝗼𝘀𝗼𝗽𝗵𝗶𝗰𝗮𝗹 𝗗𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝗰𝗲𝘀: Sometimes, everyone has the same facts but different priorities. One side might focus on quality vs. speed. Having a common set of principles or philosophies helps drive alignment.     While leading the transition from G Suite to Google Workspace, we restructured features across 20+ apps. Each app team had different approaches, making alignment difficult. But once we agreed on principles—like target customers profiles per subscription tier—decision-making became much easier.     𝟯. 𝗘𝗴𝗼: Sometimes it's not about data or principles— it's personal. A party may feel slighted or passed over, leading them to derail plans (consciously or unconsciously). In such cases, escalation is often the best solution.     At Adobe, I worked to align product leaders on a strategy, but some personal grievances and turf wars slowed progress. Even with shared data and principles, the conflict persisted. Escalating to senior management helped resolve the impasse and get everyone on board. 𝗛𝗲𝗿𝗲’𝘀 𝗮 𝗺𝗲𝘁𝗵𝗼𝗱𝗼𝗹𝗼𝗴𝘆 𝘁𝗵𝗮𝘁 𝗵𝗮𝘀 𝗵𝗲𝗹𝗽𝗲𝗱 𝗺𝗲 𝗿𝗲𝘀𝗼𝗹𝘃𝗲 𝗰𝗼𝗻𝗳𝗹𝗶𝗰𝘁: 𝟭. 𝗦𝗲𝗲𝗸 𝘁𝗼 𝗨𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱: Identify the root cause: data gap, philosophical difference, or ego? Approach with empathy, curiosity, and zero judgment. 𝟮. 𝗔𝗹𝗶𝗴𝗻 𝗼𝗻 𝘁𝗵𝗲 𝗙𝗮𝗰𝘁𝘀: Share all relevant info. Ensure both sides work from the same set of truths. 𝟯. 𝗔𝗴𝗿𝗲𝗲 𝗼𝗻 𝗣𝗿𝗶𝗻𝗰𝗶𝗽𝗹𝗲𝘀: Once aligned on facts, agree on guiding principles. Debate principles, not the issue itself. 𝟰. 𝗪𝗼𝗿𝗸𝘀𝗵𝗼𝗽 𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻𝘀: Collaborate on options, weighing pros and cons together. 𝟱. 𝗖𝗼𝗺𝗺𝗶𝘁 𝗮𝗻𝗱 𝗗𝗼𝗰𝘂𝗺𝗲𝗻𝘁: Choose a solution, document it, and share with all involved. Include names and dates—this adds accountability and prevents reopening the issue. 𝟲. 𝗘𝘀𝗰𝗮𝗹𝗮𝘁𝗲 𝗶𝗳 𝗡𝗲𝗰𝗲𝘀𝘀𝗮𝗿𝘆: If all else fails, it's likely ego-driven and escalation might be necessary—and that’s okay when done responsibly. Next time conflict arises, don’t rush to fix it or let frustration take over. Step back, identify the cause, and handle it methodically. #leadership #conflict

Dan and Todd? They used to be best friends. But things got messy, and now they can't stand each other. Dan's ready to move on, but Todd? Not so much. Problem is, they work on the same team you manage, and now Dan's knocking on your door, hoping you'll step in and fix things. Sure, you could tell them, "Just avoid each other and carry on." Sounds easy, right? Why make two people who aren't friends anymore work together if they don't want to? But here's the catch: avoiding this issue might be an easy short-term fix, but it's not a long-term solution that actually works. In most workplaces, people can't just steer clear of each other, especially if they need to interact on the daily. So instead of hoping it all blows over, try these steps to get Dan and Todd back on the same page professionally—even if the friendship ship has sailed. Step 1: Acknowledge the drama, privately. Don't cross your fingers and hope they'll magically "work it out." Have a quick, private chat with each of them to figure out what's going on. Listening to them (without playing favorites) shows them you're taking this seriously. Step 2: Shift the focus to work goals. The end game? You want them thinking about work, not their personal beef. Remind them that the team has goals, and their collaboration matters for everyone's success (including their own). Step 3: Set some ground rules. Lay down clear expectations for communication, respect, and behavior. They don't have to be besties, but they do need to keep it professional and act with respect. That way, everyone's on the same page. Step 4: If it's still tense, bring in a mediator. Sometimes a neutral third party can get things out in the open, defuse the tension, and help them both refocus on moving forward. Step 5: Keep an eye on things. Conflict resolution is never a "one and done." Check in now and then to make sure they're meeting expectations and catching any new issues early. Bonus step: Document everything. Keep records of your conversations and any actions taken. If Todd's behavior begins to impact the team or work quality, documentation will support any future action you might need to take. Bottom line: Telling them to avoid each other sounds easy, but it's not sustainable. By helping them work through this professionally, you're building a culture of respect and collaboration—and a stronger team all around.

2/n #AILeadershipSeries The biggest mistake in a senior-level interview? Framing conflict as a personality problem. 😬 As leaders, we don't interview well by saying, "We disagreed, but I was right." High-stakes tech interviews—especially for Staff and Manager roles—test your ability to navigate structural conflicts (e.g., product launch speed vs. engineering stability, or allocating limited resources). The goal is to show you can engineer the resolution by implementing a neutral, data-driven framework. Amaresh's Playbook for Conflict: Stop the Subjectivity: Don't focus on who was right; focus on establishing neutral ground. For one candidate struggling with a feature vs. architecture debate, the advice was clear: "Did you establish clear success metrics upfront? Did you create a single, shared one-pager that tied both parties' concerns to a common business goal?" Detail the Mechanics: Leaders create systems. Instead of saying "I talked it out," describe the mechanism: a joint, weekly scrum between the two conflicting teams, a RACI chart to clarify roles, or a structured trade-off analysis document. Quantify the Win: Your story must end by converting the friction into a quantifiable business result. You didn't just resolve a fight; you accelerated a critical service by 20%, or avoided $5 million in future tech debt by aligning on the long-term solution. Prove you don't just solve problems—you build unbreakable partnership mechanisms into your organization. #EngineeringLeadership #ConflictResolution #BehavioralInterview #TechManagement

I was a director of e-commerce that almost got fired because I yelled at a co-worker. I was wrong to raise my voice. Nothing is worth that. But the conflict itself? It led to a breakthrough which saved our quarter. Predictably we were arguing about brand and conversion rates. My coworker was right. So was I. We just cared about different things. They wanted creative control. I wanted a better conversion rate. And we were both fighting for what we thought mattered most. That argument forced us to finally have the hard conversation what are we optimizing for and what are our incentives? We walked away bruised, but aligned. Conflict isn’t the enemy. Conflict is the job. Conflict is necessary and should be embraced. Because when your goal is to grow revenue, you're only successful when people including yourself are pushed outside their comfort zone. Dev will say it’s too hard to build. Creative will say it breaks the brand. Merchandising will say it doesn’t fit the assortment. But that’s the job. To push. To prioritize what impacts the highest percentage of revenue, even when it pisses people off. Here is how I understand the heart of the conflict. Ask and understand what are the incentives at play? -How are you measured, and what do you care about? -How will your bonus be calculated? -What will your boss use to fight for your raise and promotion? -What is the one thing that your boss is always sending 9 PM emails about? The Director of E-Commerce doesn’t have to have all the answers. But they have to create the space where those arguments surface and get resolved with empirical evidence. (Experiments are often the strongest empirical evidence available to us.) That’s how great e-commerce teams operate. Not through harmony. Through tension. How do you work with your teams to ensure you're not hamstrung by conflict?

Scrum Master: How would you manage team conflict? Conflict is inevitable. Staying stuck is optional. Ever found yourself in the middle of a heated conversation during a Sprint Retrospective or a planning session? You’re not alone. Conflict is a sign that people care but without the right approach, it can derail progress fast. Here’s a 5-Step Conflict Resolution Framework from Harry Karydes I’ve used (and coached teams on) to turn tension into TRUST 1. Identify the Root Cause ↳ Get beyond surface-level complaints. ↳ Ask open-ended questions: “What’s really bothering you?” ↳ Separate symptoms from the real issue. 2. Acknowledge & Validate Perspectives ↳ Let each person speak without interruptions. ↳ Reflect back what you heard: “What I hear you saying is…” ↳ Validate emotions, even if you don’t agree. 3. Focus on Solutions, Not Blame ↳ Shift from “Who’s at fault?” to “What’s the best way forward?” ↳ Brainstorm options together. ↳ Align solutions with team goals. 4. Create a Clear Action Plan ↳ Define who does what by when. ↳ Set measurable steps and accountability. ↳ Write it down; verbal agreements fade. 5. Reinforce the Resolution ↳ Follow up: “Is the solution working?” ↳ Address lingering issues early. ↳ Celebrate progress to rebuild trust. Pro Tip: The BEST Scrum Masters and Agile Coaches don’t avoid conflict. They facilitate healthy resolution that strengthens the team. What’s your go-to approach when conflict surfaces in your team? Drop your thoughts or tips in the comments!