🔎
Nov 8 2005

Hackoff – The Blook, Part II

Hackoff – The Blook, Part II

A few weeks back, I posted about a new blook (book delivered in single episodes via blog) called Hackoff.com – An Historic Murder Mystery Set in the Internet Bubble and Rubble, by Tom Evslin.  A few weeks into it, and I’m hooked.  It’s:

– complete and total brain candy, or mental floss as Brad calls it

– a great 2 minute break in the middle of the day (episodes are delivered once a day during the week)

– a very entertaining reminder about some of the wacky things that went on back in the Internet heyday

– a good look into some of the processes that go on behind the scenes in taking a company public

If you haven’t started the blook yet and want to give it a try, you can catch up on all of the first episodes and subscribe to the new ones here.   You can also preorder a hardcover copy of the book here on Amazon.com.

Jun 24 2009

On the Other Hand…

On the Other Hand…

A couple days ago, I wrote about how crummy the customer service experience was with Clear going out of business with no notice and no apology. 

Today my inbox revealed the exact opposite experience:

Greetings from Amazon.com.

 

You saved $1.40 with Amazon.com’s Pre-order Price Guarantee!

 

The price of the item(s) decreased after you ordered them, and we gave you the lowest price.

I didn’t even know Amazon had a Pre-order Price Guarantee.  They could have gotten away with not giving it to me, and I would have never even thought about it.  Great experience!

Jan 28 2016

Ideas Matter Less Than Execution Which Matters Less Than Timing Which Matters Less Than Luck

Well, that’s a mouthful.  Let me break it down.

Ideas Matter Less Than Execution

Execution Matters Less Than Timing

Timing Matters Less Than Luck

There’s a persistent myth about entrepreneurs as heroes – the people with the brilliant ideas and Eureka moments that bring companies to life and create success.  I’ve never believed in that myth, or at least not in its universality, as I’ve always valued both ideation and execution in terms of business building.  But as I was thinking about that construct more the other day, it occurred to me that there’s actually a hierarchy of the two, and not just of the two, but of timing and luck as well.  The best businesses — the runaway successes — probably have all four of these things going, or at least three.  And in many cases, THE IDEA is the least important of the bunch.  Consider these examples:

Plaxo was launched a year or two before LinkedIn.

Friendster was launched a couple years before MySpace, which was launched before Facebook.  (You can go back even further and look at things like PlanetAll and Classmates.com).

Geocities predated blogging and Tumblr by more than a decade.

The Diamond Rio was launched three years before the first iPod.

Lycos, Excite, Infoseek, Altavista, Yahoo, and lots of other search engines and web crawlers were started well before Google.  Goto.com (Overture) did paid search before Google.

The ideas were all pretty similar.  In most cases, if not all, execution won out.  In the case of the iPod vs the Rio, it’s not that the world wasn’t ready for portable music – my Sony Walkman from the early 1980s is testament to that.  It’s that the combination of iTunes and the iPod, combined with Apple’s phenomenal design and packaging — all elements of execution — won the day.

The role that timing plays is also key.  Sometimes the world isn’t ready for a great technology yet, or it may be ready, but not for sustained growth and usage.  Friendster and MySpace vs. Facebook is the best example of this.  Facebook isn’t necessarily a better service, better marketed.  Friendster and MySpace were similarly viral in adoption at the beginning.  But the world was still in the Visionary or Early Adopter stage (in the language of Geoffrey Moore’s Crossing the Chasm).  By the time Facebook came around, the world was ready to mass adopt a social network.  Geocities, for example, was a big financial success at the time (Yahoo acquired the business for $5B – they “only” acquired Tumblr for $1B, give or take), but then it disappeared from the scene, where Tumblr seems much more durable.

The role of luck is harder to explain, or at least harder to separate from that of timing, and there’s a good argument that luck can be at the bottom of this particular chain, not the top (as in, luck is hard to separate from ideas).  Sometimes luck means avoiding bad luck, as in the story about Southwest Airlines — a great idea with promising early execution and good timing — narrowly avoiding a major crash during its first week of operations in 1967.  Sometimes luck means being in the right place at the right time, or making an accidental discovery, as in the case of the Princeton University professor, Edward Taylor, who discovered a powerful cancer treatment a bit accidentally while studying the pigments that produce the colors on the wings of butterflies for a completely unrelated purpose.

Don’t get me wrong.  Ideas are still important.  They are the spark that starts the fire.  And ideas can be partly created by the luck of being in the right place at the right time, so maybe this whole construct is more of a virtual circle than a hierarchy.  But entrepreneurs need to remember that a spark only gets you so far.  As the old saying goes, I’d rather be lucky than good!

Sep 15 2004

Change of Name?

Change of Name

Fellow CEO Greg Reinacker posted an open question on his blog about whether he should change the name of his company, NewsGator. This is a GREAT topic.

