How to Scale a Team | Original
-
Think about it for the long term. Do you have enough budget? How long can your team survive? What if there is no gain after scaling the team?
-
Be cautious about doing it after getting investment. It is easy to burn money but hard to earn it.
-
Keep a very high standard when hiring. The people you hire should be at least as good as you.
-
Observe people who have energy and a good attitude; age or experience doesn’t matter that much.
-
Fire people quickly if they are not a good fit. A wrong hire costs money and time and forces other good people to deal with the mess that the poor hire leaves.
-
Loyalty is a good thing. However, an exceptional person working for your team for 1 year is better than an average person working for 2 years.
-
Distribute tasks wisely and more evenly. This way, exceptional people can work fast and efficiently.
-
Salary and compensation do matter. After all, we work for freedom. Offer more than the market standard or provide equity.
-
Exceptional people enter the market from time to time. It’s better to plan hires for the next year or two and meet candidates periodically. Hire only when it is a good fit.
-
Approach hiring scientifically. Observe people carefully and measure their output, then adjust. Hire people as you would use libraries of code. Build a great team just as you would build great software.
-
Keep the company with a clean structure and highly efficient. Simplify and simplify. It is easy to become complicated and bureaucratic but hard to be cohesive and simple.
-
Think long-term again and again. For companies, we hire people to build and earn profit, not to do charity.
-
Good people help you achieve your mission, while bad people distract you from it.
-
Don’t try to change others; it is impossible. A person’s mindset or worldview is shaped over their entire life. Instead, ask yourself, “What is my mission, and how can I attract a great team to achieve it?”
-
Having a good attitude is better than current ability.
-
Scaling a team is similar to scaling backend services. Certainly, the number or performance of servers is important. However, the code and system design are at least equally important, if not more. Similarly, while the raw headcount or quality of employees is important, the mission, company structure, and product are at least equally important, if not more.