User Interface and User Experience: It’s Not All About Design, But About Solve The Problem

— Balancing in Product Development

High Fidelity — Lakon Apps

Take one example in making a disaster application — Lakon Apps.

The background of making this application, because of the frequent occurrence of natural disasters in Indonesia, and there is still no knowledge or education platform for citizens against disasters, then how to deal with them.

So, from this problem, we make a disaster application with the aim to provide a platform where citizens can get education about disasters and how to deal with them, so that citizens are better prepared to face disasters. This application is made for android platform, where citizens can access content wherever and whenever.
Lakon apps is done by a team of 19 peoples “this is a big team” in 2.5 months, which are divided into product managers, UI and ux designs, front end, Android, back end, and QA.

How To Solve It ?

First, What’s The Problem?

Design Process in this case study — Muhammad Raufan Yusup

The first thing we have to do before solving any problem is to identify the problem or make observations. First, as UI and UX team, we began with mini-research on existing disaster apps. After we know our opportunity, we will try to resolve what is the root of the problem.

To solve the problem you are facing, you have to connect between the situation that is happening and the goal you want to achieve.

Second, Make Priority and Why?

Priority is important when working on a product, especially in the long term. Without the right priorities, teams can move in the wrong direction, maybe even spend resources to create features that are not valuable. This is very dangerous for the survival of the product.

In product management, priority is not just “sorting what must be done first.” Moreover, priority setting is the art of delivering products to the vision that we want. —id.techinasia.com

The method used to determine priorities by Sleekr is voting. In this method, the product manager will gather all team members to discuss the importance of work (importance) and whether the work is possible (feasibility).

Then how to assess that a job is important and feasible to do?

The trick is to adjust the work to three important priority pillars, such as: Product vision, Job weight, and Product Roadmap. — Sleekr

Everyone has the right to give importance and feasibility values ​​to a job, then the results will be mapped to the Cartesian field. The importance value acts as the X axis, while feasibility is the Y axis. Tasks located in the most positive quadrant are the most important.

Third, Now it’s time to test the hypothesis for your potential solution.

The next step, make an execution plan and validation of problems encountered with user interview

You can’t just assume to make a UX design. You must “listen” to the voices of existing users in order to create a product that answers their needs.

Fourth, Make A Move to Solve The Problem

Remember, a plan doesn’t mean anything if you don’t run it. So don’t forget to implement the plan correctly.