culture

Nobody Pushed Back: Why Engineers Stay Silent Until It’s Too Late

/ , , ,

The article explains that major engineering failures often occur not because of a lack of knowledge but because engineers stay silent when they foresee problems, as speaking up is socially or professionally costly. Cases from Nokia, TSB, Boeing, and Microsoft illustrate how technical risks were known internally but suppressed due to company culture, fear of backlash, and a prioritization of “alignment” over genuine dissent, leading to disastrous outcomes. The piece emphasizes the need for organizational environments that encourage safe and constructive pushback to prevent such failures.

https://howtocenterdiv.com/beyond-the-div/nobody-pushed-back

Why a ‘Risk Position’ Should Be The Next Big Thing In Business Leadership

/ , , ,

Dr Emma Soane argues that an organization's “risk position”—its intentional stance on risk-taking and management—should be regarded as fundamental as its strategy, culture, and leadership. Highlighting examples like Netflix and The Royal Mint, she explains that a clear risk position enables organizations to align risk with strategic goals, foster open risk dialogue, and move beyond viewing risk solely as a compliance issue or threat.

https://www.lse.ac.uk/study-at-lse/executive-education/insights/articles/why-a-risk-position-should-be-the-next-big-thing-in-business-leadership

No Management Needed: Anti-patterns in Early-stage Engineering Teams

/ , ,

TLDR: Early-stage founders should avoid meddling in engineering management problems, focusing instead on building products and engaging with users. Key advice includes: don't try to motivate engineers—hire motivated ones instead; refrain from hiring managers too early; avoid adopting management practices from successful companies without context; and maintain a simple, transparent, and flexible management style. Prioritize hiring exceptional talent over management complexities to foster a productive environment.

https://www.ablg.io/blog/no-management-needed

21 Lessons From 14 Years at Google

/ ,

21 Lessons from 14 Years at Google: Key Insights

  1. Focus on solving user problems rather than technology for its own sake.
  2. Collaboration and alignment matter more than just being right.
  3. Taking action is vital; perfection can lead to paralysis.
  4. Clarity trumps cleverness in code for easier maintenance.
  5. Innovate selectively to avoid added complexity and risk.
  6. Build relationships; your work alone won’t advocate for you.
  7. Aim to avoid writing code if possible—less is more.
  8. Recognize that bugs affect users; treat compatibility as essential.
  9. Misalignment often slows teams more than execution issues.
  10. Control what you can; don’t waste energy on the rest.
  11. Understand underlying complexities even with high-level abstractions.
  12. Teaching reinforces your understanding; write for clarity.
  13. Acknowledge the importance of often-invisible supportive work.
  14. Winning debates can lead to silent resistance; seek true alignment.
  15. Avoid gaming metrics; focus on trends and insights instead.
  16. Admitting ignorance fosters a safer learning environment.
  17. Invest in networking for long-term career benefits.
  18. Removing unnecessary work often improves performance more than adding complexity.
  19. Effective processes reduce uncertainty, not just create documentation.
  20. Prioritize time over money as your career progresses.
  21. Learning builds on itself; expertise comes with time and reflection.

The essence: Stay curious, humble, and people-focused in your engineering journey.

https://addyosmani.com/blog/21-lessons/

Scroll to Top