When the lines get blurred
In cross-functional teams, sometimes it's hard to tell who's responsible for what. For example, when the design team helps out with the PRD, a PM creates wireframes, or an engineer pushes code that wasn't agreed on, it can be quite frustrating if this happens repeatedly without clear definition.
Things can get even messier when there are tight deadlines or pressure from the higher-ups. That's why it's important to have a chat with your team members and clear things up.
Now, you might think of running to your manager to sort things out, but that can sometimes make matters worse. It might make your teammate feel like they've been slighted and often times they may think they're doing the right thing. So, it's best to have these conversations directly.
Here are some things to consider when doing so:
Avoid personal accusations
When addressing role-related issues, the first rule is to refrain from making personal comments or attacks. Accusations like "you're being unprofessional" or "stepping out of your role" can be emotionally triggering and shut down productive conversations. Instead, focus on mutual agreements and shared values.
Start with common ground
Begin the conversation by identifying common ground—company missions, product principles, or organizational values that everyone has aligned on. This lays a constructive foundation and signals that you're all in this together. It assumes the best intentions from all parties and acknowledges that mistakes can happen in haste rather than out of malice.
Show empathy
Empathy is key. We've all be there, external factors, such as tight deadlines or workload pressures, might lead to colleagues making decisions that deviate from their usual roles. Sometimes, a seemingly small output may require substantial behind-the-scenes effort. Communicate your understanding of the situation and appreciate the effort invested.
Communicate thought processes
In instances where roles blur, explain your thought processes. Sometimes, while the output may appear different, the thinking behind it might involve considerable effort and consideration. Highlighting this can help clarify your colleague's intentions and bridge the understanding gap.
Take action
After a discussion, ensure that you and your colleague agree on a follow-up action plan. This serves as a reference point in case the issue arises again. It demonstrates a commitment to learning from past experiences and working collaboratively to avoid repeating mistakes.
When all else fails
If you're having an ongoing struggle with a coworker, try talking to them face-to-face before running to your boss. This way, you can work on resolving the issue yourselves. It also shows that you're committed to finding a solution. If that doesn't work, involving your manager can be a good way to get some feedback and guidance. Remember, soft skills, especially when dealing with work-related obstacles, are super important for both your personal growth and the success of your team.
Senior Product Designer
4 个月I agree, i also think its what separates a seasoned designer over a straight out of bootcamper. Design more than ever has become more collaborative. Chucking egos at the door is something most new designers will learn after working with teams, especially those who are cross functioning & agile.
Principal Product Designer @Dell | Design Strategy | Product Design | Design Systems | DesignOps | Service Design | AI/ML
5 个月This is especially helpful for folks that have worked in a start-up environment and are transitioning to roles in a larger company/organization where roles are more defined. As a designer, earlyon inmy career working in start-up environments, I had to be the PM, Designer, and Front-End Dev all-in-one. because the budget wasn't available to hire these specified roles, but I took on the challenge to grow my skill-sets. As I shifted to working for larger companies, I learned to trust my cross-functional team with what I normally would do as a PM or Engineer. I even use it as a cheat code because I understand their challenges and goals; as a designer I'll maximize what I can provide to help them do what they need to get done. But yes these situations are common, healthy communication is always key.
Senior UX/UI Designer at Pinellas County Government | Web & Product Design
6 个月Agreed ??% Never lose the lesson! Happened to me a few times but going back to clarifing expectations, and actively listening the “whys” of each action can get everyone back on the same page.