4 Comments
User's avatar
Nick Lampros's avatar

Enjoyed the distinction between optimizing and satisficing. This concept is utilized outside the RECM discipline by technology product managers as well. Here is one framework I particularly like by John Cutler: https://cutlefish.substack.com/p/tbm-1953-drivers-constraints-and

Either way, the work seems to be in the introspection required to define what is "good enough" in advance :)

Expand full comment
Matt Hoffman's avatar

Super interesting...I wonder if you could look at lean/agile development as short-term satisficing in service of longer-term optimizing...

I have to note that I feel like you and the author buried the lede here, what with the article's brief reference to "naps" ;-p

Expand full comment
Nick Lampros's avatar

From my read, the value of the distinction is the evocation of what is truly important. Besides that, I believe optimizing vs satisficing is a bit of a false dichotomy as you point out. I think we are always optimizing; the question is "for what?" For me, external pressures often cause my actions to drift--especially in any form of creation when I unconsciously bias toward perfection over speed. Good enough seems to be a forcing construct to re-evaluate.

Expand full comment
Matt Hoffman's avatar

I like it -- satisficing is optimizing in disguise, which really comes to how you define "good enough." Kind of like when you lie down to nap and don't lose consh but still get up feeling refreshed...see, it all comes back to napping :)

Expand full comment