How we move work forward
Work moves through problem understanding, scope, evidence and checks. Each stage should make the current position, remaining uncertainty and reason for the next step understandable.
Understand the problem and define scope
Identify users, current processes and the result that should change. State what is included, what is deferred, and the available information, systems and constraints. This prevents a shared term from concealing different expectations.
Develop candidates from sources
Preserve source material and usage conditions before analysis, structure, content or prototypes are developed. Unaccepted directions remain candidates. A demonstration checks understanding; it does not automatically become an approved decision.
Check and deliver
Checks depend on the artifact: evidence and completeness for content, readability and behavior for interfaces, and functionality and failure conditions for software. Record passed, failed and untested conditions along with versions and maintenance entry points.
Connect feedback to the next iteration
Relate feedback to the initial problem and acceptance criteria before classifying it as correction, extension or a change of direction. Explain the impact of scope changes and preserve earlier versions and failed attempts for future understanding.