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 How UXers Think We're All Users

Posted by armelbile
armelbile
325 Points

If I got this right, as a UXer, I must take input of all users and aim at finding solutions for all needs in budget...

Maybe I'm adding an Agile twist, but are all users really equals here? I mean, I understand that we aim at producing a holistic solution that benefit to all users within a given budget. But does this always work? I mean, if working on an app that targets 5 different needs (use case or usage scenario) and getting a lot of input from users from a 6th or 7th target, should we work in successive loops and prioritise the main targets first, the other later...? (a phased holistic approach :D )

heather dietz
heather dietz
2,590 Points
heather dietz
heather dietz
2,590 Points

You don't take the INPUT of ALL users when initially designing your product, but you do take the different sorts of users of your product into consideration. You probably can't address ALL user needs, but UX is iterative so each time you test your product (solicit user input) and refine your product, you may be able to solve more problems.