Turn field feedback into a product prioritization memo

Forward-deployed work produces rich feedback, but the loudest request is not automatically the best product priority. Convert anecdotes into comparable evidence and preserve the difference between a client promise and a product decision.

Build the decision artifact

Normalize feedback into the underlying job or failure. Record frequency, affected users, impact, confidence, workaround, strategic fit, security effect and effort. Link source observations, score only as a decision aid and write the chosen action, rejected alternatives and new evidence that could reverse it.

The commercial leadership lab makes the artifact inspectable with authored inputs:

from leadership_cases import prioritization_case

result = prioritization_case()
assert result["priority"] == "show source page"
assert result["decision"] == "build source-page evidence"
assert result["scores"]["show source page"] == 100
assert result["client_promised"] is False

Showing the source page scores 100 and outranks a dark theme plus a costly second connector. The memo selects evidence visibility and makes no client promise. The score is based on authored inputs, so product judgment still reviews qualitative and strategic constraints.

Protect the decision from weak evidence

Frequency counts can overrepresent one noisy client. Normalize by exposure and preserve segment context. Do not combine security obligations with optional enhancements in one score; mandatory controls should pass a separate gate.

Keep these artifacts for review:

• anonymized feedback statements
• frequency/exposure and impact analysis
• confidence and effort basis
• decision memo with rejected options

This practice aligns with the discovery, productisation, client enablement, technical leadership and capstone sequence in the FDE for Professionals course. The course link describes the pathway; the local scenario is fictional and does not claim a client engagement, investment result, hiring decision or certificate.

Practice task

Collect ten synthetic feedback items, merge duplicates by underlying job and write a one-page recommendation with reversal conditions.

Continue learning

This article is part of the Commercial judgement and delivery leadership sequence. Use the neighbouring tasks when you need the prerequisite or the next application.

• Review the prerequisite or neighbouring task in Plan user adoption alongside technical deployment.
• Continue with Measure the support burden of client-specific customization.

Reference: GOV.UK Service Manual: Alpha Phase.