A thread (and story) about managing with different cultural contexts. 👇
Some of you immigrants/minorities will know what I'm talking about when I say that it took me maybe three decades to know how to answer: "What do you want? What do you care about?"
This seems like a staggeringly simple question in American society. But I'd freeze whenever someone asked me that.
And it came up all the time. When meeting new folks in college.
In a job interview.
When asked about my 3-5 year career plans.
If you come from an individualist culture, since you were a toddler people have asked you what you wanted, what makes you happy, etc.
But growing up in China, I was asked to consider: "What is appropriate to this context?" "What's best for this group?" "What does Person X need?"
So in my twenties, when my managers would ask me what my personal goals were, my answers always felt so complicated.
I'd say, "What does the company need from me?"
I'd say, "What can I do to help you?"
And they'd look at me like: "Uhh this is supposed to be about *you*."
But I didn't see myself as just "me!" I saw myself as a unit within the larger group!
As time passed, I've learned to be more individualistic. I admired the ease in which my colleagues knew themselves. And you become what you admire. But neither is better nor worse. It just is.
So. If you manage folks today, and you feel you aren't getting a rich, detailed answer to "What do you want?" or you feel you don't know their unique identity b/c they can't describe themselves, consider whether it might be because they come from a different cultural context.
(I am still discovering this lesson with my parents, btw. :)
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Whenever I hear a product pitch, the thing I most want to know (and that most often gets left out) is: who is this product for?
This seems like a simple question, but there are many ways the answer can be of insufficient depth. Thread 👇
1) Audience of "you"
A common pitch pattern involves walking "you"—the viewer—through a product demo ("you land on the website. You click Login... You go to the dashboard...")
This is great for seeing how the product works, but doesn't tell you at all who the audience is!
"You" are not audience, and the actions "you" take in this demo are what the product creator wants a user to take, not a guarantee of how they will actually use it!
Always ask: "So who are you imagining using your product this way? Why would they?"
Do you ever get called upon to give design or product feedback?
A guide below 👇
Step 1: Recap for the feedback receiver your take on...
a) what problem this project is solving for users
b) who the primary users are
c) what success for the project is
Get aligned on this before giving any feedback, otherwise you might speak past each other.
Step 2: Put yourself in the shoes of someone who is the primary user, and go through the flow step-by-step.
Wear your user hat right now, not your 'company employee' hat, and don't just focus on key screens. Experience the actual end-to-end experience.
Okay, serious question: what net results in greater efficiency for everyone when A asks B for a favor via e-mail.
1) B declines by not responding. 2) B declines through e-mail response with why they are declining. 3) B declines but it's just a simple "no" with no explanation.
I used to think 2 (because I prefer to get a definitive response as A and it's a nice human touch to know why from B). 2 and 3 also saves A from not having to reping if it's actually a favor A cares about.
On the flip side, there are situations where A asks for a favor but wouldn't reping, and getting 2 or 3 can feel worse than not hearing back. And as B it's effort to craft a decline e-mail, especially with a response, and particularly if saying no is hard for them.
Ask people all the time for feedback. Make your asks specific, and your tone curious so it's safe for the other person to tell something critical. People know when you're just fishing for compliments. Examples (thread)
After a presentation you gave: "How well did you think my points landed? What would have made them clearer?"
After an analysis you completed: "How impactful was this to your team? What would have made it more useful?"
How to describe your design work in a portfolio or presentation (thread below)
Describe the problem you set out to solve.
Explain the things that made this problem interesting or challenging—what was the space of options? What were the constraints you were forced to balance?