Before we can design for a user we need to know our users. User Analysis is necessary to understand the needs and propensities of the users. Who is this for? Demographics? Likes/Dislikes? Hobbies? Occupation?
What is the primary action the users need to perform? There may be many things someone can do on your site or application but there’s always a main task.
What needs to happen on the back-end vs. the front-end? Do you have multiple systems and/or servers? Which ones will handle a function the best.
Sketch. A lot. It’s quick. It’s cheap. It’s effective. Sketching gets a lot of ideas out of your head and onto paper quickly. It helps shape good ideas and eliminate bad ones. You can iterate on sketches very quickly. The investment is low for the return.
The information architecture should start to take place. This is where things go from a bunch of loosely connected concepts and pieces of information into a more cohesive documentation of how the product looks and functions. For wireframes I use Axure, UXPIN or Balsamiq.
There are lots of different prototypes you can do. These can range from a very simple clickable PDF to an almost fully functioning HTML/CSS website. It really depends on what you need for your project as to how far you go with it.
This is where you then go back and start to make the wireframes high-fidelity. Add all the definition you need. Cover as many details about the layout and interaction as you can. Anything you leave open to interpretation may easily be taken the opposite way you wanted.
This step can take place wherever you need it to during the design process. It sometimes fits at the end and sometimes more towards the beginning of a project. However, this is where you get actual user feedback.
This may not be quite as collaborative but there are often issues that arise during this stage in which you’ll need to adjust the UX. This also helps you to gain an understanding of the technical limitations for future projects. Your developers will be much happier for you to gain this knowledge rather than designing impossible solutions.
There are lots of different prototypes you can create. These can range from a very simple clickable PDF to an almost fully functioning HTML/CSS website. It really depends on what you need for your project as to how far you go with it.
Michael did an excellent job in his position during his tenure with the company. Michael is organized, can work independently, and is able to effectively multi-task to ensure that all projects are completed in a timely manner. I recommend Michael Lawless without reservations. I am confident he would be an asset to any employer.
Michael is a very passionate designer always interested in learning new technologies and new techniques. He handled our application assignment with aplomb and diligence, displaying the ability to follow creative direction while adding his own creative input in a diplomatic and useful way.