Thursday, 25 September 2014

4 simple hacks to boost your sales and marketing efficiency

MarketingToolsForEntrepreneurs

I know his name … How do I get his email address?
How do I get to know more about this guy?
Did he open my email? Did he read it? Should I write again?
Eureka, Will send a mail in the evening.
(next day)
Oh God, totally forgot to send!
Oh God, I had to follow up with him last week …. Totally forgot …
He is not in my network, how do I get in touch with him?
Does this sound familiar? These are common day to day obstacles holding us back everyday in our path to glory. This not only leads to productivity loss, unnecessary delays but a lot of frustration as well.
I have myself suffered for a long time because of this and decided to take matters in my own hand. After a lot of research and experiments with various tools for over more than 12 months, I found answer to most of these problems. I was mighty surprised by the simplicity of these solutions and thought of sharing them.
In this post, I am not going to give the traditional route of various standard complex tools available but rather show you a few simple yet powerful tricks that work to improve your efficiency:
Yesware: Next time you want to know who opened your email, when was it opened, where was it opened? Look no more. This powerful tool will take care of all of this and give your powerful analytics to measure as well. I use this very effectively to know when to follow up and to whom. To top it up, you can even set up reminders to follow up if you have not heard up from your prospective customer/anyone. You all know, reaching out to your prospect at the right time is heck important to close a sale. A must have if you are targeting a lot of people and want to make the impact you looking for.
Note: The paid version has a whole bunch of powerful features to make you look really sexy.
Rapportive: Next time you need to find out an email address and want to know a little more about the prospect to send a personalized email and not sound cold, be sure to check out the Rapportive extension and this excel file to find anyone’s email address.
Rapportive extension gives you a brief about the person available from his social profiles including LinkedIn by just having their email address (even if you aren’t connected to the person). The excel file will allow you to have a number of possible email address by just knowing someone’s first and last name. Then, you put those email addresses one by one in your compose window and if the email address is valid, the rapportive extension will show you their social profiles. It’s just a brilliant way to find out anyone’s email address in a whiff. So, now crib no more about not having anyone’s email id to reach out to and just shoot your way into your prospects inbox. Happy mailing.
Boomerang: Another brilliant tool that I love. Are you the kind of person who has a thousand eureka moments a day and want to shoot out an email immediately (even if it may not be the correct time to send the mail, given that the chances of the other person opening the mail is low)? Well, then you are no different, there are millions of them with the same problem. Now, this is where Boomerang comes in, use this tool to create the message with the eureka idea that just popped and schedule the mail for a date and time you deem will make the most impact. The icing on cake is “Remind me” feature, if you want to follow up with the person after sometime in case you do not hear from him then use this feature to get a reminder to follow up. That’s it. No more getting lost in the maze of emails.
LinkedIn Groups: A kickass method to message a Linkedin user if you are not connected to him. This is one of the lesser known yet powerful tricks to get in touch with someone. Let me tell you now on how to do it: A) Assumption, you are not able to connect with the prospect B) Do not have any common connects to ask for reference. To connect with your prospect, the first thing you need to check is the groups you are associated with. Join the groups he is in blindly. Go to the group and then click on members tab. You will be surprised to see that you are allowed to message the member even if you are not connected to them. Cool, right? Happy sane spamming.
These are small yet extremely powerful tools to take your sales and marketing process to the next notch and make you fall in love all over again. There are few more powerful tools for growth hacking but these are a good starting point. These have personally done wonders for me and I would recommend all to use it and more.

Wednesday, 10 September 2014

7 Programmer Recruiting Mistakes

We’ve all met them. The programmers that can’t program. They can hardly write anything that compiles on their own. Producing quality quality code is way above their skills. Somehow they still get hired. Trying to find out why, I’ve listed 7 common mistakes made during recruiting.

The Seven Mistakes

  1. Focusing on years of experience.
  2. Trust peoples own assessment of their skill.
  3. Don’t ask the candidate to write code.
  4. Recruiting for “the other team”.
  5. Be forgiving to spelling mistakes in the CV.
  6. Focus on technical skills and not communication skills.
  7. Fear of hiring someone better.

Focus on Years of Experience

Years of experience is simple and objective to measure. For any single individual any added experience adds to the skills, so it’s natural to make the conclusion that the number of years of experience is the most important measure for skill.
Unfortunately that conclusion is totally flawed, especially for programming. The single most important skill to become a great programmer is talent. Some people have the aptitude to become a programmer; some doesn’t. The number one priority when recruiting programmers is to find out if the candidate has the aptitude. If the candidate hasn’t, several years of experience won’t help. The candidate isn’t and will never be a great programmer.

