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.
4/ But in high growth companies, problems never go away.

If every year you have 100 problems in your company. With the product, people, processes... what ever... every single year you will still have 100 problems. EVERY YEAR... 100 problems. They aren't going away.
5/ If problems never go away, you have to measure progress differently. It will require building an entire new mental model for progress.

Throw out burn down charts completely. This sounds simple, but it's the number one reason why most people can't handle hyper growth.
6/ Say hello to the "problem upgrade chart". Burn this into your mind. It will save you.

Yearly progress is when 5-15% of your problems are new. And not that they go away. Remember, you will always have 100 problems.
7/ Why will this save you? Because your entire self-worth is based on a bad mental model. If you can start seeing problem upgrades vs problem disappearing you will learn to see progress.

And progress is the fuel for our work.
8/ The hard part is that you can't log into JIRA and see a problem upgrade chart. So you have to build some ways to see your company with this lens without a tool.

Write down a problem list at the start of the year, things that really piss you off.
9/ Every year review that list and if you can cross out 10-15% of the items, you're killing it! Pop open the champagne, have a progress dance, and be super happy!
10/ Then start sharing this mindset with your colleagues.

There are a lot of people around you who are devout pessimists that will drag you down. It's really hard to stay positive in a sea of burndown zealots.

But keep pushing. You've got this!
11/ It's an absolute honour being in a growing company.

The problem upgrade chart & mindset will make it fun in addition to being an honour.

This has been my secret to not burning out over 26 years in high growth teams/companies.

Happy company building to all!

• • •

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

Keep Current with Jean-Michel Lemieux

Jean-Michel Lemieux 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 @jmwind

1 Dec 20
Congrats to the entrepreneurs who survived and thrived. @ShopifyEng was here for you. A year of BFCM traffic every day with a $5.1B ending.

So much more to build... I’ve decided to double our eng team in 2021 by hiring 2,021 new technical roles. 🙌🏼

shopify.com/careers/2021 1/ Image
We’ve hesitated to grow too quickly, we’ve moved fast and scaled with a relatively small team. @ShopifyEng has definitely been lean and mean. But from web stores to warehouses, banking, logistics, shop, fulfillment network we are ready to double down and scale bigger. 2/
If you’ve read our engineering blog, you know that we are building the planetary commerce platform for entrepreneurs to start and scale their businesses. Our traffic is doubling every year and we’re redefining the primitives of commerce. 3/
Read 6 tweets
30 Nov 19
How about some nerd stats for #BlackFriday2019 with @ShopifyEng?

128,000 Unicorn workers served 90m unique sessions at a steady 17M RPM (requests/min) throughout the day. Over 1b webhooks sent, transformed 280m webp images at the edge and 34b requests to CDNs. 74m Flows ran.
36% of traffic was http/1.1 and 64% http/2

#BlackFriday2019 with @ShopifyEng
28m transactional emails sent

#BlackFriday2019 with @ShopifyEng
Read 6 tweets
1 May 19
1/ So great, thanks @Eli_White for the being open and honest about how hard it is to build a platform. You prioritized dog fooding and taking the raw/hash feedback about performance and addressing was the right move. Here's why i'm bullish on RN...
2/ Companies that are focused on Apps&Products have to do dev gymnastics to ship anything across the matrix of platforms. It's slow and bad for our entire industry.
3/ The ratio of companies that are focused on Apps&Products vs platforms is 25,000,000:2. Apple and Google being the 2. And they don't care enough about our pains in App land and instead favour their platform winning over developers solving problems quickly for the planet.
Read 8 tweets
23 Apr 19
1/ Compared to web, mobile CI/CD has been in the dark ages. Waiting 15+ minutes for builds, testing PRs hard, and complex app-store submission. But the amazing team of @sanderlijbrink @pepibumur @markrcote @Alexrs95 fixed this for @ShopifyEng. Let me share the story...
2/ Like for web apps, each mobile commit has its own dedicated @buildkite build and to speed up CI build artifacts are shared between parallel testing steps. This takes developer machines and gives us fast and reproducible environments. More later on what this enables.
3/ iOS automation can be particularly tricky. Using a cluster of Mac minis in MacStadium and Anka virtualization, we provide disposable macOS environments to build our iOS apps in a fast and reproducible way. Read more in engineering.shopify.com/blogs/engineer…
Read 8 tweets
22 Apr 18
Has anyone put in place a structured training program for software developers and data to support that it helped prevent basic preventable quality issues?
Most other professions where quality issues result in deaths have improved with training and made mandatory.
For example after a lot of deaths in blue water sailing races that were preventable they instituted a ocean survival course.
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

Thank you for your support!

Follow Us on Twitter!

:(