Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

Design UX Basics What Do UX Designers Do? Problem Solvers

Li Mbo
Li Mbo
5,096 Points
Posted by Li Mbo
Li Mbo
5,096 Points

Why?

If the client wants an iPad app, why not just build it? Logically if we are trying to get clients, the question should be how do you want it and not why do you want it. He assumed wrongly that the app is what brings more users, it is his problem. You build the app, deliver it, get paid for it after the client is satisfaid and then you leave all the marketing stuff for him to take care of, since the initial problem (wanting an iPad app) was accomplished.

3 Answers

Michalis Efstathiou
Michalis Efstathiou
Courses Plus Student 4,638 Points

ethics

but I guess if you dont really care about ethics you can see it this way, by being honest with your client and helping him improve his business, you are creating a long term business relationship and a loyal client, which will lead to referals and more clients, as opposed to doing a one off job, getting the fee but ending up with an unhappy client which you will probably never hear from again and which will not recommend you to anyone else

Li Mbo
Li Mbo
5,096 Points
Li Mbo
Li Mbo
5,096 Points

Wow! Amazing answer Michalis! this is really the way business should be conducted.

Darren Joy
Darren Joy
19,573 Points
Darren Joy
Darren Joy
19,573 Points

In the world of project management and business analysis, it's considered a 'fail' if your deliverable doesn't satisfy the client, even if it's what they originally thought they wanted.. They take a look at the finished product and go "actually, I think I wanted this other slightly different thing..."

In some methodologies they actually have a word for his: VOC (voice of the customer). It's always best practice to listen to the voice of the customer. even if it's relatively silent. They want something and you need to figure out what that something is...

In the world of trying to build something of value and delight the customer (that's many fields, but design people particularly delight in delighting the customer by creating something from nothing [an idea]..), inthat world you want to be sure that your requirements as gleaned from the customer match what they really want.

If they say they want a donut but they really want a sandwich, and you investigate and ask and observe and give them a sandwich they will usually go "holy wow! I didn't even KNOW I wanted a sandwich! Thaaaaanks!" If you give them a donut they might be "that's cool" or they might be like "ah, actually I just realized I need something more substantial.."

That's the gist of what they are trying to convey in the video...

Find the problem, solve the problem. Don't 'assume' the problem. Find it. Root analysis... root cause... solve that and you are adding value to the world...

James Page
James Page
9,621 Points
James Page
James Page
9,621 Points

If you're a design/development team, then perhaps fair enough. However, if you're engaged by the business as a full-service agency or as UX consultants, then you would have to ask if you're the right people for the project or if you'd be providing an authentic or honest service (do you think a vet would pull someone's tooth out instead of a dentist if they were asked to?). From a UX perspective, it would be difficult to have defend the idea that you were able to satisfy both users' and the business' objectives - core requirements for UXers - because you wouldn't necessarily know what they were.