712 karma · joined November 7, 2012
I got lost around "wank word" and UX being the "Web 2.0 of the design world." Most UX people I know are focused on user research, usability, information architecture, and interaction design. I'd say maybe, 1 in 5 are visual designers, and maybe 1 in 3 have any passable graphic design skill at all.
Maybe you're saying that people will be just called "user researcher", "information architect", etc etc and not use the word UX. But I think "wank word" is a tad inaccurate.
(im the author if that wasn't clear)
Unless you just want a grid and no other part of the Bootstrap styles. I think if you only include the Bootstrap grid in your compiled CSS, it's pretty lightweight. Not as much as this, but you don't need to include everything else.
There's an element of user-advocacy that I'm doing where I take the experience they are having and translate it back into business, design, and development goals as when someone is trying to use an enterprise piece of software and the experience is terrible, that is going to fall on designers, developers, PM's, and all the other people involved in the creation of the "thing" which becomes the user's experience.
That's another ambiguous situation. I go spend 2 days with users out at a company HQ, and I come back with tons of data that now has to be consumed by devs, designers, pm, marketers, executives, QA, customer service etc etc. The experience of what we build is a collection of every role in the entire company as far as the user is concerned, and all those various business roles need that UX information brought back. So at this point I'm so far from UI and visual design I'm closer to a PM or product owner now, but soon will be jumping back into the design an development realm to start to fix those experience problems.. unless the problems result in bad business drivers or invalid use-cases, so then I'm back at the PM and management table,
I still can't find a clear distinction about what I'm supposed to say I do. I just know that there is a certain disservice to just tell people "UI design, look and feel."
So yeah, I'll be in a PM meeting and then leading the PM meeting. Then I'll go out and into a meeting where we're analyzing analytics on the website, then to a meeting with devs on how we're implementing the interface literally, and getting me set up so I can run builds, edit the html/css, write all the front end views while devs create the models.
And then the CEO pulls me aside and wants to know what 'I'm doing to help turn this company culture into one that is user-centered and customer driven."
So it is like being a consultant on this huge spectrum of "customer/user experience" touch-points, and it's way more than just 1 or 2 people can do. And then all of this is rolled up into the perception that you're there for "look and feel" which probably only takes up 15-20% of your actual job.
You've made a really good summary of how I feel often.
It goes from 50/50 one day, to 90/10, to 10/90. And yes, often as I have lived and witnessed, UX is set up to fail through that structure, especially when they don't actually "own" anything.
"Company Culture evangelism" is a funny one because yes, at 2 companies part of the "UX" job, by request of C-level execs, was to work daily on spreading and educating on a "user centered culture" throughout the company :D
Reading the stuff here in HN, I agree with almost everything said. My intent wasn't to take a hard line tone, and in retrospect after getting tons and tons of feedback, I'd write it differently, but I'll take this chance to clarify some things, both for myself and for others.
It is not written in a snarky or superior voice. It wasn't a rant. If it sounded so, I apologize. It also comes off as a list of "this is what a UX job title should be", which also wasn't my intent. The simplest way to say what I was trying to convey is that if you label yourself as anything "UX whatever", it is perceived as "graphic artist for interfaces."
The article often seems to convey that UX "owns" all these different things, like it's a panacea role above all others. It's not.
It's not something that I can clearly define. On the little 2-column lists, the things on the left were supposed to be things that I/we "do" in the sense of what often becomes the reality of the job, not in the sense of responsibilities that should be granted to use to be accountable for. And if that large list does become the reality of the job, it's more than anyone can or should do. It was intended to be a "these are some of the things a UX person might be responsible for." And yes there are some silly ones on there.
I don't think UX is in a position of being a land-grab of everything that isn't writing code because "it's what we do", but it's more of a "this is what we are often doing" list. And some of the things on it should be owned by other discrete jobs careers. The motivation to write the article came from being in role after role where that list on the left was the list of things I was inadvertently responsible for, but "graphic designer for interfaces" is all that is seen by others, which isn't fair to UX people who don't focus on interface design, and isn't fair to interface designers who don't focus on the UX work that isn't based on UI or visuals or interaction.
It's sort of just a response to the introductory conversation I have the first few weeks at any job. "What is your role here?" "Well I'm the new UX guy." "Great! Our stuff is ugly, you're gonna give it that sexy look and feel?" "Yes, but I am going to be doing other things that sort of result in that look and feel you want" And then when I list off some of those things, typically the other person looks at me like I'm a lunatic and we both end up confused on what I'm actually supposed to be doing, and the disappointment that I'm not just there for look and feel.
But for sure, the article is not meant to be a land-grab or king of the hill situation of "UX OWNS EVERYTHING", but just a glimpse into the terrible ambiguity of what UX is and how the very common initial perception of "graphic designer for interfaces" makes it even more unclear.
Staples folding banquet table, 72".
Full size apple keyboard.
Microsoft Intellipoint Optical Mouse, 1.1 (USB/PS2)
It's not the visual or web designers primary job to A/B test or step into the users shoes on every detail, that's what a responsible and valuable UX person should be doing (note I didn't say UX designer).
Maybe we're talking about different types of personas. The question I'd ask from the very beginning is "who are we building this for and what problem is it going to solve?" And adding a little definition to the "who" and what problem they have is the first step in building anything, and making sure you don't waste time.
In the end, from day 1, from the first utterance of what your startup is about, you're building something for a human. Without empathy, you can't build the right product. And you can't empathize without personas. It's not even really a question of user experience, or user interface, it's just about nailing down the human problem.
I don't see how you can "know your market" without some sort of idea on who your user is, what their behaviors are, and have some sort of empathy with them.
Regarding pivoting and "throwing out" the work... each discipline of a team would do that. That's your UX designers job, just like a programmer would have to throw away code or a graphic artist would throw away design collateral for the new direction.
The "realize nobody cares" is exactly what good UX personas prevent. I guess if a startup doesn't know how to incorporate or conduct good UX you could run into those problems.
I guess I just don't agree with your premise. You're basically describing what happens when something goes wrong with your UX and personas - so of course your argument makes sense since you're highlighting a worst case scenario. But you're neglecting to acknowledge that every day, many startups effectively use and get tremendous value from personas and UX, and you can't do real UX without personas.
I'm sure you know about Alan Cooper's books, but another that I've found helps maximize the benefit, and minimize the danger, of personas is Tamara Adlin's "The Persona Lifecycle" : http://www.amazon.com/Persona-Lifecycle-Throughout-Interacti...
Plus, Microsoft isn't exactly known for it's effective UX.
When used to build something that should be visibly unique, the visual design and appeal is something that should be created aside from bootstrap, maybe with the grid in mind, and delivered as mockups or pattern guides.
No wonder I can never hit the semicolon or parens/braces/brackets. I use my index finger...
I had no idea how many of us could connect over our love of filming coffee preparation, or cats, or traffic, or terrible attempts at stop motion. Hey look another magic trick!
Seriously though. Fascinating and, for now, quite engaging. I vote against re-wind or links to previous clips though. Keep it ephemeral and impermanent. Like real life - a moment is here, then it is gone.
I guess, what is the plan for people who do complete the 30 days and try their best, get a positive evaluation from a peer, but then don't meet your criteria? "Sorry you did your best, but I'm keeping your 20 bucks."
I already paid, so you'll be hearing back :)
I put it up on github here: https://github.com/erikflowers/retina-mixin