docs: update all documentation and add AI tooling configs
- Rewrite README.md with current architecture, features and stack - Update docs/API.md with all current endpoints (corporate, BI, client 360) - Update docs/ARCHITECTURE.md with cache, modular queries, services, ETL - Update docs/GUIA-USUARIO.md for all roles (admin, corporate, agente) - Add docs/INDEX.md documentation index - Add PROJETO.md comprehensive project reference - Add BI-CCC-Implementation-Guide.md - Include AI agent configs (.claude, .agents, .gemini, _bmad) - Add netbird VPN configuration - Add status report Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -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.
|
||||
@@ -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)
|
||||
@@ -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)
|
||||
@@ -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)
|
||||
@@ -0,0 +1,69 @@
|
||||
# Question 4: What's the End Goal (Mutual Success)?
|
||||
|
||||
**Define winning for both business and user**
|
||||
|
||||
---
|
||||
|
||||
## The Question
|
||||
|
||||
```
|
||||
Agent: "What does success look like for both sides?
|
||||
|
||||
For the business: [what outcome?]
|
||||
For the user: [what state/feeling/outcome?]"
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Why This Matters
|
||||
|
||||
Success must be mutual:
|
||||
|
||||
- Business gets value
|
||||
- User gets value
|
||||
- Both are happy
|
||||
|
||||
**If only one side wins, the relationship fails.**
|
||||
|
||||
---
|
||||
|
||||
## Example: Dog Week
|
||||
|
||||
```
|
||||
Designer: "Business: Active subscription
|
||||
User: Family harmony restored, dog gets walked consistently,
|
||||
no more nagging needed"
|
||||
```
|
||||
|
||||
**Why both matter:**
|
||||
|
||||
- Business needs subscription (revenue)
|
||||
- User needs harmony (problem solved)
|
||||
- Subscription only works if harmony is real
|
||||
- Harmony only happens if product delivers
|
||||
|
||||
**Mutual success = sustainable business.**
|
||||
|
||||
---
|
||||
|
||||
## What Agent Captures
|
||||
|
||||
```
|
||||
MUTUAL SUCCESS:
|
||||
|
||||
Business Goal: Active subscription (recurring revenue)
|
||||
User Goal: Family harmony + consistent dog care + no nagging
|
||||
|
||||
Success Metric: User stays subscribed because harmony is real
|
||||
Failure Point: User cancels if product doesn't reduce conflict
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Next Question
|
||||
|
||||
[What's the shortest path to get there?](05-shortest-path.md)
|
||||
|
||||
---
|
||||
|
||||
[← Back to Guide](00-SCENARIO-INIT-GUIDE.md)
|
||||
@@ -0,0 +1,92 @@
|
||||
# Question 5: What's the Shortest Path?
|
||||
|
||||
**Map the minimum journey from starting point to mutual success**
|
||||
|
||||
---
|
||||
|
||||
## The Question
|
||||
|
||||
```
|
||||
Agent: "Let's map the shortest possible journey from
|
||||
[starting point] to [mutual success]:
|
||||
|
||||
What's the absolute minimum path?"
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Why This Matters
|
||||
|
||||
Shortest path means:
|
||||
|
||||
- No unnecessary steps
|
||||
- No feature bloat
|
||||
- Clear focus
|
||||
- Faster to mutual success
|
||||
|
||||
**Every extra step is a chance to lose the user.**
|
||||
|
||||
---
|
||||
|
||||
## Example: Dog Week
|
||||
|
||||
```
|
||||
Agent: "From 'frustrated parent on Google' to 'active subscription + harmony':
|
||||
What's the minimum path?"
|
||||
|
||||
Designer: "Google → Landing page → See how it works →
|
||||
Sign up → Set up family → Start using calendar →
|
||||
First walk completed → Everyone happy"
|
||||
```
|
||||
|
||||
**Why this path:**
|
||||
|
||||
- Landing: Understand solution (addresses frustration)
|
||||
- How it works: See it's simple (addresses complexity fear)
|
||||
- Sign up: Commit to trying (low friction)
|
||||
- Family setup: Get everyone involved (necessary for accountability)
|
||||
- Calendar: Plan first week (immediate action)
|
||||
- First walk: Proof it works (mutual success moment)
|
||||
|
||||
---
|
||||
|
||||
## What 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
|
||||
|
||||
Each step serves the journey. Nothing extra.
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Next Step
|
||||
|
||||
With all 5 questions answered, you have:
|
||||
|
||||
- ✅ Core feature (what to design)
|
||||
- ✅ Entry point (where to start)
|
||||
- ✅ Mental state (how they feel)
|
||||
- ✅ Mutual success (where to end)
|
||||
- ✅ Shortest path (how to get there)
|
||||
|
||||
**→ Proceed to [Step 7: Reference Trigger Map](07-reference-trigger-map.md)**
|
||||
|
||||
Before sketching, identify the relevant Trigger Map context for this scenario.
|
||||
|
||||
---
|
||||
|
||||
[← Back to Guide](00-SCENARIO-INIT-GUIDE.md)
|
||||
@@ -0,0 +1,80 @@
|
||||
# 7. Reference Trigger Map for Scenario
|
||||
|
||||
**Purpose:** Identify the relevant Trigger Map nodes for this scenario before sketching
|
||||
|
||||
---
|
||||
|
||||
## Why Now?
|
||||
|
||||
You've defined:
|
||||
- Feature that delivers value
|
||||
- Entry point
|
||||
- Mental state
|
||||
- Mutual success
|
||||
- Shortest path
|
||||
|
||||
**Perfect time to anchor the scenario to the Trigger Map.** Pick the specific business goal, persona, and driving forces that apply to this scenario.
|
||||
|
||||
---
|
||||
|
||||
## Agent Instructions
|
||||
|
||||
> "Before we start sketching, let's identify the Trigger Map context for this scenario.
|
||||
>
|
||||
> From your Trigger Map, which of these apply to this scenario?
|
||||
> - **Business Goal** — which goal does this scenario serve?
|
||||
> - **User** — which persona is this scenario for?
|
||||
> - **Driving Forces** — which positive and negative drivers are most relevant?
|
||||
>
|
||||
> This anchors every design decision to strategy."
|
||||
|
||||
---
|
||||
|
||||
## Process
|
||||
|
||||
1. **Load the Trigger Map** from `{output_folder}/B-Trigger-Map/00-trigger-map.md`
|
||||
2. **Present the business goals** — ask which one this scenario primarily serves
|
||||
3. **Present the personas** — confirm which persona this scenario targets
|
||||
4. **Present driving forces** for that persona — ask which 2-4 are most relevant here
|
||||
5. **Summarize** the selected context
|
||||
|
||||
This is a **selection exercise**, not a workshop. It takes 2-3 minutes.
|
||||
|
||||
---
|
||||
|
||||
## Save Context
|
||||
|
||||
Note the selected Trigger Map context in the scenario overview file:
|
||||
|
||||
```markdown
|
||||
## Trigger Map Context
|
||||
|
||||
**Business Goal:** [selected goal from Trigger Map]
|
||||
**Persona:** [selected persona]
|
||||
**Key Driving Forces:**
|
||||
- Positive: [selected positive drivers]
|
||||
- Negative: [selected negative drivers]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## If No Trigger Map Exists
|
||||
|
||||
If the Trigger Map hasn't been created yet:
|
||||
- Inform the user: "There's no Trigger Map for this project yet. I'd recommend completing Phase 2 (Trigger Mapping) first — it gives us the strategic foundation for design decisions."
|
||||
- If the user wants to proceed anyway, use whatever business context is available from the Product Brief and note the gap.
|
||||
|
||||
---
|
||||
|
||||
## Next Step
|
||||
|
||||
**Start sketching the scenario journey!**
|
||||
|
||||
Each sketch should:
|
||||
- Serve the selected driving forces
|
||||
- Support the shortest path to mutual success
|
||||
- Address the target persona's needs
|
||||
|
||||
---
|
||||
|
||||
*Strategic context identified — now sketch with purpose!*
|
||||
@@ -0,0 +1,64 @@
|
||||
# Example: Service Booking (Appointment Goal)
|
||||
|
||||
**Trust-building booking flow**
|
||||
|
||||
---
|
||||
|
||||
## The 5 Questions
|
||||
|
||||
### 1. Core Feature
|
||||
|
||||
```
|
||||
"Consultation booking with social proof - testimonials + credentials"
|
||||
```
|
||||
|
||||
### 2. Entry Point
|
||||
|
||||
```
|
||||
"Friend recommendation (shared link)"
|
||||
```
|
||||
|
||||
### 3. Mental State
|
||||
|
||||
```
|
||||
"Curious but cautious, need to trust before committing time/money"
|
||||
```
|
||||
|
||||
### 4. Mutual Success
|
||||
|
||||
```
|
||||
Business: Consultation booked (lead captured)
|
||||
User: Confident in decision, looking forward to meeting
|
||||
```
|
||||
|
||||
### 5. Shortest Path
|
||||
|
||||
```
|
||||
Friend link → About page → Testimonials →
|
||||
Book consultation → Confirmation
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Scenario Captured
|
||||
|
||||
```
|
||||
SCENARIO: Trust-Building Booking
|
||||
|
||||
START: Friend recommendation (curious but cautious)
|
||||
END: Consultation booked (confident, excited)
|
||||
|
||||
CRITICAL PATH:
|
||||
1. About page → Understand who you are
|
||||
2. Testimonials → See social proof
|
||||
3. Credentials → Verify expertise
|
||||
4. Book consultation → Commit with confidence
|
||||
5. Confirmation → Excitement reinforced
|
||||
|
||||
BUSINESS GOAL: Consultation booked
|
||||
USER GOAL: Confident decision, trust established
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
[← Back to Guide](../00-SCENARIO-INIT-GUIDE.md)
|
||||
@@ -0,0 +1,64 @@
|
||||
# Example: E-commerce (Sales Goal)
|
||||
|
||||
**Transparent purchase journey**
|
||||
|
||||
---
|
||||
|
||||
## The 5 Questions
|
||||
|
||||
### 1. Core Feature
|
||||
|
||||
```
|
||||
"Transparent pricing breakdown - shows all costs upfront"
|
||||
```
|
||||
|
||||
### 2. Entry Point
|
||||
|
||||
```
|
||||
"Google search 'affordable [product]'"
|
||||
```
|
||||
|
||||
### 3. Mental State
|
||||
|
||||
```
|
||||
"Anxious about hidden costs, need transparency before committing"
|
||||
```
|
||||
|
||||
### 4. Mutual Success
|
||||
|
||||
```
|
||||
Business: Purchase completed
|
||||
User: Confident in value, no surprise costs
|
||||
```
|
||||
|
||||
### 5. Shortest Path
|
||||
|
||||
```
|
||||
Google → Product page → Transparent pricing →
|
||||
Add to cart → Checkout → Confirmation
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Scenario Captured
|
||||
|
||||
```
|
||||
SCENARIO: Transparent Purchase Journey
|
||||
|
||||
START: Google search (anxious about hidden costs)
|
||||
END: Purchase completed (confident in value)
|
||||
|
||||
CRITICAL PATH:
|
||||
1. Product page → See product + upfront pricing
|
||||
2. Pricing breakdown → Understand all costs
|
||||
3. Add to cart → Commit to purchase
|
||||
4. Checkout → Complete transaction
|
||||
5. Confirmation → Confidence reinforced
|
||||
|
||||
BUSINESS GOAL: Product sale
|
||||
USER GOAL: Confident purchase, no surprises
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
[← Back to Guide](../00-SCENARIO-INIT-GUIDE.md)
|
||||
@@ -0,0 +1,64 @@
|
||||
# Example: SaaS (Subscription Goal)
|
||||
|
||||
**Frictionless onboarding**
|
||||
|
||||
---
|
||||
|
||||
## The 5 Questions
|
||||
|
||||
### 1. Core Feature
|
||||
|
||||
```
|
||||
"Quick setup wizard - gets users to first success fast"
|
||||
```
|
||||
|
||||
### 2. Entry Point
|
||||
|
||||
```
|
||||
"ChatGPT recommendation"
|
||||
```
|
||||
|
||||
### 3. Mental State
|
||||
|
||||
```
|
||||
"Overwhelmed by current tools, need simple solution that just works"
|
||||
```
|
||||
|
||||
### 4. Mutual Success
|
||||
|
||||
```
|
||||
Business: Active monthly subscription
|
||||
User: Problem solved, no complexity added
|
||||
```
|
||||
|
||||
### 5. Shortest Path
|
||||
|
||||
```
|
||||
ChatGPT → Landing → See demo → Sign up →
|
||||
Quick setup → First success
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Scenario Captured
|
||||
|
||||
```
|
||||
SCENARIO: Frictionless Onboarding
|
||||
|
||||
START: ChatGPT recommendation (overwhelmed, need simplicity)
|
||||
END: First success (problem solved, staying subscribed)
|
||||
|
||||
CRITICAL PATH:
|
||||
1. Landing → Understand it's simple
|
||||
2. Demo → See it in action
|
||||
3. Sign up → Low friction entry
|
||||
4. Quick setup → Minimal configuration
|
||||
5. First success → Immediate value
|
||||
|
||||
BUSINESS GOAL: Monthly subscription
|
||||
USER GOAL: Problem solved without complexity
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
[← Back to Guide](../00-SCENARIO-INIT-GUIDE.md)
|
||||
@@ -0,0 +1,536 @@
|
||||
# Scenario Initialization Dialog
|
||||
|
||||
**Agent**: Freya WDS Designer Agent
|
||||
**Purpose**: Define a complete user scenario before creating page specifications or prototypes
|
||||
**Output**: `[Scenario-Number]-[Scenario-Name].md` (scenario specification)
|
||||
|
||||
---
|
||||
|
||||
## 🎯 **When to Use This Workflow**
|
||||
|
||||
**Use when**:
|
||||
- Starting a new user journey/scenario
|
||||
- No scenario specification exists yet
|
||||
- Need to define what pages belong in this scenario
|
||||
|
||||
**Skip when**:
|
||||
- Scenario specification already exists
|
||||
- Just adding one new page to existing scenario
|
||||
|
||||
---
|
||||
|
||||
## 🤝 **Collaboration Approach**
|
||||
|
||||
**Freya contributes both**:
|
||||
- **Business perspective** (goals, metrics, value)
|
||||
- **UX perspective** (flow, interactions, usability)
|
||||
|
||||
---
|
||||
|
||||
## 📝 **The Dialog**
|
||||
|
||||
### **Step 1: Scenario Overview**
|
||||
|
||||
> "**Let's define this user scenario together!**
|
||||
>
|
||||
> **What is the high-level purpose of this scenario?**
|
||||
>
|
||||
> In one sentence, what is the user trying to accomplish?"
|
||||
|
||||
**Wait for response**
|
||||
|
||||
**Example**: "Family members coordinate who walks the dog each day"
|
||||
|
||||
**Record**:
|
||||
- `scenario.overview`
|
||||
|
||||
---
|
||||
|
||||
### **Step 2: User Context**
|
||||
|
||||
> "**Who is the user and what's their situation?**
|
||||
>
|
||||
> Tell me about:
|
||||
> - Who is the primary user? (role, characteristics)
|
||||
> - What's their context? (where are they, what's happening)
|
||||
> - What triggered them to start this journey?"
|
||||
|
||||
**Wait for response**
|
||||
|
||||
**Example**:
|
||||
- User: Family member (parent or child)
|
||||
- Context: Planning the upcoming week, needs to coordinate dog care
|
||||
- Trigger: New week starting, family needs to divide dog walking responsibilities
|
||||
|
||||
**Record**:
|
||||
- `scenario.user_context`
|
||||
- `scenario.trigger_points`
|
||||
|
||||
---
|
||||
|
||||
### **Step 2b: Link to Trigger Map** (if Trigger Map exists)
|
||||
|
||||
**Check**: Does `docs/B-Trigger-Map/` folder exist?
|
||||
|
||||
**If YES**:
|
||||
> "**I see you have a Trigger Map defined!**
|
||||
>
|
||||
> **Which trigger(s) from your Trigger Map does this scenario address?**
|
||||
>
|
||||
> [Agent reads Trigger Map and lists triggers]
|
||||
>
|
||||
> Available triggers:
|
||||
> - [Trigger ID] [Trigger name]
|
||||
> - [Trigger ID] [Trigger name]
|
||||
> ...
|
||||
>
|
||||
> **Which trigger(s) does this scenario solve?** (list IDs or 'none')"
|
||||
|
||||
**Wait for response**
|
||||
|
||||
**Example**:
|
||||
- TM-03: "Dog forgotten at home all day"
|
||||
- TM-07: "Family arguments about who's not pulling their weight"
|
||||
- TM-12: "Kids not taking responsibility for pet care"
|
||||
|
||||
**Record**:
|
||||
- `scenario.trigger_map_links` (array of trigger IDs)
|
||||
|
||||
**If NO Trigger Map**: Skip this step
|
||||
|
||||
---
|
||||
|
||||
### **Step 3: User Goals**
|
||||
|
||||
> "**What are the user's specific goals?**
|
||||
>
|
||||
> List 2-5 concrete goals they want to achieve."
|
||||
|
||||
**Wait for response**
|
||||
|
||||
**Example**:
|
||||
1. See who has walked the dog this week
|
||||
2. Book a time slot to walk the dog
|
||||
3. Track their contributions vs. other family members
|
||||
4. Get reminded when it's their turn
|
||||
|
||||
**Record**:
|
||||
- `scenario.user_goals` (array)
|
||||
|
||||
---
|
||||
|
||||
### **Step 4: User Value & Fears**
|
||||
|
||||
> "**How will completing this scenario add value to the user?**
|
||||
>
|
||||
> **Positive Goals** (what they want to achieve):
|
||||
> - [Suggest 3-5 positive goals based on scenario]
|
||||
>
|
||||
> **Fears to Avoid** (what they want to prevent):
|
||||
> - [Suggest 3-5 fears/concerns based on scenario]
|
||||
>
|
||||
> **Does this match their motivations? Any adjustments?**"
|
||||
|
||||
**Wait for response**
|
||||
|
||||
**Example**:
|
||||
|
||||
**Positive Goals**:
|
||||
- Feel organized and in control of dog care
|
||||
- Contribute fairly without being nagged
|
||||
- See appreciation for their efforts
|
||||
- Spend quality time with the dog
|
||||
- Maintain family harmony
|
||||
|
||||
**Fears to Avoid**:
|
||||
- Dog being neglected or forgotten
|
||||
- Unfair distribution of responsibilities
|
||||
- Family conflict over who's doing more
|
||||
- Being blamed for missed walks
|
||||
- Feeling guilty about not contributing
|
||||
|
||||
**Record**:
|
||||
- `scenario.user_positive_goals` (array)
|
||||
- `scenario.user_fears` (array)
|
||||
|
||||
---
|
||||
|
||||
### **Step 5: Success Criteria**
|
||||
|
||||
> "**How do we know the user succeeded?**
|
||||
>
|
||||
> What does success look like? What metrics matter?"
|
||||
|
||||
**Wait for response**
|
||||
|
||||
**Example**:
|
||||
- User successfully books a walk
|
||||
- Family coordination is visible
|
||||
- Dog gets walked regularly (all slots filled)
|
||||
- Fair distribution of responsibilities
|
||||
|
||||
**Record**:
|
||||
- `scenario.success_criteria` (array)
|
||||
|
||||
---
|
||||
|
||||
### **Step 5: Entry Points**
|
||||
|
||||
> "**How does the user enter this scenario?**
|
||||
>
|
||||
> Where are they coming from? What actions lead them here?"
|
||||
|
||||
**Wait for response**
|
||||
|
||||
**Example**:
|
||||
- From home dashboard ("Dog Calendar" tab)
|
||||
- From notification ("Your turn to walk Rufus!")
|
||||
- From family chat ("Who's walking the dog?")
|
||||
|
||||
**Record**:
|
||||
- `scenario.entry_points` (array)
|
||||
|
||||
---
|
||||
|
||||
### **Step 6: Exit Points**
|
||||
|
||||
> "**Where does the user go after completing this scenario?**
|
||||
>
|
||||
> What are the natural next steps?"
|
||||
|
||||
**Wait for response**
|
||||
|
||||
**Example**:
|
||||
- Back to home dashboard
|
||||
- To dog health tracking (after walk completed)
|
||||
- To family leaderboard (check standings)
|
||||
- Exit app (done for now)
|
||||
|
||||
**Record**:
|
||||
- `scenario.exit_points` (array)
|
||||
|
||||
---
|
||||
|
||||
### **Step 7: Pages in Scenario**
|
||||
|
||||
> "**Let's map out the pages needed for this journey.**
|
||||
>
|
||||
> I'll suggest pages based on the goals, you can adjust.
|
||||
>
|
||||
> **Proposed pages**:
|
||||
> 1. [Page number] [Page name] - [Purpose]
|
||||
> 2. [Page number] [Page name] - [Purpose]
|
||||
> ...
|
||||
>
|
||||
> **Does this flow make sense? Any pages to add/remove/change?**"
|
||||
|
||||
**Wait for response**
|
||||
|
||||
**Example**:
|
||||
1. 3.1 Dog Calendar Booking - View week, book walks, see family contributions
|
||||
2. 3.2 Walk In Progress - Start/complete walk with timer
|
||||
3. 3.3 Walk Summary - Review completed walk, add notes
|
||||
|
||||
**Record**:
|
||||
- `scenario.pages` (array with page_number, page_name, purpose, sequence)
|
||||
|
||||
---
|
||||
|
||||
### **Step 8: Key Interactions**
|
||||
|
||||
> "**What are the critical moments in this journey?**
|
||||
>
|
||||
> What interactions are most important to get right?"
|
||||
|
||||
**Wait for response**
|
||||
|
||||
**Example**:
|
||||
- Viewing available time slots (must be clear and fast)
|
||||
- Booking a walk (must be instant feedback)
|
||||
- Seeing real-time updates (when someone else books)
|
||||
- Starting a walk (clear transition, timer visible)
|
||||
|
||||
**Record**:
|
||||
- `scenario.key_interactions` (array)
|
||||
|
||||
---
|
||||
|
||||
### **Step 9: Edge Cases & Challenges**
|
||||
|
||||
> "**What could go wrong? What edge cases should we handle?**"
|
||||
|
||||
**Wait for response**
|
||||
|
||||
**Example**:
|
||||
- Someone books same slot simultaneously
|
||||
- User tries to book when dog already out walking
|
||||
- No one has booked upcoming slots (motivation needed)
|
||||
- Child vs. parent permissions (can child edit others' bookings?)
|
||||
|
||||
**Record**:
|
||||
- `scenario.edge_cases` (array)
|
||||
|
||||
---
|
||||
|
||||
### **Step 10: Business Value** (Freya's focus)
|
||||
|
||||
> "**Freya, what's the business value of this scenario?**
|
||||
>
|
||||
> **How will users completing this scenario add value to business goals?**
|
||||
>
|
||||
> I'll suggest based on what we've discussed:
|
||||
>
|
||||
> **Suggested Business Value**:
|
||||
> - [Value 1]
|
||||
> - [Value 2]
|
||||
> - [Value 3]
|
||||
>
|
||||
> **Metrics to track**:
|
||||
> - [Metric 1]
|
||||
> - [Metric 2]
|
||||
> - [Metric 3]
|
||||
>
|
||||
> **Does this align with business goals? Any adjustments?**"
|
||||
|
||||
**Wait for response**
|
||||
|
||||
**Example**:
|
||||
|
||||
**Business Value**:
|
||||
- Increases family engagement (active users per family)
|
||||
- Reduces pet neglect (walks completed per week)
|
||||
- Demonstrates app value (feature usage = retention)
|
||||
- Drives word-of-mouth (families share success)
|
||||
- Premium feature potential (leaderboard, insights)
|
||||
|
||||
**Metrics**:
|
||||
- Walks booked vs. completed ratio
|
||||
- Family participation rate (% of members active)
|
||||
- Daily active users
|
||||
- Feature retention (return rate)
|
||||
- NPS increase
|
||||
|
||||
**Record**:
|
||||
- `scenario.business_value`
|
||||
- `scenario.metrics` (array)
|
||||
|
||||
---
|
||||
|
||||
### **Step 11: UX Priorities** (Freya's focus)
|
||||
|
||||
> "**Freya, what are the top UX priorities for this scenario?**
|
||||
>
|
||||
> What must we get right for great user experience?"
|
||||
|
||||
**Wait for response**
|
||||
|
||||
**Example**:
|
||||
- Speed: Calendar loads instantly
|
||||
- Clarity: Week view shows all info at a glance
|
||||
- Feedback: Booking feels immediate and satisfying
|
||||
- Gamification: Leaderboard motivates participation
|
||||
- Mobile-first: Easy to book on-the-go
|
||||
|
||||
**Record**:
|
||||
- `scenario.ux_priorities` (array)
|
||||
|
||||
---
|
||||
|
||||
## ✅ **Step 12: Create Scenario Specification**
|
||||
|
||||
**Agent creates**: `docs/C-UX-Scenarios/[Number]-[Name]/[Number]-[Name].md`
|
||||
|
||||
**File structure**:
|
||||
```markdown
|
||||
# [Scenario Number]: [Scenario Name]
|
||||
|
||||
## Overview
|
||||
[One sentence purpose]
|
||||
|
||||
## User Context
|
||||
**Who**: [Primary user role/characteristics]
|
||||
**Context**: [Situation/environment]
|
||||
**Trigger**: [What prompted this journey]
|
||||
|
||||
## Trigger Map Links
|
||||
**Addresses these pain points**:
|
||||
- [Trigger ID] [Trigger name from Trigger Map]
|
||||
- [Trigger ID] [Trigger name from Trigger Map]
|
||||
...
|
||||
|
||||
_(If no Trigger Map exists, omit this section)_
|
||||
|
||||
## User Goals
|
||||
1. [Goal 1]
|
||||
2. [Goal 2]
|
||||
...
|
||||
|
||||
## User Value & Fears
|
||||
|
||||
### Positive Goals (What Users Want)
|
||||
- [Positive goal 1]
|
||||
- [Positive goal 2]
|
||||
...
|
||||
|
||||
### Fears to Avoid (What Users Want to Prevent)
|
||||
- [Fear 1]
|
||||
- [Fear 2]
|
||||
...
|
||||
|
||||
## Success Criteria
|
||||
- [Criterion 1]
|
||||
- [Criterion 2]
|
||||
...
|
||||
|
||||
## Entry Points
|
||||
- [Entry point 1]
|
||||
- [Entry point 2]
|
||||
...
|
||||
|
||||
## Exit Points
|
||||
- [Exit point 1]
|
||||
- [Exit point 2]
|
||||
...
|
||||
|
||||
## Pages in This Scenario
|
||||
|
||||
### [Page Number] [Page Name]
|
||||
**Purpose**: [Why this page exists]
|
||||
**Sequence**: [When it appears in journey]
|
||||
**Key Actions**: [What user does here]
|
||||
|
||||
[Repeat for each page...]
|
||||
|
||||
## Key Interactions
|
||||
- [Interaction 1]
|
||||
- [Interaction 2]
|
||||
...
|
||||
|
||||
## Edge Cases
|
||||
- [Edge case 1]
|
||||
- [Edge case 2]
|
||||
...
|
||||
|
||||
## Business Value
|
||||
[Why this matters]
|
||||
|
||||
**Metrics**:
|
||||
- [Metric 1]
|
||||
- [Metric 2]
|
||||
...
|
||||
|
||||
## UX Priorities
|
||||
1. [Priority 1]
|
||||
2. [Priority 2]
|
||||
...
|
||||
|
||||
## Notes
|
||||
[Any additional context]
|
||||
|
||||
---
|
||||
|
||||
**Status**: Defined
|
||||
**Created by**: [Agent name]
|
||||
**Date**: [Date]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 🎉 **Step 13: Completion**
|
||||
|
||||
> "✅ **Scenario specification created!**
|
||||
>
|
||||
> **File**: `docs/C-UX-Scenarios/[Number]-[Name]/[Number]-[Name].md`
|
||||
>
|
||||
> **Next steps**:
|
||||
> 1. **Update Trigger Map** (add link to this scenario from triggers)
|
||||
> 2. **Create page specifications** (for each page in scenario)
|
||||
> 3. **Create interactive prototypes** (if needed)
|
||||
> 4. **Validate with stakeholders** (review scenario flow)
|
||||
>
|
||||
> **Would you like to**:
|
||||
> - Update the Trigger Map with this scenario link?
|
||||
> - Start defining page specifications?
|
||||
> - Create prototypes?
|
||||
> - Review the scenario doc?"
|
||||
|
||||
**If user wants to update Trigger Map**:
|
||||
|
||||
**Actions**:
|
||||
1. Read `docs/B-Trigger-Map/[Trigger-Map-File].md` for each linked trigger
|
||||
2. Add scenario link to each trigger's "How We Address This" or "Related Scenarios" section:
|
||||
```markdown
|
||||
**Addressed in**: [Scenario 03: Booking Dog Walks](../C-UX-Scenarios/03-Booking-Dog-Walks/03-Booking-Dog-Walks.md)
|
||||
```
|
||||
3. Confirm updates complete
|
||||
|
||||
---
|
||||
|
||||
## 📋 **Example Complete Exchange**
|
||||
|
||||
**User**: "I want to create a scenario for booking dog walks"
|
||||
|
||||
**Freya**: "Great! Let's define this together. What's the high-level purpose?"
|
||||
|
||||
**User**: "Family members coordinate who walks the dog each day"
|
||||
|
||||
**Freya**: "Perfect! Who is the primary user and what's their context?"
|
||||
|
||||
**User**: "Any family member - parent or child - planning the week ahead"
|
||||
|
||||
**Freya**: "What are their specific goals?"
|
||||
|
||||
**User**: "See who walked the dog, book a time slot, track contributions, get fair distribution"
|
||||
|
||||
**Freya**: "How do we know they succeeded?"
|
||||
|
||||
**User**: "They book a walk, see it confirmed, family coordination is visible"
|
||||
|
||||
[Dialog continues through all questions...]
|
||||
|
||||
**Freya**: "✅ Scenario specification created! Ready to create page specs?"
|
||||
|
||||
---
|
||||
|
||||
## 💡 **Tips for Both Agents**
|
||||
|
||||
**Business perspective focus**:
|
||||
- Business goals and metrics
|
||||
- Value to users and business
|
||||
- Priority and scope
|
||||
- Success measurement
|
||||
|
||||
**Freya focuses on**:
|
||||
- User experience flow
|
||||
- Key interactions
|
||||
- Visual journey
|
||||
- Usability and delight
|
||||
|
||||
**Both contribute to**:
|
||||
- Complete scenario understanding
|
||||
- Page identification and sequencing
|
||||
- Edge case identification
|
||||
- Overall quality
|
||||
- Linking scenarios back to Trigger Map (traceability)
|
||||
|
||||
---
|
||||
|
||||
## 🔗 **Trigger Map Integration**
|
||||
|
||||
**Why link scenarios to triggers?**:
|
||||
- ✅ **Traceability**: See which pain points are addressed
|
||||
- ✅ **Coverage**: Identify triggers not yet solved
|
||||
- ✅ **Validation**: Ensure solutions match problems
|
||||
- ✅ **Stakeholder clarity**: Show how software solves real problems
|
||||
- ✅ **Prioritization**: Focus on high-impact triggers first
|
||||
|
||||
**Bidirectional linking**:
|
||||
- **In Trigger Map**: "Addressed in Scenario X"
|
||||
- **In Scenario**: "Solves Trigger Y, Z from Trigger Map"
|
||||
|
||||
**This creates a complete story**: Problem → Solution → Implementation
|
||||
|
||||
---
|
||||
|
||||
**This dialog should take 10-15 minutes and result in a complete scenario specification!** 🎯
|
||||
|
||||
@@ -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. Reference Trigger Map](07-reference-trigger-map.md)
|
||||
|
||||
Identify the relevant Trigger Map context for this scenario
|
||||
|
||||
---
|
||||
|
||||
## 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 strategic context), **start sketching the journey.**
|
||||
|
||||
Each sketch serves the path from trigger to mutual success, guided by the Trigger Map.
|
||||
|
||||
---
|
||||
|
||||
[← Back to Business Model Workflow](../README.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)
|
||||
Reference in New Issue
Block a user