2 ms·
For me the biggest issue with making a good UX when developing is primarily that, by virtue of being the developer making the thing, I have a perfect mental mod
by magicalhippo 6y ago
For me the biggest issue with making a good UX when developing is primarily that, by virtue of being the developer making the thing, I have a perfect mental model of how the software works.
This makes it difficult to view the software from the POV of someone who is not in that position. It takes a conscious effort, and even then I find it difficult.
That's why I enjoy taking support calls every now and then, looking at screenshots or viewing the customer reproducing an issue over Teamviewer and having the customer explain what they think should happen and what actually happens. I might prod a bit, ask about why they do things a certain way, or to discover more about how they work and what they need our software to do.
Invariably I learn how we can improve some area of our application, making it more intuitive, less error prone or simply improve the workflow.
- rutthenut 6y agoI think your statements are the nub of the issue - as a developer, the view is of how the software is designed and operates internally. Users don't (normally) have that same view. This is why 'Use Cases' and/or 'User Stories' can help cross the divide between what the user needs the software to do, and the technical details of how it may do it internally. Of course, Use Cases or User Stories don't easily capture the UI/UX aspects, which would come from a broader level of business modelling in the application/user domain.