Firing People

I hate firing people. It’s the worst part of my job. Even after all these years I still spend days or even weeks agonizing over a decision to let someone go. I feel absurd complaining about this, given that of course it’s a hundred times worse for the person being fired than it is for me. Still, I hate firing people.

My first firing at Top Hat was our VP Sales. He was employee number two, he joined right after we raised our angel round. In retrospect it was doomed from the start, and it was entirely my fault. I had no idea what I was doing when it came to building a sales organization and brought him into a role that didn’t make sense (read about the lessons learned in building a sales team). It took me 6 months before I finally pulled the trigger. In the end, it was undoubtedly the right decision and set the company back on track. But at the time it was an extremely tough call. It was admitting failure – to myself and to our investors – that this first major hire was a mistake. I felt  ashamed about it for months and kept convincing and re-convincing myself that we could still make it work.

As a general rule once you’ve lost faith in an employee, things rarely get better. You can sometimes fix a skill-level problem by giving someone time to grow, but you can never fix a personality problem. If you’ve identified that someone isn’t a fit you need to move on it quickly and decisively. The longer you wait the worse it will be for both parties.

Firing is an essential part of running a successful company.

In a narrow way, it’s actually more important than hiring. You could, in theory, use a shit-against-the-wall style hiring strategy and as long as you filter out the bad apples quickly enough you’ll be able to build up a functional team over time. Of course that’s probably not the best approach.

The reality is that even the most effective interviewers are rarely more than 70% or 80% accurate. The average interviewer is quite a bit worse than that and isn’t much better than chance – often even worse, because the naive approach just selects people who are great in interviews, which disproportionately selects for bullshitters. However, even if you’re some kind of super-human talent screening machine with a 95% success rate, that 5% will accumulate and degrade the culture until you’re surrounded by bozos.

The Best Firing Process is a Better Hiring Process

Of course the best “firing process” is not to have to fire people, which can only be done through effective hiring. That being said, not having an effective firing process is like not having an immune system – the first cold will eventually kill you.

It’s fairly common knowledge these days that A players only like to work with other A players. A slightly more subtle observation is that someone’s status as an A player isn’t fixed. Bringing a weak player onto a team has a tendency to poison the culture and downgrade the rest of the team (especially if that weak player has a shitty attitude.) This bad apple syndrome has been observed to happen fairly reliably in studies on organizational dynamics.

CC-BY_SA-20  Some rights reserved by MrB-MMX
AttributionShare Alike Some rights reserved by MrB-MMX

The Bad Apple Syndrome

We’ve experience this at Top Hat a couple of times. One of the most instructive was with our inside sales team. Early on when we were in a pinch to fill the team we lowered our standards and brought on a few people that we should have passed on. The results were disastrous. The quality of the team degraded and eventually hurt not only the inside team but also other parts of the company that came into contact with it. It took nearly a year of solid effort to rebuild the team. For a time it seemed hopeless. No matter what changes we put in place, no matter how much talent we threw at the team, the cancer of negativity and poor morale just wouldn’t go away. The most profound mistake we made in the process of trying to fix the team was to keep those who were performing well but had a negative attitude.

There was a pattern we observed a few times: we’d put a new person into the team, their performance would be great and they’d be super enthusiastic. Then like clockwork after a week or two their numbers would slowly drop, and they’d become engrossed in the culture of negativity and gossip. It was only after the cleared out the ringleaders who were perpetuating the negativity (who happened to have decent performance numbers!) and put in strong positive management that things finally began to change. The most amazing thing is that many of the people who were B or even C players when the team was dominated by negativity shot up to solid A player status. The overall output of the team per person went up by nearly 300%. In addition it seems as though life was trying to setup a lab experiment for us to prove just how much things had improved – we had a person who had left the company a few months prior re-join the team. His feedback was that he was blow away, he couldn’t believe it was the same team.

Lessons Learned

The first lesson we learned was that no matter how strapped for manpower you are, no matter how much it seems like the world will end if you don’t fill a position, compromising on the quality of talent will surely be more damaging. Second, we learned that in fixing a damaged team the key is to identify the cultural sources of the underlying problem and focus on those. Finally, we learned to use a divide and conquer approach – we would pull all the top talent into a separate team while rehabilitating the broken remaining team separately – it really helped prevent the “negativity cancer” from spreading while we were fixing things. These are simple things in retrospect, but it took a while to pull it off.

