"Some people are simplifiers. You're a complexifier."
This was a piece of feedback I received once from a colleague.
Yeah, it burned.
It felt like a shitty thing to say.
Thread 👇(1/11)
Why did I think that? Let's break down the ways:
1) Immediately I'm cast as different, part of the "other" group
2) Saying I'm a "complexifier" makes it sound like this sucky label is my permanent identity.
3) Geez this statement is broad. How about some examples?
(2/11)
I can't say why my colleague gave me feedback this way.
Were they trying to sound insightful? Smart? Superior?
Maybe they thought this kind of delivery would have the biggest impact?
Maybe they wanted to see me squirm?
(3/11)
Would it have been so hard for them to say it differently?
"Hey Julie, when you presented XYZ the other day, I found it hard to follow. It'd be great to know the summary of your point right at the beginning."
"Thank you!" I would have said. "That's really helpful!"
(4/11)
Or:
"I couldn't wrap my head around your explanation of ABC; there were too many details and I got lost trying to figure out what you thought I should take away."
(5/11)
Or simply:
"I've noticed when you explain things like XYZ and ABC, you have a tendency to include complex details when I'm just looking for a three-sentence summary."
(6/11)
At the time I heard this, I felt justifiably defensive.
I activated my armor and let the words bounce right off of me.
I thought *their feedback* was the problem.
It's a shame I did.
(7/11)
It took me years to see that my colleague had a point.
I *did* tend to over-provide context.
My points weren't succinct.
My thinking was sometimes muddled.
There's a kernel of truth in every feedback.
I could have asked for clarification and learned this sooner.
(8/11)
So what's the lesson here?
If you're the feedback giver: aim for your words to be helpful and actionable.
* Let them know you care about them (don't give the feedback if this isn't true)
* Give examples of their behavior and its impact
* Suggest things to try
(9/11)
If you're the feedback receiver: try your best to see all feedback as a gift, a mirror to reflect back and sharpen your self-awareness.
Unless they are trolling, don't let the delivery of the feedback impede your ability to hear the message.
(10/11)
You can't control someone's feedback, and how or what is said, but you can control whether you receive it graciously and whether you allow it to help you improve.
Not sprawling networks of people (though technically that's right)
Rather, thinking about a company as an individual makes many things easier to understand.
Pick the company to join like you'd pick who you'd want to hang out with every day.
Thread👇
Companies have personalities, just like people do. Some companies are flashy and dramatic. Others are staid and quiet. Some live in the future, constantly tossing out new inventions. Others are ruthlessly competitive.
(2/13)
Like with people, all strengths have shadow downsides. Apple's quality and cool comes from a secretive, top-down culture.
Zoom's focus on superior tech leaves it lacking when it comes to product features.
One of the stories we used to tell in the early days of Facebook was how a small, two-engineer project came to dominate the entire photo sharing landscape in the late 2000s.
Thread 👇 1/10
Let's zoom back to 2005, when pre-mobile Internet photo sharing services were one upping each other on storage, features, and slickness.
Across Photobucket, Shutterfly, Flickr and Picasa, there were high-res uploads, preview navigation, theme tags, search by color, + more
2/10
Facebook Photos, built by a scant team over two months, was extremely bare-bones in comparison. It only supported low-res photos. No comments. No likes. It didn't even have a nice full-screen view.
1) I loved the people 2) I was continuously challenged and learning 3) The mission spoke to me 4) I felt deep loyalty
But there was another big reason that was hard for me to admit then...
(1/10)
The hard-to-admit reason was this: my sense of identity was deeply tied to my job.
I felt I *belonged* there.
I had a great career there.
I'd made many wonderful friends there.
And so, it was terrifying to imagine: who would I be if I *didn't* work there?
(2/10)
"My identity = My job" is a common thought pattern for folks (more likely founders or young) who...
1) have invested tons of time/capital/energy into the job 2) are ambitious 3) are recognized for their job 4) have mostly work friends 5) believe deeply in job's mission
I've participated in too many conversations about the role of design / pm / eng to count.
Of course there are differences.
But every tech manager role, regardless of discipline, ends up converging at higher levels.
What does this mean for you as a manager?
Thread below 👇
If you climb the management ladder to the very top, guess what? You’re the CEO. And you manage *every* function.
So if your goal is to be CEO someday, or even VP or director within your discipline, you need to get out of your box and learn how other disciplines work.
(2/9)
The most thoughtful designs don’t get used if engineering doesn't build them.
The most sophisticated algorithms don’t help people if they can't be put into a clear product.
The tightest roadmap doesn’t get you customers if the experience isn’t good, or you can't sell it.
Your launch date is in a week. Your whole team's credibility is riding on your collective ability to make it happen. Leadership is Eye-of-Sauron-ing this project.
There's just one problem.
You suspect the product sucks.
What do you do? A thread 👇 (1/9)
Prior to a launch, saying "Our product sucks" is not what your tired, overworked colleagues want to hear. But if you feel this way, you need to bring it up.
Align the team around the launch goals. Ask: "What are we aiming for?" Then frame your concern around that.
Ex... (2/9)
"We want to fail fast and get learnings asap" → Are we well set up to get new learnings if we already know so much is broken?
"We want to make a big splash and get tons of new users" → Will these new users retain if our product is buggy?