this post was updated on september 6, 2016 based on changes we’ve made to our approach.
many founders and vcs espouse the mantra hire fast, fire fast. there’s a sense of urgency to fill every open position, because every day a position is open is a day that work isn’t getting done. and if you make a hiring mistake, well, you can always fire that employee and try again with someone else. sounds like good business, right?
but there’s a problem: employees are people, not resources. they are people with lives, obligations, and financial needs. yes, you should focus on doing what’s best for your company, but you should also treat people with the respect they deserve.
an all-too-common anecdote (based on a real story)
saasco, a bay area startup, just raised a $7m round of funding and is hiring fast. they found aaron, who lives in cleveland, oh, and who had been searching for software engineering jobs in the bay area. saasco interviewed aaron giving him a coding test and technical design question. they even flew him out so he could meet the team over lunch. all went well. aaron got the job and relocated with his wife and kids (relocation expenses paid). the change was disruptive and expensive (due to the high cost of living) for his family , but he had a high-paying job at well-funded startup, and he and his family would adjust.
six weeks into the role, the founder calls aaron into his office and fires him. aaron wasn’t delivering results. he was used to a slower pace with more structure, but saasco was a bit chaotic. employees needed to make progress without being guided; the company needed to hit their metrics to raise their next round of funding. aaron was struggling with the ambiguity and others were getting frustrated. the company paid aaron a week of severance, and the founder knew he made the right business decision to let aaron go.
was the company right in letting aaron go? probably. could they have handled the situation better? definitely. these types of occurrences happen all too often. this “churn and burn” culture is not something i (or magoosh) want to be part of. so how do we approach it?
hire slow
slow doesn’t mean what you might think it means. when hiring, you should move candidates through the process as quickly as possible. and when you find someone who’s a good fit, you should move quickly and make an offer.
hiring slow means that you should be thorough. don’t make the hiring decision based on a snap judgement. create a structured process that tests for job and culture fit and fights against your biases. google’s senior vice president of people operations has written quite a bit on the topic.
a thorough process is fairer to potential employees. you’re doing the hard work of assessing fit up front, so that hopefully you won’t need to let them go. we’ve iterated on our process many times, and we’ll continue to do so. you can read more about our hiring process in detail here.
fire fast, but humanely
occasionally, you’ll need to let people go to protect your company and your other employees. after all, one person who’s not a fit can negatively affect everyone else. however, you can let people go and treat them with respect. here’s how:
1. share your stance on firing with employees before they join.
when new employees join companies, they often assume they have some level of job protection, maybe for a year—it’s an implicit understanding especially for those who have not worked in a fast-paced startup culture. but if you believe in firing fast, then you should explicitly let the new hire know about your approach. even better, let them know what percent of people have been let go in the first 3 months. let them opt into the risk of joining your company. don’t rely on the employee’s understanding of at-will employment. don’t lie by omission to get them to join.
2. communicate expectations clearly and regularly
after you hire someone, spend time crafting a 3-month plan with them. share what you expect them to accomplish and how you will measure their performance. if you don’t know all the specifics, then share your general expectations about performance and values. have weekly one-on-ones (and daily check-ins in the first week or two) to share feedback and to give them time to ask questions. your job is to help the new employee be successful, so early feedback is critical.
at magoosh, we’re now better at this then we used to be, but we still have a lot of room for improvement. (i’m sure many magooshers reading this didn’t have a clearly laid out 3-month plan when they joined—sorry!) we now try to do the following:
- provide specific culture and competency feedback during weekly 1-on-1’s.
- regularly (every 2 weeks or so) communicate how well the new employees are doing in their role.
- solicit feedback from new employees about their experience at magoosh and what we can do to help them succeed.
3. offer a reasonable and well-defined severance.
for any number of reasons, things may not work out. but remember, when you fire someone, it’s your fault. if you had a better hiring process, you could have identified that this person wasn’t well-suited for the role or the company. now the employee has to find another job, which takes time. we took inspiration from rand fishkin of moz and offer one month of severance (assuming there were no egregious behavior issues). think of severance as a “hiring penalty”: you pay it because you didn’t invest enough time in the hiring process, and it’s your incentive to make the hiring process better.
here’s a link to a google doc we share with candidates during the hiring process which outlines how we approach the first few months, the intro period:
in the fast-paced startup culture — where every day matters — it’s easy for founders to hire and fire quickly. however, step back and evaluate the consequences of those actions. the people you hire are not disposable resources. sometimes a relationship between an employee and a company doesn’t work out, and that’s ok. let them go, but do so humanely and then improve your hiring process for the next hire.
read more by bhavin:
why we don’t negotiate salary and neither should you
how being named the happiest company made me less happy
leave a reply