Created
August 10, 2018 21:16
-
-
Save mjchamplin/f0426a47dd8010976a078d9fb80ad777 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Method | Teaser | | |
| ------------- |:-------------:| | |
| affinity diagram | Find natural relationships between data points and organize information with this collaborative sorting exercise. | | |
| design brief | Set requirements and expectations and define success for your project.| | |
| design values | Workshop a set of values to help you frame future conversations around product success.| | |
| experience attributes | Workshop descriptive words to help inform the visual direction of the project.| | |
| feedback session | Collect constructive feedback for designs and prototypes to help share risks and responsibilities with stakeholders.| | |
| human spectrogram | Establish a shared vocabulary and empower stakeholders to open up about where they stand on design decisions.| | |
| hypothesis definition | State assumptions as hypotheses which can be designed for and later validated with user testing. | | |
| interface inventory| Break designs into components to ensure consistency, eliminate redundancy, and create a catalog for use in code.| | |
| interviews | Talk to users to identify their needs and collect information to be synthesized through other research methods.| | |
| journey maps | Take a large-scale view of a product to identify pain points and define the happy path for your personas. | | |
| mood boards | Collect thematic images associated with a project's brand to serve as inspiration for visual studies.| | |
| personas | Create user archetypes based on interviews and conversations with real people to keep the design and development process user-focused. | | |
| sitemap| Define the scope, organization, and flow of your project.| | |
| style guide | Document the styles and components that make up the product to ensure consistency of design and code.| | |
| style tiles | Identify crucial interface components and iterate on visual styles. | | |
| usability test | Validate design decisions by observing users interacting with a product or feature.| | |
| visual design workshop | Collaborate with key stakeholders to define an approach to visual design.| | |
Author
mjchamplin
commented
Aug 10, 2018
Method | Teaser |
---|---|
affinity diagram | Find natural relationships between data points and organize information with this collaborative sorting exercise. |
design brief | Set requirements and expectations and define success for your project. |
design values | Workshop a set of values to help you frame future conversations around product success. |
experience attributes | Workshop descriptive words to help inform the visual direction of the project. |
feedback session | Collect constructive feedback for designs and prototypes to help share risks and responsibilities with stakeholders. |
human spectrogram | Establish a shared vocabulary and empower stakeholders to open up about where they stand on design decisions. |
hypothesis definition | State assumptions as hypotheses which can be designed for and later validated with user testing. |
interface inventory | Break designs into components to ensure consistency, eliminate redundancy, and create a catalog for use in code. |
interviews | Talk to users to identify their needs and collect information to be synthesized through other research methods. |
journey maps | Take a large-scale view of a product to identify pain points and define the happy path for your personas. |
mood boards | Collect thematic images associated with a project's brand to serve as inspiration for visual studies. |
personas | Create user archetypes based on interviews and conversations with real people to keep the design and development process user-focused. |
sitemap | Define the scope, organization, and flow of your project. |
style guide | Document the styles and components that make up the product to ensure consistency of design and code. |
style tiles | Identify crucial interface components and iterate on visual styles. |
usability test | Validate design decisions by observing users interacting with a product or feature. |
visual design workshop | Collaborate with key stakeholders to define an approach to visual design. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment