whiteport-design-studio 0.1.0

package/src/workflows/shared/vtc-workshop/creation-steps-c/step-03-describe-user.md

@@ -0,0 +1,131 @@
+# Step 3: Describe User
+
+**Duration:** 5 minutes
+
+**Purpose:** Identify and describe the primary user with psychological depth
+
+---
+
+## What You'll Do
+
+Create a rich description of ONE primary user who will use this solution.
+
+---
+
+## Questions to Ask User
+
+> "Who is the primary user for this solution? Tell me about them."
+
+**Follow-up questions:**
+- "What's their role or context?"
+- "What are their key traits or characteristics?"
+- "When/where do they encounter this solution?"
+- "What are they trying to accomplish?"
+
+---
+
+## Guidelines
+
+**Go beyond demographics to psychology:**
+- Not just "female, 35, urban"
+- Include mindset, goals, context
+- Make them feel like a real person
+
+**Focus on ONE primary user:**
+- Can add others later with separate VTCs
+- Multiple users = multiple VTCs
+
+---
+
+## Template
+
+```
+[Name] ([role/context], [key traits])
+Context: [when/where they encounter solution]
+Current state: [what they're trying to accomplish]
+```
+
+**Example:**
+```
+Harriet (hairdresser, ambitious, small-town salon owner)
+Context: Late evening, researching industry trends online
+Current state: Wants to stay ahead of local competitors
+```
+
+---
+
+## Capture Format
+
+```yaml
+user:
+  name: "[Name or type]"
+  description: "[Role, traits, context]"
+  context: "[When/where they encounter solution]"
+  current_state: "[What they're trying to accomplish]"
+```
+
+**Example:**
+```yaml
+user:
+  name: "Harriet"
+  description: "Hairdresser, ambitious, small-town salon owner"
+  context: "Late evening, researching industry trends online"
+  current_state: "Wants to stay ahead of local competitors"
+```
+
+---
+
+## Validation Checklist
+
+Before proceeding, confirm:
+
+- [ ] Can you picture this person?
+- [ ] Clear why they'd care about this solution?
+- [ ] Understand what they're trying to achieve?
+- [ ] Description feels real (not generic)?
+- [ ] User confirms this matches their target?
+
+---
+
+## Common Issues
+
+**Issue:** User gives demographics only ("women 25-45")
+
+**Solution:**
+> "Let's go deeper. Pick ONE person from that group. What's their name? What are they trying to achieve? What's their mindset?"
+
+**Issue:** User wants multiple people
+
+**Solution:**
+> "For THIS VTC, let's focus on one primary user. We can create additional VTCs for other users. Who matters most for this solution?"
+
+**Issue:** Too generic ("busy professional")
+
+**Solution:**
+> "Can you be more specific? What kind of professional? What makes them busy? What are they trying to accomplish?"
+
+---
+
+## Next Step
+
+Once user is described and validated:
+
+**→ Proceed to [Step 4: Identify Positive Driving Forces](./step-04-positive-driving-forces.md)**
+
+---
+
+## Output at This Point
+
+You now have:
+- ✅ Business goal
+- ✅ Solution
+- ✅ User description
+
+Still need:
+- ⏸️ Driving Forces (positive and negative)
+- ⏸️ Customer Awareness
+
+---
+
+*Step 3 complete - User identified*
+

package/src/workflows/shared/vtc-workshop/creation-steps-c/step-04-positive-driving-forces.md

