Team workflow

DD6 works best when every intake receives a score before discovery starts.

A consistent workflow ensures proportional discovery across all problem types.

01

An intake arrives

From any source — ticket, Slack message, stakeholder request, incident report.

02

The intake receives a DD6 score

Score I, D, S, T, P, B (1–3 each) before discovery begins.

03

The score determines discovery depth

Skip, shallow, standard, deep, or emergency. Learn about depth mapping →

04

Discovery sessions follow the depth policy

The depth determines methodology, number of sessions, and human involvement.

05

Discovery produces a spec

The output of discovery is a well-defined specification ready for execution.

06

The spec receives a CIRK score

CIRK classifies execution governance. Learn about CIRK →

07

Outcomes calibrate future DD6 scoring

Track results and refine scoring over time. Learn about calibration →

Depth interpretation

What each signal means for your team.

Low I, low B

Problem is clear — skip or shallow discovery

High S

Schedule stakeholder alignment before anything else

High D

Bring in domain experts early

Low P

Allocate time for exploration and prototyping

Low T (high score)

Define what "done" looks like before proceeding

High B

Boundaries unclear — scope the edges first

What DD6 replaces

From ad-hoc to proportional discovery.

× Ad-hoc discovery ("let's just have a meeting")
× Inconsistent depth across PMs and teams
× Invisible discovery debt
× Wasted discovery on trivial problems

Shared language

How teams talk using DD6.

Once a team uses DD6 consistently, people start speaking in a shared problem language.

"This is high S — we need alignment before the agent touches it."
"This is low P — nobody's done this before, let's explore first."
"This is I3 B3 — we don't even know the scope yet."
"Score 7 — just skip and spec it."

That shared language is what makes a standard adoptable.

Understand the problem before the agent touches it.