Sounds a lot like anything you can iteratively improve. Could also be applied to marketing, cold-call-sales, making a great coffee, ...
Don't look for a UX guy, be a UX guy
11–20 of 44 posts
Re: Don't look for a UX guy, be a UX guy
#12"To build a great UX, one has to step back and think about what’s most important, try to come up with the most simple and shortest path to get there, build, analyze what works and why(not), measure, test, rinse, and repeat." This is true, but in my experience, the best UX people are even more excellent at figuring out what is NOT important and getting rid of it (or not investing any time in those things at all). Also…
I believe that's what the OP implied when he stated most simple and shortest path to get there, simplifying the UX/UI is based on deduction, archetype development and enough experience/knowledge to start off with a barebones wireframe instead of a bloated mess. Loosely basing the method of delivering an effective UX on Occam's Razor, a philosophy that states if you base your decision on the path with the fewest assumptions and thereby offers the simplest explanation of the effect, that's usually the best route to take.
The most simple path is one that only relies on what's important to your goals and skips all the bloated "data" and "ideas" that would hurt the UX.
Re: Don't look for a UX guy, be a UX guy
#13"To build a great UX, one has to step back and think about what’s most important, try to come up with the most simple and shortest path to get there, build, analyze what works and why(not), measure, test, rinse, and repeat." This is true, but in my experience, the best UX people are even more excellent at figuring out what is NOT important and getting rid of it (or not investing any time in those things at all). Also…
everyone should be aligned, everyone should be focused on the audience they are building for and the needs of those users. that is what differentiates a stripe from a google checkout and, to be cliche, an iphone from a treo.
even the concept of having a "ux guy" means there are others in the org who are "not ux guys"
there is nobody at most of the companies who model "good ux" responsible for that "good ux"
Re: Don't look for a UX guy, be a UX guy
#14Re: Don't look for a UX guy, be a UX guy
#15Earlier quoted context omitted.
Forgetting for a moment all the theory of color and contrast /equilibrium in a design: 1 - different people see different shades (difference in monitors) 2 - Unless there is a glaring problem with the shade of color chosen (like something most designers wouldn't approve), changing shades is one of the least important areas of improvement possible 3 - The current redesigns of GMail / G+ / GReader (among others) are ve…
(1) Can't that be accounted for in some manner, especially when you have so much data? Typically when I design tests at work, it is not unusual to add many rules and exceptions to make sure the data is as accurate as possible. (2) This is where it becomes tricky. You have to understand that these decisions are made at a very local level by small teams with specific goals(for example, "bump revenue from sidebar links…
2 Google does an can certainly work with whatever they want, but they should try the big improvements first. Their work with page loading times is great, and that has been shown to correlate with earnings. But trying to tune the shades when there are more important things to be worked is pointless
3 It goes to show they don't understand design. In some aspects they do (like GMaps) but it seems to be declining
Re: Don't look for a UX guy, be a UX guy
#16I couldn't disagree more. I have never met anybody who can program AND do UX well. Maybe there are very very rare exceptions, but these two skills are pretty much mutually exclusive.
First of all, you need completely different modes of thinking while coding and while doing UX. Left/right brain, and all that. But more importantly, to be a good UX person, you need tons of training - design, marketing and psychology being three main areas. To be a great programmer, you need completely different set of training. Both UX and programming require single-minded attention, dedication and years to master.
To expect someone to do both of those things well is not only unrealistic, but plain WRONG.
Re: Don't look for a UX guy, be a UX guy
#17> I think the greatest companies of the next few years will be build by teams that consist of people that can program AND can do UX. I couldn't disagree more. I have never met anybody who can program AND do UX well . Maybe there are very very rare exceptions, but these two skills are pretty much mutually exclusive. First of all, you need completely different modes of thinking while coding and while doing UX. Left/rig…
Re: Don't look for a UX guy, be a UX guy
#18> I think the greatest companies of the next few years will be build by teams that consist of people that can program AND can do UX. I couldn't disagree more. I have never met anybody who can program AND do UX well . Maybe there are very very rare exceptions, but these two skills are pretty much mutually exclusive. First of all, you need completely different modes of thinking while coding and while doing UX. Left/rig…
Re: Don't look for a UX guy, be a UX guy
#19> I think the greatest companies of the next few years will be build by teams that consist of people that can program AND can do UX. I couldn't disagree more. I have never met anybody who can program AND do UX well . Maybe there are very very rare exceptions, but these two skills are pretty much mutually exclusive. First of all, you need completely different modes of thinking while coding and while doing UX. Left/rig…
Re: Don't look for a UX guy, be a UX guy
#20> I think the greatest companies of the next few years will be build by teams that consist of people that can program AND can do UX. I couldn't disagree more. I have never met anybody who can program AND do UX well . Maybe there are very very rare exceptions, but these two skills are pretty much mutually exclusive. First of all, you need completely different modes of thinking while coding and while doing UX. Left/rig…
Does our position really require years to master? Is a java or ruby programmer with 10 years experience that much better than a java or ruby programmer with 3 years experience?
What about design? Is building a website, interactive component or application so complex that only those with decades of experience can really 'get it'? Is someone who has twenty years of UX experience, dating back to the days of VB and Access applications, that much better than someone with five years?
I believe combining technical with creative is something that must be taken as a given with our industry.