nw-discovery-methodology

Featured

Question-first approach to understanding user journeys. Load when starting a new journey design or when the discovery phase needs deepening.

AI & Automation 636 stars 68 forks Updated today MIT

Install

View on GitHub

Quality Score: 95/100

Stars 20%
93
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Discovery Methodology Discover journeys through deep questioning before any sketching. The sketch is proof of understanding, not the starting point. ## Session Flow ### Phase 1: Goal Discovery (First 5-10 minutes) Focus: What is the user trying to accomplish? Questions: - "What's the ultimate goal you're trying to achieve?" - "What triggers this journey? When does a user start this?" - "How will you know when you've succeeded?" - "What's the happy path in your mind?" #### Draft Sketch (after first 3 answers) After collecting goal, trigger, and success criteria, output a rough draft sketch showing what the journey might look like. Mark unknowns with `???`. Purpose: make value visible immediately so the user sees progress, not just questions. ``` [Trigger: ???] → [Step 1: ???] → [Step 2: ???] → [Goal: {stated goal}] Feels: ??? Sees: ??? Sees: ??? Feels: {success criteria} Artifacts: ??? Artifacts: ??? Artifacts: ??? ``` This is a working hypothesis, not a commitment. Update it after each phase as understanding deepens. The sketch gives the user something concrete to react to — "no, step 2 happens before step 1" is more productive than abstract discussion. ### Phase 2: Mental Model (10-20 minutes) Focus: What does the user EXPECT to see? Questions: - "Walk me through step by step -- what do you type, what do you see?" - "At this step, what information appears on screen?" - "What would you need to see to feel confident?" - "Where do you think ...

Details

Author
nWave-ai
Repository
nWave-ai/nWave
Created
9 months ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category