One of the most revealing questions I tend to ask when interviewing potential managers is whether they’ve ever had to make the decision to fire someone. The answer and subsequent discussion usually tells you two things: first, it tells you if the person has ever had to deal with the most difficult problems in management, second it tells you if they know how to handle those problems through the process they followed. Assuming the person has ever had to hire and manage a team of a decent size for any length of time, it’s almost certain they’ve made hiring mistakes, and their answer tells you that they know how to detect and correct these mistakes. If the person simply walked into a mature team, or has had HR handle all the hiring/firing decisions for them, then they’ve been living on easy street.

The process of firing someone is always somewhat unique to each situation. That being said there are some basic principles that you should always follow:

  1. Give people plenty of notice and regular feedback. Give people several chances to improve. The actual firing should never be a surprise – if it is then you almost certainly did something wrong in setting expectations. Depending on the role the whole process should take 1-2 months (longer for senior roles.)
  2. Try to be generous with severance and leave the person in a good spot to find their next employment. I know it’s not always possible in a startup, but do what you can. It’s the decent thing to do.
  3. Take time to reassure the rest of the team and explain (with discretion) the process that was followed and why the decision was made. Letting someone go is always a huge morale hit (even if the person wasn’t well liked, it still scares people.) You need to make people understand that their job is not in danger.

Firing someone is always a brutal experience. Anyone who says otherwise is either lying or is a psychopath. That being said, it’s unfortunately a necessary evil and understanding when and why it needs to be done is essential to the success of any business.

Hiring a Growth Hacker on StartupNorth.ca

CC-BY-20  Some rights reserved by Eva Blue
Attribution Some rights reserved by Eva Blue

Did you know that we run a job board for startups? It does allow companies to reach an audience that is interested in startups.

“Amar joined us 3 weeks ago after a long trial of hunting down and applying for the “Growth Hacker” position we posted on StartupNorth. We couldn’t be happier with his progress, hunger and efficiency. Over to you Amar!” – Michael Litt, Vidyard

There are great stories of people find companies and roles like Amar Chahal (LinkedIn) and the Growth Hacker role at Vidyard. If your a looking for a new gig, go read about how Amar was hired at Vidyard. It will blow your mind how much he committed to the process. I’m actually shocked that no one has socially hacked our job board as a candidate, i.e., it’s not that expensive but you could pay to highlight your resume or portfolio, because it will only work once.

Post Your Job

Postings are only $25 for 60 days. Postings are embedded on StartupNorth.ca and all postings are shared on our Twitter account. For example:

It’s a quick, relatively inexpensive way to post jobs to a targeted audience. Get a little bit of distribution and hopefully find candidates like Amar.

We are open to discussion about how we can improve the Jobs Board for both candidates and companies. Got a suggestion for how we improve things? We are all ears.

Looking to get hired by a startup? 10 ways to stand out

Editor’s Note: This is a guest post by Bruce Dorland (LinkedIn, @brucedorland). Bruce is the Managing Director & Recruiter at Grossman Dorland Recruiting. gdR recruits for permanent and contract positions at all levels, from roles for talented young professionals to accomplished executives. Prior to founding gdR, Bruce spent time at Brightspark, Tucows shipping products that have been used by over 3MM users.

CC-BY-NC-ND-20  Some rights reserved by Candid-Moments
AttributionNoncommercialNo Derivative Works Some rights reserved by Candid-Moments

Occasionally I interview a developer that really impresses me with their ability to make their profile come to life beyond their resume.

Want to know what makes these developers stand out? Here are my top ten tips for making a big impression. Many of these tips work for both a resume and, once that stellar resume gets you in the door, a job interview.

I think developers looking for a new job can have it tough. Many, if not most, job descriptions aren’t great at describing the actual nature of the role. Traditional resume formats can be flat. Interviewers don’t always ask effective questions, and HR departments that rely heavily on keyword matching can’t differentiate you qualitatively from other candidates.

The result: unless you do something different, the odds of standing out are stacked against you. But if you’re trying to get into a startup or midsize tech company that is truly looking to build a top-notch team, it’s essential that you learn to make your mark. Here’s how:

Tip #1: Show me your side projects

