About Sales Commissions

by Krishna on January 9, 2012

Dan Ostlund at Fog Creek Software talks about how they have got rid of commissions for sales people:

We did it because we were having a lot of the problems with commissions described above even though all of our salespeople are ethical and decent. Commissions just encourage certain kinds of behavior; dysfunction is built into the logic of the system. […] So we did it, and no catastrophes struck us. No earthquakes. No plagues, and no one quit. In the year since we dropped the commission system our sales have gone up. In fact, four of the last five months have been record months.

There are many problems with sales commissions, but by introducing a fixed salary, you are introducing newer ones:

First, why did no one quit in the last one year? Usually, if people don’t find themselves earning as much as they used to, they try to find a new job. What this sounds like is that every sales person was paid a salary that was equal or close to what they were getting before. Since it is not a commission model, I am assuming that salaries are tied to an annual review: a monthly or even quarterly salary review is really a commission model without the name. In a commission scenario, the sales risk is split between the company (salesperson’s base salary) and the salesperson (their commission). Now it has almost entirely shifted to the company.

Second, was any new salesperson hired in this year? What was their salary? If their salary is similar to that of an established salesperson, that means the company is taking a huge risk (paying too much money) on an unknown resource. A good salesperson in one company may not have the same performance in another (even if they have the potential), hence the risk. But if they are starting at a lower salary, are you able to attract a salesperson who has a proven sales record and is worth investing in? The way most companies structure this is that salespeople have a base salary and, if they switch jobs, they can regain their previous income by quickly selling more so that the commissions kick in sooner. With fixed salaries, the only way you can achieve it is to keep increasing the salary as the salesperson performs, which is once again like the commission model, but locking in the risk for the company.

Third, was anyone fired this year? What is the basis of measuring the performance of a salesperson? Is it the overall company revenue or the sales closed by the salesperson? If it is the company revenue, then poor performers could coast at the expense of better sales persons. If it is individual sales, you have introduced a new commission system. In that system, very poor performance means loss of job (zero revenue), average performance means retention (with no or little hike) and good performance means a good salary hike. This is once again shifting most of the risk to the company. Unless it is a really poor market, the salesperson is usually retained or can easily find a new job.

So, there are at least 3 possible ways that you are introducing greater risk to the company. The important thing to understand with risk is that it can be independent of the salesperson. A lot of sales has to do with external factors. For example, when the economy (or an industry) slows down, companies will reduce or eliminate purchases. Usually this happens gradually and a salesperson who had been running great sales numbers suddenly hits a plateau and starts going down, despite putting the same effort as before. With a commission system, the compensation system automatically adjusts. But in a salary model, it takes time to identify the situation with the market. By then, your losses could run in the tens of thousands of dollars (and more with a large sales team). And then, you have to decide whether to lay off people or reduce everyone’s salaries.

Finally, while Theory X is counter-productive, how you approach the topic of money for people’s efforts is very important. Specifically, giving people more money does not motivate them as much as you would like. In some circumstances, giving people more money can be insulting and counter-productive. But the contrary situation where you give people less than they think they deserve: that is an absolute no-no. When people think they are being denied the fruits of their labor, they get hopping mad and will either demand more or quit producing so much.

This needs to be understood carefully. Suppose you volunteer your time at the local hospital to help some elderly patients. You are doing it out of the goodness of your heart and don’t expect to be paid. In fact, if someone offered you some money, you would feel insulted. But suppose you were hired to do the job and were told you would be paid a salary, and when the time came to get your money, they tell you, “This work is its own reward and you are gaining pleasure from the work, so we are keeping back 10% of your paycheck.” You would be outraged and quite rightly so. Essentially, employees have expectations (financial and otherwise) and you need to meet them.

So suppose you have a salesperson who is paid a salary. You asked him to bring in 15 clients and instead he brought in twenty. Well, you have to give him a good hike. Next quarter, he outdoes himself and brings in ten for the quarter. What do you do? Do you wait till the end of the year to give a hike? Suppose he brings in fifty for the year. What kind of hike does he get? What happens?

