Wonder Bread

June 25th, 2008 . by mikepk

I’ve been thinking more on names and reading a lot of the commentary that seems to have been sparked by that same GigaOm post. I still think we’re overly obsessed with startup names, but I felt like my last post on it was missing something. We all have some deep seated instinctual sense that names are important in some way. What I was trying to argue is that I think our obsession is overblown for startups.

It clicked for me when I read one of the comments on the “rules for startups” post on GigaOm by a fellow named devon :

@ the skeptics… When Logitech introduced the Scanner 2000, sales were tepid. Then they renamed it to the ScanMan, and sales doubled in 18 months without any additional advertising. That’s one example of what a strong brand name can do.

A great brand name will not make a bad business model succeed, nor will a bad brand name cause a good business model to fail. However, when all other things are equal, going to market with a powerful brand name is like sailing with the wind at your back. It makes marketing easier and cheaper, because it takes fewer repetitions for the brand promise to sink in with the target audience.

emphasis mine

How often are all things equal in a startup? By saying startup X has a better name then startup Y you’re drawing an equivalence (all startups are equal, but X is such a strong name). A startup, unless it’s a “me too” endeavor is all about creating something wholly new. Is the market space the same? Is the product the same? Does it have the same features? Is the technology the same? Is the team the same? Is the user experience the same? Most importantly, does the startup serve exactly the same user need? Unless the startup is brain dead, the answer to at least one, and probably most, of those questions in comparing startups is a resounding no.

So, for all things being equal, an array of equivalent (or mostly equivalent) products, scanners, white bread, etc, a good name can be tremendously important. But arguing the name is a critical component for success in a startup is akin to saying you have a choice between a bathtub “the flugglubernator” and a race car “the Zip2000!”. If a user wants to get clean, the fact the race car has a cool name is irrelevant. The point I was trying to make before is that the name in a startup is a second order effect on success. So I guess my new hypothesis for startup names is: The importance of the name as a component for success is inversely proportional to how unique the startup is.

I can’t find the source but I always like this quote: “Marketing is the wonder in Wonder Bread®”.


Roses By Any Other…

June 22nd, 2008 . by mikepk

Names. In startups why do we obsess about them? Naming things is fun. It’s a direct application of creative energies. It’s also something anyone can do so people feel free to give you their two cents at every turn. But how much of an effect does the name of a company really have on it’s success?

Since the inception of our company this is the single piece of feedback we’ve consistently gotten. Usually it’s someone looking at the name, never bothering to check out the service, and giving a reaction tainted with web 2.0 cynicism.

ZOMG it’s like totally web2.0! Worst company name EVAR! Total Flickr RIPOFF! I’m, like, so tired of these, like, missing vowels and stuff.

Originally my hope was that people would ask why the company was named grazr, then we could move into describing “Grazing information instead of drowning in it”, the basic philosophy the company was founded on. Domain squatters forced us to drop the ‘e’ but we also thought it would be kind of funny. In hindsight I guess we should have suspected that the “dropped vowel” company name would become popular then unpopular.

I thought this inability to see past the name was a major factor contributing to the friction we’ve had to gaining users. The truth is, I fell into the same trap as these commenters, it’s easy to focus on the name because it’s “simple”. It’s easy to do “drive-by critiques” without thinking of all the factors involved. Counterintuitively, I think that because there’s so much focus on names it actually indicates that success is not, or only slightly, related to the name choice. Since startups are so hard, and name critiquing is so easy, there is a disconnect there. Trying to bring a new product, code, service, and company to life is very difficult and usually we focus on the easy stuff.

I think the name of a startup has substantially less effect than what would seem to be indicated by the disproportionate amount of energy and effort we put into devising them and critiquing them. We are obsessed with expert rules and guidelines for naming a companies. Even when those rules are overly simplistic, contradictory, and mostly about a “subjective feel”. As startup founders we’re desperate to gain any edge we can, and we’re always on the lookout for tales of experience, rules of thumb, and other things that can help us avoid mistakes. Most naming rules come from a basically flawed process: look at successful companies, assume somehow the name had some serious impact on their success, come up with a rule to fit those names. Unfortunately these rules always contradict themselves because: the name is not what made them great. For any set of companies you use, there exists a set, equal in number, that contradicts the rule you arrive at. There is no way to find the formula for how names increase success because, except for possibly extreme cases, it has very little effect.

Now this is just my personal musing, I wonder if there’d be way to prove this scientifically? Although I know of no one doing this experiment, I’d love to actually get data on naming and how it affects success. Take the entire pool of startups at a particular stage and have experts chose the good names vs. the bad names (with only the names as data). Track those companies over their lifespan. I wonder if the ones they choose as good would show any greater success rate than the others. I’d wager that the predictive ability of experts in choosing names as a success factor would be barely better than random (some names are so truly, dreadfully, awful that they might impinge the success of a company).

So without further ado:

Mikes rules for startup names

  1. There are no rules, so even these are probably flawed
  2. Don’t obsess.
  3. Try and make it easy to remember, say, and write

Supplemental guidelines:

  1. Try not to make it sound like (or be) swear words or distasteful concepts.
  2. Careful with other languages and unintended meanings

I didn’t make the second set rules because I could easily see something like schitter.com becoming popular, depending on the context I suppose. :)


The Awesome Bar

June 18th, 2008 . by mikepk

Sounds like the name of some trying-really-hard-to-be-hip new nightspot. After playing with FireFox 3 for a couple of days, I’m surprised to find it’s my favorite feature of the new browser. I upgraded mainly because, for some unknown reason, FF2 was highly unstable on my Mac (crashing at least once a day, and yes that was after ruling out extensions). In search of stability I updated to FF3, but didn’t think much of it’s new features.

I just typed a single letter into the url field and the first item in the awesome bar’s results drop-down was exactly where I wanted to go. Freaky. If it gets any better maybe I’ll be able to navigate via thought :). A very nice addition, kudos to the Moz team.


Apple Conversation stream (thanks to Summize)

June 9th, 2008 . by mikepk

Like I’ve said before, I’m on a personal mission to try and post more, both here and in the comment space. Unfortunately the next couple of days are going to require my full coding-head-down attention. But with the WWWDC and iPhone buzz swirling, and being a self-professed apple nut, I thought I’d use my summize embed to track the conversation.

Update: it looks like Summize is feeling the pain, takes a bit of time to load at the moment.

Update2: Looks like they really went down hard. The JSON interface is returning errors.

summize


Geek + Radiohead

June 6th, 2008 . by mikepk

If you like Radiohead, and especially if you’re a tech geek, you have to check this out. It’s a remix by a fellow named James Houston of a Radiohead tune using old hardware for the sounds. For sound he uses things like an old Sinclair, printer movements and scanner mechanisms but the really trippy part is using old hard drives as speakers. Not only is it a cool idea, the video is mesmerizing. (Give it a minute or so to get going before judging).


Big Ideas (Don’t get any) from 1030 on Vimeo.

Simply amazing.

Saw this via Engadget.


Innovation in a big corporation

June 5th, 2008 . by mikepk

I was reading a post by Zoli Erdos about how Microsoft could have been first out of the gate with a web based office alternative but then canceled it. Then I saw Matthew Ingram followed up with a common interpretation of this kind of big company behavior, that they can never win (ostensibly because they fail to grok new waves of innovation). This reminded me of a post I wrote some time ago regarding this odd big company behavior so I thought I’d repost it here (with some edits). Sorry for the length, I’ve never been good at being succinct.

We’ve heard the corporate battle cry, “innovate or die!” Countless books tell us that innovation is at the heart of our economy. Those companies that innovate prosper, while those that don’t are doomed. We accept that to be innovative, especially in a corporate sense, is akin to pure virtue. So why are large companies so awful at new and sweeping innovation?

Big companies aren’t nimble. They don’t react to changing market conditions. They become buried in bureaucracy, stuck in their ways, sluggish, inefficient. Phrases like these reflect around the media echo chamber all the time. This imagery appeals to our love of the underdog especially when considering startups versus large companies, David versus Goliath, virtue versus brute strength. While this imagery is appealing I don’t think its true.

It’s important to understand the dynamics of innovation in large companies if, when creating a startup, we hope to harness the shortcomings of large companies to become successful. Too many startups believe they can succeed by virtue of being a startup, relying on the ‘fact’ that large companies are incapable of being nimble or innovative. I think this is fundamentally untrue, although clearly there is something at work that allows startups to succeed an topple more powerful incumbents. Bureaucracy and inefficiency are serious problems inside large institutions but I don’t believe this fully explains the lack of innovation.

Looking at the case for innovation in big companies, I have a unique perspective. I worked for, Data General, one of the big, old minicomputer companies that are part of the accepted technology industry narrative. DG, DEC, Wang, Prime, the mini computer companies that, as the story goes, went to their grave oblivious to the changing world around them. The fate of the minicomputer company is often used as a warning story to those that don’t worship at the altar of innovation.

There were lots of interesting historical footnotes to this ex-minicomputer company that I worked for. By the time I started there, in the late 90’s, they had long ago abandoned the minicomputer and were developing some pretty cool and cutting edge computing systems (why I had chosen to work for them). The longer I was there the more I learned about the innovations that had been pioneered but never commercialized. I learned that at one point they’d developed one of the first true laptops, with battery power, dual 3.5 inch disks, LCD screen, all in 1984. Their implementation of the Unix operating system was frequently hailed as one of the most stable and innovative. They created a new disk storage subsystem (which eventually led to their being purchased by another company). One of the business units at DG, when I started, was developing stackable, lego-block-like internet appliances for ISPs.

One day I was wandering the halls and stumbled on a strange wireless, handheld, WindowsCE based, touch-screen LCD, “clipboard” called the “wiinpad” that was sitting in a garbage palate. Apparently this “clipboard” had been developed somewhere between ‘97-’99 and then canceled. In short, there were lots of really neat and innovative things happening in the company, yet it was still considered a minicomputer company incapable of innovation.

There’s a famous quote attributed to Ken Olson who was CEO of DEC, “There is no reason for any individual to have a computer in their home”. This quote is cited frequently in support of the innovation myopia afflicting large corporations. Again I think the soundbite and the imagery it evokes are more appealing than the truth, Ken Olson himself had a computer in his home.

[That interpretation of my comment] is, of course, ridiculous because the business we were in was making PCs, and almost from the start I had them at home and my wife played Scrabble with time-sharing machines, and my sixth-grade son was networking the MIT computers and the DEC computers together, hopefully without doing mischief, using the computers I had at home. Home computers were a natural continuum of the “personal computers” that people had at work, in the laboratory, in the military.

The original quote was aparently taken out of context where he was discussing home automation (whether a computer would *control* your home, turn your lights on and off, fix your meals, etc…). Mr. Olsen defended himself on numerous occasions saying he fully understood the importance of the PC. It could be argued that he was just back peddling, but I don’t believe it.

Minicomputer companies died, it is said, because they failed to see the “strategic inflection point”, “paradigm shift” (or pick whatever sweeping term you want) of the personal computer revolution. I don’t think the innovations occurring in the company I worked for were isolated and probably occurred in all the old minicomputer companies. These companies are filled with exactly the engineers and innovators who see these trends. So they were indeed innovating. That, however, leads to the more interesting question of why weren’t any of these innovations successful?

The foundation for my understanding of innovation in a startup versus a corporate behemoth lies mostly in an excellent business book on innovation, “The Innovator’s Dilemma” by Clayton Christenson. It is a book I highly recommend all technology entrepreneurs should read. Its the closest thing I’ve found to an engineering approach to understanding the force of innovation and how it relates to big entrenched companies versus startups.

Christenson divides innovation into two broad categories, sustaining and disruptive. His theory is that big companies are amazing at the former and terrible at the latter. Sustaining involves improving on current technology such as increasing data density on a hard drive platter. Disruptive technologies are “fringe” technologies that are usually “low end” (or at least initially so) the PC versus the minicomputer.

The key to understanding this is that large companies ignore disruptive technologies because it is the right thing for them to do. All of the business structures, processes, culture, and institutions will have been rightly structured to maximize profit and growth for the company. Disruptive technologies, by their nature, will produce little initial profit and revenue (relative to the large company) and will only cater to the “worst” low end customers of the large company.

