Start with a shared brief
We begin by writing down who the product serves, the task it should help them complete, what already exists and what must remain true. That can be a short discovery note for a focused job or a fuller product brief for a larger one.
A named client lead gathers internal feedback and makes or escalates decisions. We name the person responsible for delivery too. This gives questions somewhere to land and keeps a design review from turning into several conflicting approval chains.
- The first outcome and a way to tell whether it works
- Constraints such as budget, accessibility, integration and launch date
- Who supplies content, access, data and approvals, and when
Use one decision trail
A regular check-in is for decisions and blockers, while a demonstration shows what has changed in the product. We keep agreed decisions, open questions and next actions in a shared record so people who missed a meeting can still understand the direction.
Feedback works best when it describes the user task and the observed issue. 'The checkout total is hard to find on mobile' gives the team something to investigate; 'make it pop' leaves the intended outcome unclear. We group comments by review round and resolve contradictory requests with the client lead.
Make change visible before it becomes work
New information is normal. When a request changes the agreed outcome, we describe the choice, estimate the effect on cost and timing, and agree a revised scope before building it. Smaller refinements can be handled within an agreed review round; new functionality needs its own decision.
Before a release, we walk through the acceptance criteria, access, content ownership, support arrangements and security checks. At handover we identify what was delivered, what remains open and who can operate the product. The exact obligations belong in the signed agreement.
Sources for this section
The right cadence depends on the project's size and risk. We agree it together before work starts, then adapt it as evidence arrives.