Originally posted by chocolate
View Post
But developers have a mind of their own, which is also good, because they're full of amazing ideas and suggest possibilities that nobody would have thought about.
But when there's no feedback and interpretation between both side, it can either be:
- technically impossible to realize - scoped too widely - ... (business)
- genius technically but not fulfilling any actual use cases - going in their own world - ... (IT)
If there's no counterbalance from the users, you end up like Gnome devs, going in a bunker and neglecting entirely what users actually expect or feel comfortable with. I've seen a lot of this. Clear requirements and user feedback always make for a better product. Added benefit, the user will reject the solution a lot less when he was involved in the process and gave his input.
That's also why a middle man helping to compromise between the what and the how usually drives the project towards a better outcome for the user. I call that a translator (although not in actual idiom), as geek language and operational language are as different as Finnish and Spanish or Greek and Chinese.
Leave a comment: