4 ms·
Because it’s the same situation as with any enterprise software - the buyers are not the users, and they are evaluated at how well they did or not do their job
by projectileboy 8y ago
Because it’s the same situation as with any enterprise software - the buyers are not the users, and they are evaluated at how well they did or not do their job based on a whole host of criteria that have absolutely nothing to do with satisfied users.
- brownbat 8y agoBuyers? I want the makers trained as users. Everything I've optimized really well was after a week or so using the old bad solution. Programs made for me, to automate some part of my job? Invariably break some part of my workflow that promptly gets labeled an edge case.
- TeMPOraL 8y agoSame problem. Makers are not paid to think like users. Makers are paid to satisfy whoever's actually paying.
- paulie_a 8y agoIf makers dont have a fundamental understanding of how the users will utilize it, the makers are making a bad product. Every developer should do customer service and a sales call on a regular basis.
- TeMPOraL 8y ago> If makers dont have a fundamental understanding of how the users will utilize it, the makers are making a bad product. Well, exactly. That's half of the reason why enterprise, medical, restaurant and other similar software generally sucks. > Every developer should do customer service and a sales call on a regular basis. In B2C, sure. In B2B for the examples I mentioned above, a "sales call" is where the problem starts. On such a call, you'll get the opinions of people paying for software, not of those using it.
- paulie_a 8y agoIn either case the developer the should get a first hand experience about the pain points. Developers tend to be isolated and build things that really doesn't fit the need that is required. Ask the potential customer and they will come. (Maybe, but at least the developer has a better idea of things to build)