We set up a kickoff meeting with designers, PMs, and key developers at the very beginning. The goal of the kickoff meeting is to share knowledge to understand the users so that when I move to design process, everyone on the team could feel the ownership.
1. The data informed the problems in a quantitative dimension, and it's not enough to know "who" and "what". So I try to take a deep insight into users and figure out the "why" and "how".
2. Plus, I am able to validate my hypothesis by talking with users.
New users come to the Upwork with strong expectations for an efficient and hassle-free work flow. However, the job post on the mobile web did a bad job on educating users about potential causes of confusion.
High-value jobs always need a detailed job description. However, typing is slow and painful on a mobile device.
I conducted the brainstorming session with PM, designers and key developers. The goal is to make sure that everyone is on the same page of the design process that they can contribute from different perspectives.
I like the idea of "building to think". So I created prototype and IA at very early stage. Unlike the user's feedback that identifies specific things which need to be changed. Internal feedback always helps me on uncovering opportunity and getting me outside my own head.
I got positive feedback on the friendly explainer text, and it helps users better understand the overall task flow.
I added the prompt text into the job description field. However, when users start to type, the prompt text gone, that's a problem I need to fix.
A good job description always comes with bold titles and organized details.
