Proxyclick is a startup with a Saas Product for Facility Management. Dedicated to Business users, their application lets office managers handle most aspects of a company’s general services. From catering, lunch orders, service requests to allocating parking spaces.
Rebuilt from the ground up
The Proxyclick Application had been initially developed around a single module, and over time, had grown to include more functionalities. Unfortunately, the initial architecture was not designed to handle such complexity. I was hired to do a complete redesign of the application.
User Centered Design
In order to gain a complete understanding of Proxyclick users, we conducted:
- online surveys
- on-site surveys
- on-site user interviews
- Analytics mining
Observing and interviewing the Proxyclick users in context
The qualitative and quantitative information that we gathered helped us to discover the main issues of the current version, and further define the goals of the redesign.
Creating a shared understanding of the product
After gathering the information, we mapped the whole application processes using service design maps. By visualizing the user flows, we managed to isolate several processes where we could automate interactions, and discovered areas of improvement.
Experience Mapping sample
To make sure that the whole team would be involved in crafting, and perpetuating the experience of the product, we followed an iterative process with "design studio" sessions to define the global structure of the application's screens. Having everyone involved, including sales and support staff, resulted in rich and informative discussions, and altogether, a better shared understanding of the product.
Running a collaborative design session
Once I had started more detailed wireframing of the application's views, we followed "lean ux" principles, shared all the wireframes on the company's walls, available for discussion, criticism, insight and new ideas.
Parallel visual exploration and Early Prototyping
After exploring the design of the application with paper and wireframes, we hit some questions about the interface that could only be answered with actual code. As we had also started exploration of the UI design in parallel to the wireframing work, we quickly stepped into a prototyping phase, thus gaining time over the usual visual design process.
Building the UI Framework and iterating
The rest of the process was a smooth transition to the creation of an interface framework in the form of HTML/CSS/JS UI modules. First in semi-static templates, and then, as the developers catched up with the process, as real production code. As we continuously iterated, we were able to quickly correct issues with some of the UI elements, and move forward. A styleguide was also built as a reference for all the developers.
The layout of the application was entirely built in a responsive way, handling large screens as well as tablets. And we also were extra-careful in making all the UI controls large enough to be used on touchscreens.
Built for speed
The first modules of the application are currently undergoing beta testing, and the feedback is overwhelmingly positive. Stay tuned for the official launch!