nw-jtbd-workflow-selection

JTBD Workflow Selection

Classify incoming work by job type and recommend the appropriate nWave workflow entry point. Use during Phase 1 (GATHER) to triage before crafting stories.

ODI Two-Phase Framework

Determine which phase applies before proceeding.

Phase 1: Discovery -- when you do not know what to build

[research] --> discuss --> design --> distill
    |            |           |          |
GATHER        WHAT are    HOW should  WHAT does
evidence      the needs?  it work?    "done" look like?

Phase 2: Execution Loop -- when you know what needs to change

[research] --> baseline --> roadmap --> split --> execute --> review
    |            |            |           |          |          |
GATHER        MEASURE      PLAN it     BREAK it   DO each    CHECK
evidence      first        completely  into atoms  task       quality
                                          |
                              <-----------+ (loop per task)

Key insight: research is a cross-wave capability invocable at any point for evidence-based decisions.

When to Skip Discovery

Skip discovery and enter execution loop directly when ALL hold:

• User already understands the problem domain
• Problem is identified and scoped
• No stakeholder alignment needed
• User can articulate what "done" looks like

If any fail, start with discovery (DISCUSS wave).

Five Job Types

Job 1: Build Something New (Greenfield)

"I need to create something that doesn't exist yet"

[research] -> discuss -> design -> [diagram] -> distill -> baseline -> roadmap -> split -> execute -> review

Job 2: Improve Existing System (Brownfield)

"I know what needs to change in our system"

[research] -> baseline -> roadmap -> split -> execute -> review (repeat)

Skip discovery: system understood and problem identified. Baseline is blocking gate -- measure current state before planning. Prevents "optimizing the wrong thing."

Job 3: Complex Refactoring

"Code works but structure needs improvement"

Simple refactoring:

[root-why] -> mikado -> refactor (incremental)

Complex refactoring with tracking:

[research] -> baseline -> roadmap (methodology: mikado) -> split -> execute -> review

Mikado Method explores dependencies before committing. Reversible at every step.

Job 4: Investigate and Fix Issue

"Something is broken and I need to find why"

[research] -> root-why -> develop -> deliver

Minimal sequence -- focused intervention only.

Job 5: Research and Understand

"I need to gather information before deciding"

research -> [decision point: which job to pursue next]

No execution -- pure information gathering feeding into other jobs.

Quick Reference Matrix

Items in [brackets] are optional. Cross-wave commands (usable anytime): research, diagram, root-why, git.

Baseline Type Selection

When workflow includes a baseline step, advise on which type to create.

Performance Optimization

Use when improving speed, reducing resource usage, or optimizing throughput. Required: timing measurements with breakdown | bottleneck ranking | target metrics with evidence | quick wins identified.

Process Improvement

Use when fixing workflow issues, preventing incidents, or improving reliability. Required: incident references or failure modes | simplest alternatives considered (with why insufficient).

Feature Development

Use when building new capabilities (greenfield or brownfield). Required: current state analysis | requirements source and validation.

Workflow Anti-Patterns

Operate at project/feature level, distinct from story-level anti-patterns in leanux-methodology skill.

Common Workflow Recipes

Job Categories Summary

For deep opportunity analysis with ODI scoring, defer to product-discoverer agent. Product-owner applies simpler prioritization (MoSCoW, Value/Effort) for story-level ordering -- see leanux-methodology skill.