Small and midsize companies increasingly value a well-rounded candidate with a passion for technology and a dedication to growing their technical skillset. For confidentially reasons it can be hard to show people the code you’ve been working on at your job, but side projects are a great way to show how you design and implement code. In my opinion, side projects are also a surefire sign of your passion for the craft.

A great tool for this is a code sharing and publishing platform like GitHub. The site gives you a place to contribute to open source projects and build a public reputation for your work since the community is quite transparent. For instance, if a patch you submit is accepted, you get credit for it and it shows up in your profile. The site acts like a resume that helps the maintainer of a project determine your reputation.

Tip #2: Have a relevant and up-to-date portfolio site

While it’s common for certain types of developers to have a portfolio site, UI developers in particular, I’ve found that many create a site early on in their career but don’t keep it up to date.

Most employers who refer to your portfolio site won’t necessarily have the time or patience to fill in any blanks or realize is something is out of date. It’s up to you to make sure that your site accurately reflects where your skill level is today, that sites that aren’t live anymore are removed, that screenshots are illustrative and relevant, and that you give the context of why your work was original or important at that time.

Tip #3: Form your own opinions on technology

What are the topics of the day within your company? What technologies have they chosen to use and why? Form an opinion about your current company’s choices of tools and have an opinion about where things might be going in the future (of course, you’ll want to make sure you’re observing confidentiality requirements if you intend to share this information in an interview).

In addition, know the big discussions happening in tech today. What are the latest thoughts on Continuous Integration and Deployment options? Javascript MVC frameworks? Big data? Be knowledgeable and you’ll always be ready if asked for your thoughts on the trends shaping your field.

Tip #4: Understand the users and business behind your product

Many developers are used to only describing their products from a tech perspective out, rather than a user perspective in.

To make yourself stand out from the crowd, be able to articulate who the users of your product are and the solution it provides for them, and more generally, the business side of the product.

Go into an interview from this angle in mind and a company will be confident that you always do your work with the user in mind.

Tip #5: Whiteboard your work

Many developers aren’t used to talking about themselves, their product architecture, what they’ve accomplished, or how to best articulate the technical challenges they faced. This is why whiteboarding your work is so important.

When I say whiteboarding, I mean mapping out the architecture of your product, the modules your were responsible for and the technological challenges you faced. It’s about taking all this information and putting it into words so that you can talk about it during an interview.

This might also literally mean drawing this all out on a whiteboard, as I often ask candidates to do during an interview. You can’t lie to yourself or anyone else in front of that whiteboard – either you can map out and explain your work, or you can’t.

If you can bring sample documents to reinforce your whiteboard map without breaking confidentiality agreements, that helps too.

Tip #6: Make it interactive – demo your work!

In an interview, I’m always much more engaged if a developer can demo their product for me. This might seem obvious, but you’d be surprised how seldom I’m asked if I want a live tour of the product they’ve been working on.

If you worked for a SaaS company, for example, and you still have an account, offer to log in and show me around. Tell me which modules you were responsible for. This is always much more visual and stimulating than a written summary of your work.

Tip #7: Be articulate, simple & concise.

Once you’ve prepared your whiteboard, be prepared to articulate all this information (your skills, your current responsibilities and your product) in a simple, concise manner. Start with less detail and drill down where appropriate. If you don’t know how deep to go, just ask the interviewer if they want to know more.

Be prepared to guide some of the questioning so you know the interviewer is getting all the information that makes you an appealing candidate. An interview is an interactive process, after all.

Tip #8: Tell me what you find exciting in tech today.

Even if you haven’t been working for the sexiest company, products or applications, always be prepared to talk about what you DO admire and why.

Please do me a favour – don’t say Apple or Google (and definitely don’t say Microsoft!). Come up with unique ideas that reflect your professional opinions on what makes a product or service shine.

Tip #9: Get to know the company you’re interviewing for.

Obvious, right? But it can speak volumes if a candidate isn’t informed, which happens a lot.

Find out what technology stack the company uses and review their FAQs, support forums, training guides and blog. If they have a free trial account of their product, sign up for an account and give it a test drive. The more you know, the more enthusiastic you’ll appear and the better and more useful your own questions will be.

Tip #10: Come to the interview with great questions.

Hopefully after having done all the research I’ve suggested, you’ll have some original questions to ask that not only show that you’ve come prepared, but that will also help you make a decision about how the company, product, technology and team fit your overall career goals.