@@ -0,0 +1,150 @@
+# Step 4: Identify Positive Driving Forces
+
+**Duration:** 5 minutes
+
+**Purpose:** Discover what the user WANTS to achieve (aspirations, wishes)
+
+---
+
+## What You'll Do
+
+Identify 2-3 positive driving forces - what makes this user want to engage with the solution.
+
+---
+
+## Questions to Ask User
+
+> "What does [user name] WANT to achieve? What would make them feel successful?"
+
+**Probing questions:**
+- "What would 'winning' look like for them?"
+- "What outcome would they be proud of?"
+- "What would they brag about to colleagues/friends?"
+- "What capability would transform their work/life?"
+
+---
+
+## Guidelines
+
+**Think aspirations, not just functional needs:**
+- Not: "Upload files"
+- Yes: "Wish to feel organized and in control"
+
+**What would they feel:**
+- Proud of?
+- Excited about?
+- Validated by?
+- Transformed by?
+
+**Aim for 2-3 strong wishes:**
+- Quality over quantity
+- Specific enough to inform design
+- Emotionally resonant
+
+---
+
+## Examples
+
+**Hairdresser (Harriet):**
+- "Wish to be the local beauty authority"
+- "Wish to attract premium clients"
+- "Wish to be seen as cutting-edge"
+
+**Developer (reviewing code):**
+- "Wish to be helpful to teammates"
+- "Wish to catch critical bugs"
+- "Wish to be recognized for thorough reviews"
+
+**Small business owner:**
+- "Wish to understand finances clearly"
+- "Wish to make confident decisions"
+- "Wish to prove business is growing"
+
+---
+
+## Capture Format
+
+```yaml
+driving_forces:
+  positive:
+    - "Wish to [aspiration]"
+    - "Wish to [aspiration]"
+    - "Wish to [aspiration]"
+```
+
+**Example:**
+```yaml
+driving_forces:
+  positive:
+    - "Wish to be local beauty authority"
+    - "Wish to attract premium clients"
+    - "Wish to be seen as cutting-edge"
+```
+
+---
+
+## Validation Checklist
+
+Before proceeding, confirm:
+
+- [ ] Forces feel true for this user?
+- [ ] Specific enough to inform design?
+- [ ] Emotionally resonant (not just functional)?
+- [ ] 2-3 forces captured (not too many)?
+- [ ] User agrees these motivate their target?
+
+---
+
+## Common Issues
+
+**Issue:** Forces too generic ("want to save time")
+
+**Solution:**
+> "Save time doing WHAT specifically? WHY does saving that time matter to them? What would they do with that time?"
+
+**Issue:** Too many wishes listed (7+)
+
+**Solution:**
+> "Which 2-3 matter MOST? If we could only address three, which would transform their experience?"
+
+**Issue:** Only functional needs ("need to upload files")
+
+**Solution:**
+> "Why do they need that? What would having that enable them to achieve? What would they feel?"
+
+---
+
+## Design Hint
+
+These positive forces should inform:
+- Success messaging
+- Aspirational content
+- Celebration moments
+- Value proposition
+
+---
+
+## Next Step
+
+Once positive driving forces are captured:
+
+**→ Proceed to [Step 5: Identify Negative Driving Forces](./step-05-negative-driving-forces.md)**
+
+---
+
+## Output at This Point
+
+You now have:
+- ✅ Business goal
+- ✅ Solution
+- ✅ User description
+- ✅ Positive driving forces
+
+Still need:
+- ⏸️ Negative driving forces
+- ⏸️ Customer Awareness
+
+---
+
+*Step 4 complete - Aspirations captured*
+

package/src/workflows/shared/vtc-workshop/creation-steps-c/step-05-negative-driving-forces.md