Trust Peoples Own Assessment of Their Skill

When interviewing I always ask the candidate of their own assessment of their skill in different areas. Knowing their own view of their skills is critical, but I would never trust them. The problem is that those with the highest competence will usually be very humble. On the other hand there will be candidates that has some basic skills and will boast about it.
Instead of trusting the candidates’ own skill assessment I’m looking for candidates with a realistic view on their skills.
I also use the question to find out the areas where the candidate claims the highest competence. Then I pick one of those areas for the code test. I’m trying to be nice, letting the candidates show their code skills in their strongest area.

Don’t Ask the Canditate to Write Code

I think that a code test is a critical part of a programmer’s interview, yet many people obviously ignore it. I’m astonished by that, because there are people that can talk, but get completely stuck when asked to write code.
The code test doesn’t have to be very hard. Those who can’t program at all will show that even on a simple test. In my recent interviews I’ve used two tasks.
The first is about data access. I present a small database with the tables Persons and Cars. There is also a foreign key from the cars table to the person table pointing out the owner of each car. I let the candidate explain how the relationship is to be implemented through a foreign key, which also requires establishing a primary key on the person table. Then I ask them to produce a simple result set.
Car Reg NoOwner Name
ABC123Anders Abel
LDB109Anders Abel
CED456Albin Sunnanbo
I let the candidate choose between LINQ and SQL for implementing the query. Either way, for an experienced developer that is used to writing data access code the query should be really simple to write down.
The other I’ve been using is to write a subclass Square to a Shape base class that I provide.
public abstract class Shape
{
  public abstract float GetArea();
}
I’ve also thought about asking people to solve the fizz buzz problem but haven’t yet taken that step. What do you think, should I give it a try?

Recruiting for “the other team”

At the end of the interview I always ask myself the critical question.
Would I like to have this person in one of my projects, sitting at the desk next to mine for several months?

If not, it’s a no hire. As Joel Spolsky writes in his Guerrilla Guide to Interviewing it’s a bad idea to recruit for the other team:
Never say, “Hire, but not for my team.” This is rude and implies that the candidate is not smart enough to work with you, but maybe he’s smart enough for those losers over in that other team.

Be forgiving to spelling mistakes in the CV

Before doing an interview I always read through the CV of the candidate. Of course I look at the information provided, but I also look closely at how it is provided. Does it have a good structure? Is it spelled correctly?
Written communication skills are always important in any programmer job. Even though the programmer will mostly be writing code they should also be able to write documentation and occasionally write emails to the customer. If they can’t express their CV clearly they will probably not be able to express anything else clearly either.
If there are a lot of spelling mistakes that any word processing would mark as incorrect it is a sign of pure laziness to leave them without fixing. If the candidate is lazy about the job application, there’s a huge risk for laziness in the job too.

Focus on technical skills and not communication skills

People sometimes claim that spoken communcation skills are not important for programmers. As long as they write great code that’s all that’s relevant.
In a team environment nothing can be more wrong. It doesn’t matter if everyone in the team writes great code if they can’t communicate their intentions. To produce a great result the team has to work together on a collective idea.
I usually ask the candidate to outline the architecture of a previous system worked on. It doesn’t really matter what system it is. What I look for is if the candidate has understood the basics of the architecture and can communicate it.

Fear of Hiring Someone Better

The technical interview (if there is one at all) is usually performed by a senior developer or architect. That developer probably has a certain position in the company, being the only one knowing how to solve the really hard problems.
What happens if an equally good, or maybe even better, programmer is interviewed? There are two possible reactions from the interviewer.
  • This person is really good, I won’t be the best at the company any more. This will threaten my entire position.
  • This person is really good, finally I’ll have someone that challenges me. Together we can form a really strong team and become even better.
The threat thought is very common (not only among programmers). Unfortunately it leads down the road of ever falling competence, if everyone always recruits someone that is less competent than themselves.
Would you dare to hire someone that might be better than yourself?

Hiring is Hard

Hiring is hard and requires hard work. It requires self confidence to dare to hire someone that can challenge yourself (in a positive way). It requires some very tough decisions in the end, taking the “no hire” option even if their is a huge pressure from management to grow the company.
I sometimes think of recruiting as having a single date and then having to decide whether to break up or propose. It’s a decisions about what people you will spend 40 hours a week with for the next few years.