Archive for December, 2007

The Last Post of 2007…

NickN| December 31, 2007 11:59 pm

This one will be short and sweet as I’m a bit fuzzy thanks to the ~9 hour flight back from the UK.  In keeping with the impending New Year, a good old fashioned Top 10 list seems like the way to go.

Since I triple-U’d Heathrow (three people in a row were helpful, which is Unlikely, Un-nerving and likely to be Unrepeatable), I’m feeling optimistic.

All of which means I’ll skip the bad parts of 2007 and go straight to the top ten best parts of the year.  Since I’m being lazy, it’s a mix of business and personal.

Let me begin…

10. Seeing our logo for the first time
9.   Selling my house in AZ before the market really really imploded (I still took a beating, but nothing like the one I’d be taking now)
8.   Getting settled in North Carolina (and finally living in just one place at a time)
7.   Finding some fantastic board members
6.   Hearing from my sister and her better half that they’re expecting a baby girl just before my birthday next year

5.   Seeing the first ugly version of Unifyr come to life
4.   Getting Brad Feld’s attention

And purely for dramatic purposes, here’s a quick pause before hitting the final three…

3.   Seeing Logan shepherd the development and implementation of the ideas we’ve been talking about for 15 months.
2.   Watching my daughter change from a wriggly but cute spit-up machine into a vocal thinking walking talking funster.
1.   The unbelievable support I’ve had from my wife.  She’s a rockstar.

2008 will be an interesting year in Monkey Land.  May it bring new and exciting things to all of you!

You can’t always get what you want: The snarky nature of incentives…

NickN| December 28, 2007 3:46 pm

Back in mid-December, Bijan Sabet had a short post about channel conflict.   When you’re selling any kind of product, you sell it through a channel e.g. direct sales (your own sales people/website selling directly to customers), reseller sales, distributor sales or perhaps some combination of all three.

Conflict arises when you put two or more channels in direct competition with each other, usually while providing an unfair advantage to one of the channels involved.  A typical example would be conflict between in-house sales people and resellers.  If the customer can get a lower price from an in-house sales guy (or gal) than from a reseller, you’ll have a conflict.  The reseller will lose sales and eventually drop your product.

Much of the conflict revolves around pricing, and big product manufacturers go to great lengths to try and keep pricing consistent across all the channels that they use.  You may have noticed that there is almost NO variation in price on new Apple products regardless of where you buy them.  And that’s because Apple exercises very strict control over it’s pricing (for legal reasons, they can’t exactly force everyone to sell at a certain price, but they can make it awfully unattractive NOT to sell at a certain price.).

One of the things that people often forget about when they are considering channel conflict (or when they are trying to repair its aftermath) is how the sales team are compensated.

Sales people usually make a base salary plus a commission.  The commission structure can range from simple (x% of all sales) to somewhat complex (x% for direct sales, y% for sales through resellers, z% for distributor sales) to mind-numbingly tedious and complex with a range of percentages driven by monthly and quarterly sales targets with escalators based on breaking through certain sales volumes.

The key thing to remember is that you ALWAYS get the behavior you incentivize for.  I once worked for a company who’s sales team sold direct and also worked with resellers.  The company was keen to increase direct sales and did so by raising the rate of commission on those sales.  i.e. a sales person would make more selling a product direct than selling it to a reseller.

Now a typical reseller discount on a product was 30-35%.  i.e. a $1000 product would be sold to a reseller for $650-700.  But direct sales were, in theory, at full price.  In other words, the company would make a lot more money on a direct sale and could afford to be quite generous with the commission rate.

But, as often happens, someone outside the sales team pointed out that this new commission rate would amount to a lot of money (ignoring the fact that the company would be making a lot more money on each sale).  This lead to the brilliant notion that there should be a minimum sales volume that the sales person would have to reach in order to get this crazy new rate of commission.

The new sales plan was rolled out.  Reseller sales jumped.  Direct sales actually fell.  Why?  Because the sales guys knew that if they didn’t hit the minimum quota, they wouldn’t get any commission for their direct sales.  So they stockpiled them until the end of the month.  If they hadn’t generated enough direct sales to get a commission, they rolled all of them through their favorite channel partner.  So they still got a commission, and the company lost 30-35% on each sale.

Incentives are equally tricky outside the realm of sales.  In one of my earliest jobs, I was working as a contract employee for a large company.  Three of us joined at the same time.  Two of us (including me) worked our butts off, while the third was, to be polite, incredibly lazy.  When a permanent position became available, all three of us applied for it.  Captain Lazy was given the job.  Come to find out that the department Manager’s bonus was tied to employee turnover.  Promotions were treated the same as someone leaving from a bonus-accounting point of view, so the Manager in question wanted a dullard that would stay in the same job for a long period of time, whereas I (and the other guy) would have wanted to progress to more senior positions as soon as they became available.  So the net result of a good idea — trying to build a solid team — was to build an environment that rewarded laziness and weeded out competence.

