A reviewable way to work
Know what you will see and decide at every stage.
The exact plan depends on the product and team. This four-stage model keeps understanding, scope, progress, and handoff visible without promising a timeline before the work is known.
01
Understand the real requirement
02
Shape a bounded first scope
03
Keep progress observable
04
Review and hand over
The artifacts below are reconstructed examples
They demonstrate the structure of a useful brief, scope note, status update, and handoff summary. They are not presented as original client documents or proof of an undisclosed engagement.
From your point of view
Four stages, four explicit decisions
Each stage starts with a question, produces something reviewable, and advances through a decision you can name.
Stage 01
Understand the real requirement
Are we solving the right first problem?
We turn scattered context into a shared description of the user, current situation, constraints, and first useful outcome.
What you see
- A concise problem statement in plain language
- Known constraints and unanswered questions
- A proposed first useful outcome
Decision you make
Confirm that the user, problem, and first outcome describe the right place to start.
Stage 02
Shape a bounded first scope
What exactly are we agreeing to deliver?
The first outcome becomes a defined piece of work with inclusions, exclusions, dependencies, owners, and review criteria.
What you see
- The implementation boundary and tangible outputs
- Dependencies, assumptions, and named owners
- Review points and acceptance signals
Decision you make
Choose the first delivery slice and confirm what is deliberately outside it.
Stage 03
Keep progress observable
What changed, what needs review, and what is blocked?
Implementation moves in reviewable increments. Important choices and scope changes are surfaced while they can still be discussed.
What you see
- A working increment or focused source change
- The context behind consequential decisions
- Blockers and scope changes before they are hidden
Decision you make
Accept the increment, give focused feedback, or change the next slice with the trade-off made visible.
Stage 04
Review and hand over
What was delivered, what remains limited, and what can happen next?
The result is reviewed against the agreed outcome, then transferred with the source and context needed for continuation.
What you see
- The delivered result compared with the agreed scope
- Known limitations and unresolved items
- Source locations, implementation context, and next options
Decision you make
Accept the agreed outcome and choose whether to continue, transfer ownership, or stop at the completed boundary.
Responsibility stays explicit
Before implementation, we name the part I own, the inputs I need, and the person who makes product decisions. If the scope depends on work outside my role, that dependency is recorded before it becomes a surprise.
Start with the context
Share the product, role, or implementation problem. The first useful response is a fit check and a clearer next step—not a preset promise.