We struggled with it for years at MovieFone, because at some point, the Internet became a huge part of the business, and the name seemed antiquated. Plus, everyone knew us by the phone number, 777-FILM (or whatever number it happened to be in any given city). But it had 10 years of brand equity at that point behind it.

Return Path used to be called uLocate.com a really long time ago, and we changed the name to be less “dot com” three months after we got started (that’a story for another posting as well). People ask me all the time if I sitll think that Return Path is the best name possible for the company. I’m sure there’s a better one out there, but I am sure it’s going to be hard to convince me to change it. Why? Let’s start with these 3 reasons:

1. It’s close enough. We’re in the email business, in general, and Return Path is a good name for people in the industry to remember (it’s the first two words in every email header) for people in the industry, and it’s easy enough to say.

2. It has good equity.
Almost five years in, most of our customers and industry watchers know it. Of course, it’s not Coke and has limited equity in the grand scheme of things, but its equity relative to the size of our enterprise is meaningful. That’s the important part. There’s a reason GE is still called GE even though its primary business is financial services now.

3. I have no idea what business we’re going to be in three years from now. Ok that’s an overstatement. I’m pretty sure we’ll still be in email. But while there are perhaps more appropriate names for us today, in today’s dynamic technology market, the company might look very different down the road, and changing a name is painful enough that I wouldn’t do it without a MAJOR event underway like a dramatic change of focus for the company, or a massive acquisition.

That said, if I had happened to name the company CompuTyco or EmailEnron, I’d change it because the collateral damage or risk thereof. If my mom had named me Adolph, Osama, or Saddam, I’d also be headed down to the courthouse to switch to a new one. They’re not as evil as a bad dictator of course, but Gator has so much baggage — they changed their own name to Claria!

So Greg, change that name despite the challenges outlined above. You’re lucky in that t’s still early enough for you. Just make sure you pick a new name that’s flexible and extensible into other areas in case the business you have in three years isn’t the business you have today. And don’t bother with an expensive naming consultant (let me know if you want to hear about that nightmare). Just have a good, structured brainstorm with your team.

Feb 24 2005

Everyone’s a Direct Marketer, Part III

Everyone’s a Direct Marketer, Part III

With every company as a direct marketer, and with (hopefully!) every company embracing some of the best DM principles, what does this shift mean for the way companies will be structured in the future?

First, let’s talk about the internal structure of a company.  The biggest shift going on here is that customers are becoming a more important part of all employees’ daily lives, not just those in the advertising department.  I wrote an earlier posting called Everyone’s a Marketer which applies here.  Most likely, more and more members of your organization are touching customers every day — and they need to be trained how to think like marketers.

But beyond that, companies will be constructed differently in the future as well.  While not true in some industries, there are many industries founded on the “mass” which will never be the same again.  Here are three examples of how direct marketing is infiltrating — but enhancing the opportunities of — corporate America.

– Disney’s film unit used to make movies only for theatrical release.  Today, they have an enormous volume of direct-to-video (or DVD) movies that never see the big screen but that drive huge sales numbers when marketed to Disney’s customer email database.

– Ralph Lauren used to make Polo shirts with a fixed number of configurations of shirt color and knitting color of the logo.  Now, you can go onto Polo.com and custom build a personalized shirt for someone with the right size and color combination of their college or company or favorite baseball team.

– Barry Diller used to run a studio, then he bought a TV network called the Home Shoping Network (and, I’d add, a lot of people laughed at him for doing so).  He has now turned HSN into InterActive Corp, a true convergence company that mixes content and media with commerce and direct marketing with brands like Match.com, Ticketmaster, eVite, CitySearch, and Expedia.

That’s it for this series.  All thoughts and comments are welcome.

Sep 5 2006

Seth Responds

Seth Responds

About an hour after I posted a not so flattering review of Seth Godin’s new book this morning, I got an email from Seth with a couple good points worth responding to here.

His main points (other than offering me a refund, which was nice) were that (a) the book itself was very clear about its content — on the book itself (back cover, inside flap, marketing copy), kind of like a ‘live album’ for a recording artist; and (b) if I thought the blog postings were worthwhile, why  did I still feel like there was a downward trend in his writing?

Ok, so these are fair points.  Let me try to clarify.  I am 99% sure that I bought the book off the Amazon.com email which said “if you enjoyed other books by Seth Godin, then here’s his latest,” which prompted my robotic one-click order without paying attention to the fine print.  That’s why I was disappointed when I got the book.  My bad, I guess, although that’s somehow an unsatisfying thought as a consumer — that I should have paid more attention to the fine print.  Live albums from musicians usually have that in the title so the marketing is clear, and they still sell a ton, probably even more so.

