Joe Natoli Profile picture
Oct 3 11 tweets 3 min read
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.

(3/11)
In these situations, you have to get REAL — fast. What you *want* is irrelevant and any time you spend bitching about it is time wasted. So — what can we do in eight hours?

I suggested to the team that we spend 15 to 20 minutes with five users. Which is what we did.

(4/11)
We recorded the interviews via audio, ran it through transcription software which was about 80% accurate. A lot of garbled words, but very usable. Three of us sat down at a table, each person with a hard copy of the transcripts of all 5 interviews and a red sharpie.

(5/11)
Here's what we're looking for: anything that shows up in *all five* of those conversations.

Same comment, same complaint, same part of the app that was an issue, same point of interaction, same thing they couldn’t find. If it shows up more than once, circle it in red.

(6/11)
And then we're gonna put our heads together, make a master list of all this stuff and that's what we're presenting.

And then we're gonna spend another couple hours thinking: what does that mean in terms of what we start designing tomorrow?

(7/11)
It tells us that these are five things that are potentially issues that we have to address in that design work.

Do we *know* these are the right things?

No.

Are we *certain* we're making the right calls?

Also no.

What we have are CLUES — and that's it.

(8/11)
Clues to point us in the direction we need to go in terms of solving problems for these users + this business. Issues we need to design for + do our best to solve.

We design it the best of our ability, get it in the build, put it out there, see how people do with it.

(9/11)
And we're gonna find out how right we are (or aren't).

That's the gig. It's not about being right — it's about getting REAL. Using what you've got to work with.

Because when you're up against the wall like this, there's no way to BE right.

It's not possible.

(10/11)
So the next time you have less time or resources than you'd like — and you can't do anything to change it — take a look around. Look outside formal processes, best practices. Improvise.

Something is ALWAYS better than nothing.

(11/11)

#uxResearch #uxDesign #LetsGetRealAboutUX

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Joe Natoli

Joe Natoli Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @joenatoli

Jul 6
<ux_rant>

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.

(3/11)
Read 12 tweets
May 19
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.

And in reality, it's not their fault.

(3/9)
Read 9 tweets
May 17
Rules for Pitching to #UX Stakeholders Dept.

To me, EVERY meeting is a working meeting. So the very first time I speak to a room of stakeholders during a consulting gig, I am absolutely not doing the dog-and-pony show of presenting with slides.

(1/12)
I am here to do one thing and one thing only: make an IMPACT.

Leave a firm, lasting impression that they will not ever meet another consultant cares as much about helping them succeed as I do.

Which means I’m here to talk about *them.*

(2/12)
What they need. What they’re struggling with. What they think is wrong and what needs to be made right.

This also means that even if I don't have the gig yet, instead of sitting politely + taking turns, we’re going to dive in together + interact. Trade ideas.

(3/12)
Read 12 tweets
Jan 29, 2021
#UX and #design friends, we need to talk about estimating. I'd like to share some advice that's come up 3 times this week, in hopes it's useful. And it's echoed, by the way, in the BUSINESS OF UX course @EliNatoli and I are teaching at my UX 365 Academy (link at the end).

(1/12)
Avoiding wars with clients is a matter of how you structure your engagements, along with how you spell out what you're doing in your proposals/contracts. That starts with estimating.

The biggest 2 rules I follow are these:

(2/12)
1. I do not EVER estimate a project in full from start-to-finish.

2. Once we're past initial Discovery (see below), I estimate in small chunks, e.g. "here's what will take us to the next iteration/review."

(3/12)
Read 12 tweets
Oct 30, 2020
PSA: Three weeks ago I tested positive for #COVID19. Four days later, while on a video call with my doctor I found myself gasping for breath, my pulse oxygen levels diving, with her yelling at me to CALL 911 NOW.

(1/8)
An ambulance took me to the ER where they scrambled to hook me up to Oxygen and IV tubes and heart monitors. I’m going to tell you straight: I thought I was going to suffocate on that gurney. This is the first time in my life I ever literally thought I was going to die.

(2/8)
I had developed severe inflammation and pneumonia in my lungs in a matter of DAYS. So for 36 hours they pumped me non-stop full of various antibiotics and steroids. When one bag emptied, they hooked up another.

(3/8)
Read 8 tweets
Dec 17, 2019
@rohanpaldesign @mgoldst When a client doesn’t pay, you send a series of letters, each one with a more serious tone: the first assumes oversight, and the last says unless I get a check on X date, we’re going to court.
@rohanpaldesign @mgoldst In all cases you set specific dates for response/check and a consequence: “if I don’t hear from you/receive payment by X date, here’s what will happen next.”

In most states, you can file a claim in small claims court if the $ owed is less than $20K. It’s not hard, just tedious.
@rohanpaldesign @mgoldst If you get in front of a judge, that contract saves you. They’re not interested in details of the case, client scope creep, etc. They’re not going to listen to that clients whining about how they expected A but you delivered B, the subtleties of interpretation.
Read 5 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(