I guess my point is that there are reasons for it's done a certain way, even if it's not the best; and if you're unfamiliar with that mindset it can seem incredibly stupid and without merit whatsoever.Agreed. Is there such a thing as software development perfection? or maybe it is relevant to the application at hand.. However, I do think it is important to keep commonly accepted UX/design principles in mind on any project, even when facing highly customized/pressure situations.. somewhat like finding a working balance between sound design and precise functionality. IMO, systems that favor one over the other simply don't make it, or are more susceptible to becoming 'obsolete' in the long run.. (which is fine if a short-term desired goal has been achieved)
In the end, it's the case of companies defining their service based on existing solutions and hoping it meets user needs. Instead, companies should identify user needs first and then decide on the features.I could not agree more with this statement. A lot of businesses out there fall into the same pitfall. They provide services assuming users are going to like it, only to discover that users' interests actually have different priorities. That's is why I really like business models that let their products be shaped by evolving user needs.. starting simple, continuously providing users with features that are being needed/requested the most, in order of escalating complexity (simplest most frequently requested features first). I believe such models have higher likelihood of success, mostly because they save time, $$ and have higher rate of appreciation/acceptance by their end-user community - all key elements in a successful product launch.
© 2023 Created by Daniel Leuck. Powered by
You need to be a member of TechHui to add comments!