ProductSomeone using a piece of software or a service daily for their own work

When I hit a real problem with a product, I want it to reach whoever decides, so my feedback does not stop at a form.

Khi tôi gặp một vấn đề thật với sản phẩm, tôi muốn nó tới được người quyết định, để góp ý của mình không dừng lại ở một biểu mẫu.

Job context

Who
A user hitting a recurring problem
When
After hitting the same problem a third time
Trigger
A fault that has persisted for years
Situation
Feedback channels are built to collect rather than to answer
Constraints
No way to know where feedback went

5 Pains

  • Feedback receives no reply

    High

    With no way to know if anyone read it.

    Root cause: Replying individually costs effort and produces no metric

  • Support is not connected to the product team

    High

    So the problem stops there.

    Root cause: Support is organised to close cases rather than to relay them

  • A small problem affecting many is counted by nobody

    High

    Each person works around it and nobody reports.

    Root cause: Only problems large enough to report appear in the data

  • The product team does not use it to work

    Medium

    So they never meet these problems.

    Root cause: Whoever builds a tool rarely uses it all day

  • New features arrive while old faults remain

    Medium

    Because a new feature can be presented.

    Root cause: Achievement is measured by what was added rather than by what was fixed

5 Desired Outcomes

  • Know where their feedback went

    Social

  • Have the problem reach someone who can fix it

    Functional

  • Have small widespread problems counted

    Functional

  • Have the builders meet the problems users meet

    Social

  • Have old faults fixed rather than only new things added

    Functional

5 Existing Solutions

A solution is not the same thing as a product, a customer can hire a behaviour or a workaround too.

  • Send it through the feedback form

    Product

    The official channel, a box that never opens back.

  • Post about it publicly

    Workaround

    Far more effective than the official channel, and only with an audience.

  • Find a user forum

    Behaviour

    Where a problem is confirmed as real, and it does not reach the product team.

  • Work around it

    Workaround

    What most people do, which makes the problem vanish from all data.

  • Stop using the product

    Behaviour

    The clearest signal, arriving after everything is too late.

2 Opportunity Gaps

  • The user speaks to support while the decision sits with the product team, and between them there is no route for a problem to travel.

    Why existing solutions fail: Support is measured on cases closed and handling time, so escalating a problem is extra effort that helps none of their numbers, and the product team receives a summary with all the detail gone.

    Potential opportunity: Rotating product people through support duty, so problems arrive directly rather than as a summary.

  • Product teams count reported problems because those exist in a system, while what affects the most people is the small problem everyone works around, which is never reported.

    Why existing solutions fail: The threshold at which someone bothers to report is far above the threshold of annoyance, so the whole band between them, where most of the real damage happens, exists in no data at all.

    Potential opportunity: Watching how users actually work instead of waiting for reports, to see what sits below the reporting threshold.