Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.
Shared PRD template for the team
Most teams have three or four spec formats in circulation, so every reader has to relearn where the scope and the open questions live. One agreed template with fixed sections (problem, goals and non-goals, users and stories, requirements, edge cases, success measures, open questions, decision log) cuts the time engineers spend hunting through a document and makes gaps visible at a glance.
First tasks
- Collect the last six specs the team wrote and list their headings
- Draft a one-page template with eight fixed sections and a prompt under each
- Ask an engineer and a designer to mark what they skip when reading a spec
- Publish the template and mark the older formats as retired
One-paragraph problem statement before any solution
Specs go wrong at the top far more often than in the detail: they open with the feature and leave the reader guessing which customer pain it fixes. Writing a problem statement that names the user, the situation, the current workaround and the cost of leaving it alone, before a single requirement, gives every later decision something to be tested against.
First tasks
- Write the current spec's problem in one paragraph without naming any feature
- Link one piece of evidence such as a ticket count or interview quote
- Ask an engineer to restate the problem in their own words
- Strike out any word that describes a screen, button or setting
Goals, non-goals and out-of-scope list
Scope arguments in week four of a build usually trace back to a spec that never said what it was not doing. Writing three to five goals, an explicit non-goals list and a 'later, not now' parking list turns those arguments into a quick lookup and protects the delivery date.
First tasks
- List three to five goals that follow directly from the problem statement
- Write three non-goals a stakeholder might wrongly assume are in scope
- Move ideas raised during drafting to a parked list with their source
- Get written confirmation of the boundaries from the design and engineering leads