whiteport-design-studio 0.1.0

package/src/workflows/shared/vtc-workshop/creation-steps-c/step-07-review-and-save.md

@@ -0,0 +1,233 @@
+# Step 7: Review and Save VTC
+
+**Duration:** 3 minutes
+
+**Purpose:** Validate completeness and save the VTC for use
+
+---
+
+## What You'll Do
+
+Review the complete VTC for coherence, then save it to the appropriate location.
+
+---
+
+## Step 7A: Read Back Complete VTC
+
+**Present the full VTC to user:**
+
+```yaml
+vtc:
+  business_goal: "[goal]"
+  solution: "[solution]"
+  user:
+    name: "[name]"
+    description: "[description]"
+    context: "[context]"
+  driving_forces:
+    positive:
+      - "[wish 1]"
+      - "[wish 2]"
+    negative:
+      - "[fear 1]"
+      - "[fear 2]"
+  customer_awareness:
+    start: "[start stage]"
+    end: "[end stage]"
+```
+
+---
+
+## Step 7B: Validate with Questions
+
+**Ask each validation question:**
+
+### 1. Coherence
+> "Does this tell a coherent story?"
+
+- Business goal → Solution → User → Forces → Awareness
+- Does it flow logically?
+- Does each piece connect to the others?
+
+### 2. Actionable
+> "Can you make design decisions from this?"
+
+- Specific enough to guide choices?
+- Clear what would/wouldn't serve this VTC?
+- Could someone else use this?
+
+### 3. Specific
+> "Are the driving forces specific enough?"
+
+- Go beyond generic?
+- Emotionally resonant?
+- Different from other users?
+
+### 4. Realistic
+> "Does the awareness progression make sense?"
+
+- Can solution realistically move user that far?
+- Appropriate for this interaction type?
+- Supports business goal?
+
+**All YES?** → VTC is ready to save  
+**Any NO?** → Refine that specific element
+
+---
+
+## Step 7C: Quick Refinement (if needed)
+
+**If any validation failed:**
+
+1. Identify which element needs work
+2. Return to that step briefly
+3. Make adjustment
+4. Re-validate
+
+**Keep momentum** - don't get stuck perfecting. "Good enough to guide design" is the bar.
+
+---
+
+## Step 7D: Determine Save Location
+
+**Ask:**
+> "What is this VTC for?"
+
+**If Product Pitch:**
+- Location: `docs/A-Product-Brief/vtc-primary.yaml`
+- Purpose: Stakeholder communication, strategic alignment
+
+**If Scenario:**
+- Location: `docs/D-UX-Design/[scenario-name]/vtc.yaml`
+- Purpose: Guide scenario design decisions
+- Example: `docs/D-UX-Design/1.1-landing-page/vtc.yaml`
+
+**If Prototype/Other:**
+- Location: `docs/[appropriate-folder]/vtc-[name].yaml`
+- Purpose: As defined by user
+
+---
+
+## Step 7E: Create VTC File
+
+**Use template:** Copy from `workflows/shared/vtc-workshop/vtc-template.yaml`
+
+**Fill in all sections:**
+
+```yaml
+vtc:
+  business_goal: "[captured value]"
+  solution: "[captured value]"
+  user:
+    name: "[captured value]"
+    description: "[captured value]"
+    context: "[captured value]"
+  driving_forces:
+    positive: [captured values]
+    negative: [captured values]
+  customer_awareness:
+    start: "[captured value]"
+    end: "[captured value]"
+
+metadata:
+  created_date: "[today's date]"
+  created_by: "[team/person]"
+  version: "1.0"
+  source: "creation"  # Created from scratch
+  purpose: "[product_pitch / scenario / etc]"
+  phase: "[WDS phase]"
+
+notes: |
+  Created: [date]
+  Context: [why this VTC was created]
+  
+  Key decisions made:
+  - [Important choices during workshop]
+  - [Insights captured]
+  
+  Usage guidance:
+  - [How this VTC should inform design]
+```
+
+**Save file to determined location**
+
+---
+
+## Step 7F: Communicate What They Have
+
+**Explain to user:**
+
+> "Excellent! We've created a Value Trigger Chain that shows:
+> 
+> **Business Goal:** [goal]  
+> **User:** [name] who wants to [positive force] and avoid [negative force]  
+> **Solution:** [solution] that moves them from [start] to [end] awareness
+> 
+> This VTC will guide all design decisions for [context]. Every piece of content, every interaction, every design choice should serve this strategic chain.
+> 
+> **Next time you're making a design decision, ask:**  
+> 'Does this serve the business goal by triggering these driving forces while moving the user forward in awareness?'
+> 
+> If yes → Good decision  
+> If no → Reconsider"
+
+---
+
+## Step 7G: Define Next Actions
+
+**Based on context:**
+
+**If Product Pitch:**
+> "Next steps:
+> 1. Add this VTC to your pitch document
+> 2. Structure pitch narrative around this chain
+> 3. Use it to explain strategic reasoning to stakeholders
+> 4. Can evolve into full Trigger Map later as project grows"
+
+**If Scenario:**
+> "Next steps:
+> 1. Use this VTC to guide page design in this scenario
+> 2. All content should address these driving forces
+> 3. Track if you're actually moving users through awareness
+> 4. Create additional VTCs for other scenarios as needed"
+
+---
+
+## Completion Checklist
+
+- [ ] VTC validated with all 4 questions
+- [ ] VTC saved to appropriate location
+- [ ] Metadata completed (date, source, purpose)
+- [ ] Notes section filled with context
+- [ ] User understands what they have
+- [ ] User knows how to use VTC
+- [ ] Next actions defined
+
+---
+
+## Workshop Complete! 🎉
+
+**What was accomplished:**
+
+✅ Created strategic VTC from scratch  
+✅ Captured business goal, user psychology, solution  
+✅ Identified positive and negative driving forces  
+✅ Positioned customer awareness progression  
+✅ Validated coherence and actionability  
+✅ Saved for use in design process  
+
+**Time invested:** 20-30 minutes  
+**Strategic value:** Guides all future design decisions
+
+---
+
+## Related Resources
+
+- [Value Trigger Chain Guide](../../../../docs/method/value-trigger-chain-guide.md) - Full methodology
+- [Using VTC in Design](../vtc-workshop-guide.md) - Applications and examples
+- [Trigger Mapping Guide](../../../../docs/method/phase-2-trigger-mapping-guide.md) - When to create full map
+
+---
+
+*VTC Creation Workshop Complete - Strategic clarity achieved!*
+

