Choose Your Customers First, said Seth Godin in his post yesterday. “First figure out who you’d like to do business with, then go make something just for them.”
It’s a message I’ve been evangelizing for the past year: define the problem before devising the solution.
Research > Strategy > Design. If you don’t know why and who before you come up with what, you’ll end up creating nothing for no one.
— Whitney Hess (@whitneyhess) February 1, 2012
Mobile First and Content First both imply that your platform and your materials (= your solution) are where you should begin your design process. But how will you ever know if it’s the right platform and the right materials? No amount of best practices can get you there.
That’s why I advocate for Customers First — decide who you want your business to serve, find out everything there is to know about them, build empathy for them throughout your team, and then determine what you can offer to solve their problems that no one else can.
I assert that design is problem solving in my presentation and essay, What’s Your Problem? Putting Purpose Back Into Your Projects.
Design is both problem and solution. In order to know we are creating the right solution, we have to make sure we’re solving the right problem.
It’s amazing how often this reality is ignored. Companies invent for the sake of invention without caring, understanding or appreciating the problems their customers actually face.
To combat this nonsensical behavior, I share my three principles of problem solving:
- Define the problem before trying to solve it
- Ask questions to root out the truth
- Be obsessed with the problem, not the solution
Read the full text of my essay at: What’s Your Problem? Putting Purpose Back Into Your Projects
And remember, Customers First!
- Give Your Team a UX Jump-Start May 21, 2013 | 0 comments
- User Experience Coaching for Drupal.org May 3, 2014 | 1 comments
- Knowing Why Beats Knowing How August 6, 2012 | 13 comments
- Foreword to Digital Product Management May 8, 2014 | 0 comments
- What’s Your Problem? Putting Purpose Back into Your Projects October 18, 2012 | 48 comments