Julie Zhuo Profile picture
13 Jan, 8 tweets, 2 min read
Someone asked me what I felt were the biggest differences between my Facebook role versus starting a new company.

Some (very early!) thoughts 👇
1) The first is, of course, the huge contrast in scale between the companies. I went from back-to-back daily meetings where my "work" was mostly on alignment in my area of expertise (design) to now very few meetings and a lot of tasks--code, design, research, cost projections, et
"Alignment" went from 80% to 5% of my time. We're so small that one weekly team meeting is usually sufficient to make sure we're all on the same page about what's going on.
2) I spend a lot of time on things of the form "Figure out _____" (like, comp philosophy, equity, locations, service for X)
There isn't an in-house expert, so we just have to figure it out ourselves (via asking folks for advice, watching Youtube videos, reading blog posts, etc).

I am seeing firsthand the power and generosity of the SV network in sharing knowledge.
Just when you think you've gotten an initial handle on something, it always blossoms into another 7 layers of complexity. I'm sure I'm doing a vast number of things suboptimally, but everything has tradeoffs, including time spent to do it well.
4) The blue sky feeling is incredible. We're on page three, and there aren't many prior plot knots to untangle yet. We can change chapter three completely at this point. There's sure to be a lot more character building and growth, no matter where the story leads.
What hasn't changed?

1) It's energizing to work with great people.

2) A lot of meetings continue to be recruiting meetings :D

3) Telling the story of who we are and what we want to do is still a big focus (although the story is more external now than internal)

• • •

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

Keep Current with Julie Zhuo

Julie Zhuo 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 @joulee

28 Jan
4 months ago, I woke up one day and decided to start a mentorship circle with a small group of talented, high-potential female designers.

It was the most amazing experience. Here's a thread on what I learned 👇
Some background first—in my own career, I came to the benefits of mentorship late. I really struggled with asking for help. I saw it as a weakness.

This is a fallacy many folks with imposter syndrome believe. We like the idea of "mentorship", but not "exposing vulnerabilities."
To have a mentor truly help you, three things need to be true:

1) You have to know when to ask for help and what specifically you need help with,
2) You have to be willing to honestly share your dreams
3) You have to be willing to honestly share your worries
Read 21 tweets
22 Jan
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?"
Read 7 tweets
4 Jan
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?"
Read 10 tweets
14 Dec 20
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.
Read 11 tweets
20 Oct 20
Formula for a better day:

1) Zoom meetings tend to be more energy draining than reg meetings

+

2) The meeting is online and can be recorded

= Decline meetings you aren't essential for and ask the organizer to record it. Watch it if you need to later.
Often, we attend meetings even if we expect to be silent observers to avoid "missing the context of the conversation" (esp on key decisions)

Usually, reading the notes afterwards is sufficient, but there's still this nagging feeling.

Knowing there is a recording solves that.
Bonuses of watching recorded meetings later:
1) You can watch at 1.5x, 2x speed
2) You can watch it on your own time

Still waiting for automatic video transcription, which would make this even better.
Read 6 tweets
26 May 20
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.
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

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

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!