Skip to main content

What competes with an iPad?

Well it's that time of year again,  Consumer Electronics Show in Las Vegas time, where all the companies roll out their iPad killers (circa 2010 & 2011).  If it were circa 2008 the theme would be iPhone killers, but we have progressed as a society.

One great quote I read on the web was from Steve Martin in reference to CES - "Saw large wooden device that can fling boulders over castle walls. iPad killer."

There are great minds trying to help companies unseat the Great and Powerful Oz ... uh Jobs, but even they are missing the silver slippers (that got ruby-ized for the Technicolor movie).  Note dear reader that I have a personal misconception that all allegories in America stem from the Wizard of Oz and I subscribe to the Monitery reform allegory of Frank Braum.
I have gone so far as to require people on my teams to watch the movie and eat popcorn in order to better understand the idioms of their village idiot.

Quick Toto, into the twister (worm hole) and back to the CES, where the theme repeats like an album at the end of the track.  For you digital natives - in old school tech, just after the steam punk tech died out and we got the 1950s good nuke generation (power so inexpensive it would not be cost effective to meter it) the music player of the day was a turn table and we had several media file formats 45s, 78s or the LP (that means long playing, about an hour).  Oh - wait, wrong exit, back into the twister... 2010... no 2011 is our exit.  It is not the iPod killer CES we wish to see, its the iPad CES we are looking for, pod, pad, "you say potato, I say patato - let's call the whole thing off".

Back at the 2011 CES the theme is iPad killers - or slate computers.  A whole new industry just materialized in front of Steve Jobs' in 2010 as he waved his magical wand (with an Apple logo at the tip) and created the elusive new market segment that couldn't be successful. Yet here we are one year later and it appears that the segment is successful.  Apple stock has continued to rise.  The yellow brick road leads to Cupertino.

Andy Ihnatko gives us Lessons at CES - how your tablet can compete with iPad. He list over 10 lessons to help competitors run to catch up with the wizard.  However I think he misses the key.

Great lessons in the play book to create an iSomething product killer. But there is a repeating meme here. I keep hearing the melody repeat but at a different pitch. Oh... I think we are in a fugue! So what is the subject of this fugue, the beginning point, the pattern's purpose?

It can be traced back to 2001, when the Great Oz stepped out from behind the curtain and presented the eHub strategy. The key to understanding the whole formation of the Land of Oz. It is the one thing that all other companies creating their iSomething replacement keep missing. It is the key to happiness that Dorthy is looking for.  The key she finds it in her own backyard. It is what makes the grass in Kansas greener than in Colorado. (An aside - the grass is always greener where you water it.) Its virtue is simplicity itself.

The eHub strategy is about creating an eco-system. Not one product. Not one device. An interconnected, interdependent, well integrated ecosystem of many products and services and a holistic land where not just one wizard was capable of printing money - but a land where many people could work and play. A land that gives people Autonomy, Mastery and Purpose (thanks Dan Pink). A land that maximizes Happiness (my core value).

The 2001 MacWorld keynote where the wizard in black turtel neck sweater steps from behind the curtain to describe the land.

  Related Post:  Bashing the iPad - But will you purchase?

Post a Comment

Most Popular on Agile Complexification Inverter

Exercise:: Definition of Ready & Done

Assuming you are on a Scrum/Agile software development team, then one of the first 'working agreements' you have created with your team is a 'Definition of Done' - right?

Oh - you don't have a definition of what aspects a user story that is done will exhibit. Well then, you need to create a list of attributes of a done story. One way to do this would be to Google 'definition of done' ... here let me do that for you: Then you could just use someone else's definition - there DONE!

But that would be cheating -- right? It is not the artifact - the list of done criteria, that is important for your team - it is the act of doing it for themselves, it is that shared understanding of having a debate over some of the gray areas that create a true working agreement. If some of the team believes that a story being done means that there can be no bugs found in the code - but some believe that there can be some minor issues - well, …

Elements of an Effective Scrum Task Board

What are the individual elements that make a Scrum task board effective for the team and the leadership of the team?  There are a few basic elements that are quite obvious when you have seen a few good Scrum boards... but there are some other elements that appear to elude even the most servant of leaders of Scrum teams.

In general I'm referring to a physical Scrum board.  Although software applications will replicated may of the elements of a good Scrum board there will be affordances that are not easily replicated.  And software applications offer features not easily implemented in the physical domain also.

Scrum Info Radiator Checklist (PDF) Basic Elements
Board Framework - columns and rows laid out in bold colors (blue tape works well)
Attributes:  space for the total number of stickies that will need to belong in each cell of the matrix;  lines that are not easy eroded, but are also easy to replace;  see Orientation.

Columns (or Rows) - labeled
    To Do
    Work In P…

Webinar: Collaboration at Scale: Defining Done, Ready, and NO.

I was invited to participate in a Scrum Alliance Webinar.  Maybe you would like to listen to us in a discussion of techniques to collaborate at scale (remotely and with many people).  The topic is one that I've got some experience in discussions - yet I never seem to get to done...
Collaboration at Scale: Defining Done and Ready and NO for Distributed Teams
With Joel Bancroft-Connors, Agile Organizational Coach; David A. Koontz, Agile Transition Guide; and Luke Hohmann, CEO and Founder of Conteneo, Inc.

14 February 2018 11 a.m. ET (USA).

The Scrum Guide is pretty clear on the criticality of the definition of Done: "When a Product Backlog item or an Increment is described as "Done," everyone must understand what "Done" means. However, the Scrum Guide ALSO says that the definition of Done can "vary significantly per Scrum Team." This leads us to examine when and how the definition of Done should vary, how distributed teams should cr…

A T-Shaped 21st Century Knowledge Worker

Knowledge workers in the 21st Century must have many areas of deep knowledge, while also be capable of collaboration across multiple other domains with dissimilar T-shaped individuals.  This description of a person is a metaphor.  Compare it to the shape of the "I" in the classic saying there is no "I" in Team.

I first read about Scott Ambler's term "Generalizing Specialist" - but it's so hard to remember the proper order of the words... get it backwards and it has an inverted meaning... T-Shaped is easier to remember. 
A generalizing specialist is someone who:
Has one or more technical specialties (e.g. Java programming, Project Management, Database Administration, ...). Has at least a general knowledge of software development. Has at least a general knowledge of the business domain in which they work. Actively seeks to gain new skills in both their existing specialties as well as in other areas, including both technical and domain areas.  General…

A FAILURE to Communicate

I was working with a failing team some time ago.  I use "failing" to describe the outcome of the team - not the people on the team.  Are you OK with that description?

An issue arrose in the stand up - a team member that was to verify the quality of a procedure did so and reported that there were a few records that didn't match expectation in the data set.  Upon inquire the number of records not matching was over 2000.  Most people acknowledged immediately the exaggeration - I could tell by the laughter.  After about 10 minutes of discussing the details of the problem - it appeared the team had a handle on the specific situation.

I stopped the discussion and inquired if they could name the impediment.  One team member did a great job of describing the impediment as a _communication gap_.  Wonderful - I could work with that - the problem had a name and it didn't include anyones Proper Name.

"If the problem has a first name; we are going to have a problem."