I'm currently tasked with designing a user form for a data solution product, but facing a bit of challenges. I do have a basic knowledge of the products' goals but haven't been provided with clear and specific details about what input fields are necessary for the users to fill out. Right now, I only have the opportunity to gather insights from the backend developer who has the system design ready.

I'm assuming JSON format would be helpful but want to know if any strategies can be followed.

I appreciate any advice or, real-life examples from your experiences that could guide me in the right direction. Thanks in advance!

  • 1
    If the backend has an API (REST, GraphQL etc.) it likely has generated documentation that shows the type of each field with a description (containing the requirements and limitations) and an example. Ask the backend developer for the URL because it is easier to read than a JSON document.
    – jazZRo
    Commented Jun 25 at 12:30
  • If the dev has developed the API, he/she has defined requirements informed by business requirements. So follow what the API needs. Ask the dev for the documentation. If no documentation exists, then you will have to interview the dev and write it out. Make sure the dev has developed it based on some sort of requirement and not in silo. A product manager would also have more contextual knowledge about what is needed.
    – Nicolas
    Commented Jun 25 at 19:46


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.