Vivus and Human Design

blog-details

Across each business and personal aspect of life, it’s no surprise to see people tapping into web and app tools to improve their day-to-day. Unfortunately, users are more likely to receive a poor experience rather than a great one. 

Many factors lead any team or project towards a poorly built experience even though the product solves the problem. In most cases, the speed in which the industry works leads a project towards focusing on features, partnerships, and functionality. These items require specific attention that lose key details depending on the process addressed.

Regardless of where you fall in the business pipeline, designers and project managers are missing an important step when determining the best way to solve a user’s problem: consider the human behind each product.  The problem will be crystal clear, allowing the designer to modify the look and feel with thoughtful experience design.

A few strategies to keep people in mind as you work towards tackling the market, product design, and the functionality of the web or mobile app. Here is a quick checklist to utilize: 

  1. Pre-work leads to great work and allows for better post-work
  2. Have a focus on the end goal directionally at each step 
  3. Tap into the personality of a product/service 
  4. As with everything, as humans change, so does their problems

Pre-work leads to great work and allows for better post-work

While projects keep growing, data is collected at all points. For those fortunate able to plan, tap into user feedback to understand the dialogue surrounding similar or same builds or projects. While surveys may seem dull and repetitive, those insights are indicators and potential guidelines for those building the roadmap ahead. 

Once you have mapped a direction towards your end goal, look to tap into the prototype stage to test and experiment with human insights and reactions. A tool to consider during this phase is Proto.io and Invision, which allows you to demo, pull insights, and feedback to develop the phases ahead.

Feedback correlates with pain points. Just like an Uber driver talking too much about how his theory of “flat earth”. Don’t assume how the user is going to experience the product, like how the driver expected you to join him at the next flat earth convention.