Which set is holding you back?

Entry-level diagnosis. Surfaces how a team perceives its balance across Tool-, Skill-, and Mind-Set. The spread matters more than the average — where leadership and team disagree.

When to use: When it's unclear where the team stands. Also as the entry to any larger diagnosis.

Checks whether reality can become visible at all. Without safety, skill gaps stay hidden, tool problems get worked around, wrong decisions get corrected late.

When to use: When mood is low, or other diagnostics feel suspiciously rosy.

A short observation of real work where it happens. Don't analyze, don't interview — watch. Surfaces the gap between process-on-paper and process-in-practice.

When to use: When reports and reality diverge. When workarounds become noticeable.

Surfaces how work flows through a system — processing, waiting, rework, handoffs. Key metric: Process Cycle Efficiency. In knowledge work often only 5–15 %.

When to use: When a lot is being worked on but little reaches the customer. When lead times are long.

Surfaces skills. Important: a development map, *not* an evaluation grid against people. Finds single-points-of-failure and skills no-one holds at target level.

When to use: When knowledge is concentrated on individuals. When cross-skilling or onboarding stalls.

Per tool: problem fit, adoption, skill fit, integration, cost, ownership, risk, sunset path. Traffic light: Keep / Improve / Consolidate / Replace / Sunset. Rule: sunset at least one tool per quarter.

When to use: When tools pile up. When tool chaos is claimed but nobody declutters.

Brings problem, current state, target state, cause, action, measurement, and follow-up onto one A3 page. With built-in 3sets diagnosis. Forces clarity.

When to use: When a concrete, recurring problem needs structured treatment.

See past the first explanation. Simple but not trivial. Works only with honest questions, not blame-hunting. Rule of thumb: three to seven whys, depending on depth.

When to use: When the same problems recur. When the first explanation arrives suspiciously fast.

Instead of "How do we improve?" it asks "What would we do to fail guaranteed?" The inversion breaks defensive conversations. Laughter is allowed — laughter produces truth.

When to use: When discussion is stuck. When improvement ideas seem exhausted.

Imagine the failure before it happens. "It's six months later. Our initiative has failed. Why?" Surfaces the most likely risks — with preventive actions, owners, and dates.

When to use: Before any major change, workshop format, or method introduction.

Helps identify the problem type — clear, complicated, complex, chaotic. Prevents complex problems from being smashed with simple standards, or clear problems from being over-debated.

When to use: When the situation is diffuse. When three experts give three different answers.

Checks whether team structure and workflow match — value stream, autonomy, cognitive load, dependencies, enabling, platform, interfaces. Sometimes the team isn't immature — the structure is.

When to use: When teams block each other. When ownership is demanded but not enabled.

Measures productivity multi-dimensionally. Five dimensions: Satisfaction, Performance, Activity, Communication, Efficiency. Measuring only activity creates wrong incentives.

When to use: When productivity is measured by tickets or lines of code. When burnout signals appear.

Four software delivery metrics: Deployment Frequency, Lead Time, Change Failure Rate, Time to Restore. DORA shows *that* a problem exists. 3sets helps understand *why*.

When to use: In software and IT teams. When teams believe they're fast but data says otherwise.

Aligns diagnosis with value, not activity. Five lead questions: current value, unrealized value, learning speed, innovation capability, which sets constrain value creation.

When to use: When a team is getting faster but nobody notices. When "deliver more" became the main goal.

Strategic diagnosis: which capabilities and components are strategic, which are commodity? Are we building what we should buy? Holding onto skills that won't differentiate in two years?

When to use: For strategy, leadership, product development, platform decisions. Not an everyday tool.

Twelve fields, one order, one rule of thumb: read fields 9 and 10 back-to-back — does the word "because" make sense? The canvas guides you from trigger through set analysis to intervention.

When to use: When a complete diagnosis is needed. As the central tool in workshops and coaching sessions.