2 ms·
There certainly can be a disconnect which impacts a developers ability to see what a user wants, but even if there is no disconnect, bad software can still resu
by singular 15y ago
There certainly can be a disconnect which impacts a developers ability to see what a user wants, but even if there is no disconnect, bad software can still result.
Consider internal software - there is literally no disconnect whatsoever, but very often the software is terrible. This is relevant because it raises the issue that the business simply may not care about quality, and thus putting in the work required to make the thing good might simply not be possible.
There are many, many factors involved in determining whether software sucks or not, and key is the understanding or lack thereof of what the users want and need, agreed. But keep in mind, there is a big difference between seeing what the users' need superficially vs. understanding clearly and deeply what the users' need and implementing it well.
- benohear 15y agoAt the risk of sounding like a broken record: Paper protoyping. Even if it's for yourself, it never feels the same to interact with a product than you think it will. This holds even more true when it's for other people. For internal projects, investment is obviously a huge problem, and once you've built the wrong thing you're unlikely to get more money to do it right. But for a given price point, there's a huge range of quality you can obtain. Paper protoyping helps you maximize that at very low expense.