22 / 25Grooming

Solutioning

Technical design as a grooming step

Solutioning is the grooming pattern where the Architect persona produces a lightweight technical design for a story before implementation begins. It prevents the Developer persona from making uncontrolled architectural decisions mid-implementation.

Implementation ambiguity is not always about requirements. A story can be requirement-complete — the acceptance criteria are clear, the scope is correct — and still leave the Developer persona with unresolved architectural decisions. Which data structure? Which API design? Which error-handling strategy? If these decisions are not made in advance, the Developer makes them silently, and they may conflict with decisions made in adjacent stories. Solutioning makes these micro-architectural decisions explicit before they are implemented.

Solutioning is an Architect persona session triggered by stories that contain implementation decisions above a certain complexity threshold. The Architect reads the story and produces a lightweight design note: the approach, the key data structures or interfaces, the error handling strategy, and any constraints from existing ADRs that apply. This note becomes part of the story before it is handed to the Developer. The Developer implements within the design note — any deviation requires a new ADR.

Solutioning is not full architecture work. It is not an ADR. It is a focused mini-design that answers the questions the Developer persona would otherwise answer silently. The right scope is: what are the decisions in this story that, if made poorly, would be expensive to reverse? Solutioning answers those questions and only those questions. Everything else is left to the Developer's judgment.

Key Concepts

  • Solutioning addresses implementation-layer ambiguity, not requirements ambiguity
  • Triggered by stories containing decisions above a complexity threshold
  • Output is a lightweight design note, not a full ADR
  • Developer implements within the design note — deviations require a new ADR
  • Scope: only decisions that would be expensive to reverse if made poorly