@@ -0,0 +1,190 @@
+# Step 5: Identify Negative Driving Forces
+
+**Duration:** 5 minutes
+
+**Purpose:** Discover what the user FEARS or wants to avoid (anxieties, frustrations)
+
+---
+
+## What You'll Do
+
+Identify 2-3 negative driving forces - what pushes the user away from failure/frustration.
+
+---
+
+## Questions to Ask User
+
+> "What does [user name] FEAR or want to avoid? What keeps them up at night?"
+
+**Probing questions:**
+- "What are they worried about?"
+- "What would be embarrassing or costly?"
+- "What would feel like failure?"
+- "What friction do they currently experience?"
+- "What do they NOT want to happen?"
+
+---
+
+## Guidelines
+
+**Think anxieties and frustrations:**
+- Not: "Don't want slow system"
+- Yes: "Fear of wasting hours on complex tools"
+
+**What do they fear:**
+- Losing?
+- Missing?
+- Being seen as?
+- Experiencing?
+
+**Aim for 2-3 strong fears:**
+- Often opposite side of positive forces
+- Specific and emotionally real
+- Inform risk reduction in design
+
+---
+
+## Examples
+
+**Hairdresser (Harriet):**
+- "Fear of missing industry trends"
+- "Fear of losing clients to trendier salons"
+- "Avoid appearing outdated to clients"
+
+**Developer (reviewing code):**
+- "Fear of missing critical bugs"
+- "Fear of slowing down teammates"
+- "Avoid looking careless or rushed"
+
+**Small business owner:**
+- "Fear of making wrong financial decisions"
+- "Fear of tax compliance issues"
+- "Avoid feeling stupid about numbers"
+
+---
+
+## Connection to Positive Forces
+
+**Notice patterns:**
+- Positive: "Wish to be authority" ↔ Negative: "Fear of appearing outdated"
+- Positive: "Wish to catch bugs" ↔ Negative: "Fear of missing bugs"
+
+**Both sides of same coin** - this is good! Shows coherent psychology.
+
+---
+
+## Capture Format
+
+```yaml
+driving_forces:
+  positive:
+    - "[from previous step]"
+  negative:
+    - "Fear of [anxiety]"
+    - "Fear of [frustration]"
+    - "Avoid [problem]"
+```
+
+**Example:**
+```yaml
+driving_forces:
+  positive:
+    - "Wish to be local beauty authority"
+    - "Wish to attract premium clients"
+  negative:
+    - "Fear of missing industry trends"
+    - "Fear of losing clients to trendier salons"
+```
+
+---
+
+## Validation Checklist
+
+Before proceeding, confirm:
+
+- [ ] Forces feel true for this user?
+- [ ] Specific enough to inform design?
+- [ ] Connect to positive forces (opposite sides)?
+- [ ] 2-3 forces captured (total 4-6 positive + negative)?
+- [ ] User agrees these are real anxieties?
+
+---
+
+## Common Issues
+
+**Issue:** Forces too mild ("don't like complexity")
+
+**Solution:**
+> "What's the REAL fear behind that? What happens if they encounter complexity? What cost do they pay?"
+
+**Issue:** Only negative stated as positive inverse ("want to not fail")
+
+**Solution:**
+> "What ARE they afraid of specifically? What would failure look like?"
+
+**Issue:** Too many fears (overwhelming)
+
+**Solution:**
+> "Which 2-3 fears are strongest? Which would prevent them from using this solution?"
+
+---
+
+## Design Hint
+
+These negative forces should inform:
+- Risk reduction features
+- Reassurance messaging
+- Error prevention
+- Trust signals
+- Recovery paths
+
+---
+
+## Review Combined Forces
+
+**At this point, review ALL driving forces together:**
+
+```yaml
+driving_forces:
+  positive:
+    - "[wish 1]"
+    - "[wish 2]"
+    - "[wish 3]"
+  negative:
+    - "[fear 1]"
+    - "[fear 2]"
+```
+
+**Ask:** "Do these forces tell a coherent story about what drives [user name]?"
+
+If yes → Proceed  
+If no → Refine before moving forward
+
+---
+
+## Next Step
+
+Once negative driving forces are captured and all forces validated:
+
+**→ Proceed to [Step 6: Position Customer Awareness](./step-06-customer-awareness.md)**
+
+---
+
+## Output at This Point
+
+You now have:
+- ✅ Business goal
+- ✅ Solution
+- ✅ User description
+- ✅ Positive driving forces
+- ✅ Negative driving forces
+
+Still need:
+- ⏸️ Customer Awareness
+
+**This is the core strategic content! Almost done.**
+
+---
+
+*Step 5 complete - Fears and frustrations captured*
+

