Skip to main content

Is Time-to-Market really a Key Differentiator?

Why do some product win in the market place and some lose?  Is being first to market the key distinction between winning and losing?

The Agile software development movement has this one aspect (time-to-market) as key differentiator.  Many surveys note this aspect as a reason to adopt Agile methods.  Business people resonate with this value proposition.  The Lean Startup movement has this within its core.  It appears just common sense.  But is it good practice - is it a true cause and effect relationship?  If one is first in the market place with a new product, will it capture market share and become the de-facto standard product in the market segment?

Take the case of the cookie - the Oreo Cookie (introduced in 1912) - have you heard the back story?  It was the perhaps a knock-off of the Hydrox cookie (introduced in 1908), the first in the market segment, yet always labeled "imitator" and never a strong competitor (Oreos to Hydrox: Resistance is Futile).

It certainly did not work for Apple Computer in 1985 when they introduced the world to a computer for the rest of us.  Their graphical user interface was new and created a key differentiator, perhaps the key innovation since they had created a new market segment with the introduction of the personal computer in 1977 (see Apple History Timeline).  Yet Apple consistently a first to market innovator, appears to always run in second place to Microsoft.  That is until very recently (the post PC era).

Why It Feels Like We're Falling Behind It can take years to notice a life-changing invention. - Motley Fool

The typical path of how people respond to life-changing inventions is something like this:
  • I've never heard of it.
  • I've heard of it but don't understand it.
  • I understand it, but I don't see how it's useful.
  • I see how it could be fun for rich people, but not me.
  • I use it, but it's just a toy.
  • It's becoming more useful for me.
  • I use it all the time.
  • I could not imagine life without it.
  • Seriously, people lived without it?
This process can take years, or decades. It always looks like we haven't innovated in 10 or 20 years because it takes 10 or 20 years to notice an innovation.

  One aspect of the difference between first movers and the rest of the pack is not the timing of the introduction (being "first") but in having a better and more compelling story.  Much of the product story has to do with marketing, distribution, partnerships, and customer satisfaction and adoptions of the product story as their own personal story.  A case in point the Teddy Bear.

Steiff Billy Possum
A great story, the origin story of the Teddy Bear is in pod-cast audio on 99% Invisible.  It is told from the perspective of the second mover - the air-apparent to the thrown of the assumed temporary Teddy Bear toy - Billy Possum - the next big thing.  This toy was designed to succeed the outgoing president's (Roosevelt) plush toy with the incoming president's (Taft) product designed and marketing flop toy - a plush possum.

Which would you purchase for your child to play with - a teddy bear or a billy possum?

How's this for marketing - and the rest of the story is not for youngins.  While he would not shoot the bear - doesn't mean he wouldn't eat the bear.


See Also:  
51 Most Popular Tech Gadgets through the Years - Popular Mechanics
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: http://tinyurl.com/3br9o6n. 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
    Stories
    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."

I&#…