package/src/workflows/shared/vtc-workshop/creation-steps-c/workflow.md

@@ -0,0 +1,43 @@
+# VTC Creation Workshop - Entry Point
+
+**Purpose:** Create Value Trigger Chain from scratch (no Trigger Map)
+
+**Duration:** 20-30 minutes (estimated - ALPHA)
+
+---
+
+## ⚠️ Alpha Workshop
+
+**Not yet validated in real projects.**
+
+Please note in your VTC file:
+- Actual time taken
+- Steps that were unclear
+- What you wish you'd known
+
+Your feedback improves this for everyone.
+
+---
+
+## Agent Instructions
+
+**Execute steps sequentially. Do not skip steps.**
+
+Each step:
+1. Completes one atomic task
+2. Validates before proceeding
+3. Captures output in working document
+4. Moves to next step ONLY when complete
+
+**Do not look ahead. Execute one step at a time.**
+
+---
+
+## Begin Workshop
+
+**→ Start with [Step 1: Define Business Goal](./step-01-define-business-goal.md)**
+
+---
+
+*Follow the steps. Trust the process.*
+

package/src/workflows/shared/vtc-workshop/selection-steps-c/step-01-load-trigger-map.md

@@ -0,0 +1,81 @@
+# Step 1: Load Trigger Map
+
+**Duration:** 1 minute
+
+**Purpose:** Access existing Trigger Map and verify it's ready for VTC extraction
+
+---
+
+## What You'll Do
+
+Load the Trigger Map document and confirm it contains necessary elements.
+
+---
+
+## Ask User
+
+> "What's the path to your Trigger Map document?"
+
+**Expected locations:**
+- `docs/B-Trigger-Map/trigger-map.md`
+- `docs/B-Trigger-Map/trigger-map.yaml`
+- `docs/B-Trigger-Map/00-trigger-map.md`
+- `docs/02-trigger-map/trigger-map.md`
+- `docs/02-trigger-map/00-trigger-map.md`
+
+---
+
+## Load and Verify
+
+**Check Trigger Map contains:**
+- [ ] Business goals (with priorities if available)
+- [ ] Target groups/users (with descriptions)
+- [ ] Driving forces per user (positive and negative)
+- [ ] Priorities/scores (optional but helpful)
+
+**Confirm availability:**
+```
+Found Trigger Map with:
+- [X] business goals
+- [X] target groups/users
+- [Y] total driving forces
+- Priorities: [Yes/No]
+
+Ready to extract VTC!
+```
+
+---
+
+## If Trigger Map Incomplete
+
+**Missing elements?**
+
+**Option A** - Pause and complete map:
+> "Your Trigger Map seems incomplete. Should we finish mapping first, or work with what we have?"
+
+**Option B** - Switch to Creation Workshop:
+> "Since the Trigger Map isn't complete, would you prefer to create a VTC from scratch instead?"
+
+---
+
+## Capture Map Reference
+
+```yaml
+metadata:
+  source: "trigger_map"
+  trigger_map_path: "[path to map file]"
+  trigger_map_date: "[last modified date]"
+```
+
+---
+
+## Next Step
+
+Once Trigger Map is loaded and verified:
+
+**→ Proceed to [Step 2: Select Business Goal](./step-02-select-business-goal.md)**
+
+---
+
+*Step 1 complete - Map loaded*
+

