Monthly Archives: April 2011

Determine the importance of each feature

It is easy to overbuild. What can help you determine the importance of a feature? 1. Develop a baseline for a minimal viable product based on research (users, subject matter experts, business, competitive analysis). Determine the minimum set of features the product needs … Continue reading

Posted in Product Owner | Leave a comment

Most people suffice

People are busy and often don’t take time to learn applications, even if they use them everyday. Most people suffice, or learn just enough to complete the task at hand, rather then investing more time to learn the most effective … Continue reading

Posted in Design, Usability | Leave a comment

Revisit your users- conduct Longitudinal Research

Once our product is released, it is important to remember our work is not finished. Over time some of our users change from first time users to power users, their needs may have changed and they may begin to use our product … Continue reading

Posted in Design, Research, Usability | Leave a comment

The work is the gift

Durning an interview on the program Inside the Actors Studio Matt Damon said, “The work is the gift”. I think about that statement often. Our work, the processes of  solving problems, empathizing with people, growing as craftsman in design and … Continue reading

Posted in Goals | Leave a comment

In Context Usability Testing

Recently I pulled a car up to a toll-both to pay to exit parking lot in an airport. In theory this is a relatively simple interaction. The system needs to have a way for me to enter in my ticket so it … Continue reading

Posted in Design, Usability | Leave a comment

Provide the needed information at the right time

Throughout New York City, restaurants are now required to post a sanitary grades on their front windows. I have seen the letters A, B and even one C displayed. Initially I thought any restaurant that received anything less then an “A” would soon close. I have not seen … Continue reading

Posted in Design, Usability | Leave a comment

Understand your users flow before you build your solution

 A company spends millions of dollars to create a new web application with the goal of making their outside sales team  more efficient.  After the application is launched, it gets little to no users. There are a number of reasons why the … Continue reading

Posted in Design, Problem Solving | Leave a comment

Solve your client’s problems first, then push further

During a client meeting we may decide on a problem to solve or a solution to implement. After the meeting, as we spend more time on the problem, we may uncover a new understanding or a better implementation. If we … Continue reading

Posted in Client Relationships | Leave a comment

Challenging Assumptions with Reverse Thinking

An often used approach to problem solving is to start by understanding the situation then devise a solution. A simplified example is when  looking for a job you may determine, “I need to contact companies with my resume.” The complexity with this approach is that you … Continue reading

Posted in Problem Solving | Leave a comment

Guide your design with an experience strategy

We don’t buy a Wii, we buy the experience the Wii creates. Products or services facilitate or create experiences. With that thought in mind, one way to approach design is to start with an experience strategy.  An over simplified example for the Wii could … Continue reading

Posted in Design | Leave a comment