Archive for November, 2010

Public Service Announcement #2

November 29th, 2010

But a moment ago I discovered that the word wont (not won’t as in will not (why does the “o” stick around anyway?))…where was I?…oh yes! Wont doesn’t mean what I’ve come to think it means:

wont /wɔnt, woʊnt, wʌnt/ : accustomed; used to
He was wont to rise at dawn.
(adjective, noun, verb) wont, wont or wont·ed, wont·ing

I thought it meant doing an unpleasant task. Like going through the drudgery of paperwork or some other obligation. I can see that I’ve internalized this definition because the context of the word is almost always used to explain a repetitive or monotonous task (hence being used to it)–tasks which are innately unpleasant.

I know this is how words pick up definitions as language evolves. If I recall correctly (I’d double check this), that’s how terrific branched off of terror to mean something good. Maybe I can do some language analysis and figure out what words will morph into the future (clearly for the purposes of domain squatting).

Things You Should Probably Ignore

I’m innoventing!

November 16th, 2010

I just read a pretty interesting article by Robert Scoble entitled “Why Google can’t build Instagram”. It centers on why big companies have trouble innovating. In this particular instance, the company is Google, which is somewhat vindicating to me for reasons I won’t get into now.

I have an ever increasing interest in both innovation practices and how large companies operate and found a lot of interesting theories related to both there-in. Allow me to paraphrase the important points:

  1. It’s difficult to innovate without small teams
  2. It’s difficult to innovate without reducing scope
  3. It’s difficult to innovate when you have lots of groupies
  4. It’s difficult to innovate with pre-established infrastructure
  5. It’s difficult to innovate if you have to support everyone from the get-go
  6. It’s difficult to innovate without leveraging the work of outside parties
  7. It’s difficult to innovate behind an iron curtain (although Apple seems to handle it well)
  8. It’s difficult to innovate without Eric Ries-style “lean methodology”

These is a direct translation of the 8 reasons that Google has trouble with innovation listed in the article (and I’d encourage you to read them if you haven’t already). There is some overlap and I don’t necessarily agree that Google can’t do some of them (particularly the last two), but I think the key idea present in all of these points is:

It’s difficult to innovate unless you can move quickly and flexibly.

As companies get larger, they tend to become more bloated with bureaucracy, process, and opinions, which naturally slows down innovation. Consequently, as mentioned in the article, it can come to the point where the only way for a large company to be “innovative” is to exert its power (and not it’s agility) by buying smaller companies or doing things that are prohibitively expensive/risky that could easily destroy a weaker company.

So the question to ask is, how can large companies continue to innovate?