Question

Identify a popular/common computer related product/solution that utilizes an interface that are not optimal for human interaction. It must clearly identify the original problem that lead to the development of the solution. Describe how the users resolve the problem before the solution was developed and after the development of the solution. Explain why you think the solution is not optimal and how to improve the solution to provide a better interface for human interaction.

Answer 1

The first step of product thinking is to determine the problem that your users are looking to solve. That’s the reason that they will buy your product (as long as it actually solves the problem in a meaningful and valuable way).

If the problem you choose doesn’t actually exist or the solution you propose doesn’t actually solve the problem – your products are going to be worthless to users. Products without users end up at the scrap heap (often with the jobs of the people who created them).

Sure, there’s the possibility that if you get the solution wrong – you can fix it but if you solve a problem that doesn’t exist; there’s little you can do about that in the post-launch analysis.

Finding real problems is difficult sometimes. Even when you do a bunch of research – it’s possible that you will identify a problem that doesn’t exist. However, the right place to start is always by talking to would-be users.

Don’t forget that users may not be able to articulate their problems very well (it’s not their job as Steve Jobs would have said) so you may need to dig deep and do some real life observations as well as just talking to your users.

It’s vital that your process delivers a solution that solves the problem. Features that enhance this solution are welcome but if you don’t solve the problem – the whole product is fluff nothing more. It’s important to remember that while Interaction Design and Visual Design can build something beautiful – it’s wasted without the product being useful.It allows you to create features that matter for the users of your products.

It lets you see the product in context and not as a combination of features and design efforts. It makes sure that you’re tackling meaningful problems. It reduces the risks of creating product failures (though nothing can eliminate these risks entirely).