|
| 1 | +created_by: Misjohns |
| 2 | +version: 3 |
| 3 | +domain: user_experience |
| 4 | +document_outline: >- |
| 5 | + UX principles are the fundamentals that build a strong foundation for open |
| 6 | + design to thrive. We use these principles to keep products aligned on a shared |
| 7 | + vision. |
| 8 | +seed_examples: |
| 9 | + - context: >- |
| 10 | + Start intentionally. Identify the problem well before you start to solve |
| 11 | + it. Know why you're designing. If you don't, ask questions to gain |
| 12 | + insights. Those answers will lead to better questions or new directions. |
| 13 | + questions_and_answers: |
| 14 | + - question: How should I start a design project? |
| 15 | + answer: Identify the problem well before you start to solve it |
| 16 | + - question: Why is it important to ask questions? |
| 17 | + answer: To gain insights and understand why you're designing. |
| 18 | + - question: How will asking questions help? |
| 19 | + answer: They will lead to better questions or new directions |
| 20 | + - context: >- |
| 21 | + Lean on research. Know who you’re designing for and what they need; talk |
| 22 | + to them if you can. When you understand their motivations, you’re able to |
| 23 | + demonstrate real empathy for the user, and the most impactful choices |
| 24 | + become clear. |
| 25 | + questions_and_answers: |
| 26 | + - question: Why is it important to have empathy for the user? |
| 27 | + answer: To understand their motivations and needs. |
| 28 | + - question: How do you learn about the user? |
| 29 | + answer: Through research. |
| 30 | + - question: What's a good way to gain knowledge about the user? |
| 31 | + answer: To know who you’re designing for it's important to talk to the users. |
| 32 | + - context: >- |
| 33 | + Design with bravery. Take risks, even when it’s scary or difficult. |
| 34 | + Suggest something unexpected, remove something unnecessary, or even know |
| 35 | + when to try again — facing the challenge results in the best work |
| 36 | + possible. |
| 37 | + questions_and_answers: |
| 38 | + - question: What can be scary in design? |
| 39 | + answer: Taking risks. |
| 40 | + - question: What are some brave design moves? |
| 41 | + answer: Suggest something unexpected, remove something unnecessary. |
| 42 | + - question: Can design be scary? |
| 43 | + answer: Yes, design can be difficult and takes bravery. |
| 44 | + - context: >- |
| 45 | + Red Hatters believe in transparency, collaboration, and inclusion. These |
| 46 | + principles aren’t just for creating technology — they shape how we design, |
| 47 | + too. |
| 48 | + questions_and_answers: |
| 49 | + - question: What do Ret Hatters believe in? |
| 50 | + answer: They believe in believe in transparency, collaboration, and inclusion. |
| 51 | + - question: What are the principles Ret Hatters use in their design process? |
| 52 | + answer: >- |
| 53 | + Red Hatters use the principles of transparency, collaboration, and |
| 54 | + inclusion to shape how they design. |
| 55 | + - question: What shapes the way they design? |
| 56 | + answer: >- |
| 57 | + Their principles for creating technology - transparency, |
| 58 | + collaboration, and inclusion. |
| 59 | + - context: >- |
| 60 | + How we work. Open design is built on collaboration. It's a conversation |
| 61 | + between diverse voices. It's about listening to what our community needs, |
| 62 | + taking that feedback, and creating systems that work together, across |
| 63 | + teams and contexts. Open design creates helpful and accessible experiences |
| 64 | + for real people. |
| 65 | + questions_and_answers: |
| 66 | + - question: What is open design built on? |
| 67 | + answer: Collaboration. |
| 68 | + - question: What is collaboration? |
| 69 | + answer: >- |
| 70 | + It's having conversations to listen to the needs of a community and |
| 71 | + using that feedback to create a design. |
| 72 | + - question: What does open design create? |
| 73 | + answer: Open design creates helpful and accessible experiences. |
| 74 | +document: |
| 75 | + repo: https://github.com/Misjohns/taxonomy-knowledge-docs |
| 76 | + commit: 0022286dba7226d79efebb424ddb7cf2696eb2a6 |
| 77 | + patterns: |
| 78 | + - Design_at_Red_Hat-20241107T210400607.md |
0 commit comments