Follow

What makes a good request?

A good request encompasses two things:

  1. The problem statement - what problem are you trying to solve?
  2. The use case - who is the user? Why do they need this? What region/market does this affect?

Example:

  • As a [product] customer, I need to submit requests to technical support in a simple, intuitive way, with a minimum number of clicks or other unnecessary steps.

A bad request will:

  1. Be prescriptive about a solution, but not tell the product team what problem the solution solves
  2. Be vague about customer use case or workflow

Example:

  • Our customer wants a big red ‘Submit Support Ticket’ button in the top right corner of our web app.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk