Example data. Fieldnote is a fictional company used to fill all 61 boards, so the examples tell one consistent story.
Scale-up, Karim writes the one-pager for offline mode release 1, because the Field app squad that builds it was not in the discovery.
What the team took away
The page was validated in a 30-minute review; the open question about deleted jobs became the first spike of the sprint.
How to run it
Preparation
The PM writes a first draft alone before the session and sends it 24 hours ahead. The workshop is a review, not a writing session with six people.
Invite the tech lead, the designer and one stakeholder who will use the outcome. Four people, five max.
Pre-fill the board with the draft in the seven blocks. Leave the Open questions block deliberately empty: it gets filled live.
Agenda
15 min
Silent read Everyone reads the whole page in silence and drops a sticky on any sentence they disagree with or do not understand. No talking until the timer ends.
20 min
Problem and goal Go through the stickies on the first two blocks. The test: can the stakeholder repeat the problem in their own words? Can the tech lead say which metric moves? Rewrite until both say yes.
30 min
Scope and out of scope Read Scope aloud. For every item, the tech lead asks 'is this needed to move the metric?' Anything that gets a no moves to Out of scope, written down, not deleted.
25 min
User stories Check each story has a user, an action and a reason. Merge stories that describe the same screen. If there are more than ten, the scope is too big for one page: split the PRD.
20 min
Open questions Collect every remaining sticky into the Open questions block. Each one gets an owner and a date. A question without an owner is not open, it is ignored.
10 min
Sign Read the goal and the scope one last time. The stakeholder, the tech lead and the designer each write 'OK' with their name on the board. That is the approval; no separate meeting.
Pitfalls
Do not exceed one page. If it does not fit, the scope is too big, and the second page is where the misunderstandings hide.
Do not write solutions in the Problem block. 'Users need a dashboard' is a solution; 'users cannot see if their order shipped' is a problem.
Do not leave Out of scope empty. It is the block that protects the team during the sprint.
Afterwards
The signed PRD is the reference for the user flow and the wireframes. Open questions go into the team channel with their dates. Any scope change after signing is a new paragraph in the PRD with a date, never a hallway agreement.