package/src/workflows/shared/vtc-workshop/selection-steps-c/step-02-select-business-goal.md

@@ -0,0 +1,84 @@
+# Step 2: Select Business Goal
+
+**Duration:** 2 minutes
+
+**Purpose:** Choose which business goal from Trigger Map this VTC serves
+
+---
+
+## Present Available Goals
+
+Show user all business goals from Trigger Map:
+
+> "Your Trigger Map has these business goals:
+> 
+> 1. [Goal 1] - Priority: [score/rank]
+> 2. [Goal 2] - Priority: [score/rank]
+> 3. [Goal 3] - Priority: [score/rank]
+> 
+> Which goal does this [solution/scenario] primarily serve?"
+
+---
+
+## User Selects
+
+**One primary goal** - This VTC will focus here
+
+**Can note secondary:**
+> "Does this also support another goal?"
+
+If yes, capture but keep one primary.
+
+---
+
+## If Goal Not in Map
+
+**User:** "Actually, none of these goals fit. This is about [different goal]."
+
+**Options:**
+
+**A) Add to Trigger Map now:**
+1. Pause VTC workshop
+2. Add new goal to Trigger Map
+3. Resume with new goal available
+
+**B) Add to VTC and note for map update:**
+1. Use new goal in this VTC
+2. Note: "Add to Trigger Map: [new goal]"
+3. Update map in separate session
+
+**C) Refine existing goal:**
+1. Adjust wording for clarity
+2. Use refined version in VTC
+3. Consider updating map
+
+**Recommendation:** If this is a significant gap, pause and update the Trigger Map. It will benefit all future VTCs.
+
+---
+
+## Capture Format
+
+```yaml
+business_goal:
+  primary: "[Selected goal from map]"
+  priority: "[Priority from map]"
+  secondary: "[Optional secondary goal]"
+```
+
+---
+
+## Validation
+
+- [ ] Goal selected makes sense for this solution/scenario?
+- [ ] User confirms this is the right focus?
+
+---
+
+## Next Step
+
+**→ Proceed to [Step 3: Select User](./step-03-select-user.md)**
+
+---
+
+*Step 2 complete - Goal selected*
+

package/src/workflows/shared/vtc-workshop/selection-steps-c/step-03-select-user.md

@@ -0,0 +1,88 @@
+# Step 3: Select User
+
+**Duration:** 2 minutes
+
+**Purpose:** Choose which user/target group from Trigger Map this VTC focuses on
+
+---
+
+## Present Available Users
+
+Show users connected to selected business goal:
+
+> "For [selected goal], your Trigger Map has these target groups:
+> 
+> 1. [User 1 - brief description]
+>    Priority: [score]
+>    Key driving forces: [top 2-3]
+> 
+> 2. [User 2 - brief description]
+>    Priority: [score]
+>    Key driving forces: [top 2-3]
+> 
+> Which user is primary for this [solution/scenario]?"
+
+---
+
+## User Selects
+
+**One primary user** for this VTC
+
+**If multiple users important:**
+> "We can create additional VTCs for other users. For THIS VTC, let's focus on one."
+
+---
+
+## If User Not in Map
+
+**User:** "None of these users match. My scenario is for [different user type]."
+
+**Options:**
+
+**A) Add to Trigger Map now:**
+1. Pause VTC workshop
+2. Add new user/target group to Trigger Map
+3. Map their driving forces
+4. Resume with new user available
+
+**B) Switch to Creation Workshop:**
+1. If this is a one-off scenario
+2. Create VTC from scratch for this user
+3. Consider adding to Trigger Map later
+
+**C) Adapt existing user:**
+1. Pick closest match
+2. Note variations in VTC
+3. Consider if map needs new segment
+
+**Recommendation:** If this represents a significant new user segment, add to Trigger Map. Future scenarios will benefit.
+
+---
+
+## Capture Format
+
+```yaml
+user:
+  name: "[Selected user name from map]"
+  description: "[From Trigger Map]"
+  context: "[From Trigger Map]"
+  priority: "[Priority score from map]"
+```
+
+---
+
+## Validation
+
+- [ ] User selection makes sense for this solution/scenario?
+- [ ] User confirms this is primary target?
+
+---
+
+## Next Step
+
+**→ Proceed to [Step 4: Select Driving Forces](./step-04-select-driving-forces.md)**
+
+---
+
+*Step 3 complete - User selected*
+

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