As you can probably guess from human nature, this will not go that far. As soon as a sales person starts doing way more than you had asked them to do on the basis of their fixed salary, the first thing they will look for is greater compensation. They know that the money coming in is proportional to the company’s profits. If such compensation is not provided (either in the form of higher salaries or company shares), they will most likely quit or, if that is not possible for whatever reason, calibrate their efforts accordingly.

In sum, a fixed salary serves primarily to transfer greater risk to the company and create a trend for salespersons in the company to maintain a constant sales-to-salary ratio over time. That may be acceptable to you, especially when marketing can support sales efforts in a rising economy. It may not work at other times.

{ 3 comments }

How Many Hours Can a Programmer Program?

by Krishna on January 5, 2012

I am a little late to this party where Michael Arrington says that startups mean working hard and sleeping under your desk. But I will add a few words. I read a lot of commentary about how such death marches can be counter-productive and ultimately unsuccessful, and also the real dangers they pose to the well-being (short-term and long-term) of the lives of the programmers. But I didn’t see many people actually do a quantitative analysis. So here it is.

Your average working day is 8 hours and the average week has 40 hours. Now,  in the absolute best case (unworldly) scenario, your startup has a programmer who does nothing other than program, 24 x 7 (not even sleep). That translates to 168 hours, which means you have a programmer working 4 times harder than usual.

But of course, programmers are not machines running all the time and even those break down. They are subject to the same biological needs that other human beings have. Like, sleep. The optimal amount of sleep for human beings is between 7 to 8 hours. Now, you can survive a day or two with less sleep, but it will catch up and in the meantime, you are operating at below-peak efficiency and it is a wash. Using an estimate of 7.5 hours, we are down to 115.5 hours.

Then food. And you need to first get the food (order or cook) and eat it, at least three times a day. On average, let us say that takes 30 minutes per meal and 90 minutes overall. Now, if you are ordering pizza delivered all the time, maybe you can bring that down to 15 minutes per meal and cut that down to 45 minutes. So, let us average it to an hour per day. We are down to 108.5 hours. Hygiene? Brush your teeth? Take a shower sometime? Best case, let us say 30 minutes a day => Down to 105 hours. Commute from and to work? The average commute in 2007 was around 45 minutes round-trip. 5.25 hours per week => Down to 100 hours. Maybe you can reduce that by sleeping under the desk!

At 100 hours, that is just working two and a half times more. And we have not even talked about productivity, family needs, illness, having friends, non-work needs and activities, etc. For all intents and purposes, you are looking at somewhere between 10 and 14 hours of work 7 days a week.  And even that can only be sustained on a short duration (months).

So, here is the question: Is working about 2.5 times more going to make your startups yield the astronomical (i.e., 10 times or 100 times) returns expected? What is the value of the extra 150% put in by the programmer? Does 40 hours a week mean regular company returns, and 100 hours means Facebook-like valuation? And if that is the case, why not hire extra programmers while you are at it? Seriously, if putting in more hours means a huge guaranteed return, then surely adding more people gives you bang for the buck, right?

If not, why is it not? And why do people like Arrington and Jason Calacanis want people to work themselves to death? One possibility is that they don’t know how to count and seriously think that working a few extra hours suddenly translates into huge profits. I think there is something subtler happening.

The truth is that even with sophisticated metrics collection at work, you cannot properly gauge programmer productivity. There are ways to game the system, and even if people are not trying to game it, you have to spend time looking at the code in detail to see what is being churned out. People like Arrington don’t have the time or the expertise to do that. Instead they measure productivity by the number of hours the programmer is available to them. This means how much time the programmer is at work (they must be coding every second!) or how easily they can reach the programmer when not at work. If a programmer picks up a call from Arrington at 1 am, she is practically working all the time, regardless of the fact that it might only take her 10 minutes to answer the call and fix an issue.

So while Arrington and Calacanis say and even think that they want the programmer to work all the time, what they actually want is the person to be available all the time. More so because they cannot produce or fix anything without their help. This has nothing to do with startup success or failure. You can read similar stories in established companies with stupid bosses, where leaving one minute earlier than the boss has a whole different meaning than leaving one minute after.

{ 4 comments }

Helvetica The Movie

by Krishna on November 23, 2011

