233 karma · joined April 6, 2010
The "Product-Minded Software Engineer" is someone who has the opportunity to be informed by the analysis of the user research data, and offers his or her technical support to translate ideas and design in a working product or service.
UXTools.com just relased the results of the 2018 Design Tools Survey [2].
In november, Jeff Sauro published "the methods ux professionals use" post [3]. There, you can find an exaustive coverage of the most important methods and deliverables in the field.
[0] https://github.com/bussolon/awesome-ux/blob/master/books.md [1] https://github.com/bussolon/awesome-ux/issues/3 [2] http://uxtools.co/survey-2018 [3] https://measuringu.com/ux-methods-2018/
- an exploratory phase, where the designer interviews the stakeholders, analyzes the current product (if it is a redesign), makes a benchmark of the competing products and services;
- a research phase, where the designer involves actual or potential users to understand their needs, goals, their knowledge, their behaviors; she does interviews, observations, and uses methods like the laddering, the free listing, the card sorting, the task analysis and so on
- the raw results of the research are documented in a number of deliverables:
* personae
* scenarios
* customer journeys / experience maps
* conceptualizations
* taxonomies and navigation trees
- the research is translated into the design of the product, producing wireframes or low fidelity prototypes, designing the macro and the micro information architecture, the interaction, the navigation;
- a design system should be adopted and / or developed, identifying the components, the colors, the typography, the tone of voice
- a high fidelity prototype applies the design system to the low fidelity prototipes
- everything should be tested with the users, in different moments: competitive testing (to test the competitors' products), exploratory testing, confirmatory testing; prototypes should also be evaluated to verify the conformity to the standards and to the design system / style guides;This is UX design (different experts will describe it in slightly different ways, but the structure remains the same).
I'm obviously aware that this process would be a big effort for a side project. But it's very important to keep in mind that this is the right approach, and in the long run, the process will decrease the risk of failure.
I couldn't help to notice the involuntary pun. What you say is sadly true, and it is a sort of cognitive blindness.
- Consumer A already chose what she wants, and she just needs to find it out. - Consumer B knows her preferences, but she needs to make the choice. - Consumer C is not aware of which attributes are important in the decision process.
You are a consumer A, so this simplification did not help YOU. It did help consumers B and consumer C.
http://www.hyperlabs.net/ergonomia/presentazioni/euroia11/ the slides of my presentation at Euro IA 2011: Designing Interactions that Help Customers in Decision Making