But often in life as in OpenBSD, the key to making a good decision is simply MAKING A DECISION, then you worry about making it the RIGHT decision. This is a problem you can see in almost any committee designed system, compromise takes place to try to keep everyone happy-ish, but no one is completely happy, and the result is usually far from ideal. “A” could work, “B” could work, “A+B” and “neither” suck. Most committees end up going for the “A+B” or “neither” option for fear of pissing off the A or B camps.
Simply making a hard decision quickly and focusing all efforts behind that decision produces better results than compromises that split development efforts and drag out problems produces better results.
I was inspired to post this by a section from a friend’s text on conflict resolution. I disagreed in the general case, but this quote would support it in cases other than the ones she was discussing.