Publisher Application
When open registration no longer fit our business model, we needed to design an application process. I split the project into two parts; the application, and the approval process. Here I focus on the application itself.
Information Architecture
To start, I conducted brainstorms and interviews with the group that would be approving the applications. This gave us a list of fields that we would need from a user to process their application. I compared those fields with the information the system required for an account to ensure approval didn't result in requests for additional random information. I used card sorting to group and order the fields.
back to top ↑
User Input Design
I defined what type of input to use for each field (text, select, checkbox, etc), refined labels and terminology, and defined options for selects. The error state is often overlooked but error prevention and recovery are extremely important. I wrote input validation rules for each field depending on its type, and an error message for each failure case.
back to top ↑
Wireframes
I created high-fidelity wireframes of the application page, including the error state. I addressed issues like field length, select height, and default values. I used real content to ensure the layout worked. I identified questions users might have about their application and provided the answers in context.
back to top ↑
Results
The final application offers a streamlined and intuitive process that makes it quick and easy for publishers to apply, while collecting enough information for the publisher team to evaluate each applicant. By setting expectations and answering questions along the way users feel reassured about the process. Abandon rates were low and the account team was thrilled with the completeness of data the process ensured.
back to top ↑