If decisions about requirements, #productdesign and #UX are being made without you, I have a suggestion:
Stop waiting for an invitation.
Start inviting yourself.
(a LONG thread ahead...settle in)
1/13
I’m sure in your organization there are strategic meetings you’re not part of, where product strategy or requirements or sprint plans are made and decided without you.
Everyone else knows things you don’t; information upstream never makes it to you.
2/13
You feel marginalized, left out, disrespected, OK, fine. I get it. That happens, more often than it should, I agree.
So what are you gonna DO about it?
Where do you need to be to know what they know — when they know it?
What activities? Conversations? Meetings?
3/13
Think about your company: what do those cross-departmental interactions look like, where do they happen, how do they happen?
Who’s currently invited — and why?
Who lives on the front lines of these bigger, more strategic, upstream problems?
4/13
Are you hanging out with these people regularly? If not, why not? What’s stopping you? Well, if I had to guess, it's the fact that you’re not invited to any of those discussions.
But guess what? You do not have to wait for an invite.
Invite yourself.
5/13
Ask: “hey, can I sit in on that meeting? It'd really help me understand the larger business goals driving the work I’m doing. It'd help me make sure the choices and decisions I make are in line with what you’re after, in line with the goals of the department (or business).”
6/13
You’re asking to be a fly on the wall, under the guise of learning.
And that’s an honest ask, but make no mistake: the goal of being in these meetings is to eventually *hijack* them. 😎
To be there to speak up and contribute to those conversations.
7/13
To demonstrate that you get what goes on at the big kids table.
To show you're uniquely positioned to clear the road for those outcomes they want.
To have the opportunity to point out and speak to #UX issues that you know can drive customer and business results.
8/13
Your focus in those meetings, what you’re listening for is how issues affect *people,* not the organization as some nebulous whole.
Other people in other roles in other departments who have strategic influence on product decisions.
What are they struggling with?
9/13
Are those issues persistent?
How would solving them make them (and you) look like heroes?
Why this matters:
YOUR BEHAVIOR REINFORCES THEIR BELIEFS.
10/13
If you’re a passive order taker or someone who only preaches the gospel of UX and design — or worse, says nothing at all — you are reinforcing all the things you hate about how they see you.
You're saying "this is what UX and Design work looks like."
11/13
You're saying "my work happens at the end of the process; I make it pretty; you dictate, I do."
Your business counterparts do not realize they can get something more, something better from you; this is all they know.
12/13
It is up to you to change that perception.
And in order to do that, you must find a way to get more face time with those people.
I teach UXers + Designers how to do this and other things that raise their profile + respect at my UX 365 Academy: learn.givegoodux.com.
13/13
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Since so many ask so often, I will finally share my #UX process (a thread):
1) Get clear on why this app, site or system exists, who needs it and what they expect to be able to do with it.
2) Assess the current state of the app, site or system and map out how people use it.
3) Determine where and how the product (and the company) is falling short and what the consequences of each of those instances are, for users and for the business (existing or new research).
4) Prioritize and rank those failure areas: how bad and how often?
7) Be willing to completely blow all of this up and do something else entirely depending on the company, the team, the users, customers, constraints, etc.
I was in a meeting once where there was a religious argument between groups of developers, database folks, product owners and executive managers.
The topic: why a certain report screen was taking so long to load.
(1/12)
It was a report clients were asking for; they log in, enter their credentials, enter a date range, set some filters — and then the system would literally take up to three full minutes to fully load the report.
You literally got a blank screen for several minutes.
(2/12)
The database folks are barking: "our infrastructure prevents us from doing this any other way, dev needs to do things differently." #Developers fire back: "it's a needlessly complex data structure." #UX folks are angry with both groups: "we TOLD you this would happen."
A significantly large number of companies and organizations share three specific traits when it comes to #UX improvement and #ProductDesign in general:
1 - They don’t really know what their users or customers actually want.
(1/13)
2 - They’re under the mistaken assumption that surveys or their NPS scores tell them what the value of their product/service is to those users.
3 - They’re not willing to allow you to talk to those users to find out what they actually need or hope to accomplish.
(2/13)
I get enough emails and DMs every day to tell me that this is reality for most of you. And the question folks ask me is always the same:
What the hell do I DO?
My answer tends to ruffle some feathers, but here it is.
Them: "We never have enough time to do proper user interviews."
Me: "How much time do you have?"
Them: "a week."
Me: "Let me tell you a story..."
And the story, #UX and #design friends, goes like this:
(1/11)
I was consulting with an organization, whose team needed to do some research; interviews specifically. They said "well, we have 24 hours based on our schedule…but we have to get to this other work to make deadline and right now it's all hands on deck."
(2/11)
So the team can't spare the manpower or the people and there were lots of reasons why that date couldn't move. In the end, we got eight hours.
Eight hours to talk to users and get some sense of what's going on here.
I will be 54 this year. I have helped product design and development teams and individuals in startups, mid sized orgs and global Fortune 100 orgs in 23 U.S. states and six countries in almost every industry you can think of for thirty (30) years.
(1/11)
And across that span and across all those companies and industries, I have seen the same patterns and the same situations over and over and over again when it comes to the power, autonomy and authority far too many people assume #UX and #UI Designers have.
(2/11)
The common thread over every experience across that time is that the majority of organizations still operate in command-and-control fashion when it comes to Design + UX.
The marginalization, devaluing + disempowering of UX and Design folks isn’t a bug, it’s a feature.
Ever wonder why executives and bosses are often so resistant to doing #UX work?
Why they seem to become personally offended at the very mention of user research or #IA or prototyping, in a way as if you were suggesting a diabolical plot to overthrow the government?
(1/9)
From "we don’t have time for that," to "we know what our customers want," to "just make the #UI better looking," the wall of rejection is thrown up fast and furious.
Where does this come from, and more importantly, how do you deal with it?
(2/9)
Let’s start here: most people in management or executive positions can’t truly see what’s broken, because they’re usually only looking at the side that’s working.