Desk template · Product managers writing a PRD and deciding what goes on the roadmap.
Product requirements desk: from feature requests to a PRD and roadmap
the PRD is argued from a requests Table — counts by feature and segment charted beside it — and the same table becomes the roadmap in Gantt view and the delivery board in Kanban, so priority, spec and plan share one source. Distinct from design-doc (engineering) and multi-project-dashboard.
What goes on the desk
- Page ‘PRD’ (problem, users, evidence, scope, open questions) (widget page)
- Table ‘Requests’ (Request, Count, Segment (single select), Status (single select), Start and End (dates)) with Kanban and Gantt views (table views)
- Chart ‘Requests by feature’ (widget chart)
- Mind map ‘Scope and open questions’ (widget mind map)
- Tasks (widget tasks)
- Browser on your analytics tool (widget browser).
Set it up
import requests from a support export CSV (widget table import); add the views.
- Create a desk named for the real outcome, client or deadline.
- Add the suggested widgets and rename each one for the job it performs.
- Bring in the existing files or tables before inventing another copy of the information.
- Set a due date, add the first visible next action, then save the arrangement as a template if you will repeat it.
Open this desk in the interactive demo
Use it day to day
triage new requests weekly; update the PRD’s evidence.
A useful desk should reduce copying. Keep each changing fact in one widget, and let charts, summaries or views read from that source.
A worked starting point
Fictional example. Create the desk, add three real items that are already in motion, then use one full work cycle before changing the layout. At the end, remove anything you did not consult and add only the object that would have prevented a real interruption.
Where Plexii helps
the Page’s AI draft writes PRD sections you review (widget page); a Mind map branch becomes a task or a canvas of its own (widget mind map); Build a table with AI (widget table ai).