@comfanion/workflow 4.38.4-dev.0 → 4.39.0-dev.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/bin/cli.js +52 -529
- package/package.json +1 -1
- package/src/build-info.json +2 -2
- package/src/opencode/skills/acceptance-criteria/SKILL.md +58 -176
- package/src/opencode/skills/architecture-design/SKILL.md +86 -576
- package/src/opencode/skills/archiving/SKILL.md +60 -140
- package/src/opencode/skills/coding-standards/SKILL.md +113 -434
- package/src/opencode/skills/coding-standards/what-to-document.md +512 -0
- package/src/opencode/skills/database-design/SKILL.md +94 -778
- package/src/opencode/skills/database-design/indexing.md +187 -0
- package/src/opencode/skills/database-design/migrations.md +239 -0
- package/src/opencode/skills/database-design/schema-design.md +319 -0
- package/src/opencode/skills/doc-todo/SKILL.md +35 -27
- package/src/opencode/skills/epic-writing/SKILL.md +156 -244
- package/src/opencode/skills/epic-writing/template.md +11 -1
- package/src/opencode/skills/methodologies/SKILL.md +91 -354
- package/src/opencode/skills/methodologies/define.md +336 -0
- package/src/opencode/skills/methodologies/diagnose.md +374 -0
- package/src/opencode/skills/methodologies/empathize.md +253 -0
- package/src/opencode/skills/methodologies/ideate.md +458 -0
- package/src/opencode/skills/prd-writing/SKILL.md +162 -366
- package/src/opencode/skills/prd-writing/template.md +178 -48
- package/src/opencode/skills/requirements-gathering/SKILL.md +102 -117
- package/src/opencode/skills/requirements-gathering/template.md +97 -17
- package/src/opencode/skills/sprint-planning/SKILL.md +76 -225
- package/src/opencode/skills/sprint-planning/template.yaml +8 -0
- package/src/opencode/skills/story-writing/SKILL.md +76 -210
- package/src/opencode/skills/story-writing/template.md +10 -1
- package/src/opencode/skills/test-design/SKILL.md +78 -84
- package/src/opencode/skills/test-design/test-strategy.md +279 -0
- package/src/opencode/skills/test-design/unit-tests-mocking.md +247 -0
- package/src/opencode/skills/test-design/unit-tests-patterns.md +181 -0
- package/src/opencode/skills/test-design/unit-tests.md +117 -0
- package/src/opencode/skills/unit-writing/SKILL.md +119 -377
- package/src/opencode/skills/module-documentation/SKILL.md +0 -224
- package/src/opencode/skills/module-documentation/template.md +0 -139
- /package/src/opencode/skills/test-design/{template-integration.md → templates/template-integration.md} +0 -0
- /package/src/opencode/skills/test-design/{template-module.md → templates/template-module.md} +0 -0
|
@@ -0,0 +1,253 @@
|
|
|
1
|
+
# Empathize Methods
|
|
2
|
+
|
|
3
|
+
Methods for understanding users, their needs, emotions, and behaviors.
|
|
4
|
+
|
|
5
|
+
## User Interviews
|
|
6
|
+
|
|
7
|
+
**Purpose:** Deep conversations to uncover needs, frustrations, and motivations
|
|
8
|
+
|
|
9
|
+
**When to use:**
|
|
10
|
+
- Starting new project
|
|
11
|
+
- Validating assumptions
|
|
12
|
+
- Understanding user context
|
|
13
|
+
- Discovering pain points
|
|
14
|
+
|
|
15
|
+
**How to conduct:**
|
|
16
|
+
|
|
17
|
+
1. **Prepare:**
|
|
18
|
+
- Define research goals
|
|
19
|
+
- Identify user segments
|
|
20
|
+
- Prepare open-ended questions
|
|
21
|
+
- Schedule 30-60 min sessions
|
|
22
|
+
|
|
23
|
+
2. **Interview Structure:**
|
|
24
|
+
```
|
|
25
|
+
Opening (5 min):
|
|
26
|
+
- Build rapport
|
|
27
|
+
- Explain purpose
|
|
28
|
+
- Get consent
|
|
29
|
+
|
|
30
|
+
Main Questions (40 min):
|
|
31
|
+
- "Tell me about the last time you..."
|
|
32
|
+
- "Walk me through your process for..."
|
|
33
|
+
- "What frustrates you most about..."
|
|
34
|
+
- "What would make this easier?"
|
|
35
|
+
- "Why is that important to you?"
|
|
36
|
+
|
|
37
|
+
Closing (5 min):
|
|
38
|
+
- "Is there anything else I should know?"
|
|
39
|
+
- Thank participant
|
|
40
|
+
```
|
|
41
|
+
|
|
42
|
+
3. **Question Types:**
|
|
43
|
+
- **Context:** "Tell me about your role..."
|
|
44
|
+
- **Behavior:** "Walk me through how you..."
|
|
45
|
+
- **Emotion:** "How did that make you feel?"
|
|
46
|
+
- **Motivation:** "Why is that important?"
|
|
47
|
+
- **Pain Points:** "What frustrates you about..."
|
|
48
|
+
- **Ideal State:** "In a perfect world, what would..."
|
|
49
|
+
|
|
50
|
+
4. **Best Practices:**
|
|
51
|
+
- Ask "Why?" to dig deeper
|
|
52
|
+
- Listen more than talk (80/20 rule)
|
|
53
|
+
- Avoid leading questions
|
|
54
|
+
- Record with permission
|
|
55
|
+
- Take notes on emotions
|
|
56
|
+
- Look for patterns across interviews
|
|
57
|
+
|
|
58
|
+
**Output:** Interview notes, quotes, observations
|
|
59
|
+
|
|
60
|
+
---
|
|
61
|
+
|
|
62
|
+
## Empathy Mapping
|
|
63
|
+
|
|
64
|
+
**Purpose:** Visualize what users say, think, do, and feel
|
|
65
|
+
|
|
66
|
+
**When to use:**
|
|
67
|
+
- After user interviews
|
|
68
|
+
- To synthesize research
|
|
69
|
+
- To build shared understanding
|
|
70
|
+
- Before defining problems
|
|
71
|
+
|
|
72
|
+
**Structure:**
|
|
73
|
+
|
|
74
|
+
```
|
|
75
|
+
┌─────────────────────────────────────┐
|
|
76
|
+
│ USER: [Name/Persona] │
|
|
77
|
+
├─────────────────┬───────────────────┤
|
|
78
|
+
│ SAYS │ THINKS │
|
|
79
|
+
│ │ │
|
|
80
|
+
│ Direct quotes │ Unspoken thoughts │
|
|
81
|
+
│ from interviews │ and beliefs │
|
|
82
|
+
│ │ │
|
|
83
|
+
├─────────────────┼───────────────────┤
|
|
84
|
+
│ DOES │ FEELS │
|
|
85
|
+
│ │ │
|
|
86
|
+
│ Observable │ Emotional state │
|
|
87
|
+
│ behaviors │ (use emojis) │
|
|
88
|
+
│ │ │
|
|
89
|
+
└─────────────────┴───────────────────┘
|
|
90
|
+
```
|
|
91
|
+
|
|
92
|
+
**How to create:**
|
|
93
|
+
|
|
94
|
+
1. **Identify User:** Choose specific user or persona
|
|
95
|
+
2. **Fill Quadrants:**
|
|
96
|
+
- **Says:** Direct quotes from interviews
|
|
97
|
+
- **Thinks:** Inferred thoughts, beliefs, concerns
|
|
98
|
+
- **Does:** Observable actions, behaviors
|
|
99
|
+
- **Feels:** Emotions (frustrated 😤, anxious 😰, happy 😊)
|
|
100
|
+
|
|
101
|
+
3. **Look for Contradictions:**
|
|
102
|
+
- Says vs Thinks (what they don't say)
|
|
103
|
+
- Does vs Feels (actions vs emotions)
|
|
104
|
+
|
|
105
|
+
4. **Extract Insights:**
|
|
106
|
+
- What patterns emerge?
|
|
107
|
+
- What contradictions exist?
|
|
108
|
+
- What needs are unmet?
|
|
109
|
+
|
|
110
|
+
**Example:**
|
|
111
|
+
|
|
112
|
+
```markdown
|
|
113
|
+
## Empathy Map: Busy Merchant
|
|
114
|
+
|
|
115
|
+
| Says | Thinks |
|
|
116
|
+
|------|--------|
|
|
117
|
+
| "I don't have time for this" | "This is too complicated" |
|
|
118
|
+
| "Just let me finish" | "Why do they need all this info?" |
|
|
119
|
+
| "Can't I skip this?" | "I hope I don't mess this up" |
|
|
120
|
+
|
|
121
|
+
| Does | Feels |
|
|
122
|
+
|------|-------|
|
|
123
|
+
| Skips optional fields | Frustrated 😤 |
|
|
124
|
+
| Rushes through forms | Anxious 😰 |
|
|
125
|
+
| Abandons at payment | Overwhelmed 😵 |
|
|
126
|
+
|
|
127
|
+
**Insight:** Merchants value speed over completeness. They feel anxious about making mistakes and frustrated by unnecessary complexity.
|
|
128
|
+
```
|
|
129
|
+
|
|
130
|
+
**Output:** Visual map, insights, user needs
|
|
131
|
+
|
|
132
|
+
---
|
|
133
|
+
|
|
134
|
+
## Journey Mapping
|
|
135
|
+
|
|
136
|
+
**Purpose:** Map user's experience across all touchpoints over time
|
|
137
|
+
|
|
138
|
+
**When to use:**
|
|
139
|
+
- Understanding full user experience
|
|
140
|
+
- Identifying pain points
|
|
141
|
+
- Finding opportunities
|
|
142
|
+
- Aligning team on user flow
|
|
143
|
+
|
|
144
|
+
**Structure:**
|
|
145
|
+
|
|
146
|
+
```
|
|
147
|
+
Stage → Awareness → Consideration → Action → Use → Support
|
|
148
|
+
↓ ↓ ↓ ↓ ↓
|
|
149
|
+
Actions [what user does at each stage]
|
|
150
|
+
↓ ↓ ↓ ↓ ↓
|
|
151
|
+
Emotions 😊 😐 😤 😰 [how user feels]
|
|
152
|
+
↓ ↓ ↓ ↓ ↓
|
|
153
|
+
Pain Points [problems, frustrations]
|
|
154
|
+
↓ ↓ ↓ ↓ ↓
|
|
155
|
+
Opportunities [how to improve]
|
|
156
|
+
```
|
|
157
|
+
|
|
158
|
+
**How to create:**
|
|
159
|
+
|
|
160
|
+
1. **Define Stages:**
|
|
161
|
+
- **Awareness:** User discovers need
|
|
162
|
+
- **Consideration:** User researches options
|
|
163
|
+
- **Action:** User makes decision
|
|
164
|
+
- **Use:** User uses product
|
|
165
|
+
- **Support:** User needs help
|
|
166
|
+
|
|
167
|
+
2. **For Each Stage, Document:**
|
|
168
|
+
- **Actions:** What user does
|
|
169
|
+
- **Touchpoints:** Where interaction happens
|
|
170
|
+
- **Emotions:** How user feels (use emojis)
|
|
171
|
+
- **Pain Points:** Problems, frustrations
|
|
172
|
+
- **Opportunities:** How to improve
|
|
173
|
+
|
|
174
|
+
3. **Identify Patterns:**
|
|
175
|
+
- Where do emotions drop? (pain points)
|
|
176
|
+
- Where are gaps in experience?
|
|
177
|
+
- What causes frustration?
|
|
178
|
+
- What delights users?
|
|
179
|
+
|
|
180
|
+
**Example:**
|
|
181
|
+
|
|
182
|
+
```markdown
|
|
183
|
+
## Journey Map: Merchant Onboarding
|
|
184
|
+
|
|
185
|
+
### Stage 1: Awareness
|
|
186
|
+
**Actions:** Hears about platform from friend
|
|
187
|
+
**Emotions:** Curious 🤔, Hopeful 😊
|
|
188
|
+
**Pain Points:** None yet
|
|
189
|
+
**Opportunities:** Clear value proposition
|
|
190
|
+
|
|
191
|
+
### Stage 2: Consideration
|
|
192
|
+
**Actions:** Visits website, reads features, compares pricing
|
|
193
|
+
**Emotions:** Interested 😊, Uncertain 😐
|
|
194
|
+
**Pain Points:** Too many options, unclear pricing
|
|
195
|
+
**Opportunities:** Simplify pricing, add comparison table
|
|
196
|
+
|
|
197
|
+
### Stage 3: Action (Sign Up)
|
|
198
|
+
**Actions:** Fills registration form, verifies email
|
|
199
|
+
**Emotions:** Anxious 😰, Frustrated 😤
|
|
200
|
+
**Pain Points:** Form too long, asks for unnecessary data
|
|
201
|
+
**Opportunities:** ⭐ Reduce form fields, add progress indicator
|
|
202
|
+
|
|
203
|
+
### Stage 4: Use (First Product)
|
|
204
|
+
**Actions:** Creates first product listing
|
|
205
|
+
**Emotions:** Confused 😕, Overwhelmed 😵
|
|
206
|
+
**Pain Points:** Unclear what's required, no guidance
|
|
207
|
+
**Opportunities:** ⭐ Add onboarding wizard, inline help
|
|
208
|
+
|
|
209
|
+
### Stage 5: Support
|
|
210
|
+
**Actions:** Searches help docs, contacts support
|
|
211
|
+
**Emotions:** Frustrated 😤, Relieved 😌 (after help)
|
|
212
|
+
**Pain Points:** Hard to find answers
|
|
213
|
+
**Opportunities:** Better search, contextual help
|
|
214
|
+
```
|
|
215
|
+
|
|
216
|
+
**Output:** Journey map, prioritized pain points, opportunities
|
|
217
|
+
|
|
218
|
+
---
|
|
219
|
+
|
|
220
|
+
## When to Use Each Method
|
|
221
|
+
|
|
222
|
+
| Method | Best For | Time | Output |
|
|
223
|
+
|--------|----------|------|--------|
|
|
224
|
+
| **User Interviews** | Deep understanding, discovery | 30-60 min/user | Quotes, observations |
|
|
225
|
+
| **Empathy Mapping** | Synthesizing research, building empathy | 30-60 min | Visual map, insights |
|
|
226
|
+
| **Journey Mapping** | Understanding full experience, finding gaps | 1-2 hours | Journey map, opportunities |
|
|
227
|
+
|
|
228
|
+
**Typical Workflow:**
|
|
229
|
+
```
|
|
230
|
+
User Interviews → Empathy Map → Journey Map → Requirements
|
|
231
|
+
```
|
|
232
|
+
|
|
233
|
+
---
|
|
234
|
+
|
|
235
|
+
## Tips
|
|
236
|
+
|
|
237
|
+
**User Interviews:**
|
|
238
|
+
- Interview 5-8 users per segment (patterns emerge)
|
|
239
|
+
- Record with permission
|
|
240
|
+
- Ask "Why?" at least 3 times
|
|
241
|
+
- Look for emotions, not just facts
|
|
242
|
+
|
|
243
|
+
**Empathy Mapping:**
|
|
244
|
+
- Do it as a team (shared understanding)
|
|
245
|
+
- Use real quotes from interviews
|
|
246
|
+
- Focus on one user at a time
|
|
247
|
+
- Look for contradictions (Says vs Thinks)
|
|
248
|
+
|
|
249
|
+
**Journey Mapping:**
|
|
250
|
+
- Start with current state (as-is)
|
|
251
|
+
- Then create future state (to-be)
|
|
252
|
+
- Use emojis for emotions (visual impact)
|
|
253
|
+
- Prioritize opportunities (⭐ = high impact)
|
|
@@ -0,0 +1,458 @@
|
|
|
1
|
+
# Ideate Methods
|
|
2
|
+
|
|
3
|
+
Methods for generating creative solutions.
|
|
4
|
+
|
|
5
|
+
## Brainstorming
|
|
6
|
+
|
|
7
|
+
**Purpose:** Generate large quantity of diverse ideas without judgment
|
|
8
|
+
|
|
9
|
+
**When to use:**
|
|
10
|
+
- After defining problem (HMW)
|
|
11
|
+
- Need many options
|
|
12
|
+
- Team ideation
|
|
13
|
+
- Breaking mental blocks
|
|
14
|
+
|
|
15
|
+
**Rules:**
|
|
16
|
+
|
|
17
|
+
1. **Defer judgment** - No criticism during generation
|
|
18
|
+
2. **Go for quantity** - Aim for 50+ ideas
|
|
19
|
+
3. **Encourage wild ideas** - Crazy ideas spark breakthroughs
|
|
20
|
+
4. **Build on others** - "Yes, and..." not "Yes, but..."
|
|
21
|
+
5. **Stay focused** - Keep HMW question visible
|
|
22
|
+
6. **Be visual** - Sketch, don't just write
|
|
23
|
+
|
|
24
|
+
**How to run:**
|
|
25
|
+
|
|
26
|
+
1. **Setup (5 min):**
|
|
27
|
+
- Write HMW question on board
|
|
28
|
+
- Review rules
|
|
29
|
+
- Set timer (15-30 min)
|
|
30
|
+
|
|
31
|
+
2. **Generate (15-30 min):**
|
|
32
|
+
- Everyone writes ideas on sticky notes
|
|
33
|
+
- One idea per note
|
|
34
|
+
- Call out ideas to spark others
|
|
35
|
+
- Build on what you hear
|
|
36
|
+
|
|
37
|
+
3. **Share (10 min):**
|
|
38
|
+
- Post all ideas on wall
|
|
39
|
+
- Quick read-through
|
|
40
|
+
- No discussion yet
|
|
41
|
+
|
|
42
|
+
4. **Cluster (10 min):**
|
|
43
|
+
- Group similar ideas
|
|
44
|
+
- Name themes
|
|
45
|
+
- Identify patterns
|
|
46
|
+
|
|
47
|
+
**Tips:**
|
|
48
|
+
- Warm up first (practice round)
|
|
49
|
+
- Set quantity goal (50 ideas)
|
|
50
|
+
- Use timer (creates urgency)
|
|
51
|
+
- Stand up (more energy)
|
|
52
|
+
- Play music (sets mood)
|
|
53
|
+
|
|
54
|
+
**Example:**
|
|
55
|
+
|
|
56
|
+
HMW: "How might we guide merchants through product creation?"
|
|
57
|
+
|
|
58
|
+
Ideas:
|
|
59
|
+
- Wizard with steps
|
|
60
|
+
- Inline help text
|
|
61
|
+
- Video tutorials
|
|
62
|
+
- Live chat support
|
|
63
|
+
- Pre-filled templates
|
|
64
|
+
- Show examples
|
|
65
|
+
- Progressive disclosure (show fields as needed)
|
|
66
|
+
- Voice input
|
|
67
|
+
- AI assistant
|
|
68
|
+
- Copy from competitor
|
|
69
|
+
- Mobile app with camera
|
|
70
|
+
- Gamification (points for completion)
|
|
71
|
+
- ... (50+ more)
|
|
72
|
+
|
|
73
|
+
---
|
|
74
|
+
|
|
75
|
+
## SCAMPER
|
|
76
|
+
|
|
77
|
+
**Purpose:** Apply seven creative lenses to existing solutions to generate variations
|
|
78
|
+
|
|
79
|
+
**When to use:**
|
|
80
|
+
- Improving existing solution
|
|
81
|
+
- Need structured creativity
|
|
82
|
+
- Stuck in obvious ideas
|
|
83
|
+
- Solo ideation
|
|
84
|
+
|
|
85
|
+
**Seven Lenses:**
|
|
86
|
+
|
|
87
|
+
### S - Substitute
|
|
88
|
+
**What can we replace?**
|
|
89
|
+
- Materials, components, people, processes
|
|
90
|
+
- "What if we used X instead of Y?"
|
|
91
|
+
|
|
92
|
+
Examples:
|
|
93
|
+
- Replace text form → voice input
|
|
94
|
+
- Replace manual entry → import from spreadsheet
|
|
95
|
+
- Replace tooltips → video tutorials
|
|
96
|
+
|
|
97
|
+
### C - Combine
|
|
98
|
+
**What can we merge?**
|
|
99
|
+
- Features, steps, tools, ideas
|
|
100
|
+
- "What if we combined X and Y?"
|
|
101
|
+
|
|
102
|
+
Examples:
|
|
103
|
+
- Combine product creation + inventory setup
|
|
104
|
+
- Combine form + preview
|
|
105
|
+
- Combine help docs + form fields
|
|
106
|
+
|
|
107
|
+
### A - Adapt
|
|
108
|
+
**What can we borrow from elsewhere?**
|
|
109
|
+
- Other industries, nature, history
|
|
110
|
+
- "What does X do that we could adapt?"
|
|
111
|
+
|
|
112
|
+
Examples:
|
|
113
|
+
- Adapt TurboTax interview style
|
|
114
|
+
- Adapt Instagram's photo filters
|
|
115
|
+
- Adapt video game tutorials
|
|
116
|
+
|
|
117
|
+
### M - Modify/Magnify/Minify
|
|
118
|
+
**What can we change, enlarge, or reduce?**
|
|
119
|
+
- Size, shape, frequency, intensity
|
|
120
|
+
- "What if we made X bigger/smaller/different?"
|
|
121
|
+
|
|
122
|
+
Examples:
|
|
123
|
+
- Magnify: Show huge preview
|
|
124
|
+
- Minify: Reduce to 3 required fields
|
|
125
|
+
- Modify: Change form to conversation
|
|
126
|
+
|
|
127
|
+
### P - Put to other uses
|
|
128
|
+
**What else could this be used for?**
|
|
129
|
+
- New contexts, users, purposes
|
|
130
|
+
- "What if X was used for Y?"
|
|
131
|
+
|
|
132
|
+
Examples:
|
|
133
|
+
- Product form → inventory import tool
|
|
134
|
+
- Preview → marketing material generator
|
|
135
|
+
- Templates → learning resource
|
|
136
|
+
|
|
137
|
+
### E - Eliminate
|
|
138
|
+
**What can we remove?**
|
|
139
|
+
- Features, steps, complexity
|
|
140
|
+
- "What if we removed X?"
|
|
141
|
+
|
|
142
|
+
Examples:
|
|
143
|
+
- Eliminate optional fields
|
|
144
|
+
- Eliminate separate steps
|
|
145
|
+
- Eliminate technical terms
|
|
146
|
+
|
|
147
|
+
### R - Reverse/Rearrange
|
|
148
|
+
**What if we flipped or reordered?**
|
|
149
|
+
- Sequence, roles, perspective
|
|
150
|
+
- "What if we did X backwards?"
|
|
151
|
+
|
|
152
|
+
Examples:
|
|
153
|
+
- Reverse: Start with preview, work backwards
|
|
154
|
+
- Rearrange: Put images first, details later
|
|
155
|
+
- Reverse: Let AI generate, user edits
|
|
156
|
+
|
|
157
|
+
**How to use:**
|
|
158
|
+
|
|
159
|
+
1. **Start with existing solution:**
|
|
160
|
+
- Current product form
|
|
161
|
+
|
|
162
|
+
2. **Apply each lens:**
|
|
163
|
+
- Go through S-C-A-M-P-E-R
|
|
164
|
+
- Generate 3-5 ideas per lens
|
|
165
|
+
- Don't judge, just generate
|
|
166
|
+
|
|
167
|
+
3. **Review ideas:**
|
|
168
|
+
- Which are interesting?
|
|
169
|
+
- Which could work?
|
|
170
|
+
- Which to prototype?
|
|
171
|
+
|
|
172
|
+
**Example Session:**
|
|
173
|
+
|
|
174
|
+
Current: "15-field product creation form"
|
|
175
|
+
|
|
176
|
+
**Substitute:**
|
|
177
|
+
- Voice input instead of typing
|
|
178
|
+
- AI generates description from photo
|
|
179
|
+
- Import from competitor
|
|
180
|
+
|
|
181
|
+
**Combine:**
|
|
182
|
+
- Form + preview side-by-side
|
|
183
|
+
- Creation + inventory in one flow
|
|
184
|
+
- Help + form fields inline
|
|
185
|
+
|
|
186
|
+
**Adapt:**
|
|
187
|
+
- TurboTax interview style
|
|
188
|
+
- Instagram's simple photo upload
|
|
189
|
+
- Notion's slash commands
|
|
190
|
+
|
|
191
|
+
**Modify:**
|
|
192
|
+
- Reduce to 3 required fields
|
|
193
|
+
- Expand preview to full page
|
|
194
|
+
- Change to conversational UI
|
|
195
|
+
|
|
196
|
+
**Put to other uses:**
|
|
197
|
+
- Form becomes product catalog
|
|
198
|
+
- Preview becomes marketing page
|
|
199
|
+
- Template becomes tutorial
|
|
200
|
+
|
|
201
|
+
**Eliminate:**
|
|
202
|
+
- Remove all optional fields
|
|
203
|
+
- Remove separate steps
|
|
204
|
+
- Remove save button (auto-save)
|
|
205
|
+
|
|
206
|
+
**Reverse:**
|
|
207
|
+
- Start with preview, fill backwards
|
|
208
|
+
- AI generates, user edits
|
|
209
|
+
- Show examples first, form second
|
|
210
|
+
|
|
211
|
+
---
|
|
212
|
+
|
|
213
|
+
## Crazy 8s
|
|
214
|
+
|
|
215
|
+
**Purpose:** Force rapid idea generation through time constraint
|
|
216
|
+
|
|
217
|
+
**When to use:**
|
|
218
|
+
- Need to break past obvious ideas
|
|
219
|
+
- Individual ideation
|
|
220
|
+
- Quick exploration
|
|
221
|
+
- Before detailed brainstorming
|
|
222
|
+
|
|
223
|
+
**How to do it:**
|
|
224
|
+
|
|
225
|
+
1. **Prepare:**
|
|
226
|
+
- Fold paper into 8 sections
|
|
227
|
+
- Set timer for 8 minutes
|
|
228
|
+
- Have HMW question ready
|
|
229
|
+
|
|
230
|
+
2. **Sketch:**
|
|
231
|
+
- 1 minute per section
|
|
232
|
+
- Sketch solution idea
|
|
233
|
+
- Don't overthink
|
|
234
|
+
- Quantity over quality
|
|
235
|
+
|
|
236
|
+
3. **Review:**
|
|
237
|
+
- Which ideas are interesting?
|
|
238
|
+
- Which to explore further?
|
|
239
|
+
- Share with team
|
|
240
|
+
|
|
241
|
+
**Tips:**
|
|
242
|
+
- First 3 ideas will be obvious (that's OK)
|
|
243
|
+
- Ideas 4-6 get more interesting
|
|
244
|
+
- Ideas 7-8 are often breakthrough
|
|
245
|
+
- Don't worry about drawing skills
|
|
246
|
+
- Use stick figures and boxes
|
|
247
|
+
|
|
248
|
+
**Example:**
|
|
249
|
+
|
|
250
|
+
HMW: "How might we guide merchants through product creation?"
|
|
251
|
+
|
|
252
|
+
8 sketches (1 min each):
|
|
253
|
+
1. Step-by-step wizard
|
|
254
|
+
2. Inline help tooltips
|
|
255
|
+
3. Video tutorial overlay
|
|
256
|
+
4. AI chatbot assistant
|
|
257
|
+
5. Voice-guided creation
|
|
258
|
+
6. Copy from example
|
|
259
|
+
7. AR camera scan product
|
|
260
|
+
8. Collaborative creation (invite expert)
|
|
261
|
+
|
|
262
|
+
---
|
|
263
|
+
|
|
264
|
+
## Provotype Sketching
|
|
265
|
+
|
|
266
|
+
**Purpose:** Create deliberately extreme or provocative prototypes to spark breakthrough thinking
|
|
267
|
+
|
|
268
|
+
**When to use:**
|
|
269
|
+
- Stuck in incremental ideas
|
|
270
|
+
- Need to challenge assumptions
|
|
271
|
+
- Want to push boundaries
|
|
272
|
+
- Before converging on solution
|
|
273
|
+
|
|
274
|
+
**How to create:**
|
|
275
|
+
|
|
276
|
+
1. **Make it extreme:**
|
|
277
|
+
- What's the most radical version?
|
|
278
|
+
- What if we had unlimited resources?
|
|
279
|
+
- What if we ignored all constraints?
|
|
280
|
+
|
|
281
|
+
2. **Make it provocative:**
|
|
282
|
+
- What would shock users?
|
|
283
|
+
- What would competitors never do?
|
|
284
|
+
- What breaks all rules?
|
|
285
|
+
|
|
286
|
+
3. **Extract insights:**
|
|
287
|
+
- What's interesting about this?
|
|
288
|
+
- What could actually work?
|
|
289
|
+
- What assumptions does it challenge?
|
|
290
|
+
|
|
291
|
+
**Examples:**
|
|
292
|
+
|
|
293
|
+
Problem: "Product creation form is too complex"
|
|
294
|
+
|
|
295
|
+
**Provotypes:**
|
|
296
|
+
|
|
297
|
+
1. **Zero-Field Form:**
|
|
298
|
+
- No form at all
|
|
299
|
+
- Just upload photo
|
|
300
|
+
- AI generates everything
|
|
301
|
+
- *Insight:* Could we reduce to 1-2 fields?
|
|
302
|
+
|
|
303
|
+
2. **100-Field Form:**
|
|
304
|
+
- Every possible detail
|
|
305
|
+
- Takes 2 hours to complete
|
|
306
|
+
- Professional-grade
|
|
307
|
+
- *Insight:* Different users need different depth
|
|
308
|
+
|
|
309
|
+
3. **Voice-Only:**
|
|
310
|
+
- No typing allowed
|
|
311
|
+
- Speak to create product
|
|
312
|
+
- AI interprets
|
|
313
|
+
- *Insight:* Could voice be an option?
|
|
314
|
+
|
|
315
|
+
4. **Collaborative:**
|
|
316
|
+
- Can't create alone
|
|
317
|
+
- Must invite expert
|
|
318
|
+
- Expert fills technical fields
|
|
319
|
+
- *Insight:* Could we offer expert help?
|
|
320
|
+
|
|
321
|
+
5. **Gamified:**
|
|
322
|
+
- Product creation is a game
|
|
323
|
+
- Earn points for fields
|
|
324
|
+
- Unlock features
|
|
325
|
+
- *Insight:* Could we make it fun?
|
|
326
|
+
|
|
327
|
+
**From Provotype to Real Solution:**
|
|
328
|
+
|
|
329
|
+
Provotype: "Zero-field form - just upload photo"
|
|
330
|
+
|
|
331
|
+
Real Solution: "Smart form that pre-fills from photo, user confirms/edits"
|
|
332
|
+
|
|
333
|
+
---
|
|
334
|
+
|
|
335
|
+
## Analogous Inspiration
|
|
336
|
+
|
|
337
|
+
**Purpose:** Find inspiration from completely different domains
|
|
338
|
+
|
|
339
|
+
**When to use:**
|
|
340
|
+
- Stuck in industry thinking
|
|
341
|
+
- Need fresh perspective
|
|
342
|
+
- Looking for innovation
|
|
343
|
+
- Breaking assumptions
|
|
344
|
+
|
|
345
|
+
**How to use:**
|
|
346
|
+
|
|
347
|
+
1. **Identify the challenge:**
|
|
348
|
+
- What's the core problem?
|
|
349
|
+
- Abstract it from your domain
|
|
350
|
+
|
|
351
|
+
2. **Find analogies:**
|
|
352
|
+
- How does nature solve this?
|
|
353
|
+
- How do other industries handle it?
|
|
354
|
+
- What's a similar problem elsewhere?
|
|
355
|
+
|
|
356
|
+
3. **Extract principles:**
|
|
357
|
+
- What's the underlying principle?
|
|
358
|
+
- How does it work?
|
|
359
|
+
- What can we borrow?
|
|
360
|
+
|
|
361
|
+
4. **Adapt to your context:**
|
|
362
|
+
- How could this work here?
|
|
363
|
+
- What would we need to change?
|
|
364
|
+
- What's the adapted solution?
|
|
365
|
+
|
|
366
|
+
**Examples:**
|
|
367
|
+
|
|
368
|
+
**Problem:** "Merchants abandon complex product form"
|
|
369
|
+
|
|
370
|
+
**Analogies:**
|
|
371
|
+
|
|
372
|
+
1. **Nature: How do ants navigate?**
|
|
373
|
+
- Ants leave pheromone trails
|
|
374
|
+
- Others follow successful paths
|
|
375
|
+
- *Principle:* Show the path others took
|
|
376
|
+
- *Adaptation:* Show "most merchants fill these 5 fields first"
|
|
377
|
+
|
|
378
|
+
2. **Video Games: How do games teach?**
|
|
379
|
+
- Tutorial levels
|
|
380
|
+
- Gradual complexity
|
|
381
|
+
- Immediate feedback
|
|
382
|
+
- *Principle:* Progressive disclosure
|
|
383
|
+
- *Adaptation:* Start with 3 fields, unlock more
|
|
384
|
+
|
|
385
|
+
3. **Restaurants: How do menus work?**
|
|
386
|
+
- Specials highlighted
|
|
387
|
+
- Descriptions for complex items
|
|
388
|
+
- Pictures for popular items
|
|
389
|
+
- *Principle:* Guide choices with visuals
|
|
390
|
+
- *Adaptation:* Show examples of good products
|
|
391
|
+
|
|
392
|
+
4. **GPS Navigation: How does it guide?**
|
|
393
|
+
- Shows current position
|
|
394
|
+
- Shows destination
|
|
395
|
+
- Shows next step
|
|
396
|
+
- Recalculates if you deviate
|
|
397
|
+
- *Principle:* Show progress and next step
|
|
398
|
+
- *Adaptation:* Progress bar + "Next: add photo"
|
|
399
|
+
|
|
400
|
+
**Domains to explore:**
|
|
401
|
+
- Nature (biomimicry)
|
|
402
|
+
- Other industries
|
|
403
|
+
- History
|
|
404
|
+
- Games
|
|
405
|
+
- Sports
|
|
406
|
+
- Art
|
|
407
|
+
- Science
|
|
408
|
+
|
|
409
|
+
---
|
|
410
|
+
|
|
411
|
+
## When to Use Each Method
|
|
412
|
+
|
|
413
|
+
| Method | Best For | Time | Output |
|
|
414
|
+
|--------|----------|------|--------|
|
|
415
|
+
| **Brainstorming** | Team ideation, quantity | 30-60 min | 50+ ideas |
|
|
416
|
+
| **SCAMPER** | Structured creativity, solo | 30-45 min | 21+ variations |
|
|
417
|
+
| **Crazy 8s** | Quick exploration, individual | 8 min | 8 sketches |
|
|
418
|
+
| **Provotypes** | Breaking assumptions | 30 min | Extreme concepts |
|
|
419
|
+
| **Analogous Inspiration** | Fresh perspective | 30-60 min | Cross-domain ideas |
|
|
420
|
+
|
|
421
|
+
**Typical Workflow:**
|
|
422
|
+
```
|
|
423
|
+
Crazy 8s (warm up) → Brainstorming (quantity) → SCAMPER (variations) → Provotypes (extreme) → Converge
|
|
424
|
+
```
|
|
425
|
+
|
|
426
|
+
---
|
|
427
|
+
|
|
428
|
+
## Tips
|
|
429
|
+
|
|
430
|
+
**Brainstorming:**
|
|
431
|
+
- Set quantity goal (50+ ideas)
|
|
432
|
+
- Use timer (creates urgency)
|
|
433
|
+
- Build on others ("Yes, and...")
|
|
434
|
+
- No judgment during generation
|
|
435
|
+
|
|
436
|
+
**SCAMPER:**
|
|
437
|
+
- Go through all 7 lenses
|
|
438
|
+
- Generate 3-5 ideas per lens
|
|
439
|
+
- Don't skip "obvious" ones
|
|
440
|
+
- Combine ideas from different lenses
|
|
441
|
+
|
|
442
|
+
**Crazy 8s:**
|
|
443
|
+
- First 3 will be obvious (that's OK)
|
|
444
|
+
- Don't overthink
|
|
445
|
+
- Stick figures are fine
|
|
446
|
+
- Ideas 7-8 are often best
|
|
447
|
+
|
|
448
|
+
**Provotypes:**
|
|
449
|
+
- Make it extreme (not realistic)
|
|
450
|
+
- Extract insights (what's interesting?)
|
|
451
|
+
- Don't implement provotype directly
|
|
452
|
+
- Use to challenge assumptions
|
|
453
|
+
|
|
454
|
+
**Analogous Inspiration:**
|
|
455
|
+
- Look far from your domain
|
|
456
|
+
- Abstract the principle
|
|
457
|
+
- Adapt, don't copy directly
|
|
458
|
+
- Nature is great source
|