{"id":3061,"date":"2015-08-26t20:19:05","date_gmt":"2015-08-26t20:19:05","guid":{"rendered":"\/\/www.catharsisit.com\/?p=3061"},"modified":"2015-08-26t20:19:05","modified_gmt":"2015-08-26t20:19:05","slug":"hire-slow-fire-fast-humanely","status":"publish","type":"post","link":"\/\/www.catharsisit.com\/blog\/hire-slow-fire-fast-humanely\/","title":{"rendered":"hire slow, fire fast (but do it humanely)"},"content":{"rendered":"
this post was updated on september 6, 2016 based on changes we’ve made to our approach.<\/em><\/p>\n many founders and vcs espouse the mantra <\/span>hire fast, fire fast<\/span><\/a>. there\u2019s a sense of urgency to fill every open position, because every day a position is open is a day that work isn\u2019t 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?<\/span><\/p>\n but there\u2019s a problem: employees are people, not resources.<\/strong> they are people with lives, obligations, and financial needs. yes, you should focus on doing what\u2019s best for your company, but you should also treat people with the respect they deserve.<\/p>\n saasco, a bay area startup, \u00a0just 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.<\/span><\/i><\/p>\n six weeks into the role, the founder calls aaron into his office and fires him. aaron wasn\u2019t 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. <\/span><\/i><\/p>\n 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 \u201cchurn and burn\u201d culture is not something i (or magoosh) want to be part of. so how do we approach it?<\/span><\/p>\n slow doesn\u2019t mean what you might think it means. \u00a0when hiring, you should move candidates through the process as quickly as possible. and when you find someone who\u2019s a good fit, you should move quickly and make an offer.<\/span><\/p>\n hiring slow means that you should be thorough. don\u2019t make the hiring decision based on a snap judgement. create a structured process<\/a> that tests for job and culture fit and fights against your biases. google\u2019s senior vice president of people operations <\/span>has written quite a bit on the topic<\/span><\/a>.<\/span><\/p>\n a thorough process is fairer to potential employees. you\u2019re doing the hard work of assessing fit up front, so that hopefully you won\u2019t need to let them go. we\u2019ve iterated on our process many times, and we\u2019ll continue to do so. you can read more about our hiring process in detail <\/span>here<\/span><\/a>.<\/span><\/p>\n occasionally, you\u2019ll need to let people go to protect your company and your other employees. after all, one person who\u2019s not a fit can negatively affect everyone else. however, you can let people go and<\/i> treat them with respect. here\u2019s how:<\/p>\n <\/p>\n when new employees join companies, they often assume they have some level of job protection, maybe for a year\u2014it\u2019s 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\u2019t rely on the employee\u2019s understanding of <\/span>at-will employment<\/span><\/a>. don\u2019t lie by omission to get them to join. <\/span><\/p>\n 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\u2019t 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. <\/span> for any number of reasons, things may not work out. <\/span>but remember, when you fire someone, it\u2019s your fault.<\/b>\u00a0if you had a better hiring process, you could have identified that this person wasn\u2019t well-suited for the role or the company. now the employee has to find another job, which takes time. we took <\/span>inspiration from rand fishkin of moz<\/span><\/a> and offer one month of severance (assuming there were no egregious behavior issues). think of severance as a \u201chiring penalty\u201d: \u00a0you pay it because you didn\u2019t invest enough time in the hiring process, and it\u2019s your incentive to make the hiring process better.<\/span><\/p>\n here\u2019s a link<\/a> to a google doc we share with candidates during the hiring process which outlines how we approach the first few months, the intro period<\/em>:<\/p>\n <\/p>\n <\/p>\n in the fast-paced startup culture \u2014 where every day matters \u2014 it\u2019s 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\u2019t work out, and that\u2019s ok. let them go, but do so humanely and then improve your hiring process for the next hire.<\/p>\n <\/p>\n read more by bhavin:<\/p>\n why we don’t negotiate salary and neither should you<\/a><\/p>\nan all-too-common anecdote (based on a real story)<\/b><\/h2>\n
hire slow<\/b><\/h2>\n
<\/h2>\n
fire fast, but humanely<\/b><\/h2>\n
1. share your stance on firing with employees before they join. <\/b>
\n<\/span><\/h5>\n2. communicate expectations clearly and regularly<\/b><\/h5>\n
\n<\/span>
\n<\/span>at magoosh, we\u2019re now better at this then we used to be, but we still have a lot of room for improvement. (i\u2019m sure many magooshers reading this didn\u2019t have a clearly laid out 3-month plan when they joined\u2014sorry!) we now try to do the following: <\/span><\/p>\n\n
3. offer a reasonable and well-defined severance.\u00a0<\/b><\/h5>\n