Optimize for the {whole, business unit, team}. Pick one of these options to help the team understand how they should balance decisions between impacting their team and impacting other teams. It’s also a good example of how values and architecture intersect: you can’t really optimize only for your team if you’re in a monolithic service without causing significant problems elsewhere.
Setting engineering org values.
from Irrational Exuberance
Filed under:
Same Source
- **Create capacity (rather than capture it).** This value focuses le...
- **Default to vendors unless it’s our core competency.** You can als...
- **Follow existing patterns unless there’s an order of magnitude imp...
- Approach conflict with curiosity. One of my foundational beliefs is...
- As described in Rumelt’s Good Strategy, Bad Strategy, a strategy is...
- View all
Related Notes
- Rigid adherence to any prioritization model, even one that’s concep...from Irrational Exuberance
- Original layout ![](https://www.joelsimon.net/imgs/evo_plans/resul...from joelsimon.net
- More things than you would think are dynamic strategic problems. If...from marcelo.rinesi
- A great framework for delegating work or encouraging a team member ...from Ken Britton
- We're talking about a guy who in all seriousness has said on ma...from gist.github.com
- I designed the RAMBO Model as a simple framework to lead a great en...from thecodecompany.com
- These constraints create better decisions both because constraints ...from Irrational Exuberance
- Amdahl's law is often used in [parallel computing](https://en.w...from en.wikipedia.org