Another common question I’m answering working with scaling tech companies is…
Q. What’s the worst leadership advice you’ve heard?
A. By far the worst is “Hire great people and get out of their way”.
Let me explain… 🧵 (1/32)
2/ After a year leading engineering at Atlassian @scottfarkas told me in my perf review that I was doing ok but wondered why I didn’t talk and involve him more regularly.
3/ My answer was “I thought that was my job — to take away all this crap from you and let you do your CEO thing. I thought you wanted me to be autonomous. I need autonomy.”
He said sure, but you should cheat “and use my brain to help you”
4/ At that point I changed some habits, involved him more in different ways, got over the autonomy complex, and we got a lot more done together. I learned a lot and we made better decisions.
5/ Since then I've hired many leaders and had to repeat the same conversation that @scottfarkas had with me over and over and over.
Most people default to expect the wrong version of autonomy.
6/ These experiences sent me down a multi-year reflection.
Why did I feel like success was maximizing autonomy and showing that I could take care of things without bugging my boss?
7/ I prioritized autonomy over alignment.
It's a million times easier to measure and feel high autonomy than it is to measure high alignment.
8/ What I've learned since, way too slowly, is that companies are performing a monumental balancing act trying to decide what 98% of their problem space to focus, what to ignore, and how to ship.
That’s your strategy. And it’s complex, ambiguous, and changing.
9/ The hardest part of building a company is alignment on strategy and clearly communicating it.
Think about it this way, a 1 degree deviation in course of a rocket heading to the sun means it will miss the sun by 1.2 million miles.
A lack of alignment compounds quickly.
10/ Every leader in the company is trying to keep on course using the strategy as a compass… and readjusting as new information comes in.
11/ You're never confronted with problems that are independent of each other. Your problems are part of a complex systems & interact with each other.
Situational messes.
Much of the alignment process is understanding the mess with others. And then simplifying it and focusing.
12/ Alignment the difference between progress and stagnation.
You need a good level of alignment on everything, from culture and architecture to which customers to build for which to not build for.
13/ And here's the hard part...the second you leave an alignment meeting, you’re mis-aligned again. That’s fine, it’s normal.
Alignment decays incredibly quickly.
14/ There's mass confusion on what to align on?
Most people just want to know the very high level goals.
And this causes most companies that I work with to align superficially. Their strategy is a superficial incomplete map, they don't remove scope, communicate clearly, etc...
15/ Here’s an example. If you want to sail a boat across the Atlantic, what is your strategy?
Strategy 1: Leave from Portugal and head towards St Lucie and not die. And have fun!
But that’s not a strategy...
16/ Strategy 2: when do we leave and why? What kind of boat and why? What systems do you have & backups, how many crew, sail selection, route planning options?
Strategy is multi-faceted and evolving.
You can discuss this strategy in depth, but not do the trip together.
17/ The biggest alignment problem is the gap between how much people think they have to align versus what they should align on.
There are many strategic decisions in the "how". eg, what technologies to use, new system vs integration, build in core or in an app.
18/ Alignment forces you to talk with your boss and peers to:
- define a strategy, narrow focus
- communicate it clearly together
- and ensure you're hired enough people who "get it" and can fill in the implementation details with their teams
19/ So...when you hire someone or you have a new leader, your number one job is alignment. And you do this continuously.
It’s definitely never going to be “hire them and get out of their way”.
20/ There is so much research on pair programming, yet we don’t have the same cultural acceptance of pairing in leadership.
21/ But why are we in this predicament of worshipping autonomy more than alignment?
22/ I know what you're thinking. Isn't this micro-managing?
It isn't.
@scottfarkas and @tobi let me run the team and implement our strategy fully.
But together we frequently dug into the “how” to understand and navigate the nuances of our strategy together and often.
23/ Tech companies worship autonomy to distance themselves from any inkling of command-and-control.
If you get labelled as micro-managing you're burnt at the stake.
But the nuances or organizational problem solving has been lost.
Without alignment, autonomy is squandered.
24/ Even after all this, I messed up again in 2015 when starting at Shopify. @tobi gave me the same feedback again… I’m a slow learner.
At that point I told myself... You HAVE to take responsibility for alignment. It’s YOUR job, as much as your bosses.
25/ I've became very upfront about alignment with new hires. Gist of our first conversation is:
"We're going to spend more time pairing and going deep on strategy and decisions than you're used to... we have a lot to learn from each other...but you'll own the implementation."
26/ ...and then I'll share these 3 alignment tips with them that we can use together:
✅ Role allocation model
✅ Decision tree model
✅ Alignment habits
27/ First tip, be clear and open about the types of conversations you need with your direct reports:
25% of my time your boss,
50% your peer,
25% I work for you
This encourages collaboration and sets the tone of alignment and a strong habit of working together.
28/ Second tip: Susan Scott, author of “Fierce Conversations,” offers a wonderful alignment model: the Decision Tree.
29/ The decision tree is great as it's a reminder that you don't have to align on everything.
Decisions have different costs to unwind. Spend time alignment based on the impact of the decisions.
30/ Third tip: take FULL responsibility for alignment with your boss and peers.
Send your boss at minimum 2 async notes a week. Decisions, wins, lessons, how you’re doing. Schedule it in your calendar.
Seek feedback, but share decision logic not just outcomes.
31/ Feel responsible, take ownership of alignment. Don’t blame the process. It takes active work to build and maintain. You'll make better decisions.
32/ Netflix's slogan of "highly aligned, loosely coupled" was spot on.
But it's a lot harder to implement than you think.
Without alignment, autonomy is squandered.
So hire great people, and expect highly coupled frequent alignment with loosely coupled implementation.
/end
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Our mistake in tech was allowing lawnmower-managers to take over. It’s caused manager bloat, layers, and 1:1 overload. Let’s undo? 🧵
2/ It’s not uncommon to see 5 layers of « servant leaders » before you find someone actually building your product or who’s immersed in the problem space.
3/ So what happened? We stopped treating people as adults. We moved responsibility for careers, progress, human decisions mostly away from the individual. And created an entire career track of facilitators, aka lawnmowers.
Following the advice in this slide will kill your company. 🧵
This advice is spread all over the internet. Two groups of people (product and engineering) want a nice clean API about who does what.
But it's like being in a marriage and thinking that you'll each clean your side of the bedroom only and then cook half of each meal.
The danger in this model is that at the surface it looks great. It's clean. And it's been told for years. So it will lure you into a false sense of comfort... for years. But it will eat away at you from the inside out.
2/ If what you're looking for is inside information on $SHOP you just had to ask. Here's what I know that hasn't made the press or an analyst report yet.
3/ I'm an engineer, so will avoid any market crystal ball madness.
Call it Retail DTC or Run DMC... pick any buzzword you want but people have been buying stuff since before the silk road. That ain't stopping.
Another common question I’m answering working with scaling tech companies is…
Q. What virus infects growing engineering orgs the most?
A. Layerinitis. Let me explain... 🧵 (1/27)
2/ As your eng org grows you have to organize into teams. Companies start with shared ownership of the code base and small project teams that form and disband. It's a good model, but past 50+ engineers that falls apart...
3/ In 2015 at Shopify there was a busy file called api_client.rb. I spoke to the last 20 committers. Everyone was adding new attributes, but when asked why the answer was "I was just following what the previous committer did" an "had a deadline".
Another common question I’m answering working with scaling tech companies is…
Q. How much of your r&d spend should be focused on platform work?
A. 50%, and most teams are way off what it should be. Let me explain…🧵 (1/21)
2/ This question is a proxy question for many underlying issues…
✳️ Lack of trust in the engineering team
✳️ Lack of understand of your strategy
✳️ Lack of long term thinking and culture
✳️ Lack of understanding of compounding technology investments
3/ This comes up is often in panic situations, “the engineering team says that there’s too much technical debt and can’t work on features”… but the problems started way before.
This is the most common question I'm answering in recent fireside chats...
Q. How do you handle/manage the stress of working in a hyper-growth company where there's always too much to do?"
A. It's a mindset change: problems upgrade but don't go away. Let me explain... 🧵
2/ The reason this problem mindset is hard to develop is our human bias that gets in the way...
From childhood we are trained to see work equate with problems diminishing over time. You finish your assignment, and it's done. You complete your courses, you finish a sports game.
3/ The Agile development process is the worst for this as the coveted "burn down" chart is what you use to see if you're doing a good job as a team.
You equate progress with "less story points". You measure your self-worth with problems going away.