Stop trying to engineer your way out of listening to people
This piece argues that engineers often attempt to solve communication breakdowns with complex frameworks instead of simply engaging in genuine listening. It challenges common assumptions and biases that prevent effective interpersonal understanding in technical environments. The Hacker News discussion debated whether the article's critique was condescending or if it accurately pinpointed a crucial, often-ignored aspect of successful project delivery.
The Lowdown
The article posits that many software project failures stem not from a lack of sophisticated systems or frameworks, but from a fundamental human problem: people aren't talking to or, more critically, listening to each other. The author contends that the engineering mindset often tries to 'engineer its way out' of this human element, when the real solution is to embrace the 'harder work' of listening. The core problem, the author insists, is avoiding this essential human work.
Key pitfalls preventing effective listening include:
- Confusing listening with simply acceding to stated wants, rather than understanding underlying needs (e.g., Jobs To Be Done).
- Underestimating how one's own specialized worldview limits understanding of others' knowledge.
- Assuming 'technical' is a monolithic skill, ignoring the diverse knowledge areas within it.
- Presuming others share the same resources, energy, or skills.
- Generalizing character traits from a single individual to an entire group.
- Assuming people and organizations are static, which undermines fixed-requirement project management.
- Mistaking what people say for what they are truly thinking.
- Judging individuals, which inherently hinders the ability to listen effectively.
- Treating a group of individuals as a single, homogenous entity, ignoring complex group dynamics.
Ultimately, the author argues that failing to listen leads to missing crucial insights that drive success, profit, and even help mitigate technical debt, as misunderstandings often translate into future code complexities. By highlighting these common traps, the piece aims to encourage better listening practices across the board.
The Gossip
Condescension or Clarity?
Many commenters found the article's tone to be condescending or a 'vent,' particularly in its perceived criticism of developers. They felt it offered little practical advice beyond 'just listen,' while overlooking the systemic reasons why people resort to frameworks. Others, however, agreed with the core message, seeing it as a necessary challenge to common, ineffective practices.
Metaphorical Misinterpretations
One popular comment reinterpreted the article's opening Spongebob metaphor. Instead of a failure to listen, they suggested that many involved stakeholders are primarily interested in the 'ribbon cutting' (superficial achievement) rather than the actual 'road' (functional outcome), implying a deeper misalignment of incentives.
Meeting Mayhem & Meaningful Communication
A significant discussion revolved around the efficacy of meetings and the quantity of communication. Some argued that 'too much time' is spent communicating ineffectively, leading to a call for fewer, more focused interactions. Counterarguments emphasized that many meetings aren't truly about communication but rather prescription or control, and that listening is a distinct skill independent of meeting volume.
Documentation's Role and Framework Fetishes
Commenters also discussed the role of detailed written documentation as a critical tool for unambiguous communication, contrasting with the article's critique of over-engineering solutions. There was also a desire for the author to have linked to the 'tonnes of frameworks' mentioned, as these could offer practical approaches to the very listening problems highlighted.