design-protocol 1.0.0

package/skills/dp-research/references/facilitation-guide.md

@@ -0,0 +1,291 @@
+# Session Facilitation Guide
+
+Running research sessions without contaminating the data.
+
+---
+
+## Your Role
+
+You are a **curious observer**, not an expert or advisor.
+
+**Your job:**
+- Create safety for honesty
+- Listen more than talk (80/20 rule)
+- Follow their lead
+- Capture their reality
+
+**Not your job:**
+- Validate your ideas
+- Convince them of anything
+- Fix their problems (during the session)
+- Demonstrate how smart you are
+
+---
+
+## Before the Session
+
+### Mindset Preparation
+
+- Set aside your hypotheses temporarily
+- Remind yourself: "I'm here to learn, not to validate"
+- Accept that you might be wrong about everything
+- Prepare to be surprised
+
+### Practical Prep
+
+- [ ] Test all technology (video, audio, screen share, recording)
+- [ ] Have backup recording method (phone as backup audio)
+- [ ] Prepare note-taking template with question prompts
+- [ ] Brief any observers: silent, no reactions, notes only
+- [ ] Have water nearby (you'll be talking)
+- [ ] Remove distractions (notifications off, phone away)
+
+---
+
+## The First 2 Minutes Set the Tone
+
+**Establish:**
+- This is a conversation, not an interrogation
+- There are no wrong answers
+- Honest criticism is valuable
+- They're the expert on their experience
+
+**Verbal cues:**
+> "I'm really interested in learning how you work — you're the expert here."
+
+> "Please be completely honest. Critical feedback is the most helpful thing you can give me."
+
+> "If something doesn't make sense, that's a problem with the design, not with you."
+
+---
+
+## Active Listening Techniques
+
+### Show You're Listening
+
+- Nod and give small verbal acknowledgments ("mm-hmm", "I see")
+- Mirror their body language (subtly)
+- Take notes visibly (shows you value their input)
+- Make eye contact (on video: look at camera when they speak)
+
+### Reflect Back
+
+- "It sounds like you're saying..."
+- "So if I understand correctly..."
+- "Let me make sure I got that..."
+
+This confirms understanding AND makes them feel heard.
+
+### Follow the Energy
+
+- When they show emotion, follow it: "You seem frustrated by that — tell me more"
+- When they speed up (excited), lean in
+- When they pause (thinking), give space
+
+---
+
+## The Art of Silence
+
+**The 5-Second Rule:**
+After they finish speaking, count to 5 before responding.
+
+Why it works:
+- People often add their most important point as an afterthought
+- Silence signals you want more
+- Resisting the urge to fill silence shows you're truly listening
+
+**Comfortable silence phrases:**
+- "Take your time."
+- [Just wait and nod slightly]
+- "Mmm..." [trails off]
+
+---
+
+## Probing Without Leading
+
+### Neutral Follow-Ups
+
+✅ "Tell me more about that."
+✅ "What happened next?"
+✅ "Can you give me an example?"
+✅ "What do you mean by [their word]?"
+✅ "Why was that important?"
+✅ "How did that make you feel?"
+✅ "What were you expecting?"
+
+### Avoid Suggesting Answers
+
+❌ "So was that frustrating?" → ✅ "What was that like?"
+❌ "Did that confuse you?" → ✅ "Walk me through your thinking."
+❌ "That sounds difficult" → ✅ "How would you describe that?"
+
+### The Echo Technique
+
+Simply repeat their last few words as a question:
+
+**Them:** "And then I just gave up and used the old system."
+**You:** "Used the old system?"
+**Them:** "Yeah, because..." [continues with explanation]
+
+---
+
+## When They Get Stuck (Usability Testing)
+
+**First: Wait.** Give them at least 30 seconds.
+
+**Then, ask:**
+- "What are you thinking?"
+- "What are you looking for?"
+- "What would you try next?"
+- "Where would you expect to find that?"
+
+**If truly stuck (2+ minutes):**
+- Give the smallest possible hint
+- Note it as a failure point
+- "Let's say it's under [section]. What would you do from there?"
+
+**Don't:**
+- Jump in immediately
+- Show them the answer
+- Make them feel bad about being stuck
+
+---
+
+## Handling Difficult Situations
+
+### They Give One-Word Answers
+
+- Ask for specifics: "Can you give me an example?"
+- Ask about a recent instance: "Tell me about the last time..."
+- Reframe as storytelling: "Walk me through..."
+- Check if the topic is uncomfortable and adjust
+
+### They Go Off-Topic
+
+- Listen for valuable tangents (often gold)
+- Gently redirect: "That's interesting. Coming back to [topic]..."
+- Note for later: "I'd love to hear more about that after we cover a few more things"
+
+### They Ask You Questions
+
+**During exploration:**
+- "What do you think?" (turn it back)
+- "I'm curious what your expectation is"
+- "There's no right answer — I'm interested in your perspective"
+
+**During usability testing:**
+- "What would you normally do?"
+- "Let's see what happens"
+- "I'll explain afterward — for now, just try what you'd do naturally"
+
+### They Get Frustrated
+
+- Acknowledge: "I can see this is frustrating"
+- Reframe: "This is exactly the kind of thing we need to find"
+- Reassure: "You're doing great — this feedback is really valuable"
+- Offer an out: "Would you like to skip this one and move on?"
+
+### They Apologize
+
+**They say:** "Sorry, I'm not very tech-savvy"
+
+**You say:** "Please don't apologize — if this is confusing, that's something we need to fix in the design, not something you need to learn."
+
+### They Try to Please You
+
+**Signs:**
+- "This is good, right?"
+- "I think this is what you're looking for?"
+- Excessive positive feedback with no criticism
+
+**Response:**
+- "I really need to hear what doesn't work too"
+- "What would make this better?"
+- "If your colleague asked for your honest opinion, what would you say?"
+- "What's the one thing you'd change?"
+
+### They Have Strong Opinions About Solutions
+
+**They say:** "You should just add a button that does X"
+
+**You say:** "That's interesting — tell me more about what problem that would solve for you?"
+
+(Redirect from solution to problem)
+
+---
+
+## Body Language & Presence
+
+### Do:
+- Lean in slightly (engaged)
+- Open posture (arms uncrossed)
+- Nod occasionally
+- Maintain comfortable eye contact
+- Smile when appropriate
+
+### Don't:
+- Cross arms (defensive)
+- Look at your phone/notes constantly
+- Fidget
+- React negatively to criticism
+- Look surprised/disappointed at their answers
+
+### For Video Calls:
+- Camera at eye level
+- Look at camera when they speak (feels like eye contact)
+- Good lighting on your face
+- Neutral background
+- Mute notifications
+
+---
+
+## Managing Observers
+
+**Before:**
+- Brief them: "Your job is to take notes silently"
+- No facial reactions, typing sounds should be quiet
+- Questions saved for after, not during
+- They should not be visible to participant if possible
+
+**During:**
+- If they unmute or react, politely redirect
+- "Let me check with my colleague after the session"
+
+**After:**
+- Debrief together immediately
+- Compare notes
+- Discuss interpretations
+
+---
+
+## Post-Session Habits
+
+**Immediately after (within 1 hour):**
+
+1. Write your top 3-5 takeaways while fresh
+2. Note any "aha moments"
+3. Flag surprising or contradictory statements
+4. Capture emotional moments
+5. Record your own feelings/reactions (may indicate bias)
+
+**Questions to ask yourself:**
+- What surprised me?
+- What confirmed my assumptions?
+- What contradicted my assumptions?
+- What do I still not understand?
+- What would I ask differently next time?
+
+---
+
+## Common Facilitator Mistakes
+
+| Mistake | Why It's Bad | Better Approach |
+|---------|--------------|-----------------|
+| Talking too much | Reduces data, leads witness | Ask, then listen |
+| Filling silences | Loses afterthought insights | Wait 5 seconds |
+| Leading questions | Contaminates data | Use neutral probes |
+| Defending the design | Makes them hold back criticism | Stay curious |
+| Showing disappointment | Makes them soften feedback | Neutral reactions |
+| Going off-script too early | Misses key questions | Stick to structure first |
+| Not following tangents | Misses unexpected insights | Balance script vs. exploration |
+| Rescuing them too fast | Misses usability issues | Let them struggle (within reason) |

package/skills/dp-research/references/interview-guide-template.md

@@ -0,0 +1,190 @@
+# Interview Guide Template
+
+Copy and customize this template for user or stakeholder interviews.
+
+---
+
+## Interview Guide: [Project Name]
+
+**Research Goal:** [What we're trying to learn]
+
+**Participant Criteria:** [Who we're talking to]
+
+**Duration:** 45-60 minutes
+
+**Materials Needed:**
+- [ ] Recording consent form
+- [ ] Note-taking template
+- [ ] Any prototypes/concepts to show
+- [ ] Incentive (if applicable)
+
+---
+
+## Pre-Interview Checklist
+
+- [ ] Test recording equipment/software
+- [ ] Have backup recording method
+- [ ] Send calendar invite with video link
+- [ ] Prepare note-taking doc
+- [ ] Review participant background (if known)
+- [ ] Brief any observers
+
+---
+
+## Interview Script
+
+### 1. Introduction (5 minutes)
+
+> "Hi [Name], thank you so much for taking the time to talk with me today. I'm [Your name], and I'm a designer at [Company].
+>
+> We're working on [general topic area] and I'm really interested in learning about your experience with [relevant domain]. There are no right or wrong answers — I'm just trying to understand how you work today.
+>
+> Before we start, I want to mention:
+> - This conversation is confidential. Your name won't be attached to any quotes we use.
+> - I'd like to record this so I can focus on our conversation instead of taking notes. The recording is just for our team. Is that okay with you?
+> - Please feel free to ask me questions at any time, or let me know if you need to skip anything.
+> - We have about [X] minutes together. I'll keep an eye on time.
+>
+> Do you have any questions before we begin?"
+
+**[Get verbal consent for recording, then start recording]**
+
+---
+
+### 2. Context & Background (10 minutes)
+
+*Goal: Understand their world before diving into specifics*
+
+**Role & Responsibilities:**
+- "Tell me a bit about your role. What do you do day-to-day?"
+- "How long have you been doing this type of work?"
+- "Who do you work with most closely?"
+
+**Typical Workflow:**
+- "Walk me through a typical day/week. What does that look like?"
+- "What tools or systems do you use regularly?"
+- "What takes up most of your time?"
+
+**[Probe based on their answers]**
+
+---
+
+### 3. Core Exploration (25-30 minutes)
+
+*Goal: Deep dive on your research questions*
+
+#### Topic A: [Research Question 1]
+
+**Opening question:**
+- "[Open-ended question about the topic]"
+
+**Follow-up probes:**
+- "Tell me more about that..."
+- "Can you give me a specific example?"
+- "What happened the last time you [did that thing]?"
+- "How did that make you feel?"
+- "Why was that important?"
+
+**Specific questions:**
+- "[Specific question 1]"
+- "[Specific question 2]"
+- "[Specific question 3]"
+
+#### Topic B: [Research Question 2]
+
+**Opening question:**
+- "[Open-ended question about the topic]"
+
+**Follow-up probes:**
+- [Same probing techniques]
+
+**Specific questions:**
+- "[Specific question 1]"
+- "[Specific question 2]"
+
+#### Topic C: [Research Question 3]
+
+[Same structure]
+
+---
+
+### 4. Reactions / Concept Feedback (10 minutes)
+
+*Optional: Only if you have something to show*
+
+> "I'd like to show you something we've been thinking about. This is early work, so please don't hold back — honest feedback is really valuable, and you won't hurt my feelings."
+
+**[Show prototype/concept]**
+
+- "What's your first impression?"
+- "What do you think this is for?"
+- "What would you expect to happen if you [action]?"
+- "How does this compare to what you do today?"
+- "What's confusing or unclear?"
+- "What's missing?"
+
+---
+
+### 5. Wrap-Up (5 minutes)
+
+**Summary check:**
+- "Before we wrap up, I want to make sure I understood correctly. [Summarize key points]. Did I get that right?"
+
+**Open floor:**
+- "Is there anything else about [topic] that I should have asked about but didn't?"
+- "Is there anything you want to add?"
+
+**Referrals:**
+- "Is there anyone else you think I should talk to about this?"
+
+**Close:**
+> "Thank you so much for your time today. This has been really helpful. If you think of anything else, feel free to email me at [email].
+>
+> [If incentive:] We'll send your [gift card/incentive] within [timeframe]."
+
+**[Stop recording]**
+
+---
+
+## Post-Interview
+
+Immediately after (within 1 hour):
+- [ ] Write top 3-5 takeaways while fresh
+- [ ] Note any surprising moments
+- [ ] Flag questions that didn't work well
+- [ ] Note quotes worth highlighting
+- [ ] Update discussion guide if needed for next interview
+
+---
+
+## Question Bank
+
+### Understanding Current Behavior
+- "Walk me through the last time you [did X]..."
+- "What's the first thing you do when [situation]?"
+- "How do you currently handle [task]?"
+- "What tools do you use for [activity]?"
+
+### Exploring Pain Points
+- "What's the most frustrating part of [process]?"
+- "What workarounds have you developed?"
+- "If you could wave a magic wand, what would you change?"
+- "What takes longer than it should?"
+
+### Understanding Motivations
+- "Why is [that] important to you?"
+- "What are you trying to achieve when you [action]?"
+- "What does success look like?"
+- "What happens if [task] doesn't get done?"
+
+### Exploring Context
+- "When do you typically [do this]?"
+- "Who else is involved in [process]?"
+- "What information do you need to [make this decision]?"
+- "What triggers you to [start this task]?"
+
+### Getting Specifics
+- "Can you give me a recent example?"
+- "What happened next?"
+- "How often does that happen?"
+- "Who did you talk to about it?"

package/skills/dp-research/references/method-selection.md

@@ -0,0 +1,195 @@
+# Research Method Selection Guide
+
+Pick the right method for what you need to learn.
+
+## Quick Decision Framework
+
+**What do you need to learn?**
+
+| Question Type | Best Method | Sample Size |
+|---------------|-------------|-------------|
+| "Why do users do X?" | User Interviews | 5-8 |
+| "Can users do X with our design?" | Usability Testing | 5-8 |
+| "How many users do X?" | Survey | 100+ |
+| "How do users naturally work?" | Contextual Inquiry | 4-6 |
+| "How should we organize this?" | Card Sorting | 15-30 |
+| "Which version performs better?" | A/B Testing | Stat. significant |
+| "What do stakeholders need?" | Stakeholder Interviews | All key players |
+
+---
+
+## Method Deep Dives
+
+### User Interviews
+
+**Best for:**
+- Understanding motivations, goals, pain points
+- Exploring problem space before solutions
+- Learning mental models and vocabulary
+- Discovery research
+
+**Not good for:**
+- Measuring usability (use testing)
+- Getting statistically significant data (use surveys)
+- Predicting future behavior (people are bad at this)
+
+**Typical structure:** 45-60 minutes, semi-structured
+
+**Sample size:** 5-8 participants per user segment. You'll hit saturation (no new insights) around 5-6 for most topics.
+
+**B2B considerations:**
+- May need manager approval for employee participants
+- Schedule around their busy periods
+- They're experts in their domain — respect that
+
+---
+
+### Usability Testing
+
+**Best for:**
+- Evaluating whether a design works
+- Finding navigation and comprehension issues
+- Comparing design alternatives
+- Validating before development
+
+**Not good for:**
+- Discovering user needs (use interviews)
+- Testing complex multi-day workflows
+- Evaluating visual design preference
+
+**Types:**
+- **Moderated**: You guide, can probe, richer data
+- **Unmoderated**: Scales better, less depth, faster
+
+**Typical structure:** 30-60 minutes, 3-5 tasks
+
+**Sample size:** 5 users find ~85% of usability issues. 8 if high-stakes.
+
+**B2B considerations:**
+- Use realistic data (vessel names, cargo types)
+- Test with actual domain terminology
+- Consider role-specific task flows
+
+---
+
+### Surveys
+
+**Best for:**
+- Quantifying behaviors or attitudes
+- Reaching large sample sizes
+- Measuring satisfaction (NPS, CSAT)
+- Validating patterns seen in qualitative research
+
+**Not good for:**
+- Understanding "why" (use interviews)
+- Discovering unknown problems
+- Complex or nuanced topics
+
+**Typical length:** 5-10 minutes max (15-20 questions)
+
+**Sample size:** 100+ for meaningful statistics. 30+ for directional insights.
+
+**Response rate tips:**
+- Keep it short
+- Explain why it matters
+- Send from a person, not "noreply"
+- Offer incentive if appropriate
+
+---
+
+### Contextual Inquiry
+
+**Best for:**
+- Understanding real work environment
+- Discovering workarounds and tools
+- Seeing what users don't think to mention
+- Complex workflows
+
+**Not good for:**
+- Remote participants
+- Sensitive environments
+- Quick answers
+
+**Typical structure:** 1-2 hours in their workspace, observe + interview
+
+**Sample size:** 4-6 participants
+
+**B2B considerations:**
+- May require security clearance or NDA
+- Physical access to trading floors, vessels, etc.
+- Gold standard for understanding maritime operations
+
+---
+
+### Card Sorting
+
+**Best for:**
+- Information architecture
+- Navigation structure
+- Understanding user mental models for categorization
+
+**Types:**
+- **Open sort**: Users create their own categories (discovery)
+- **Closed sort**: Users sort into predefined categories (validation)
+
+**Sample size:** 15-30 participants
+
+**Tools:** Optimal Workshop, Maze, UserTesting
+
+---
+
+### A/B Testing
+
+**Best for:**
+- Measuring behavior change between versions
+- Optimizing specific metrics
+- Settling design debates with data
+
+**Not good for:**
+- Understanding why (just tells you what)
+- Low-traffic features
+- Dramatic redesigns
+
+**Requirements:**
+- Sufficient traffic for statistical significance
+- Clear success metric
+- Technical implementation capacity
+
+---
+
+## Combining Methods
+
+Research is often most powerful in combination:
+
+**Discovery phase:**
+1. Stakeholder interviews → Understand business context
+2. User interviews → Understand user context
+3. Contextual inquiry → See real behavior
+
+**Design phase:**
+1. Card sorting → Structure information
+2. Usability testing → Validate concepts
+
+**Optimization phase:**
+1. Usability testing → Find issues
+2. A/B testing → Measure improvements
+3. Survey → Track satisfaction
+
+---
+
+## Common Mistakes
+
+❌ **Using surveys for discovery**
+"We'll just ask users what features they want" → Gets wish lists, not insights
+
+❌ **Using interviews to validate solutions**
+"Do you think you'd use this?" → People are terrible at predicting their own behavior
+
+❌ **Testing with 1-2 users**
+"We got feedback" → Not enough to see patterns
+
+❌ **A/B testing too early**
+Testing button colors when the whole flow is broken
+
+❌ **Skipping research because "we know our users"**
+You know *about* them. You don't know what they actually do.