whiteport-design-studio 0.1.0

package/src/workflows/4-ux-design/scenario-init/SCENARIO-INIT-PROCESS.md

@@ -0,0 +1,221 @@
+# Scenario Initialization: From Trigger Map to First Sketch
+
+**Find the natural starting point and shortest path to mutual success**
+
+---
+
+## The Situation
+
+You've created your **Trigger Map**. You know:
+
+- WHO your target groups are
+- WHAT triggers their needs
+- WHY your business exists
+
+**Now: What should you start sketching?**
+
+---
+
+## Agent's Job: Help You Find the Journey
+
+**Agent connects Trigger Map to the first scenario:**
+
+### 1. What Feature Delivers the Most Value?
+
+```
+Agent: "Looking at your Trigger Map and prioritized feature list,
+        what's the core feature that delivers value to your
+        primary target group?
+
+        This is what we should sketch first."
+
+Designer: "The family dog walk calendar - it solves the accountability
+           problem that causes conflict."
+```
+
+---
+
+### 2. Where Does the User First Encounter This?
+
+```
+Agent: "Where does your primary target group first come into
+        contact with this solution?"
+
+Designer: "Google search - they're frustrated with family conflict
+           over dog care."
+```
+
+---
+
+### 3. What's Their Mental State at This Moment?
+
+```
+Agent: "When they find Dog Week on Google, how are they feeling?
+
+        Think about:
+        - What just happened? (trigger moment)
+        - What are they hoping for?
+        - What are they worried about?"
+
+Designer: "Just had another fight about who walks the dog.
+           Tired of nagging. Want a system that works without intervention.
+           Worried about adding more complexity to family life."
+```
+
+---
+
+### 4. What's the End Goal (Mutual Success)?
+
+```
+Agent: "What does success look like for both sides?
+
+        For the business: [subscription purchased]
+        For the parent: [what state/feeling/outcome]?"
+
+Designer: "Business: Active subscription
+           Parent: Family harmony restored, dog gets walked consistently,
+                   no more nagging needed"
+```
+
+---
+
+### 5. What's the Shortest Path?
+
+```
+Agent: "Let's map the shortest possible journey from
+        'frustrated parent on Google' to 'active subscription + harmony':
+
+        Natural starting point: Google search result
+
+        What's the absolute minimum path to mutual success?"
+
+Designer: "Google → Landing page → See how it works →
+           Sign up → Set up family → Start using calendar →
+           First walk completed → Everyone happy"
+```
+
+**Agent captures:**
+
+```
+SCENARIO: Parent Onboarding to First Success
+
+START: Google search (frustrated, tired of nagging)
+END: First walk completed (harmony, system working)
+
+CRITICAL PATH:
+1. Landing page (understand solution)
+2. Sign up (commit to trying)
+3. Family setup (get everyone involved)
+4. Calendar (plan first week)
+5. First walk (proof it works)
+
+BUSINESS GOAL: Active subscription
+USER GOAL: Family harmony without nagging
+
+Now let's start sketching this journey.
+```
+
+---
+
+## What This Gives You
+
+**Clear foundation for sketching:**
+
+- ✅ Natural starting point (where user actually is)
+- ✅ Mental state (how they're feeling)
+- ✅ End goal (mutual success defined)
+- ✅ Shortest path (no unnecessary steps)
+- ✅ WHY behind each step (trigger map connection)
+
+**Now you can sketch with purpose:**
+
+- Each page serves the journey
+- Each feature addresses mental state
+- Each step moves toward mutual success
+- Nothing extra, nothing missing
+
+---
+
+## Examples
+
+### Example 1: E-commerce (Sales Goal)
+
+```
+Business Goal: Product sales
+Target Group: Budget-conscious customers
+First Contact: Google search "affordable [product]"
+Mental State: Anxious about hidden costs, need transparency
+End Goal: Purchase completed, confident in value
+Shortest Path: Google → Product page → Transparent pricing →
+               Add to cart → Checkout → Confirmation
+
+SCENARIO: Transparent Purchase Journey
+```
+
+---
+
+### Example 2: SaaS (Subscription Goal)
+
+```
+Business Goal: Monthly subscriptions
+Target Group: Small business owners
+First Contact: ChatGPT recommendation
+Mental State: Overwhelmed, need simple solution
+End Goal: Active subscription, problem solved
+Shortest Path: ChatGPT → Landing → See demo → Sign up →
+               Quick setup → First success
+
+SCENARIO: Frictionless Onboarding
+```
+
+---
+
+### Example 3: Service Booking (Appointment Goal)
+
+```
+Business Goal: Consultation bookings
+Target Group: First-time clients
+First Contact: Friend recommendation
+Mental State: Curious but cautious, need trust
+End Goal: Appointment booked, feeling confident
+Shortest Path: Friend link → About page → Testimonials →
+               Book consultation → Confirmation
+
+SCENARIO: Trust-Building Booking
+```
+
+---
+
+## The Agent's Role
+
+**Not a script. A conversation.**
+
+Agent helps you think through:
+
+- What drives the business?
+- Who makes it happen?
+- Where do they start?
+- How do they feel?
+- What's mutual success?
+- What's the shortest path?
+
+**Then you sketch with clarity.**
+
+---
+
+## Next Step
+
+Once you have:
+
+- ✅ Natural starting point
+- ✅ Mental state
+- ✅ End goal
+- ✅ Shortest path
+
+**Start sketching the journey.**
+
+Each sketch serves the path from trigger to mutual success.
+
+---
+
+[← Back to Business Model Workflow](README.md)

package/src/workflows/4-ux-design/scenario-init/steps-c/00-SCENARIO-INIT-GUIDE.md

@@ -0,0 +1,76 @@
+# Scenario Initialization Guide
+
+**From Trigger Map to first sketch**
+
+---
+
+## Purpose
+
+You've created your Trigger Map. Now: **What should you start sketching?**
+
+This process helps you identify:
+
+- The core feature to design first
+- The natural starting point
+- The user's mental state
+- The shortest path to mutual success
+
+---
+
+## The 7 Steps
+
+### [1. Confirm Platform Strategy](01-platform-confirmation.md)
+
+Inherit platform strategy from Product Brief and confirm for this scenario
+
+### [2. What Feature Delivers Value?](02-feature-selection.md)
+
+Which core feature serves your primary target group?
+
+### [3. Where Do They Encounter It?](03-entry-point.md)
+
+Where does the user first come into contact with your solution?
+
+### [4. What's Their Mental State?](04-mental-state.md)
+
+How are they feeling at this moment?
+
+### [5. What's Mutual Success?](05-mutual-success.md)
+
+What does winning look like for both business and user?
+
+### [6. What's the Shortest Path?](06-shortest-path.md)
+
+Minimum steps from starting point to mutual success
+
+### [7. Create Value Trigger Chain](07-create-vtc.md)
+
+Crystallize scenario strategy before sketching
+
+---
+
+## Examples
+
+### [E-commerce Example](examples/ecommerce-example.md)
+
+Sales-driven transparent purchase journey
+
+### [SaaS Example](examples/saas-example.md)
+
+Subscription-driven frictionless onboarding
+
+### [Service Booking Example](examples/booking-example.md)
+
+Appointment-driven trust-building flow
+
+---
+
+## Next Step
+
+Once you have clarity on all 7 steps (including VTC), **start sketching the journey.**
+
+Each sketch serves the path from trigger to mutual success, guided by the VTC.
+
+---
+
+[← Back to Business Model Workflow](../README.md)

package/src/workflows/4-ux-design/scenario-init/steps-c/01-platform-confirmation.md

@@ -0,0 +1,167 @@
+# Step 0A: Confirm Platform Strategy for Scenario
+
+**Inherit from Product Brief, confirm for this scenario**
+
+---
+
+## Purpose
+
+Before starting scenario design, confirm that the platform strategy from the Product Brief applies to this scenario, or identify if this scenario requires different platform considerations.
+
+## Context for Agent
+
+The Product Brief defines the overall platform strategy for the product. However, some scenarios might have different platform requirements. For example:
+- Onboarding might be web-only while daily use is mobile app
+- Admin features might be desktop-only while customer features are mobile
+- Some scenarios might span multiple platforms (start on web, continue on mobile)
+
+## Instructions
+
+### 1. Load Platform Strategy from Product Brief
+
+<action>
+Read the Product Brief and extract the Platform & Device Strategy section:
+
+- primary_platform
+- supported_devices
+- device_priority
+- interaction_models
+- offline_requirements
+- native_features_needed
+</action>
+
+### 2. Present Platform Strategy
+
+<output>
+**Platform Strategy from Product Brief:**
+
+**Primary Platform:** {primary_platform}
+**Supported Devices:** {supported_devices}
+**Device Priority:** {device_priority}
+**Interaction Models:** {interaction_models}
+
+---
+
+**For this scenario: {scenario_name}**
+
+Does this platform strategy apply to this entire scenario, or does this scenario have specific platform requirements?
+</output>
+
+### 3. Ask Scenario-Specific Platform Questions
+
+<ask>
+**Scenario Platform Questions:**
+
+1. **Does this scenario use the same platform as the Product Brief?**
+   - Yes, same platform strategy applies
+   - No, this scenario has different platform requirements
+   - Partially, this scenario spans multiple platforms
+
+2. **If different or spanning platforms:**
+   - Which platforms are involved in this scenario?
+   - How does the user move between platforms?
+   - What is the primary platform for this scenario?
+
+3. **Are there scenario-specific device considerations?**
+   - Does this scenario prioritize different devices?
+   - Are there device-specific features in this scenario?
+   - Any device limitations for this scenario?
+
+4. **Page type expectations for this scenario:**
+   - Full pages (standard navigation flow)
+   - Modal dialogs (overlays, popups)
+   - Embedded components (widgets, iframes)
+   - System notifications (email, SMS, push)
+   - Mixed (specify which pages are which type)
+
+Your answers:
+</ask>
+
+### 4. Document Scenario Platform Strategy
+
+<action>
+Create or update scenario overview document with platform information:
+
+```markdown
+# Scenario {number}: {scenario_name}
+
+## Scenario Platform Strategy
+
+**Inherits From:** Product Brief Platform Strategy
+**Platform Alignment:** {same/different/spanning}
+
+### Platform Details for This Scenario
+
+**Primary Platform:** {platform for this scenario}
+**Devices Used:** {devices in this scenario}
+**Device Priority:** {device priority for this scenario}
+
+**Cross-Platform Flow (if applicable):**
+{describe how user moves between platforms in this scenario}
+
+**Page Types in This Scenario:**
+- {Page 1}: Full page (responsive web)
+- {Page 2}: Modal dialog (overlay)
+- {Page 3}: Email template
+- etc.
+
+**Scenario-Specific Considerations:**
+{any unique platform requirements or constraints for this scenario}
+
+---
+```
+</action>
+
+### 5. Confirm Understanding
+
+<output>
+**Scenario Platform Summary:**
+
+This scenario will be designed for:
+- **Platform:** {platform}
+- **Primary Device:** {device}
+- **Page Types:** {types}
+
+All pages in this scenario will inherit this platform context, ensuring consistent design decisions.
+
+Ready to proceed with scenario initialization?
+</output>
+
+<ask>
+**Confirm scenario platform strategy:**
+- [C] Continue - platform strategy is clear
+- [R] Revise - need to adjust platform for this scenario
+- [D] Discuss - have questions about platform implications
+</ask>
+
+## Next Step
+
+After confirming platform strategy, proceed to 01-feature-selection.md
+
+## State Update
+
+Store scenario platform information for reference during page specification:
+
+```yaml
+scenario_platform:
+  inherits_from: 'product_brief'
+  alignment: '{same/different/spanning}'
+  primary_platform: '{platform}'
+  devices_used: '{devices}'
+  device_priority: '{priority}'
+  page_types: '{types}'
+  cross_platform_flow: '{flow if applicable}'
+```
+
+---
+
+**Why This Matters:**
+
+Platform context affects every design decision:
+- **Layout:** Mobile-first vs desktop-first
+- **Navigation:** Touch gestures vs mouse clicks
+- **Interactions:** Native patterns vs web patterns
+- **Content:** Concise for mobile vs detailed for desktop
+- **Features:** What's possible on each platform
+
+Confirming this upfront ensures all scenario pages are designed consistently for the right platform.

package/src/workflows/4-ux-design/scenario-init/steps-c/02-feature-selection.md

@@ -0,0 +1,70 @@
+# Question 1: What Feature Delivers the Most Value?
+
+**Connect Trigger Map to the first thing you should design**
+
+---
+
+## The Question
+
+```
+Agent: "Looking at your Trigger Map and prioritized feature list,
+        what's the core feature that delivers value to your
+        primary target group?
+
+        This is what we should sketch first."
+```
+
+---
+
+## Why This Matters
+
+Your Trigger Map already identified:
+
+- Primary target group
+- What triggers their need
+- What outcome they want
+
+**This question connects that to a specific feature to design.**
+
+---
+
+## Example: Dog Week
+
+**From Trigger Map:**
+
+- Target: Parents
+- Trigger: Family conflict over dog care
+- Outcome: Accountability without nagging
+
+**Feature Selection:**
+
+```
+Designer: "The family dog walk calendar - it solves the accountability
+           problem that causes conflict."
+```
+
+**Why this feature first:**
+
+- Directly addresses the trigger (conflict)
+- Serves the primary target group (parents)
+- Delivers the desired outcome (accountability)
+
+---
+
+## What Agent Captures
+
+```
+CORE FEATURE: Family dog walk calendar
+WHY: Solves accountability problem that causes family conflict
+TARGET: Parents (primary decision makers)
+```
+
+---
+
+## Next Question
+
+[Where does the user first encounter this?](02-entry-point.md)
+
+---
+
+[← Back to Guide](00-SCENARIO-INIT-GUIDE.md)

package/src/workflows/4-ux-design/scenario-init/steps-c/03-entry-point.md

@@ -0,0 +1,67 @@
+# Question 2: Where Does the User First Encounter This?
+
+**Identify the natural starting point for your scenario**
+
+---
+
+## The Question
+
+```
+Agent: "Where does your primary target group first come into
+        contact with this solution?"
+```
+
+---
+
+## Why This Matters
+
+The entry point determines:
+
+- Where the scenario starts
+- What mental state they're in
+- What context you're designing for
+
+**Common entry points:**
+
+- Google search
+- ChatGPT recommendation
+- App store browsing
+- Friend recommendation
+- Social media ad
+- Direct URL (returning user)
+
+---
+
+## Example: Dog Week
+
+```
+Designer: "Google search - they're frustrated with family conflict
+           over dog care."
+```
+
+**Why this matters:**
+
+- They're actively searching (high intent)
+- They're frustrated (emotional state)
+- They need immediate clarity (landing page critical)
+
+---
+
+## What Agent Captures
+
+```
+ENTRY POINT: Google search
+CONTEXT: Actively searching for solution
+INTENT: High (frustrated, need help now)
+IMPLICATION: Landing page must address frustration immediately
+```
+
+---
+
+## Next Question
+
+[What's their mental state at this moment?](03-mental-state.md)
+
+---
+
+[← Back to Guide](00-SCENARIO-INIT-GUIDE.md)

package/src/workflows/4-ux-design/scenario-init/steps-c/04-mental-state.md

@@ -0,0 +1,74 @@
+# Question 3: What's Their Mental State at This Moment?
+
+**Understand the emotional context for design decisions**
+
+---
+
+## The Question
+
+```
+Agent: "When they find your solution, how are they feeling?
+
+        Think about:
+        - What just happened? (trigger moment)
+        - What are they hoping for?
+        - What are they worried about?"
+```
+
+---
+
+## Why This Matters
+
+Mental state determines:
+
+- Tone of content
+- Complexity of interface
+- Type of features needed
+- What NOT to do
+
+**Design for the human, not just the task.**
+
+---
+
+## Example: Dog Week
+
+```
+Designer: "Just had another fight about who walks the dog.
+           Tired of nagging. Want a system that works without intervention.
+           Worried about adding more complexity to family life."
+```
+
+**Design implications:**
+
+- Tone: Empathetic, not preachy
+- Interface: Simple, not complex
+- Features: Automated accountability, not more work
+- Avoid: Notifications that feel like nagging
+
+---
+
+## What Agent Captures
+
+```
+MENTAL STATE:
+- Trigger: Just had family fight
+- Feeling: Tired, frustrated
+- Hope: System that works without intervention
+- Fear: Adding more complexity
+
+DESIGN IMPLICATIONS:
+- Keep it simple
+- Automate accountability
+- Gentle, not pushy
+- No nagging-style notifications
+```
+
+---
+
+## Next Question
+
+[What's the end goal (mutual success)?](04-mutual-success.md)
+
+---
+
+[← Back to Guide](00-SCENARIO-INIT-GUIDE.md)