In re-reading my review, I actually think it’s balanced — I do say there are a bunch of circumstances where the book is a must-have — but my use of the word “sell-out” was a bit harsh given the attempts to present the book as a compendium.  But the downward trend in my mind is more than just this book.  I think a lot of Seth’s writings have been hitting the same notes for the last couple of years, while I’ve been hoping to hear his next Big Moo.

I didn’t take up Seth’s offer for a refund, as I fall somewhere between (a) and (c) in my definition of why this is a must-have.  And while I’m at it, maybe I should rethink my earlier point that this whole blog thing isn’t about conversations.

Jul 31 2006

Social Computing: An Amusing Anecdote About Who is Participating

Social Computing:  An Amusing Anecdote About Who is Participating

We learned something about Wikipedia tonight.  Mariquita was reading an article on Castro on CNN.com entitled “Castro Blames Stress on Surgery” about his upcoming intestinal surgery.

[Quick detour — I’m sorry, Castro blames the surgery on stress?  Isn’t it good to be the king?   And he’s handing  the reins of government over to his oh-so-younger brother Raul, at the tender young age of 75?]

Anyway, we were debating over whether Castro took over the government of Cuba in 1957 or 1959, so of course we turned to Wikipedia.  Ok, so Mariquita was right, it was 1959.  But more important, we learned something interesting about Wikipedia and its users.

There were three banners above the entry for Casto that I’ve never seen before in Wikipedia.  They said:

This article documents a current event.  Information may change rapidly as the event progresses.

This article or section is currently being developed or reviewed.  Some statements may be disputed, incorrect, biased or otherwise objectionable.  Please read talk page discussion before making substantial changes.

The neutrality of this article is disputed.  Please see the discussion on the talk page.

That’s interesting of the editors, and it made me rush to read the entry on our fearless leader, George W. Bush.  It only had one entry, a bit different from that of Castro (who, at least in my opinion, history will treat as a far more horrendous character than Dubya):

Because of recent vandalism or other disruption, editing of this article by anonymous or newly registered users is disabled (see semi-protection policy). Such users may discuss changes, request unprotection, or create an account.

Well, there you go.

May 10 2006

links for 2006-05-10

Apr 7 2006

links for 2006-04-07

Feb 21 2006

Agile Development

Agile Development

Sometime last year, our engineering and product teams embraced the Agile Software Development framework.  Without going into too much detail (here’s the Wikipedia entry for those who want it), the concept of Agile Development is to run software development in small pieces with a focus on more communication between product and development teams resulting in collaborative requirements development.  This leads to a “release early and often” environment where there are continual improvements.  For us, we group development projects now into a “release” that consists of a series of usually six, two-week “iterations.”

The release planning and iteration planning meetings are reasonably long meetings that involve the major stakeholders, product management and engineering.  The process also includes a very short, 10-minute Daily Stand-Up meeting with everyone on the team to review progress and identify roadblocks to completing the two-week iteration.  Requirements are not heavily documented and discussed more or less on the spot during the iteration meetings.  Because there’s a major pull-up every two weeks and a minor one every day, it’s easy to be light on requirements and for product management to constantly be in the loop with engineering to see progress, test functionality, and make mid-course corrections.

This methodology isn’t for everyone, but it’s particularly well suited to the kind of work we do at Return Path — small team, multiple internal and external stakeholders, very dynamic market, and web services as opposed to packaged software.

Our efforts have been bolstered by some limited consulting and more important, a fantastic web-based workflow management tool geared towards Agile Development run by a company called Rally Development in Boulder.  Think of it as Salesforce.com for your engineering and product team.

We’ve had great success with this methodology to date.  Engineering productivity is way up, product management visibility and input into development is way up, the level of friction/noise between product management and engineering is way down, and we have a much tighter grip on our development milestones than we ever have in the past.

Agile and Rally have worked so well for us, in fact, that we’re starting to extend the concept to other parts of our business, which I’ll write about separately.

Jul 7 2004

Taylor Made for this Blog

I haven’t done a book review yet on this blog because I haven’t found a very relevant one. I will do more as I go here — I’ve actually read a few pretty useful business books lately — but there’s no better book to kick off a new category of postings here than the one I just finished: The MouseDriver Chronicles: The True-Life Adventures of Two First-Time Entrepreneurs.

The book details how two freshly-minted Wharton MBAs skipped the dot com and investment banking job offers to start a two-person company that produced the MouseDriver (a computer mouse shaped like a the head of a golf club) back in 1999-2000. It’s a great, quick read and really captures the spirit of much of what I’m trying to do with this blog, which is talk about first-time CEO issues, or company leadership/management issues in general.

Although it’s not about an internet business, the book also has an interesting side story, which is the powerful impact that email had on the MouseDriver business, with an email newsletter the entrepreneurs started that developed great readership and ultimately some viral marketing. Sort of like a blog, circa 1999.

Thanks to Stephanie Miller at Return Path for giving me the book!