Designers Solve Problems, They Don’t Push Pixels

“I’ve been amazed at how often those outside the discipline of design assume that what designers do is decoration — likely because so much bad design simply is decoration. Good design isn’t. Good design is problem solving.”

Jeffrey Veen

When you think of the word design we get carried away to various aspects, some think of designing a website whereas few perceive it as colours which they love to look. But more or less everyone thinks it is related to making something beautiful. In the process we forget that real design is not to generate revenue by making it look beautiful but it’s more about solving user problems and accelerating business objectives.

Implementing Objective-Driven UX Design

Start with defining the problem: It’s all about what problem you are going to solve and whether it is going to add value to the customers and will it give you the proper yield.

Metrics and expected outcomes: What are the metrics that you would like to show with and the period and result of your outcome? The constraints: it tells about the scope and timeline about the project.

Identify the appropriate design mechanics: There are different mechanisms a designer uses and every designer make sure that his design gives particular yield to the organisation.

Design, Test, Iterate: It defines about the process of your project.

Measure the Outcomes: Did your design solutions had a positive impact on your output? And how much it did made?

Accelerate Outcomes: It tells us how to accelerate the outcomes by making some designs.

When you iterate on an objective-driven UX project, the focus of your iterations should never just be on the designs themselves. You should focus on iterating on the problem statement, identifying and measuring the correct outcomes, and defining the correct constraints.

Experienced designers will tell you that the biggest design challenges are not with the actual implementation of a design solution, but rather with identifying the correct problem to solve.