KNOWLEDGE WIKI  (LOCAL-MD-001)MODE: READ_ONLYSYS_TIME: --:--:--
SECTION:fdePAGES:40CURRENT:field-patterns/product-sense-and-roadmap-feedback.md
FDE-014field-patterns/product-sense-and-roadmap-feedback.mdUPDATED: 06/18/2026

Product Sense And Roadmap Feedback

Pattern

Name: Product sense and roadmap feedback

When to use it: When customer implementation work reveals a recurring need, product gap, confusing workflow, or reusable opportunity.

Why it matters for FDE roles: FDEs often translate customer reality back into product direction.

Plain-English Description

Product sense is the ability to connect user needs, technical tradeoffs, business value, and product behavior. Roadmap feedback turns field learning into useful product input.

Situation Signals

  • Job listing signal: product-minded, roadmap, product feedback, customer insights.
  • Customer signal: multiple customers ask for similar workarounds or customizations.
  • Project signal: an implementation choice may become a reusable product pattern.

What To Ask

  • Is this need unique to one customer or broadly recurring?
  • What is the underlying workflow problem?
  • What workaround are users using today?
  • What would a productized version simplify?

What To Do

  • Capture the customer scenario and evidence.
  • Separate product gaps from implementation gaps.
  • Describe impact, frequency, urgency, and workaround cost.
  • Suggest a narrow product improvement or reusable accelerator.

Artifacts To Produce

  • Diagram: before/after workflow.
  • Checklist: evidence, impact, recurrence, proposed product change.
  • Demo/prototype: reusable version of the custom solution.
  • Customer-facing note: known limitation and planned/implied workaround.

Failure Modes

  • Treating one customer request as a roadmap mandate.
  • Losing field context when reporting product feedback.
  • Proposing broad features instead of specific workflow improvements.
  • Ignoring implementation lessons after delivery.

Interview Language

One sentence I could say in an interview:

I try to turn customer-specific work into product signal by capturing the workflow, frequency, impact, workaround, and what a reusable version would change.

Relevant work experience for this pattern: