TranskribatorTranskribator
A feature request card from an interview: problem, context and workaround
Product research

A feature request card from an interview: problem, context and workaround

Document a feature request from an interview by separating the suggested feature from the problem and keeping the context, frequency, impact, workaround and evidence.

The Transkribator team5-minute read
SOURCEFEATURE REQUESTS GROUNDED IN EVIDENCESignal: a button is neededProblem: share a summarywithout project accessHypothesis: send by emailAlternative: a guestlinkFROM WORDS TO RESULTS
Working with a real recordingIllustrated training exampleTemplate to copy
Product research

“Add a button” opens the conversation

Users understand their own work; they don’t have to design a solution for everyone. One suggested button can point to a need for control, speed, collaboration or fewer errors. Keep the original request and uncover the task behind it.

A request card helps the team compare signals and decide what to investigate. It doesn’t commit anyone to building the feature. Only say “everyone asks for it” if you have a verified count made using a consistent rule.

Workflow

Distinguish the signal, problem and solution

  1. Keep the exact wording

    Save the request and its timestamp without strengthening the language. Describe the user’s role and scenario without identifying them if personal data isn’t needed.

  2. Find out what was happening

    What did the user do just before the difficulty, what did they expect, what happened instead, and what were the consequences? Ask for a recent example rather than a prediction of future behavior.

  3. Document the workaround

    Ask how they do the task now: a spreadsheet, a manual check, another service or no solution. The workaround reveals the cost of the problem, but doesn’t establish the feature’s priority on its own.

  4. Treat the solution as a hypothesis

    Record the suggestion separately and list alternatives to test. Add an implementation to the backlog once you’ve assessed its value, reach, complexity and fit with team strategy.

Worked example

A request for an export button

This is a fictional training example. The names, circumstances and outcomes are included solely to explain the method.

Excerpt from a training recording · 12:40
Add a “Send to my manager” button. Today I copy the summary into an email because my manager has no access to the project.

The underlying problem may be sharing the summary with someone who doesn’t have access. Other options include a guest link, an export, an email or a permission change.

Keep the request and context on the card: the summary is needed outside the project; the current workaround is manual copying; formatting or version information can be lost. This is a fictional example.

Signal: a buttonis neededProblem: share a summarywithout project accessHypothesis: sendby emailAlternative:a guest link
One request can reveal a problem with several possible solutions.
FieldWhat to recordWhat to avoid
Original requestExact wordingRewriting it as a specification
ContextRecent scenario and participantsListing a role without the task
ConsequenceTime lost, error or blockageMaking up the cost
SolutionsRequest and alternativesPromising to build it
Ready-to-use template

Feature request card template

Use the card to record the first signal. Keep research and specifications as separate steps.

Template for your workSelect and copy
Signal ID:
Date and source:
User role:
Exact wording / timestamp:
Task before the difficulty:
Context and participants:
What gets in the way:
Consequences:
Current workaround:
Observed frequency — verified data only:
Proposed solution:
Alternative hypotheses:
What needs checking:
Decision on the next step:
Check the result

Review the card before sharing it with the product team

  • The original request is recorded separately.
  • The problem describes something you can observe.
  • One interview hasn’t been used to invent a frequency.
  • There’s no feature promise ahead of a decision.
InterviewOriginal signalContextSituation and consequencesHypothesesSeveral solutionsCardBasis for a decision
A feature request becomes useful when the problem is clear and the solution is still open.
Frequently asked questions

A closer look

Should I include the customer’s name?

Only if the process requires it and the data rules permit it. For analysis, a role, segment and link to a protected source are often enough.

When should I write a user story?

When the team understands the user, task and limits of the proposed solution. The initial card can come earlier and should remain a record of what you learned.

Keep working with the recording