@@ -0,0 +1,100 @@
+# Step 4: Select Driving Forces
+
+**Duration:** 5 minutes
+
+**Purpose:** Choose 2-5 most relevant driving forces from Trigger Map for this VTC
+
+---
+
+## Present Available Forces
+
+Show all driving forces for selected user:
+
+> "For [selected user], your Trigger Map shows:
+> 
+> **Positive (Wishes):**
+> 1. [Force 1] - Priority: [score]
+> 2. [Force 2] - Priority: [score]
+> 3. [Force 3] - Priority: [score]
+> 
+> **Negative (Fears/Avoid):**
+> 1. [Force 1] - Priority: [score]
+> 2. [Force 2] - Priority: [score]
+> 3. [Force 3] - Priority: [score]"
+
+---
+
+## Guide Selection
+
+> "Which of these driving forces does [this solution/scenario] directly address?
+> 
+> Pick 2-5 total (mix of positive and negative) that are most relevant here."
+
+**Selection criteria:**
+- Does THIS solution actually address this force?
+- Balance positive and negative
+- Don't include everything (lose focus)
+- Higher priority forces are good candidates
+
+---
+
+## Capture Format
+
+```yaml
+driving_forces:
+  positive:
+    - "[Selected wish 1 from map]"
+    - "[Selected wish 2 from map]"
+  negative:
+    - "[Selected fear 1 from map]"
+    - "[Selected fear 2 from map]"
+```
+
+---
+
+## If Driving Force Missing
+
+**User:** "None of these capture [specific driving force]. But that's critical for this scenario!"
+
+**This is valuable discovery!** Using the map reveals gaps.
+
+**Options:**
+
+**A) Add to Trigger Map now:**
+1. Pause VTC workshop
+2. Add new driving force to Trigger Map
+3. Assign priority
+4. Resume and select it
+
+**B) Add to VTC and note for map:**
+1. Use new force in this VTC
+2. Note: "Add to Trigger Map: [new force]"
+3. Update map after workshop
+
+**C) Reword existing force:**
+1. Take closest match from map
+2. Refine wording in VTC
+3. Consider updating map
+
+**Recommendation:** If you discovered this force is critical, add it to the map. Other scenarios likely need it too.
+
+---
+
+## Validation
+
+- [ ] Selected forces directly addressed by this solution?
+- [ ] Focused enough (not too many)?
+- [ ] Includes both positive and negative?
+- [ ] User confirms these are the right ones?
+- [ ] If adding new forces, documented for map update?
+
+---
+
+## Next Step
+
+**→ Proceed to [Step 5: Define Solution](./step-05-define-solution.md)**
+
+---
+
+*Step 4 complete - Forces selected*
+

package/src/workflows/shared/vtc-workshop/selection-steps-c/step-05-define-solution.md

@@ -0,0 +1,59 @@
+# Step 5: Define Solution
+
+**Duration:** 2 minutes
+
+**Purpose:** Define what we're building (NOT in Trigger Map - solutions stay out of map)
+
+---
+
+## Ask User
+
+> "What solution are you building to serve this VTC?"
+
+**Reminder:** This is the bridge between business goal and user.
+
+---
+
+## Guidelines
+
+Same as Creation Workshop - specific about WHAT this is:
+
+**Good examples:**
+- "Landing page with newsletter signup"
+- "Onboarding flow for new users"
+- "User profile settings page"
+
+---
+
+## Capture Format
+
+```yaml
+solution: "[Specific solution being built]"
+```
+
+---
+
+## Test Connection
+
+Business Goal (from map) → Solution (new) → User (from map) → Forces (from map)
+
+Does this chain make sense?
+
+---
+
+## Validation
+
+- [ ] Solution is specific?
+- [ ] Solution serves selected business goal?
+- [ ] Solution connects to selected user and forces?
+
+---
+
+## Next Step
+
+**→ Proceed to [Step 6: Position Customer Awareness](./step-06-customer-awareness.md)**
+
+---
+
+*Step 5 complete - Solution defined*
+