A reflective conversation with a situation
My favorite way to think about the work of a designer.
My favorite way to think about the work of a designer.
Don’t talk about problems (or solutions). Instead, talk about progress. Only then can we be precise without dictating implementation details.
There’s such a thing as getting down to the root problem too quickly, particularly when it comes to product design. The value in figuring out the “Why?” behind things isn’t quite as much about the destination as it is about the journey.
We should happily take anyone’s feedback any way they want to give it. After that, it’s our job to continue the conversation and make sure we have the right information, and enough of it, to make a good choice on what to change in our products.
In short, I’d like to get specific about the fundamental skills involved in product design, a few brief examples of the type of work that can be done for each skill, and how they’re mapped to common product design roles.
Design can’t be relegated to a single role. We all care. We all want to make a better product. Unfortunately, we all too often forget the most important member of the team: the customer.
With the right background, an observer can find so much more value in their observations. But when the background of the observer is different than the intended audience, an observation can become a huge liability.
Creativity breathes life into successful websites. However, creative ideas and solutions can sometimes seem like guesswork — and guessing is risky business. So what can designers do to show clients they’re using a solid strategy and have the best intentions?