3 ms·

Your comments elsethread are further examples of someone ignoring (and apparently attempting to throw under the bus) co-workers who are trying to provide import

by thom 4y ago

Your comments elsethread are further examples of someone ignoring (and apparently attempting to throw under the bus) co-workers who are trying to provide important, actionable context.

khazhoux 4y ago
Sometimes one just needs a direct answer to a question. In fact, it’s a common anti-pattern of effective communication, to think that “more detail (all the detail) is always better.” Sometimes we just need an answer to the question, and will ask follow-ups as needed. I find a correlation actually where people who struggle to give clear answers/explanations, struggle in their own decision-making. They get ensnarled into ever-deepening details and can’t cut through them to make actual progress.
- thom 4y ago
  All the examples you've given are of team members struggling in a wider ecosystem. Yes, you can stamp your foot and hold them to their responsibilities on a single task. But you might deliver more value if you listened to the things holding them back, because there will always be future tasks.
  - khazhoux 4y ago
    Again... in many contexts, yes I appreciate the detail. I'm not saying engineer-to-manager or engineer-to-engineer communication should also be terse. But some people struggle to collect their thoughts clearly, and struggle to articulate simple answers to even the simplest of questions. I have seen this, and seen how detrimental it is to their effectiveness as engineers and teammates. My approach is to actively coach people on my team that I see with poor communication. And it's a valuable skill that I'm advocating. When an engineer is invited to a VP presentation, and the VP asks "Has this feature launched?", you better believe they don't want a 3-minute ramble of the challenges they faced, or what they'd do differently, or whatever. They want to know: "Has. This. Feature. Shipped?"
    - afarrell 4y ago
      Sometimes it is a fear response to the anticipated consequences of giving a clear answer. In your example, I imagine that the engineer is trying to be seen as still worthy of employment despite not shipping a feature. That motivates them to show themselves as: - Able to overcome some challenges. - Able to learn from mistakes. This is a self-reenforcing cycle. An engineer who struggles to make decisions will struggle to deliver at pace. An engineer who struggles to delver at pace will have more experiences of getting fired. An engineer with more experiences of getting fired will be more fearful and thus struggle more to gather their thoughts and communicate clearly. The only solution I know of is more secure professional relationships such as with a coach such as you’ve been acting as.

by thom 4y ago

Your comments elsethread are further examples of someone ignoring (and apparently attempting to throw under the bus) co-workers who are trying to provide important, actionable context.

khazhoux 4y ago

Sometimes one just needs a direct answer to a question. In fact, it’s a common anti-pattern of effective communication, to think that “more detail (all the detail) is always better.” Sometimes we just need an answer to the question, and will ask follow-ups as needed. I find a correlation actually where people who struggle to give clear answers/explanations, struggle in their own decision-making. They get ensnarled into ever-deepening details and can’t cut through them to make actual progress.

thom 4y ago
All the examples you've given are of team members struggling in a wider ecosystem. Yes, you can stamp your foot and hold them to their responsibilities on a single task. But you might deliver more value if you listened to the things holding them back, because there will always be future tasks.
- khazhoux 4y ago
  Again... in many contexts, yes I appreciate the detail. I'm not saying engineer-to-manager or engineer-to-engineer communication should also be terse. But some people struggle to collect their thoughts clearly, and struggle to articulate simple answers to even the simplest of questions. I have seen this, and seen how detrimental it is to their effectiveness as engineers and teammates. My approach is to actively coach people on my team that I see with poor communication. And it's a valuable skill that I'm advocating. When an engineer is invited to a VP presentation, and the VP asks "Has this feature launched?", you better believe they don't want a 3-minute ramble of the challenges they faced, or what they'd do differently, or whatever. They want to know: "Has. This. Feature. Shipped?"
  - afarrell 4y ago
    Sometimes it is a fear response to the anticipated consequences of giving a clear answer. In your example, I imagine that the engineer is trying to be seen as still worthy of employment despite not shipping a feature. That motivates them to show themselves as: - Able to overcome some challenges. - Able to learn from mistakes. This is a self-reenforcing cycle. An engineer who struggles to make decisions will struggle to deliver at pace. An engineer who struggles to delver at pace will have more experiences of getting fired. An engineer with more experiences of getting fired will be more fearful and thus struggle more to gather their thoughts and communicate clearly. The only solution I know of is more secure professional relationships such as with a coach such as you’ve been acting as.