UX Design


Savvior uses a simple and trusted methodology when designing for a new client. We follow the client from initial idea to nailing specifications, from creating initial mockups to an iterative prototyping process before formalizing the final design.

This process happens co-operatively with the client as they are invited to provide feedback and input at all stages of design. By letting the entire process remain open to users Savvior removes the risk of last minute changes or sudden “stop gaps” in user experience by ironing out known flaws during the mockup and prototype process.

The end goal for our design flow is a product that sharpens into focus, rather than a switch flip into final design. That is to say, the end product should be very familiar with the client as they will have seen it grow from skeleton to fully-fleshed out product.






During the discovery process the key stakeholders in the project from both the client and Savvior will meet to discuss everything from big-picture overviews, to look and feel, to specific “I want that” options. Savvior will bring its operations lead, project manager, and design team to provide expert level insight into the design of the app.

During these meeting(s) everything from the idea phase is fleshed out on paper, questions are asked from us based on past experience, and answers are given to any comments and concerns you the customer might have. This process also includes running through any process currently in use by you or your team. By running through how a potential current system operates we can identify with you known pros, cons, and flaws in the process.

While this discussion is occurring everything will be recorded onto a document available to everyone who is a key stakeholder to the project. This document will be in flex as new features or clarifications are discussed over the course of the discovery process. Once the specifications document is complete and both parties are happy with the results we move to the mockups or wireframes.


The initial mockups are usually done in a program we use specifically for its speed and ease of use. This will produce what are the most basic of mockup designs for the app, one that will give you a rough idea of the flow of the app and will allows for firming up of requirements for the project.

This initial mock up is done with user experience in mind and will most likely only represent the layout of the final design. That being said, by using these quick and messy mockups we can eliminate both any haziness in application flow and some of the potential roadblocks end users might run into. 

While this first mockup cycle is running, we can have our branding and visual design process begin if required. Any logos, pictures, or color schemes not provided for by the client can be fleshed out by our lead designer. 


Once the initial mockups are in a state where they are an accurate representation of the user experience flow the UX engineering team takes over. They combine the initial mockup with the finalized branding and visual design to produce a usable prototype.

This prototype will be partially functional and will allow for further testing of user experience bottlenecks, as well as to allow for a run through of application look and feel. That being said the prototype is still not the final design and is subject to changes.

Once the prototype is in the client's hands we will again look for feedback and comments regarding its look, feel, usability, and aesthetics. This testing of the prototype design can come from the client themselves, or through the use of focus groups provided by the client at meetings that Savvior will facilitate. Once again any and all comments, feedback, or concerns will go back to our UX and design team to tweak the prototype as needed until the design is completed.

Beta Testing and Focus Groups

While the document has already used the above terms this section will be used to explain the exact nature of our focus group and beta testing procedure. The focus groups usually consist of a group of 10 users, accessing a certain demographic which are provided by the client.

We can facilitate meetings with these groups (at Savvior HQ 800 Vinial Street, Pittsburgh PA 15212, or elsewhere) but do not usually provide the individual themselves. The open beta will consist of a number of users (recommended 100-500) who will download a beta version of the app for testing. This process will be facilitated by Savvior and the instructions for downloading the beta app can be provided.

Savvior will not be provide the individual users for the beta test, but rather look to our client to provide them to undergo Savvior’s process. 

Final Design

Once the design is finalized it should look very similar to the prototype in its last stages. This is due to the fact that the design will have gone through multiple iterations under your guidance and should at this point have its usability issues shaken out.

That being said, we understand that focus groups and QA can only go so far in user experience and design. That is why we will set up the process for an open beta of the application before it is released to the general population.

This beta represents the final testing of the design, as it will be subjected to a representation of the final user population.

This will be the point in which reported issues will switch from usability and feature problems, to bugs or fringe case problems. Once again, we will take this feedback to the developers and designers to ensure that the product both meets your requirements and will address your needs as a business.