I mean “right thing to do” from a classic business standpoint. Its the driving requirements of profit and growth. Improving the current technology by adding features, power, or general “goodness” are what allows the company to satisfy its most important and high profit customers. Clearly catering to your best customers is a good thing. A disruptive technology, like PCs during the minicomputer era, would have been interesting to the visionaries in the company but would not have satisfied the requirements of the “good” highest profit customers. Even if the minicomputer company had tried to supply this new “low end” product, all of the internal structures of the company would have been aligned against it. Not because it didn’t have the potential for great future success, but because in the present it was diverting effort from the highest profit, highest margin business, and from a “bottom line” standpoint any profit and growth would have seemed trivial.

Startups have two primary advantages. The first advantage is that the profit and growth generated by a disruptive technology, while trivial to a large company, will be quite interesting to a startup. The second advantage is that startups are directly coupled to the market for their disruptive technology. Startups will do anything to make that disruptive technology “fly”, leading to the sense of nimbleness that is really mostly borne out of desperation. Where a large company will cancel a disruptive technology project after several quarters of “insignificant” revenues, most startups will see that same income as great success and carry on.

How are the “Goliaths” toppled? Over time the “sustaining” innovation factor continues to apply to the new “low end”, disruptive technology. This disruptive technology begins to become good enough for more and more of the market originally satisfied by the large incumbent. As the disruptive technology eats at the “low end” of the big companies market, this “squeeze” forces them to focus more and more on the highest profit/margin cstomers. Eventually, the large incumbent innovates itself right out of its own market via “sustaining” development, while the new technology now satisfies all the needs of the market at a lower cost. The key is something Christenson says a few times in his book, that good companies can fail by doing everything right.


Interesting data flow

June 3rd, 2008 . by mikepk

In the embedded summize results I made in this post about politics the rapid fire tweets are counting down the required delegates for Obama to clinch the nomination. It’s kind of odd, you can almost hear a crowd of people counting down, a slow motion times square on new years eve. It’s a really interesting pattern.


Feedvolley

June 3rd, 2008 . by mikepk

Recently I’ve been playing with our stream output and messing with different publishing models, like injecting it into blog posts directly. These were mostly just experiments to get a feel for different ways of displaying Grazr content aside from our traditional “super-widget” view.

I stumbled across this service feedvolley that basically takes feeds and turns them into nicely formatted web pages (most of the themes are modeled after Tumblr). This isn’t something that’s hard to do with code, but feedvolley makes it quick and easy to play around with generating sites, and the addition of themes is nice. Here’s my “Apple News” stream in feedvolley.

It may seem counterintuitive to turn feeds into pages, but feeds can be difficult for people to understand and pages are an accessible type of content for most. It becomes especially interesting when you think of processed or filtered feeds, feeds that have no direct analog back to a particular web page. A clear example would be our streams, the amalgamation of lots of different sources.

It’s interesting to get a feel for what these new pages are like. They are something new with different purpose than their original sources.


Scoble Feedback

June 1st, 2008 . by mikepk

I wasn’t expecting this kind of a response from Robert Scoble to my comments on Mathew Ingram’s Blog regarding Twitter and their architectural issues. I really honestly appreciate the feedback on Grazr, even if it’s painful for me to hear as one if it’s creators.

First, I want to say, Grazr is still here. We have lots of users, just not as many as we’d like and not on the growth curve we’d been hoping for. We’ve been trying to evolve and iterate our service to find the elements of it that are compelling, what it “wants” to be. One of the truths of startups is that you rarely “hit it big” with your initial idea. Twitter had no idea what they were onto when they first launched the service. Flickr started as an online game for girls and it took them time to find their niche. The key is accepting feedback and looking for the aspects of your technology that people find interesting and moving emphasis. We are still very much in this process.

Robert, thanks for the feedback. What you’ve pointed out is pretty much an exact list of the issues we’ve identified as we’d planned for our next version of Grazr, one we intend to launch in a few months. The strength of our core team is the technology skill-base, which in a lot of ways gives us the opposite problem as Twitter. Our architecture, services and scaling are extremely solid, but at the same time we’ve brought in some new people to help us redesign, re-articulate and relaunch the service in ways we’re confident are going to be much more consumer-facing and understandable.

I’ll be very interested in your thoughts on the new version. I’ll let you know when we’re ready, I would love to get more (albeit brutal) honest feedback :)

(I cross posted this to our company blog Feedonomics as well)