julian
17c08e6392
- Nx 22.7 monorepo (pnpm 11.1, TypeScript 5.9, Node 24) - apps/api: NestJS 11 (CJS conforme CODING-RULES.md PGD-DB-004) - apps/web: React 19 + Vite 8 (ESM) - libs/shared/api-interface: Zod contract base - Docker Compose dev: Postgres 18, Valkey 8, MinIO, Mailpit - WDS artifacts: - design-artifacts/A-Product-Brief/ (5 docs canônicos + 16 dialogs) - design-artifacts/B-Trigger-Map/ (hub + 4 personas + feature impact) - Stack canon: STACK.md v2.2 + CODING-RULES.md v2.0 + brand.md - AGENTS.md + README.md como entrada para devs/agentes Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
67 lines
2.5 KiB
Markdown
67 lines
2.5 KiB
Markdown
# Trigger Map: {{project_name}}
|
||
|
||
> Connect business goals to user psychology — understand why people act, not just what they do.
|
||
|
||
**Created:** {{date}}
|
||
**Phase:** 2 — Trigger Mapping
|
||
**Agent:** Saga (Analyst)
|
||
|
||
---
|
||
|
||
## What Belongs Here
|
||
|
||
The Trigger Map reveals the human forces behind product decisions through five workshops:
|
||
|
||
1. **Business Goals** — What the business needs to achieve
|
||
2. **Target Groups** — Who the users are (with alliterative persona names)
|
||
3. **Driving Forces** — What motivates and frightens each persona (positive + negative)
|
||
4. **Prioritization** — Which forces matter most (scored by frequency, intensity, fit)
|
||
5. **Feature Impact** — How product features address the highest-priority forces
|
||
|
||
This folder feeds directly into Phase 4 (UX Scenarios). Every page spec should trace back to a driving force documented here.
|
||
|
||
**Learn more:**
|
||
- WDS Course Module 06: Trigger Mapping — Connect Business Goals to User Psychology
|
||
- WDS Course Module 06, Lessons 4–8: The Five Workshops
|
||
|
||
---
|
||
|
||
## For Agents
|
||
|
||
**Workflow:** `skill:wds-2-trigger-mapping`
|
||
**Agent trigger:** `TM` (Saga)
|
||
**Templates:** `./resources/wds-2-trigger-mapping/templates/`
|
||
|
||
**Before writing anything in this folder:**
|
||
1. Read the Product Brief in `A-Product-Brief/` — trigger mapping builds on it
|
||
2. Load the workflow and follow the five workshop sequence
|
||
3. Use Dialog mode — personas emerge from conversation, not invention
|
||
|
||
**File naming:** Number all documents with a two-digit prefix: `01-business-goals.md`, `02-lars-the-loyal.md`, etc. One file per persona. Update the Documents table below as each file is created.
|
||
|
||
**Harm:** Inventing personas without discovery. Fabricated driving forces produce scenarios that solve imaginary problems. The user pays to correct work that should never have been written.
|
||
|
||
**Help:** Uncovering real psychology through conversation. When driving forces are authentic, every downstream design decision has a clear "why."
|
||
|
||
---
|
||
|
||
## Documents
|
||
|
||
_This section will be updated as documents are created during Phase 2._
|
||
|
||
| # | Document | Purpose | Status |
|
||
|---|----------|---------|--------|
|
||
| 01 | Business Goals | Vision, objectives, metrics | Not started |
|
||
| 02+ | Persona files | One per target group | Not started |
|
||
| — | Feature Impact Analysis | Forces × features scoring | Not started |
|
||
|
||
---
|
||
|
||
## Trigger Map Visualization
|
||
|
||
_A mermaid diagram connecting goals → platform → personas → forces will be added here during Phase 2._
|
||
|
||
---
|
||
|
||
_Created using Whiteport Design Studio (WDS) methodology_
|