Shared Product Blueprint

Feedback Inbox

A read-only Product Blueprint created with IdeaMade.

Product feedback inbox and backlog

Feedback Inbox

An internal tool for a single signed-in product team member to capture product feedback, track it through an Inbox / Planned / In progress / Done lifecycle, link related feedback to a requirement, and record resolution notes and next steps, with a feedback list, roadmap board, and feedback detail views plus inbox and in-progress counts.

Users and roles

The people who interact with the product.

Product team member

A signed-in member of the independent product team who captures, triages, and resolves product feedback.

  • Capture incoming feedback quickly
  • Triage feedback into the roadmap
  • Track what is in progress

Key workflows

The main paths users take to reach an outcome.

Sign in to the inboxProduct team memberCore
1

Open sign inThe team member lands on the sign-in page.

2

Sign inThe team member signs in and is taken to the feedback list.

Outcome: The team member reaches the feedback list with an authenticated session.
Capture feedbackProduct team memberCore
1

Open the feedback listThe team member opens the feedback list and sees the inbox count.

2

Create feedbackThe team member enters title, description, source, category, and priority; the record is saved to the inbox.

Outcome: A new feedback record sits in the inbox with its source, category, and priority.
Triage feedback on the roadmapProduct team memberCore
1

Review the inboxThe team member searches and filters feedback and checks the inbox and in-progress counts.

2

Open feedback detailsThe team member opens a feedback item to review its full details.

3

Link to a requirementThe team member links the feedback to a requirement, creating one if needed.

4

Move status on the boardThe team member moves the feedback to Planned or In progress on the roadmap board.

Outcome: Feedback is moved to the right status and linked to the requirement it belongs to.
Resolve feedbackProduct team memberCore
1

Open in-progress feedbackThe team member opens a feedback item from the in-progress column.

2

Record resolutionThe team member writes resolution notes and next steps and sets the status to Done.

Outcome: The feedback is marked Done with resolution notes and next steps recorded.

Pages

4 pages in the MVP

Sign inLet the product team member sign in before accessing the feedback inbox.
Public
Sign in
Feedback listReview all feedback, search and filter it, see inbox and in-progress counts, and start creating a new feedback item.
Signed in
Feedback list
Search
TitleDescriptionSourceCategory
Feedback detailsOpen one feedback item to edit its details, change status, link it to a requirement, and record resolution notes and next steps.
Signed in
Feedback details
Roadmap boardSee feedback grouped by Inbox, Planned, In progress, and Done, move items between statuses, and manage requirements that group related feedback.
Signed in
Roadmap board
TitleDescriptionSourceCategory

Product decisions

Choices you can confirm directly in the Blueprint.

How should a requirement relate to the feedback items linked to it?ConfirmedHow should a requirement relate to the feedback items linked to it?
Requirement is a separate record that groups many feedback items
Should feedback statuses move only forward through Inbox, Planned, In progress, and Done, or can a team member move a record to any status at any time?ConfirmedShould feedback statuses move only forward through Inbox, Planned, In progress, and Done, or can a team member move a record to any status at any time?
Any status to any status

Assumptions

Items that should be verified before implementation.

A requirement is a separate record that groups many feedback items; each feedback item links to one requirement.

High impactAccepted

A team member can move feedback to any of the four statuses at any time, including reopening Done items.

Medium impactAccepted

The first version serves one signed-in product team member; multi-user roles and permissions are out of scope.

Medium impactAccepted

Public voting, automated email, and subscription billing are excluded from the first version.

Low impactAccepted