Every project is different.
There may be similarities to projects we have worked on in the past, but the users intent, context, devices, content and business goals are widely variable. We look at the varying factors that lead to successful designs, and align business goals with user goals.
During this phase, activities that are commonly performed are prioritizing user stories, understanding business and technical requirements, analytical analysis, user interviews, contextual inquiries, and baseline usability testing.
Every single one of these activities guides and informs the later design and development processes to a common goal.
Content Modeling, Strategy & Information Architecture
Knowing who the users are and what motivates their use of an application is one thing, the content that drives and engages them to use it intuitively is another.
Understanding the content, it’s volume, how it will be accessed and what pieces of data drives user engagement is one of the most important steps at the beginning of the design process.
Sketch to Code
We practice a new, updated approach to solving design problems at NiceUX. Instead of spending laborious hours working on static wireframes, with annotations describing the interaction, we sketch out the initial wireframes quickly and efficiently, then move right into code. The primary difference is between getting a annotated wireframe telling you there is an animated transition, and the one that shows you. Seeing the tangible slide, fade-in effect of a message leaves little to interpretation.
The medium we design for and live in everyday is dynamic, fluid and our design process should be as well.
Ever work with a company that produces 25 PSD’s of the design and then finding out the content doesn’t work too well in the design and need to tweak something here and there?
Rather jaw dropping when you see the final bill or when you hear it’s going to take two days to turn around the changes, isn’t it?
These companies spend way too much time in Photoshop. It is imperative to understand the aesthetic design before deciding if it feels right for your brand, but at what cost? But don’t worry, there is a much more efficient way to handle visual design.
We produce a few style guides of UI elements to understand the composition, balance, and how typography, textures and controls are designed.
Once the right aesthetic feel is accomplished, we apply that style to the coded prototype we already have built. That way, any changes that affect multiple pages is as simple as modifying a CSS class or shared html component. This turns that two day turn around into a 5 minute turn around.
Validation & Iteration
We usability test every product we design.
Products designed in a vacuum, or an agency that quits at making sure you, the client, likes the design is a bad partner to work with and is communicating to you that long term success of this product is not their priority, the current invoice is. The truth about product design, is that if human factors are not taken into account and the design is not validated that it works for human interaction, you’re probably going to get a product no one uses.
Our software development process is grounded in the Agile methodology of releasing small and often.
We plan our holistic vision of the design of the product, but when it comes to producing the product, we’re a well oiled machine. We take the functionality, break it down into development tasks described to the smallest level of detail and prioritize them. This gives you a viable product faster, with smaller margin of development error, and will allow us to get feedback on functionality faster than the traditional waterfall method.