The obvious one you seem to have avoided (maybe deliberately? ;-) is in software engineering. Pick 2: Speed, Quality, Cost. The thing is I have never really thought that is a great example because there may be other factors related to why you can't pick one or the other. For example if you're building a product and want to maintain speed and quality then cost will go up, but that only works to a point before diminishing returns because of the mythical man-month. Then what confounds me is that clever people who are making those decisions ignore Brooke's Law and think they can still push for speed while maintaining quality because they are happy for costs to go up. But the rising costs aren't actually contributing anything to the process. As a result, you end with "pick 1" - speed or quality.
Really enjoyed this - the triangle is great for visualising and articulating trade-offs beyond the binary, and writing out assumptions to make them clear. Love it
The obvious one you seem to have avoided (maybe deliberately? ;-) is in software engineering. Pick 2: Speed, Quality, Cost. The thing is I have never really thought that is a great example because there may be other factors related to why you can't pick one or the other. For example if you're building a product and want to maintain speed and quality then cost will go up, but that only works to a point before diminishing returns because of the mythical man-month. Then what confounds me is that clever people who are making those decisions ignore Brooke's Law and think they can still push for speed while maintaining quality because they are happy for costs to go up. But the rising costs aren't actually contributing anything to the process. As a result, you end with "pick 1" - speed or quality.
Really enjoyed this - the triangle is great for visualising and articulating trade-offs beyond the binary, and writing out assumptions to make them clear. Love it