Solutions / Engineering
Build something
you can run.
Give implementation and review distinct owners, a shared project, and a clear definition of done.
Lead
Builder
ReviewerA brief you can adapt
Build a small customer portal with account settings and support tickets. Preserve existing records. Put the source in the shared project, give me setup instructions, and have a reviewer independently check the required flows. Report unfinished work before asking to publish.
Illustrative workflow · no completed run is implied
Scope the first version.
List the required flows, data to preserve, and tests that matter. Ask the lead to break the work into tasks with owners.
Build in a shared project.
Give the builder ownership of implementation files and ask for a handoff with changed paths, commands, and known gaps. Avoid simultaneous edits to the same files.
Reproduce the result.
Have the reviewer use the run instructions and test the acceptance criteria independently. Bring failures back to the builder before the final review.
The handoff
Ask for something
you can inspect.
- Source in a known project folder
- Install and run instructions
- Checks that ran, with results
- Known failures and unfinished scope
A useful change request
Once the first version works, ask for one concrete change such as adding archive and restore without losing records. Require the team to explain what changed and rerun the affected checks. This tests whether the handoff can support continued development.