Problem solving basics
Design is primarily about communicating ideas and solving problems. The ideas you communicate should in turn contribute to your desired outcome.
Over time it becomes easier to identify bad assumptions in the process. I've listed some concepts below which will help make you a more productive problem solver.
What is a good outcome?
Outcomes justify the existence of your product. They can be anything from "raising awareness of your product", "creating excitement around your product" or "making your product easier to use". You define your outcomes and acheiving them is your measure of success.
Can outcomes ever be bad then?
Yes, that's why its important to understand the details:
Vague outcomes are common and can waste your time; acheiving something unspecific or unuseful.
Unintended outcomes can create more problems than they solve.
So what concepts are useful?
Here's some concepts that I find useful in my design process:
Combine simple ideas to create complex outcomes:
To find correct solutions, ask the correct questions:
When solving problems it feels intuitive to focus on solutions, but it's also important to understand the specifics of your problem. After all it's not much use solving the wrong problem, or worse, creating an entirely new one.
There are three types of knowledge:
a) The stuff "you know, you know"
b) the stuff "you know, you dont know"
c) the stuff "you dont know, you dont know"
In my experience its almost impossible to work solely in (a). Instead, by growing (b) and reducing (c) you will improve your awareness, becoming a better problem solver, and a more empathetic person.
In February 2020, we redesigned the account dashboard for users of the Barbican ticketing site.
Make a browser-based app for people who work at the Barbican and want to book/see available spaces in the centre.