A high-resilience org chart
“If you know what problem you're solving and you know how to solve it, a bureaucratic organization will do. Stick with what you know. If you're writing software, that's a generative activity. You need a high-resilience org chart. Fewer boxes, more flexibility.”
- from
- Engineering Team Management
- added
- 2026-10-10
- likes
- 0
similar
-
source news.ycombinator.com
). I.e. the structure of the organization is quintessential to its longevity.
-
The product roadmap is dead: welcome to the age of problem roadmaps medium.com
“Fall in love with your problems and not with your solutions.”
-
An Alternative Approach to Re-Orgs At Your Company caseyaccidental.com
“Trying not to repeat re-org mistakes, we started working on a structure that would make the re-org act like a feedback-fueled progress driven by the teams instead of by people above them.” This is an attempt to extract from the ground up signals pointing to inadequate…
-
Technical debt as a lack of understanding daverupert.com
“The problem lies in "never reorganizing (the code) to reflect your understanding." (…) Organizationally, you pay in velocity and turnover; talented people are going to leave after a few rounds of bullshit.”
-
What Team Structure is Right for DevOps to Flourish? web.devopstopologies.com
-
source news.ycombinator.com
). And that's the reason bureaucracies and highly political organizations are fertile grounds for consultants.
Engineering Team Management › Re-organizations > Company-level: ““If you know what problem you're solving and you know how to solve it, a bureaucratic organization will do. Stick with what you know. If you're writing software, that's a generative activity. You need a high-resilience org chart. Fewer boxes, more flexibility.””