package/src/workflows/shared/vtc-workshop/creation-steps-c/step-06-customer-awareness.md

@@ -0,0 +1,256 @@
+# Step 6: Position Customer Awareness
+
+**Duration:** 5-10 minutes
+
+**Purpose:** Define where user starts and where we move them in their awareness journey
+
+---
+
+## What You'll Do
+
+Explore what the user knows NOW, and what transformation we want to create.
+
+---
+
+## Step 6A: Understand Current State
+
+**Start with exploration:**
+
+> "Let's understand where [user name] is right now. When they encounter [solution], what's going on in their head?"
+
+**Ask progressively:**
+
+### 1. "Do they know something's wrong?"
+
+**If NO:**
+> "Interesting - so they don't even realize there's a problem yet. What would make them suddenly notice?"
+
+**Capture:** Starting at **Unaware**
+
+**If YES:**
+> "Okay, they know something's not working. Tell me more about that..."
+
+### 2. "What language are they using?"
+
+> "When they talk about this problem - to themselves or others - what words do they use?"
+
+**Listen for:**
+- Generic problem language → **Problem Aware**
+- Comparing solutions → **Solution Aware**
+- Mentioning your product → **Product Aware**
+- Sharing their experience → **Most Aware**
+
+### 3. "What are they looking for?"
+
+> "If they're searching for help, what would they type into Google?"
+
+**Examples show awareness:**
+- "how to fix [problem]" → Problem Aware
+- "best tools for [need]" → Solution Aware
+- "[your product name] review" → Product Aware
+
+### 4. "Have they tried anything?"
+
+> "Are they already trying other solutions? Or still figuring out if solutions exist?"
+
+**Reveals:**
+- Never tried anything → Problem Aware
+- Tried competitors → Solution Aware
+- Using your free version → Product Aware
+- Paying customer → Most Aware
+
+### 5. "Capture their current position"
+
+Based on these explorations, summarize:
+
+```yaml
+customer_awareness:
+  start: "[One of: Unaware / Problem Aware / Solution Aware / Product Aware / Most Aware]"
+  start_context: "[What they know, what they're looking for, language they use]"
+```
+
+**The 5 stages (reference):**
+- **Unaware** - Doesn't know problem exists
+- **Problem Aware** - Knows problem, doesn't know solutions exist
+- **Solution Aware** - Knows solutions exist, researching options
+- **Product Aware** - Knows YOUR solution exists specifically
+- **Most Aware** - Has used, experienced value, may advocate
+
+---
+
+## Step 6B: Define Desired Transformation
+
+**Now explore where we want to move them:**
+
+> "After they interact with [solution], what should change in their understanding?"
+
+### 1. "What will they realize?"
+
+> "What new insight or understanding will they gain?"
+
+**Examples:**
+- "Oh, I didn't know this was even possible" (Unaware → Problem Aware)
+- "This solves it without the hassle I expected" (Solution → Product Aware)
+- "This actually works!" (Product → Most Aware)
+
+### 2. "What will they be able to articulate?"
+
+> "After this experience, if they told a friend about it, what would they say?"
+
+**Their new language shows awareness shift.**
+
+### 3. "What action becomes possible?"
+
+> "What can they do NOW that they couldn't before?"
+
+**Actions show awareness level:**
+- Admit problem → Problem Aware
+- Compare solutions → Solution Aware
+- Try your product → Product Aware
+- Recommend it → Most Aware
+
+---
+
+## Step 6C: Validate Realistic Progression
+
+**Discuss realistic movement:**
+
+> "So they're starting at [start stage]. Where's realistic to move them with [this solution]?"
+
+**Important:** Usually move 1-2 stages, not jumping from Unaware → Most Aware
+
+**Guide with questions:**
+
+- "Is this a quick interaction or deep engagement?"
+- "Will they actually USE it, or just learn about it?"
+- "What's preventing bigger jump?" (skepticism, complexity, commitment)
+
+**Capture:**
+
+```yaml
+customer_awareness:
+  start: "[Current stage]"
+  start_context: "[What they know/feel NOW]"
+  end: "[Target stage]"
+  end_context: "[What they'll know/feel AFTER]"
+  transformation: "[Key shift that happens]"
+```
+
+**Example:**
+```yaml
+customer_awareness:
+  start: "Problem Aware"
+  start_context: "Knows they need to stay current with beauty trends, searching for solutions"
+  end: "Product Aware"
+  end_context: "Knows our newsletter provides curated trends, considering signup"
+  transformation: "From generic need to specific solution"
+```
+
+---
+
+## Validation Through Storytelling
+
+**Ask user to tell the story:**
+
+> "Walk me through their awareness journey:
+> 
+> They start: [knowing what?]
+> They encounter: [this solution]
+> They realize: [what new understanding?]
+> They end up: [able to do what?]"
+
+**Listen for:**
+- ✅ Coherent narrative
+- ✅ Realistic transformation
+- ✅ Matches driving forces
+- ✅ Supports business goal
+
+**If story doesn't flow** - one of the stages is wrong.
+
+---
+
+## Common Patterns
+
+**Landing Pages:** Usually Problem/Solution → Product Aware  
+*"I know solutions exist" → "I know THIS solution"*
+
+**Onboarding:** Usually Product → Most Aware  
+*"I signed up" → "I see the value, I'll keep using it"*
+
+**Educational Content:** Often Unaware → Problem Aware  
+*"Didn't know this mattered" → "Oh, this IS a problem"*
+
+**Feature Announcements:** Often Most Aware → Most Aware (deepen)  
+*"Love this product" → "Love it even more now"*
+
+---
+
+## Common Issues
+
+**Issue:** User wants to jump multiple stages (Unaware → Most Aware)
+
+**Solution:**
+> "That's the ultimate goal, but THIS interaction likely moves them 1-2 stages. What's the next realistic step for someone encountering [solution]?"
+
+**Issue:** User not sure about stages
+
+**Solution:**
+> "Let's think about it this way: What do they know BEFORE encountering your solution? What should they know AFTER?"
+
+**Issue:** Starting and ending are the same stage
+
+**Solution:**
+> "If awareness doesn't change, what IS changing for them? Maybe we're maintaining Most Aware, or maybe the starting point needs adjustment?"
+
+---
+
+## How This Guides Design
+
+**Understanding awareness informs everything:**
+
+**Content Strategy:**
+- **Start stage** tells you what language to use (theirs, not yours)
+- **End stage** tells you what message to deliver (the transformation)
+- **Gap between** tells you how much explanation needed
+
+**Examples:**
+- Problem → Product Aware: Need to explain solutions exist, then show yours is best
+- Product → Most Aware: Skip explanation, show immediate value
+
+**Tone:**
+- Earlier in awareness: More exploratory, educational, empathetic
+- Later in awareness: More direct, confident, action-oriented
+
+**Depth:**
+- Unaware: Need context (why should I care?)
+- Problem Aware: Need options (what solves this?)
+- Solution Aware: Need differentiation (why yours?)
+- Product Aware: Need proof (does it work?)
+- Most Aware: Need expansion (what else?)
+
+---
+
+## Next Step
+
+Once customer awareness is positioned and validated:
+
+**→ Proceed to [Step 7: Review and Save VTC](./step-07-review-and-save.md)**
+
+---
+
+## Output at This Point
+
+You now have:
+- ✅ Business goal
+- ✅ Solution
+- ✅ User description
+- ✅ Positive driving forces
+- ✅ Negative driving forces
+- ✅ Customer Awareness positioning
+
+**VTC is complete! Final step is review and save.**
+
+---
+
+*Step 6 complete - Awareness positioned*
+