bd495be965
All checks were successful
Deploy to Production / Build and Deploy (push) Successful in 12s
- Sidebar: dynamic brand-accent colors, brainstorm section restyled - AI chat general: popup panel with expand/collapse, hides when contextual AI open - AI chat contextual: tabs reordered (Actions first), X close button, height fix - Settings: all tabs restyled, 6 new color presets (sage, terracotta, iron, etc.) - Global color cleanup: emerald/orange hardcoded → brand-accent dynamic - Brainstorm page: orange → brand-accent throughout - PageEntry animation component added to key pages - Floating AI button: bg-brand-accent instead of hardcoded black - i18n: all 15 locales updated with new AI/billing keys - Billing: freemium quota tracking, BYOK, stripe subscription scaffolding - Admin: integrated into new design - AGENTS.md + CLAUDE.md project rules added
81 lines
2.2 KiB
Markdown
81 lines
2.2 KiB
Markdown
# 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!*
|