Non-trivial decisions always involve tradeoffs.
Nowhere is this truth less obvious (but no less true) than in software development. When I was a fairly new developer, I made a suggestion to the company that built our timekeeping software. The response I got back was that it was "impossible" to make my suggestion a reality. Of course that was not the case. Instead my suggestion would have forced the developer to the wrong side (from their perspective) of a tradeoff that I could not see from the outside.
Community software involves tradeoffs too. Every feature must make the balance between being easy for a new member to use and empowering longtime members. That's why good community software includes repulatation/karma/leveling systems.
That extends to community policies as well. We give people who have invested in the community the benefit of the doubt and sometimes we get burned as a result. This only makes sense when we acknowledge our policies can be unfair. Indeed they must be since every decision is a tradeoff.