nw-interviewing-techniques

Mom Test questioning toolkit, JTBD analysis, interview conduct, assumption testing framework, and hypothesis design

322 stars

Best use case

nw-interviewing-techniques is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Mom Test questioning toolkit, JTBD analysis, interview conduct, assumption testing framework, and hypothesis design

Teams using nw-interviewing-techniques should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/nw-interviewing-techniques/SKILL.md --create-dirs "https://raw.githubusercontent.com/nWave-ai/nWave/main/nWave/skills/nw-interviewing-techniques/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/nw-interviewing-techniques/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How nw-interviewing-techniques Compares

Feature / Agentnw-interviewing-techniquesStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Mom Test questioning toolkit, JTBD analysis, interview conduct, assumption testing framework, and hypothesis design

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Interviewing Techniques

## Questioning Toolkit by Purpose

### Problem Discovery
Understand if problem is real and worth solving.
- "Tell me about the last time you [encountered this problem]."
- "What was the hardest part about that?"
- "What did you do about it?" | "What don't you love about that solution?" | "What else have you tried?"

### Understanding the Job
Map the job-to-be-done and desired outcomes.
- "What are you ultimately trying to accomplish?"
- "Walk me through your process step by step."
- "At each step, how do you know if you've succeeded?"
- "What slows you down or frustrates you most?" | "What workarounds have you created?"

### Probing Assumptions
Challenge beliefs and uncover truth.
- "What makes you believe that?" | "What would need to be true for this to work?"
- "What could we assume instead?" | "What would change your mind?"

### Testing Commitment
Distinguish interest from commitment.
- "Would you be willing to [specific action]?" | "What would you pay for this?"
- "Can you introduce me to someone else with this problem?" | "When can we schedule a follow-up?"

### Exploring Implications
Understand impact and urgency.
- "If this were solved, what would change?" | "What would that enable you to do?"
- "What would happen if we didn't solve this?"

## Interview Conduct Rules

**Do**: Ask about past specifics | Open, non-directive questions | Seek commitment not praise | Keep informal | 80% listening | Talk about their life first

**Avoid**: Future behavior questions | Leading questions | Accepting compliments as validation | Talking >20% | Mentioning idea before understanding problem | Formal settings

## Assumption Challenging

### Triggers
Challenge when: belief without evidence | prediction about future | negative feedback dismissed | skipping to solution | single data point relied on

### Challenge Format
1. "What evidence supports this?" -- specific past examples
2. "What would disprove this?" -- falsification criteria
3. "What's the opposite assumption?" -- explore alternatives
4. "Who would disagree and why?" -- disconfirming perspectives

Tone: curious and supportive, not confrontational -- goal is truth-seeking.

## Assumption Testing Framework

### Assumption Categories
| Category | Core Question |
|----------|--------------|
| Value | Will customers want this? |
| Usability | Can customers use this? |
| Feasibility | Can we build this? |
| Viability | Does this work for our business? |

### Risk Scoring

| Factor | Weight | Low (1) | Medium (2) | High (3) |
|--------|--------|---------|------------|----------|
| Impact if wrong | 3 | Minor adjustment | Significant rework | Solution fails |
| Uncertainty | 2 | Have data | Mixed signals | Speculation |
| Ease of testing | 1 | Days, low cost | Weeks, moderate | Months, high cost |

**Risk Score** = (Impact x 3) + (Uncertainty x 2) + (Ease x 1)

| Priority | Score | Action |
|----------|-------|--------|
| Test first | > 12 | Immediate |
| Test soon | 8-12 | Schedule |
| Test later | < 8 | Backlog |

### Hypothesis Template

```
We believe [doing X] for [user type] will achieve [outcome].
We will know this is TRUE when we see [measurable signal].
We will know this is FALSE when we see [counter-signal or absence of signal].
```

### Test Methods by Category

| Category | Methods |
|----------|---------|
| Value | Landing page, Fake door, Mom Test interviews |
| Usability | Prototype testing, 5-second tests, Task completion |
| Feasibility | Spike, Technical prototype, Expert review |
| Viability | Lean Canvas review, Stakeholder interviews |

### Decision Rules

| Result | Criteria | Action |
|--------|----------|--------|
| Proven | >80% meet success criteria | Proceed |
| Disproven | <20% meet criteria | Pivot or kill |
| Inconclusive | 20-80% | Increase sample, try different method, segment |

Related Skills

nw-investigation-techniques

322
from nWave-ai/nWave

Evidence collection methods, problem categorization, analysis techniques, and solution design patterns

nw-ux-web-patterns

322
from nWave-ai/nWave

Web UI design patterns for product owners. Load when designing web application interfaces, writing web-specific acceptance criteria, or evaluating responsive designs.

nw-ux-tui-patterns

322
from nWave-ai/nWave

Terminal UI and CLI design patterns for product owners. Load when designing command-line tools, interactive terminal applications, or writing CLI-specific acceptance criteria.

nw-ux-principles

322
from nWave-ai/nWave

Core UX principles for product owners. Load when evaluating interface designs, writing acceptance criteria with UX requirements, or reviewing wireframes and mockups.

nw-ux-emotional-design

322
from nWave-ai/nWave

Emotional design and delight patterns for product owners. Load when designing onboarding flows, empty states, first-run experiences, or evaluating the emotional quality of an interface.

nw-ux-desktop-patterns

322
from nWave-ai/nWave

Desktop application UI patterns for product owners. Load when designing native or cross-platform desktop applications, writing desktop-specific acceptance criteria, or evaluating panel layouts and keyboard workflows.

nw-user-story-mapping

322
from nWave-ai/nWave

User story mapping for backlog management and outcome-based prioritization. Load during Phase 2.5 (User Story Mapping) to produce story-map.md and prioritization.md.

nw-tr-review-criteria

322
from nWave-ai/nWave

Review dimensions and scoring for root cause analysis quality assessment

nw-tlaplus-verification

322
from nWave-ai/nWave

TLA+ formal verification for design correctness and PBT pipeline integration

nw-test-refactoring-catalog

322
from nWave-ai/nWave

Detailed refactoring mechanics with step-by-step procedures, and test code smell catalog with detection patterns and before/after examples

nw-test-organization-conventions

322
from nWave-ai/nWave

Test directory structure patterns by architecture style, language conventions, naming rules, and fixture placement. Decision tree for selecting test organization strategy.

nw-test-design-mandates

322
from nWave-ai/nWave

Four design mandates for acceptance tests - hexagonal boundary enforcement, business language abstraction, user journey completeness, walking skeleton strategy, and pure function extraction