-
Change, it’s what’s for dinner
I saw this cartoon the other day and it made me chuckle.
I like that instead of the typical ‘stupid user’ punch line it’s actually a very creative user that turned a shortcoming of the program into a benefit. I think it’s also a humorous example of how a kludgy workaround can morph into standard operating procedure.
On a somewhat related note I also found this article on Slate.com called “The Danger of Good Enough“. The name kinda says it all. If things are ‘good enough’ then it’s harder to launch something better as users are typically fine when things are good as opposed to when things suck and users are ripe to accept something better if it comes along. You also get a brief look at the history of the Internet pop-up ad.
And that got me thinking about the book “The Innovator’s Dilemma” which talks about why established companies can sometimes be unseated by newer, smaller companies. The book raises a lot of good points but I feel like it basically boils down to this, the less you have to lose the easier it is to swing for the fences. Because the focus of the book primarily on established players falling to up-and-comers it does give you the feeling upstarts never falter even though, like most endeavors, there are many more failures than successes.
What does this have to do with NLEs? Maybe a little. Maybe a lot. Maybe too much by way of excessive extrapolation. Certainly more than one way to skin a cat and between the three A’s, Lightworks and Blackmagic there is a lot of representation about how to go about things (both from a business standpoint and an end product standpoint).
