[Pelam]

This! Often (actually almost always) time it self is valuable for multiple reasons. Spending precious time in the "meeting room" instead of progressing towards (almost any) implementation can decrease the overall value and increase the risks.

Also some people strongly prefer action over deliberation, especially by a committee so there is also a psychological cost to the team to consider.

With software and a capable team, there can still be an illusion that decisions are cast in stone and can't be changed later, while the opposite is true.

Implementing a solution that is almost there and then making corrections can be both more satisfying and lead to very good results. This of course requires the psychological freedom an flexibility to quickly acknowledge errors in thinking and design and not holding on to "the plan" too tightly.

[creakingstairs]

I’ve argued for just building POC approach at times and worked out great sometimes. I found the issue was usually with management. Many have been extremely reluctant to throwing away code. Even though writing POC and re-doing everything will take the same time as planning for ages and doing it once.

[navane]

Proof Of Concept.