[SoftwareMaven]

One of the most important things I've learned over the years I've managed people is that processes and policies of any sort are two-edged swords. It's easy to add a policy, and to convince oneself of the advantage the policy will confer. What is very often ignored is the cost of a policy.

Every policy comes with an associated cost, and those costs can add up quickly. People always ask "what will this policy make better", but, just as important, is to ask, "what will this policy make worse".

[BurningFrog]

I've come to believe that ignoring one side of the cost/benefit calculus is the root cause of an enormous number of mistakes.

To spell the two errors out:

A: "This has a benefit, so we should do it!"

B: "This has a cost, so we should not do it!"

[ljm]

I like to talk about trade-offs a lot, and opportunity cost is also a good way to look at it. But yeah, it’s not often I see that happen.

Even better, make that a function of time so your cost/benefit analysis looks further beyond your initial preference. Spending more to save more is a highly effective choice in the right circumstances, and equally so, a perceived rapid gain can cost a fortune a bit later on.

It’s never so easy as saying always do D, prefer Y, avoid Z. They’re prescriptive and reactionary.