We're sunsetting PodQuest on 2025-07-28. Thank you for your support!
Export Podcast Subscriptions
cover of episode Episode 433: My teammate pretends we decided, but we didn't and my team is getting worse and worse

Episode 433: My teammate pretends we decided, but we didn't and my team is getting worse and worse

2024/11/4
logo of podcast Soft Skills Engineering

Soft Skills Engineering
AI Deep Dive AI Chapters Transcript
People
A
Anonymous
无相关信息
J
Jordan
一位在摄影技术和设备方面有深入了解的播客主持人和摄影专家。
Topics
Jordan描述了一位新团队成员以“我们决定了”来结束讨论，即使该决定从未真正达成一致。他询问如何应对这种情况。 Dave 和 Jamison 建议可以委婉地询问决策的依据，例如“我们什么时候决定的？”或“你能帮我了解一下吗？”，这样可以让对方解释或意识到自己的行为。他们也建议可以直接指出这种行为，但要注意措辞，避免直接指责对方说谎。此外，他们还建议可以与经理沟通，寻求帮助和建议。

Deep Dive

Chapters
The hosts discuss strategies for addressing a teammate who claims decisions were made without actual consensus, suggesting gentle yet assertive approaches to challenge the claim and seek clarification.
  • Respond with 'we are free to change past decisions' to challenge the claim.
  • Ask for evidence of the decision to clarify the situation.
  • Consider discussing the issue with your manager for additional support.

Shownotes Transcript

In this episode, Dave and Jamison answer these questions:

-

Hey guys!

I recently moved onto a new team, and my teammate has an interesting way of resolving differences of opinions. He simply says “we decided” and then follows it up with his preferred approach. These are decisions that I know have not been made.

This engineer is mid-level, so it isn’t the “royal we” of a tech lead.

How do I handle this? Something tells me that responding with “nuh uh!” isn’t the right strat.

-

I’m a Principal Engineer at a large tech company who’s been with the same team for almost 8 years now! The team used to be part of a startup and we’ve been fortunate enough to be acquired by Big Tech three years ago. As a result, we’ve also more than doubled in team size. However, as we’ve aggressively grown over the last few years, I feel like we’ve inadvertently hired many “average” engineers. I find that some of our newer team members simply pick off the next ticket in the queue and do the bare minimum to progress the task. What happened to the boy scout rule? Where did the culture of ownership go? This also affects the genuinely great engineers on the team who start feeling like the others aren’t pulling their weight.

Any advice on how to level up the culture? Or do I need to adjust my expectations and simply accept that any team of a sufficient size will have folks from a range of abilities and attitudes?