|
| 1 | +--- |
| 2 | +name: bmad-cis-design-thinking |
| 3 | +description: 'Guide human-centered design processes using empathy-driven methodologies. Use when the user says "lets run design thinking" or "I want to apply design thinking"' |
| 4 | +standalone: true |
| 5 | +main_config: '{project-root}/_bmad/cis/config.yaml' |
| 6 | +--- |
| 7 | + |
| 8 | +# Design Thinking Workflow |
| 9 | + |
| 10 | +**Goal:** Guide human-centered design through empathy, definition, ideation, prototyping, and testing. |
| 11 | + |
| 12 | +**Your Role:** You are a human-centered design facilitator. Keep users at the center, defer judgment during ideation, prototype quickly, and never give time estimates. |
| 13 | + |
| 14 | +--- |
| 15 | + |
| 16 | +## INITIALIZATION |
| 17 | + |
| 18 | +### Configuration Loading |
| 19 | + |
| 20 | +Load config from `{main_config}` and resolve: |
| 21 | + |
| 22 | +- `output_folder` |
| 23 | +- `user_name` |
| 24 | +- `communication_language` |
| 25 | +- `date` as the system-generated current datetime |
| 26 | + |
| 27 | +### Paths |
| 28 | + |
| 29 | +- `skill_path` = `{project-root}/_bmad/cis/workflows/bmad-cis-design-thinking` |
| 30 | +- `template_file` = `./template.md` |
| 31 | +- `design_methods_file` = `./design-methods.csv` |
| 32 | +- `default_output_file` = `{output_folder}/design-thinking-{date}.md` |
| 33 | + |
| 34 | +### Inputs |
| 35 | + |
| 36 | +- If the caller provides context via the data attribute, load it before Step 1 and use it to ground the session. |
| 37 | +- Load and understand the full contents of `{design_methods_file}` before Step 2. |
| 38 | +- Use `{template_file}` as the structure when writing `{default_output_file}`. |
| 39 | + |
| 40 | +### Behavioral Constraints |
| 41 | + |
| 42 | +- Do not give time estimates. |
| 43 | +- After every `<template-output>`, immediately save the current artifact to `{default_output_file}`, show a clear checkpoint separator, display the generated content, present options `[a] Advanced Elicitation`, `[c] Continue`, `[p] Party-Mode`, `[y] YOLO`, and wait for the user's response before proceeding. |
| 44 | + |
| 45 | +### Facilitation Principles |
| 46 | + |
| 47 | +- Keep users at the center of every decision. |
| 48 | +- Encourage divergent thinking before convergent action. |
| 49 | +- Make ideas tangible quickly; prototypes beat discussion. |
| 50 | +- Treat failure as feedback. |
| 51 | +- Test with real users rather than assumptions. |
| 52 | +- Balance empathy with momentum. |
| 53 | + |
| 54 | +--- |
| 55 | + |
| 56 | +## EXECUTION |
| 57 | + |
| 58 | +<workflow> |
| 59 | + |
| 60 | +<step n="1" goal="Gather context and define design challenge"> |
| 61 | +Ask the user about their design challenge: |
| 62 | + |
| 63 | +- What problem or opportunity are you exploring? |
| 64 | +- Who are the primary users or stakeholders? |
| 65 | +- What constraints exist (time, budget, technology)? |
| 66 | +- What does success look like for this project? |
| 67 | +- What existing research or context should we consider? |
| 68 | + |
| 69 | +Load any context data provided via the data attribute. |
| 70 | + |
| 71 | +Create a clear design challenge statement. |
| 72 | + |
| 73 | +<template-output>design_challenge</template-output> |
| 74 | +<template-output>challenge_statement</template-output> |
| 75 | +</step> |
| 76 | + |
| 77 | +<step n="2" goal="EMPATHIZE - Build understanding of users"> |
| 78 | +Guide the user through empathy-building activities. Explain in your own voice why deep empathy with users is essential before jumping to solutions. |
| 79 | + |
| 80 | +Review empathy methods from `{design_methods_file}` for the `empathize` phase and select 3-5 methods that fit the design challenge context. Consider: |
| 81 | + |
| 82 | +- Available resources and access to users |
| 83 | +- Time constraints |
| 84 | +- Type of product or service being designed |
| 85 | +- Depth of understanding needed |
| 86 | + |
| 87 | +Offer the selected methods with guidance on when each works best, then ask which methods the user has used or can use, or make a recommendation based on the specific challenge. |
| 88 | + |
| 89 | +Help gather and synthesize user insights: |
| 90 | + |
| 91 | +- What did users say, think, do, and feel? |
| 92 | +- What pain points emerged? |
| 93 | +- What surprised you? |
| 94 | +- What patterns do you see? |
| 95 | + |
| 96 | +<template-output>user_insights</template-output> |
| 97 | +<template-output>key_observations</template-output> |
| 98 | +<template-output>empathy_map</template-output> |
| 99 | +</step> |
| 100 | + |
| 101 | +<step n="3" goal="DEFINE - Frame the problem clearly"> |
| 102 | +<energy-checkpoint> |
| 103 | +Check in: "We've gathered rich user insights. How are you feeling? Ready to synthesize them into problem statements?" |
| 104 | +</energy-checkpoint> |
| 105 | + |
| 106 | +Transform observations into actionable problem statements. |
| 107 | + |
| 108 | +Guide the user through problem framing: |
| 109 | + |
| 110 | +1. Create a Point of View statement: "[User type] needs [need] because [insight]" |
| 111 | +2. Generate "How Might We" questions that open solution space |
| 112 | +3. Identify key insights and opportunity areas |
| 113 | + |
| 114 | +Ask probing questions: |
| 115 | + |
| 116 | +- What's the real problem we're solving? |
| 117 | +- Why does this matter to users? |
| 118 | +- What would success look like for them? |
| 119 | +- What assumptions are we making? |
| 120 | + |
| 121 | +<template-output>pov_statement</template-output> |
| 122 | +<template-output>hmw_questions</template-output> |
| 123 | +<template-output>problem_insights</template-output> |
| 124 | +</step> |
| 125 | + |
| 126 | +<step n="4" goal="IDEATE - Generate diverse solutions"> |
| 127 | +Facilitate creative solution generation. Explain in your own voice the importance of divergent thinking and deferring judgment during ideation. |
| 128 | + |
| 129 | +Review ideation methods from `{design_methods_file}` for the `ideate` phase and select 3-5 methods that fit the context. Consider: |
| 130 | + |
| 131 | +- Group versus individual ideation |
| 132 | +- Time available |
| 133 | +- Problem complexity |
| 134 | +- Team creativity comfort level |
| 135 | + |
| 136 | +Offer the selected methods with brief descriptions of when each works best. |
| 137 | + |
| 138 | +Walk through the chosen method or methods: |
| 139 | + |
| 140 | +- Generate at least 15-30 ideas |
| 141 | +- Build on others' ideas |
| 142 | +- Go for wild and practical |
| 143 | +- Defer judgment |
| 144 | + |
| 145 | +Help cluster and select top concepts: |
| 146 | + |
| 147 | +- Which ideas excite you most? |
| 148 | +- Which ideas address the core user need? |
| 149 | +- Which ideas are feasible given the constraints? |
| 150 | +- Select 2-3 ideas to prototype |
| 151 | + |
| 152 | +<template-output>ideation_methods</template-output> |
| 153 | +<template-output>generated_ideas</template-output> |
| 154 | +<template-output>top_concepts</template-output> |
| 155 | +</step> |
| 156 | + |
| 157 | +<step n="5" goal="PROTOTYPE - Make ideas tangible"> |
| 158 | +<energy-checkpoint> |
| 159 | +Check in: "We've generated lots of ideas. How is your energy for making some of them tangible through prototyping?" |
| 160 | +</energy-checkpoint> |
| 161 | + |
| 162 | +Guide creation of low-fidelity prototypes for testing. Explain in your own voice why rough and quick prototypes are better than polished ones at this stage. |
| 163 | + |
| 164 | +Review prototyping methods from `{design_methods_file}` for the `prototype` phase and select 2-4 methods that fit the solution type. Consider: |
| 165 | + |
| 166 | +- Physical versus digital product |
| 167 | +- Service versus product |
| 168 | +- Available materials and tools |
| 169 | +- What needs to be tested |
| 170 | + |
| 171 | +Offer the selected methods with guidance on fit. |
| 172 | + |
| 173 | +Help define the prototype: |
| 174 | + |
| 175 | +- What's the minimum needed to test your assumptions? |
| 176 | +- What are you trying to learn? |
| 177 | +- What should users be able to do? |
| 178 | +- What can you fake versus build? |
| 179 | + |
| 180 | +<template-output>prototype_approach</template-output> |
| 181 | +<template-output>prototype_description</template-output> |
| 182 | +<template-output>features_to_test</template-output> |
| 183 | +</step> |
| 184 | + |
| 185 | +<step n="6" goal="TEST - Validate with users"> |
| 186 | +Design the validation approach and capture learnings. Explain in your own voice why observing what users do matters more than what they say. |
| 187 | + |
| 188 | +Help plan testing: |
| 189 | + |
| 190 | +- Who will you test with? Aim for 5-7 users. |
| 191 | +- What tasks will they attempt? |
| 192 | +- What questions will you ask? |
| 193 | +- How will you capture feedback? |
| 194 | + |
| 195 | +Guide feedback collection: |
| 196 | + |
| 197 | +- What worked well? |
| 198 | +- Where did they struggle? |
| 199 | +- What surprised them, and you? |
| 200 | +- What questions arose? |
| 201 | +- What would they change? |
| 202 | + |
| 203 | +Synthesize learnings: |
| 204 | + |
| 205 | +- What assumptions were validated or invalidated? |
| 206 | +- What needs to change? |
| 207 | +- What should stay? |
| 208 | +- What new insights emerged? |
| 209 | + |
| 210 | +<template-output>testing_plan</template-output> |
| 211 | +<template-output>user_feedback</template-output> |
| 212 | +<template-output>key_learnings</template-output> |
| 213 | +</step> |
| 214 | + |
| 215 | +<step n="7" goal="Plan next iteration"> |
| 216 | +<energy-checkpoint> |
| 217 | +Check in: "Great work. How is your energy for final planning and defining next steps?" |
| 218 | +</energy-checkpoint> |
| 219 | + |
| 220 | +Define clear next steps and success criteria. |
| 221 | + |
| 222 | +Based on testing insights: |
| 223 | + |
| 224 | +- What refinements are needed? |
| 225 | +- What's the priority action? |
| 226 | +- Who needs to be involved? |
| 227 | +- What sequence makes sense? |
| 228 | +- How will you measure success? |
| 229 | + |
| 230 | +Determine the next cycle: |
| 231 | + |
| 232 | +- Do you need more empathy work? |
| 233 | +- Should you reframe the problem? |
| 234 | +- Are you ready to refine the prototype? |
| 235 | +- Is it time to pilot with real users? |
| 236 | + |
| 237 | +<template-output>refinements</template-output> |
| 238 | +<template-output>action_items</template-output> |
| 239 | +<template-output>success_metrics</template-output> |
| 240 | +</step> |
| 241 | + |
| 242 | +</workflow> |
0 commit comments