So as I had planned, I watched the documentary “Helvetica” on Netflix. It is a well-made film consisting primarily of interviews with type designers interspersed with a zillion visuals of Helvetica font used all over the place. Not being from a graphics background, I was astounded to see how ubiquitous the Helvetica typeface is. Most corporations use it for the design of their name. Street signs are written in it. Even T-shirts!

The interviews were interesting enough with some of them having intensity and passion in their advocacy or criticism of Helvetica. Some of the type designers talk of Helvetica as the “perfect” typeface because every choice (such as the horizontal orientation of the edges in “C”) cannot be bettered. The critics say that because of this aspect and also because Helvetica is everywhere, using Helvetica implies conformity with the mainstream and when you are part of the counter-culture, you would want to go in a different route. Of course, this needs to be taken in context with the typefaces used before Helvetica in print advertisements.

If you are creating web applications, you cannot use Helvetica as a font as it is a commercial font and for some licensing issues, it doesn’t come bundled with every operating system (apart from Macs). So instead of Helvetica, we have Arial that is on everyone’s computers. If you had asked me to compare the two fonts sometime back, I wouldn’t have cared, nor would I have known the difference. But there it is. At some point, Microsoft decided to actively promote Verdana (instead of Arial) on the web, using it for everything, including the MSDN site. On the desktop, the default on Microsoft Word for Sans Serif fonts is Calibri, which strangely was a replacement for the Serif font Times New Roman.

I like Calibri for documents as it is very readable on a monitor. But for regular text on the web, I prefer Georgia, which is the default font on this blog theme (Thesis) — again a very readable font, and it does seem to be very popular online. For mono-spaced fonts for code, I like Consolas, a big improvement from Courier New. Headings — I am not so sure. Georgia looks fine, but headings are very significant in conveying the mood of a website, so doing something different and unique can be worth the effort.

{ 1 comment }

The Resistance Against Requirements Specifications

November 21, 2011

Martin Fowler re-posted this article from 2004: Tests are always going to be incomplete, so they always have to be backed up with other mechanisms. Being the twisted mind that I am, I actually see this as a plus. Since it’s clear that Specification By Example isn’t enough, it’s clear that you need to do […]

Read the full article →

Pardon the Programming Interruption

November 21, 2011

Nope, this has nothing to do with software development. But for regular readers, a few things to note: If you have subscribed to the RSS feed, please validate if you have subscribed to http://feeds2.feedburner.com/thoughtclusters. There is a digit “2” at the end of the “feeds” sub-domain. Apparently, the “new” FeedBurner wants it that way. If you are […]

Read the full article →

When Phones and PDAs Merged

November 20, 2011

John Gruber posts a photo of this misleading 2007 presentation for the original iPhone: This is true as far as phones go. But back in 2004, there was the Tungsten T5: The Tungsten T5 cost around $400, less than what the first iPhone debuted for. It was a sophisticated device doing almost everything you needed, […]

Read the full article →

Trello and Siberian Cake Shop Owners

November 17, 2011

I was reading this amusing post on the Fog Creek blog by Rock Hymas illustrating Clayton Christensen’s disruption concept through the story of a cake shop owner in Siberia (!) who has some competition in the form of an ice cream stand. It is a good analogy, but it fails to explain why the cake shop owner makes […]

Read the full article →

The Google Reader Update

November 3, 2011

Many fans of Google Reader (the online RSS client) are up in arms over the recent changes. In my opinion, the outrage is a little overblown. First off, if you are reading this on a desktop, you already have a large monitor and the reduction in reading area is negligible. Plus you can hide the […]

Read the full article →

More on Typography

November 1, 2011

To follow up on my post on typography, I noticed that “This Developer’s Life” had a new podcast on the topic. I liked the interview with Bill Hill, who has done some stellar work with Microsoft on ClearType. The previous podcast episode on “Taste” was also very interesting. There was mention about the documentary “Helvetica”. It […]

Read the full article →

No, Steve Jobs Did Not Solve the Innovator’s Dilemma

October 28, 2011

From the Harvard Business Review blog by James Allworth: To disrupt yourself, for example, Professor Christensen’s research would typically prescribe setting up a separate company that eventually goes on to defeat the parent. It’s incredibly hard to do this successfully; Dayton Dry Goods pulled it off with Target. IBM managed to do it with the […]

Read the full article →