A lot of my work is talking to UX folks about their next job.

Many struggle with "deciding what I want from my next employer."

I've come up with a way to get them past this and to start thinking about where to look first for opportunities.

1/
Thinking about their next job inevitably leads many folks down the path of "what would I like in a place to work."

This gets into lots of touchy-feely attributes about the work environment, but what's almost always missing is what they'll actually do when they get there.

2/
Don't get me wrong: there's a lot to be said about working in a high-quality work environment.

However, that environment isn't going to hire someone out of charity.

The org is hiring someone to get a job done.

That's where the job hunt needs to start. What will you do?

3/
One exercise I've come up with is to imagine you're in an interview with a hiring manager. Imagine that manager is telling you exactly what they need most in their new hire.

They're telling you, point by point, what they need done. As you're listening, you're thinking…

4/
…'OMG! This work is what my entire life has prepared me for. This is THE job I could do incredibly well, because my experiences have trained me to rock this!'

What is that job that hiring manager is describing?
What is it about that job that makes you the perfect new hire?

5/
Jot down every point that you're imagining that hiring manager said.

For each point, write down what you've done in the past that makes you the perfect person to do that thing.

This exercise has helped folks home in what their true strengths are and where to look next.

6/
A hiring manager has a job to fill. They have things they need to get done.

What makes you the perfect person to do those things? That's what you need to identify first.

Your résumé and portfolio should tell the story of those what makes you perfect.

7/
Here's another exercise that expands on the first:

Look through what you've done so far in your work experience.

What things have you done that would be truly valuable to a hiring manager?

8/
This exercise has 3 steps:
1. List the things from your experience that would make you highly valuable to a future employer.
2. Sort the list from the things you like to do most to the things you least enjoy.

This will tell you how to talk about what you want.

9/
3. For each of the top things (valuable & enjoyable), describe how you learned to do those things well.

This step is particularly crucial for early-career folks. Hiring managers are not just hiring for you to do the work. They're hiring for you to grow into the work.

10/
How you learn is as important, if not more important, than what you can do today.

We all need to learn to do any new job, even if it's similar to work we've done before.

We need to talk about how we learn in the interview process.

11/
Talking about how we learn, when we're talking with prospective hiring managers, gives us an advantage. If the manager can see how quickly we'll pick up their specific work requirements, they can see us in the job.

That's essential for them to get to an offer.

12/
I wrote about the importance of emphasizing how we've learned to do the things we've done.

uxdesign.cc/early-career-u…

13/
These two exercises (imagining a perfect job & identifying what's most your most valuable and enjoyable contributions) are great ways to learn what your next opportunity wants to be.

The folks who do these find great clarity on how to talk to recruiters and hiring managers.

14/

• • •

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

Keep Current with Jared Spool

Jared Spool 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 @jmspool

15 Dec 21
I see the same mistake repeated across many of the UX job ads I review.

The job ad describes the JOB, yet highly-qualified candidates want to learn about the WORK.

These are very different things.

1/
What we hear from candidates:

Tell me what I'll be working on.
Tell me how my work will have an important impact on people.
Tell me what makes the work challenging, especially for someone at my experience level.
Tell me what makes this work unique.

This is the WORK.

2/
UX job ads rarely talk about those things. Or maybe they give 1-2 sentences about it.

Here's one example I just found. They give 1 sentence to what the company does. The rest of the paragraph could be describing any company on the planet.

3/
Read 14 tweets
30 Nov 21
I pine for the day when UX research is no longer sold as a way to “validate” the designs of products or services.

This thinking limits what teams deliver.

Going down this path just to get a foot in the door creates so much extra work later on to break away from it.
Put another way:

If “validation” is the first time any team members are getting direct exposure to users and their problems, you’re doing it wrong.
I spend most of my time these days helping extremely frustrated UX leaders try desperately to push past the “research=validation” boundary with their leadership.

It’s really a dangerous mindset to let grow.

There are better ways to position research. We’re much smarter now.
Read 5 tweets
22 Nov 21
NPS, UMUX-lite, SUS, CSat, CES…

These are just tools for producing a number that will send your team off optimizing the wrong things.

Best thing you can do is just ignore them.

(If there’s a follow-on ‘verbatim’ question, spend your time there. That could be useful.)
The problem with ‘satisfaction’ is it’s a meaningless term.

Are you satisfied with this conversation?

If you gave me a 7, how is that different than if you gave me a 6? Or a 3?

Everyone brings a different meaning of satisfaction to the survey. We don’t know their context.
When every respondent brings their own meaning and context to a question, you can’t aggregate the answers. You’re aggregating apples, oranges, watermelons, and bees. What’s the average of all that mean?

Satisfaction measures are literally garbage measures.
Read 6 tweets
25 Sep 21
It makes me smile when a product manager tells me they need a full time researcher before they can do any research.

I look them in the eyes and say “you’re a full time user researcher.”

All PMs are user researchers.
Maybe not a good one.
However, they can become a better one.
User research is what PMs do.

They identify what users and customers need. Why the product doesn’t do that yet. What needs to change to make the user’s life better.

It’s the most important part of their job.
The great user research a PM has, the better their product will be. We’ve got 40 years of product management history to prove this.

It’s too bad the PM literature ignores this fact that user research is critical to great PM work.

It would make their jobs so much easier.
Read 7 tweets
19 Sep 21
Current status Image
Frog on a log Image
Status Update: Image
Read 4 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

Too expensive? 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!

:(