Submit New Docs Page Visuals

[ppzgenome]

This page looks fine overall; after all it's primarily a functional page. Therefore, our main concern should be: when users arrive, does the FIRST action seem: A. Intuitive, and B. Obvious. If the FIRST act qualifies in both categories, theoretically, following actions will cascade naturally.

My perspective is that the FIRST action is NOT obvious and NOT intuitive. You might think the first action is dragging and dropping and the big box is clear. But that's actually not the FIRST act, at least not in the eyes of real users (continue reading). In the current state, we are expecting users to FIRST realize that they have to select the three respective file type buttons. This is not apparent or even sensible. I tested with people walking on campus today. 16/22 didn't realize they had to toggle the three top level buttons until after trying to upload a non-resume file (b/c resume is default state).

When I asked them, "please try to upload each of these files, a resume, a cover letter, and an essay" they dragged all three files into the box without thinking about file type.

When i asked them, "Go ahead and change the drop zone type for the file you need," 7 of them didn't realize the any of the buttons were clickable. Some tried to click the drop zone. one guy tried to right click the drop zone. This worries me.

No fear...They gave us a solution. Customers don't care to select the button corresponding to the right file type. They just want to drag all of their files that need editing into a huge bucket. What this tells me is customers NATURALLY expect us to do smart sorting. The question is... how do we do it? How do we know which file type?

My proposal:

1. restate the prices of each file type clearly
2. kill the three buttons on top
3. Clearly, the technical challenge is big. using only 1 drop zone, we can't tell which file is a resume or CL or essay. Even if we could FORCE customers to name their files with file types and somehow extract that information and price accordingly, that's burdensome UI.
4. Solution should be: 3 separate buckets. It is CLEAR that we are calling users to specific drop zones for specific types. This is also symmetrical with our Price Section Structure