May 08 2013
We’ve all seen it, lived it, experienced it, and heard about it: the half-baked app. In this article we’ll discuss how defining a clear mobile considerations will prevent creating a murky user experience and alleviate existing ones.
Step 1: Understand your users
There’s a great saying that’s been said a million times over: “You are not your user”. It may sound basic, but clearly defining key metrics about your audience can help ensure user adoption, and the success of your application. Some examples of how to further define your audience include:
- What’s your users’ Average Age?
- What device type(s) do they use?
- What’s the gender spread of your user population?
- What occupations do your users hold?
Jun 10 2011
Consider the following scenario: You get a flat tire while on the interstate doing 65 miles per hour, you steer the car to the side of the road and while traffic is whizzing inches by you fight to put on your spare. Now consider doing this exact same task in the comfort and safety of your driveway. You’re probably thinking ‘apples and oranges’, right? Though the task is the exact same for each scenario, the pressures, environment and stress are on opposite ends of the spectrum.
Usability testing allows designers an opportunity to assess layouts, workflows, and users expected interactions with a system before sending it to the development team. This process can be fairly straight forward for users accessing the tool in a standard setting, but what about those in high pressure situations or those in highly specialized applications?
Dec 21 2009
Over the years that I've spent practicing, studying, and quietly observing all things analysis across a handful of projects I've come to learn that following a few simple rules can help lead to a successful project. Let's take a look at the top five things that you should always do to make your job easier in the long run, keep your customer happy, and ultimately deliver a winning product:
1.) Maintain consistency in document design, and file storage structures. It's a very simple, but often overlooked practice that can mean the difference between avoiding last minute confusion and encountering some embarrassing heartache (Read: Exactly where is it in this document?!?).
Not only is document structure an important part of successful delivery, but file structure is important as well. Forget “where in this document is that feature” when you cant find the file easily.