3 ms·
The fact that no one used it doesn't mean that building it was a mistake. Maybe the purchase officer got it wrong, but the salesperson who requested it be built
by neilkk 3y ago
The fact that no one used it doesn't mean that building it was a mistake. Maybe the purchase officer got it wrong, but the salesperson who requested it be built got it right, since the deal did in fact depends on it.
- danjac 3y agoPerhaps. But then it's important to look at the total cost of ownership: was it worth building a complex feature for one client that adds to the technical debt of a code base and tied up developer resources that could have been better employed elsewhere? Could we have pushed back on this feature or was it really a deal-breaker? In other words, perhaps landing this one client was important to that salesperson, and perhaps in the short term to the company, but in the long term it may have been better to have lost that one deal. Very often these decisions are made with little calculus about the TCO.