Episode 216: One-on-ones and inter-team power struggles
Jun 29, 2020
auto_awesome
Topics covered in this podcast include the purpose of one-on-one meetings, a power struggle between front-end, back-end, and design teams, the importance of open conversations and healthy collaboration, and bridging the ownership gap within a team.
The organization needs an arbiter role or individual to resolve conflicts between teams and ensure fairness and collaboration.
The question asker should discuss the issue with their manager to seek guidance and address the problem, emphasizing the need for open conversations and potential solutions.
Deep dives
Front End Team Impose Artificial Constraints on Other Teams
The front end team in the organization is imposing artificial constraints on the backend team and the design team by making technical decisions that limit the choices of others. For instance, they claim that certain interactions or design features cannot be implemented because of the limitations of their components. This behavior is causing confusion and frustration among other teams. When the question asker tries to challenge their team's decisions, they face anger and backlash. However, when they attempt to find compromises, they feel uncomfortable because they believe their team is wrong. They have also discussed the issue with other teams and managers, but feel uncomfortable pointing fingers or throwing their teammates under the bus. They seek guidance on how to address this problem.
Lack of an Arbiter
The organization lacks a role or individual who can act as an arbiter and resolve conflicts between teams. This missing role could be that of a software architect, principal engineer, or a senior staff member who can review and approve contracts between systems. This person would evaluate designs and decisions made by the front end team and ensure they do not impose unnecessary constraints on other teams. Having an arbiter would promote fairness, balance, and collaboration within the organization.
Open Communication with Managers
The question asker should feel comfortable discussing this issue with their own manager. It is not about throwing their team under the bus, but rather seeking help and guidance in addressing the problem. By having an open conversation, the question asker can express their concerns and provide insights into the behavior of their team. This can lead to discussions about the team's actions and potential solutions, such as implementing a review process or encouraging a culture of ownership that prioritizes the success of the entire organization.
Root Cause Analysis and Culture Gap
It is crucial to conduct a root cause analysis to understand why the front end team is so focused on imposing constraints on other teams. This analysis should identify any competency gaps or potential issues of hubris within the team. It may be necessary to address these underlying factors to change the team's behavior. Additionally, there seems to be a culture gap in which the front end team prioritizes its own self-interests over the success of the overall organization. Closing this culture gap will require fostering a culture of collaboration, empathy, and shared ownership among all teams.
In this episode, Dave and Jamison answer these questions:
Questions
I have a weekly one-on-one with my manager. What should I talk about in them? Things like feedback and career goals become old and repetitive real soon, and I end up discussing current work items.
I understand that a one-on-one is my time to ask questions and don’t want it to be a longer daily-standup.
My front-end team mates are in a power struggle with my back-end team mates and my design team mates. They’re intentionally making technical decisions that artificially constrain the choices of other teams.
For example, design wants a certain interaction for a new feature, and my team says “nope, it can’t work that way, cause the components we built don’t allow that”. Or, they make tickets for the back-end team as in “endpoints have to work this or that way, because our components assume that structure”. This often seems detrimental and confusing to other teams.
When I push back against my team they are angry. When I defend my team other people are angry. When I try to strike a compromise I feel gross because I usually think my team is wrong. I’ve tried talking with other teams and managers about the problem. I feel gross about that too because I don’t want to point fingers or throw my team mates under the bus. Where should I even start?
Get the Snipd podcast app
Unlock the knowledge in podcasts with the podcast player of the future.
AI-powered podcast player
Listen to all your favourite podcasts with AI-powered features
Discover highlights
Listen to the best highlights from the podcasts you love and dive into the full episode
Save any moment
Hear something you like? Tap your headphones to save it with AI-generated key takeaways
Share & Export
Send highlights to Twitter, WhatsApp or export them to Notion, Readwise & more
AI-powered podcast player
Listen to all your favourite podcasts with AI-powered features
Discover highlights
Listen to the best highlights from the podcasts you love and dive into the full episode