4 ms·

I think many people, especially developers, often fail to appreciate how much of decisionmaking in organizations is the result of sustained negotiation between

I think many people, especially developers, often fail to appreciate how much of decisionmaking in organizations is the result of sustained negotiation between groups that have different conceptual models of what the business does. In the OP’s article, what I heard was that his problems mostly resulted from requirements not being developed or understood in a cross-silo approach (plus the not-uncommon estimation miss on bad data sources, but that’s a mechanical estimation issue). The key lesson here, I think, is not “corporations are stupid,” but that “corporations are too complex for linear requirements-gathering to in many cases support.”

geezerjay 7y ago
> The key lesson here, I think, is not “corporations are stupid,” but that “corporations are too complex for linear requirements-gathering to in many cases support.” This comment should be featured higher in a discussion. The "stupid" label is thrown rather fast although more often than not the problem lies in how critics fail to understand the problem and, more importantly, the restrictions applied to the decision-making process. Therefore critics base their view on their personal and very over-simplified and under-informed view of the problem, don't understand how an outcome is a valid and reasonable solution, and instead of assuming that they have limited information and understanding... They instead assume they have perfect information and complete insight into a problem and therefore any outcome they didn't approve or understand can only mean stupidity.