In case you might think that this is a recent phenomenon only found in the business world, I was entertained to read (in that book) that an archaeologist named Koenigswald ran into the same problem on a dig in 1931.  They were excavating a significant trove of early hominid fossils (Ngandong Homo Erectus, if you care) and Koenigswald came up with the bright idea of offering a cash reward for each piece of fossilized bone turned in by local villagers.  It was only after the dig that he found that several villagers had smashed large, intact bones, so as to produce more bone fragments and get a larger reward.

Oops.

So the moral of the story is: compensation is always tricky.  Proceed with caution and keep your spidey-sense focused on finding the unexpected side-effects of whatever you’ve come up with…

Hard Choices & The Perils of Small Numbers…

NickN| December 27, 2007 10:00 am

As many of you know, we’re getting into our beta program and a number of folks are now playing with Unifyr.

Much of the product’s functionality has been logically obvious as we did our design work.  One idea cleanly flowed into another producing a cohesive whole.  Once we figured out our interface metaphor, a lot of loose ends also got tidied up rather neatly.

But there has been one thorn in our side that stands out: how to handle email.  It’s not that it’s technically challenging, it’s a matter of how we handle things to ensure the cleanest and simplest workflow for the most users. 

Back in our early Ugly Baby stage, we spoke with a handful of potential customers.  As you’d expect, some were Exchange users and quite a few used simple POP3 accounts.  But the largest customer we talked to used GroupWise.

For any small early stage company, deciding where to apply your efforts is always challenging.  While we’d love to have everything working at close to the level of a releasable product, it’s simply not achievable in a useful timeframe with the resources we have at hand.  Long dev cycles are NEVER a good thing — we believe very strongly in the idea of release quickly and update often.  It’s the only way to ensure that your product is evolving in a useful manner and not heading down some kind of Sauropod dead-end (sorry, still reading that book and I’m into the evolution & dinosaurs section).

Anyway.  The point is that you have to pick your battles and decide where you are going to settle for basic functionality versus something that’s actually useful.  Effectively, it’s the difference between a signpost planted on the road well on the way to somewhere and actually being there…

So… back to our chat with a handful of customers.  Prior to the arrival of Groupwise, our email efforts were going to be focused on  Outlook integration, reading PST files and a variety of other odds and ends along the same lines.  With one bullet, we hoped to have interim functionality for Exchange users and POP3 people (often using Outlook or Outlook Express). 

But hold the presses.  Here was a potentially large client that this solution would instantly alienate.  Sure, they were an oddity.  But they were also a highly recognizable and large potential customer, something any early stage company would kill for. 

Time for a new plan!

So we went with plan C, which was to give everyone their own Unifyr email address.  Like any choice, it came with a bunch of surprises.  The most recent of which was that we can’t easily automate the creation of email accounts when we setup a beta account.

This kind of situation is always hard to handle, and I’m not sure there was a clear right or wrong answer.  Whichever dev path we went down would most likely have been placeholder functionality anyway. 

On the one hand, an obvious flaw in our logic was that we only talked
to a handful of customers and small numbers are always misleading.  But
on the other hand, the customer concerned represented a big opportunity.

This is exactly the kind of scenario that makes startup life interesting and has you second guessing the choices you’ve made.  Especially when you’ve got beta testers that are less than enthusiastic about the current level of email functionality.

But as the saying goes, what doesn’t kill you makes you stronger :-)

Best Christmas Quotes…

NickN| December 26, 2007 4:32 pm

Being a crotchety old fart at times, Christmas was something I had become fairly apathetic about until I had my daughter.  Christmas with a 2 year old is a blast — she’s provided much entertainment for all.

She also has the best quotes of the holiday so far. 

From early Christmas morning:

"I like Santa.  He can come again."

and from just after nap time…

"My presents!  They all disappeared!!!" (accompanied by a look of abject horror until she was persuaded that Grandad had in fact just tidied them up.)

I ate entirely too much food, hung out with family and generally had a splendid time.  I hope all of you were doing the same thing or something equally relaxing…

Wonders of Web 2.0 and Your Tax Dollars Not At Work…

NickN| December 24, 2007 6:35 pm

Did you know that the kind hearted (?!) folks at NORAD have a Santa tracking website? It’s a Google Maps mashup that shows you in real-time where Santa (or Father Christmas ’round these parts) is busy doing his thing…

Check out NORAD Tracks Santa here.

As well intentioned as it is, I did have to laugh at the marketing copy on the site… Here’s a quote from the "How We Track Santa" page (bold added by me):

The moment our radar tells us that Santa has lifted off, we use our second mode of detection, the same satellites that we use in providing warning of possible missile launches aimed at North America. These satellites are located in a geo-synchronous
        orbit (that’s a cool phrase meaning that the satellite is always fixed over the same spot on the Earth) at 22,300 miles above the Earth. The satellites have infrared sensors, meaning they can detect heat. When a rocket or missile is launched, a tremendous amount of heat is produced - enough for the satellites to detect. Rudolph’s nose gives off an infrared signature similar to a missile launch. The satellites can detect Rudolph’s bright red nose
  with practically no problem.

       

A cheery Christmas message that ties in potential mass destruction and missiles too.  I just hope Rudolph has some cool countermeasures, just in case some trigger-happy cadet misreads the signal and decides to take him out…

For those of you on the Christmas bandwagon, Merry Christmas.  For those of you that are not, enjoy the day off!