Colorimeter

the process

Before anything could be done on the computer, the first step of the process involved a lot of user research. From talking with people in the filed using the application, to the people responsible for the data involved, and the people with the concept and funding, a lot of stakeholder interviews were held to analyze specific needs from different perspectives.

After collecting the data, wireframes were started in Axure. The wireframes were a little more in-depth than standard wireframes, in that we had a lot of analytical what-if scenarios being implemented, a lot of step-by-step interactivity built out from start to finish, and a lot of ready-to-launch content finalized in the wireframes.

when abnormal becomes the norm

It was decided, that with the remaining budget we had left after all of the up front research, and detail poured into the wireframes, that we would apply the styling within Axure itself, instead of another design program.

after the design

The complexities really started happening after the research, wireframes and designs were completed. The application was being built by a third-party, not at the agency where I worked, nor at Taylor. They sourced an agency with English as a second language, so I had to make sure I found a common ground to communicate what needed to happen and how.

code is a universal language

I put together documentation that outlined every element screen by screen, and incorporated lines of code as samples for how to style the elements. A general style guide was incorporated into the documentation, but there were a lot of unique screens throughout the application that required special consideration and varying layouts, which required documentation be very specific.