Skip to content
← Product management

CAPTURE / FEEDBACK & RESEARCH

Hear the request.
Find the real need.

Bring customer requests, research and portal feedback together. Keep the source while deciding what deserves a closer look.

A complete Product workspace. Connect the wider work when useful.
Feedback & research workflowMany signals. A need you can investigate.. An authored illustration with fictional planning examples. CUSTOMER PORTAL“Share one deliverable.”RQ-184 · Original request RESEARCHReviews move to emailINT-09 · Interview synthesis PRODUCT POLICYKeep access explicitPOL-03 · Named reviewer A NEED TO INVESTIGATEExternal-review sharing18 linked requestsFictional demand REVIEW THE NEED. CHOOSE THE NEXT STEP.
Many signals. A need you can investigate.
Product workflow illustration · Fictional planning examples
01Requests & evidence
02Reviewed triage
03Customer portal

SEE THE WORK / MAKE A CHOICE

From a customer’s words
to a considered next step.

Read the original request, then decide whether to investigate. The evidence stays with the decision.

Working demo screens · Fictional examples

PRODUCT / INSIDE THE DEMO

Start with what was asked.

Open the original customer request alongside research and policy evidence before deciding what to investigate.

18 linked requests in this sample. Repeated demand does not establish the size of the benefit.

Try the evidence reviewInteractive example · No sign-up
ProcessScout / ProductDEMO WORKSPACE
Harbor working demo: Open the original customer request alongside research and policy evidence before deciding what to investigate.

PRODUCT / INSIDE THE DEMO

A request needs a next step.

Investigate the need or keep it on hold. The source stays attached while the product team decides what comes next.

This working demo covers investigation and hold. The product also supports reviewed merging and portal moderation.

Try request triageInteractive example · No sign-up
ProcessScout / ProductDEMO WORKSPACE
Harbor working demo: Investigate the need or keep it on hold. The source stays attached while the product team decides what comes next.
01

CAPTURE THE CONTEXT

A request is more useful with its source attached.

Search and filter the request inbox by the state of the work, and inspect the original context, reporters and votes before deciding what a request means. Link it to an arc or epic when planned work already addresses it; a new idea can stay open for investigation.

Start with
Requests and their available source, reporter and customer context.
Work toward
A searchable intake with review status and links to relevant work.

Every request keeps its source

  1. Portal ideaWith its reporter
  2. Customer requestWith its votes
  3. Research noteWith its citation
Illustration · fictional example
02

MAKE A REASONED DECISION

Combine the repetition. Preserve the evidence.

Review suggested triage, set a status and merge requests that describe the same need, with unmerge when a closer reading separates them. AI-authored rows and merged-away requests are excluded from demand scoring, so a suggestion or a duplicate never counts as another customer.

Start with
Related requests, supporting context and a triage judgment.
Work toward
A clearer set of needs with links, status and the original evidence retained.
Detail of the Product demo with fictional example data
ProcessScout / Productan investigated need meets a goal · fictional data

HARBOR / THE WORKED EXAMPLE

Three requests can point to one unresolved question.

In the fictional Harbor example, customers ask to invite external reviewers, share selected work and avoid sending duplicate files. Triage brings related requests together while preserving their sources. Research can then explore the access boundaries reviewers need, before the team chooses the response.

Walk through this example

THREE SOURCES. ONE NEED TO INVESTIGATE.

  1. Customer portalShare one deliverable
    RQ-184
  2. Research noteReviews move into email
    INT-09
  3. Product policyAccess must be revocable
    POL-03
  4. Triage decisionInvestigate the need
    OPEN
Fictional planning example · No result is claimed
03

INVESTIGATE THE QUESTION

Move from a popular request to an understood problem.

Review cited customer insights, then use research-round proposals to shape the next study from existing research and contact records. A request supplies a question, not the answer, and consent and transcript protections may withhold a quotation that cannot be shared.

Start with
A product question, existing research and eligible contact records.
Work toward
A reviewable research proposal and cited insights where access permits.
Detail of the Product demo with fictional example data
ProcessScout / Productresearch with its limits stated · fictional data

THE PRACTICAL DETAILS

Where feedback
comes from.

Talk through your workflow
Can we collect ideas without exposing our internal roadmap?

The customer portal has its own audience and access controls. Portal participation does not provide general access to the internal Product workspace. Confirm the portal configuration and shared status information during setup.

Does every vote increase demand in the score?

No. Public votes and actual customer demand are distinguished. AI-authored and merged-away request rows are excluded from customer-demand scoring.

Will a research proposal contact customers for us?

Accepting the proposal does not send invitations or grant consent. Contacts, participation and appropriate access to research still need to be handled through the relevant configured workflow.

YOUR NEXT PRODUCT DECISION

Bring one request.
Keep its source attached.

Try a fictional example, or bring one question from your product.

Product view

ProcessScout interactive demo · Fictional Harbor data