This post is the second part of a series of articles that I plan to publish on User-centered Planning. Please check the Part 1 if you haven’t done that yet.
In the previous post, I presented a video from Google’s Developer Student Clubs, by Arman Hezarkhani, that talks about “How to identify a problem”. The first and most important step towards the success of a software product is the precise and correct definition of the problems it proposes to solve. However, we need to fight the urge to contemplate the system from what we think is best and instead really study our customers’ challenges and needs.
Developers, Architects, UX Designers, Business Owners, and basically everybody else have an opinion on what is best in terms of look and feel, functionalities, information architecture, usability, etc. However, even if everybody else forgets it, the reality is that what matters is (a) What do our customers want? (b) How do they think about the content and the information architecture/organization? (c) Which visual specs are more appealing to them? (d) How could the system help them solve their problems better and faster? (e) How can we make it easier for them to learn and permanently adopt our system? And so on.
Arman once again delivered a high-quality video now covering “What to do once we identify the problems our system should focus on solving?” -Identifying the problem is just the first step. So, without further ado, here it goes: