Skip to content

Shaping the Work

What is the smallest thing worth doing next?

Series identity. Learn in cycles. Move in a line. The product keeps moving forward, while understanding improves through repeated PDSA learning loops.

Use this guide to: convert a learning objective into a bounded product slice.

PDSA emphasis: Plan to Do through scope, examples, and constraints.

Purpose

Shaping the work prevents learning cycles from becoming endless discussion. The team defines a slice that is small enough to build and observe, but meaningful enough to teach something about the real product, real users, or real operating system.

When To Use It

  • When discovery has produced insight but not a buildable next step.
  • When the team is debating a large solution that can be thinned.
  • When engineering needs clarity without false precision.

Core Questions

  • What is the smallest useful product movement?
  • What must be inside this slice for learning to be valid?
  • What can stay outside without invalidating the cycle?
  • Which examples define acceptable behavior?
  • What constraints, risks, or dependencies shape the slice?

Facilitation Pattern

  1. Start from the learning objective and decision, not from the backlog.
  2. Write the smallest meaningful user or operator path.
  3. Add concrete examples and edge cases.
  4. Name what is explicitly out of scope for this cycle.
  5. Confirm what will be observed during Build and after release.

Working Example

A renewals team wants a full self-service contract change flow. The first slice is narrower: let account managers generate a draft renewal with two approved change types. That slice is enough to test whether pricing exceptions, approval delays, and customer edits are the true bottlenecks.

Common Traps

  • Shrinking scope so far that the result cannot teach the real thing.
  • Letting every exception into the first slice.
  • Writing acceptance criteria that verify construction but not learning.
  • Treating out-of-scope decisions as forgotten instead of deferred deliberately.

Outputs And Artifacts

  • Thin slice statement.
  • In-scope and out-of-scope boundaries.
  • Concrete examples and acceptance conditions.
  • Observation points.
  • Risks and constraints to monitor.

PDSA Linkage

This guide completes enough of Plan to make Do possible. It keeps product movement linear by selecting a next slice, while preserving the learning loop by attaching that slice to prediction and observation.

Working Worksheet

  • Name the user or operator path.
  • Define the smallest slice that still creates valid evidence.
  • Write examples before implementation starts.
  • Mark out-of-scope items explicitly.
  • Confirm what will be observed and by whom.

Lineage Notes

Direct lineage: Walter Shewhart's statistical view of process learning influenced W. Edwards Deming, and Deming made PDSA a disciplined loop for prediction, action, study, and adjustment. Complementary quality thinkers - Juran, Ishikawa, Feigenbaum, and Taguchi - sharpen the product team's attention to fitness for use, causes, total systems, and variation. Ackoff, Drucker, Ries, and Blank are useful adjacent thinkers for systems, management, and product discovery, but they are not presented here as the historical source of PDSA.

References