Module 1,2 Flashcards
What is UX?
What it feels like to use a product or system
3 types of design that make up a great product
- Functional Design
- Aesthetic Design
- Experience Design
3 ingredients to a successful product
- Viability
- Feasibility
- Desirability
Viability in product terms
A product must make money or save money for a business
Feasibility
A product has to be buildable by your own technical team or an external team
Desirability
There has to be a need or a want for the product. It has to be solving a problem and make the users want to reuse the product.
How do you identify desirability
- Identify if there is a problem / need for the product
- Ensure the product is ACTUALLY solving a problem
- Ensure the product solves the problem in a way that creates a great experience for the user. A product cannot just solve the problem functionally.
4 steps in a high-level UX process
- Research
- Design
- Build
- Test.
3 main steps in design cycle before building the product
- Design
- Prototype
- Validate
Benefits of design process
- Creates a clear vision
- Easy to visualise product in high fidelity
- Ideas can be iterated more cheaply in the design stage than trying to make amendments are the build stage
Considerations when adding features
- Each new feature add complexity and makes it less intuitive
- Can make an interface become cluttered and crowd out important features.
- Features must be well designed for a product to be easy to use.
- Don’t add features for the sake of it, features should be limited to what is required.
Dangers of features
- Features add complexity
- Features must be designed - adding time and money to a product
- Features must serve a purpose and solve a genuine problem.
Problems with software development
- Too much focus on features and not on genuine user goals
- Failure to follow the proper design process
- Failure to produce high fidelity designs
- Failure to prioritise
A successful product must…
Solve a genuine problem and be better than the existing solutions.
Follow every step of the product development lifecycle.
A product must be designed with….
clear user goals in mind. A clearly defined vision.
Software projects commonly fail due to….
No research and no design.
This can lead to large cost and time overruns.
Benefits of low fidelity design
- Reduces ambiguity - creates a clear vision for all involved
- Allow for designs to be validated
- Reduces risk of product failure
A use case is a ….
potential way in which a user may use your product
An edge case is a ….
rare use case that does not happen frequently
A product designer must prioritise…
the most common use case. Features to facilitate this use case must be front and centre and stand out to user.
Edge cases must be given less priority in the design process.
Progressive disclosure…
Only give user the information and features as and when they need it. Do not overload them.
Rules for prioritising:
Focus on the things that most people do most often. The features must be the most prominent on the product
Design Target (3 most important things to know about your user when designing a product)
Goals
Context of use
Behaviours
Paradox of Specificity
Design for a small number of use cases. Less worked involved and a more specific product is created.
The cabin bag is an example of a product designed for a small number of uses cases but ended up having huge mass market appeal.
Users prefer simple products that are really good at just doing one thing well.