[arzke]

"The last responsible moment (LRM) is the strategy of delaying a decision until the moment when the cost of not making the decision is greater than the cost of making it."

Quoted from: https://www.oreilly.com/library/view/software-architects-han...

[TeMPOraL]

Still trying to unlearn that one. Turns out, most decisions are cheap to revert or backtrack on, while delaying them until Last Responsible Moment often ends in shooting past that moment.

[smaudet]

Depends who you are, mostly the ones making the decisions aren't usually listening to their developers (maybe by choice maybe because they are at the whim of a customer), so their cost functions are calibrated towards course changing being more expensive than less.

By the time your devs are saying "this sucks" you've long overshot.

[lmm]

Committing to a decision is costly, but implementing it one way or the other and seeing how that works is often the cheapest way to proceed.

[cle]

I don't think you need to unlearn it, but update your cost function.

[jlundberg]

Interesting term and I am curious to learn a few examples on overshooting here!

My experience is that the new data available when postponing decisions can be very very valuable.