Dino on a Bike

Seeing Long Term Technology Adoption as Evolution

Filed under:

Much like an evolutionary tree our goal in technology adoption is to continue to move forward and evolve, rather than getting caught in a dead end.  In the natural world, becoming bigger can be good but can lead to extinction events should the environment or food source change.  Right now we are in a technology Jurassic period; oxygen and plants are plentiful and everyone can have wildly different ways to succeed.  That said, let's examine the barriers to success as well as competitive advantages and the criteria we should use as predictors. 

  1. Complexity
  2. Documentation
  3. Cost
  4. Scarcity
  5. Success Rate
  6. Community

1. Complexity

If a platform or language are complex (Drupal & Ruby are possible examples here) adoption will be slow.  The smarter you are, the less likely you are to see this issue, as complexity is relative.  However on the whole this hurts because it reduces the pool of available workers and generally pushes up rates and cost.

2. Documentation

The more documentation that is publicly available, the more chance of overcoming any issues with Complexity, helping to facilitate growth in the worker pool.  This is generally a sign of a highly active Community, because it involves not just engineers but people who generally play support roles.  This is an interesting lever, as it's relatively easy to influence (write more documentation) and yet it's value ages rapidly as the technology evolves.

3. Cost

As a technology becomes more successful, the available pool of workers is reduced and wages increase.  This is inevitable, as learning of new technology takes months or years, while the demand can grow as fast as word of mouth can recommend it.  Initially in this phase, the market can and will absorb the increased costs - employers and clients will pay more - but eventually cost increase will cause the demand itself to wane, but this occurs gradually, first as a reduction of the number of businesses willing (and able) to pay the prevailing rate, and then eventually starvation.  This is a relative measure based on the environments that can be accessed.  Looking at Drupal as an example, there is plenty more being paid by Oracle customers for less value, but if Drupal vendors can't reach Oracle markets and continue to need to compete with the less expensive options (like WordPress) they face stiff competition and will eventually be outcompeted.  I believe targeted education, such as vocational programming, is a way to artificially keep costs down, though this needs to be fixed on a market-level rather then just for an individual employer.

4. Scarcity

Scarcity in the workforce, and the corresponding increase in costs is the precursor of scarcity for the technology as a solution that is available to solve problems.  If there aren't enough people to build websites in Drupal, they will be built on other platforms, resulting is larger utilization for the most available platforms.  This availability/scarcity of workers for a platform is amplified over time, because any project is a group effort.  Every time a platform is used to solve a business problem more people are exposed to the technology and build it into their consciousness as a possible solution for their next project.

5. Success Rate

Every time a technology succeeds on a project regardless of the reason, that technology falls into the "win" category for everyone to work on the project.  Every time a project fails, the technology is invariably linked to failure and is less likely to be accepted as a viable solution for the next project.  This means success rate on a market-level (not just individual companies) combined with scarcity/abundance is a key factor in determining future total usage and community.

6. Community

There are a number of measures of community including: 

  1. total usage (how many sites/developers) - votes for your software
  2. code contributions - the engine of forward progress
  3. organizational infrastructure - likelihood the evolution path will be a smart one
  4. community events - engagement

Looking at this from an evolutionary stand point, total usage is the most important stat, as "winning" should be defined as the being the most prolific platform.  Being the "best" is subjective, and evolutionarily speaking is less important than being "more".  Code contributions should be equated to how much evolutionary potential there is, which is an important factor, but only represents future potential.  Organizational structure is less important, though I would liken it to intelligence - how well can we use the tools we have at our disposal?  Community events are an indicator of engagement and show potential for increasing usage and code contributions.


Ultimately technologies that want to survive should pay close attention to these levers and predictors.  Programmers, technologists and companies that want to be on a winning branch of the evolutionary tree should as well.  History and nature have not been kind to those who fail to adapt.

Date posted: October 29, 2014


First, All the best and thanks for sharing your ideas. My stand is to keep the complex new releases for the ones who have time to learn them and re-learn them and of course for the one who created them. At the same time, great work had been put into Drupal so far, but I am considering to keep using Drupal 7.

I'm with you.  I actually think that Drupal has a great future, but only for the evolutionary lines that start moving into Oracle (SAP, etc.) dominated "geography".  On those continents Drupal is fast, nimble, and big enough to compete with the incumbents.

My point was simply that the more complex it gets, the harder it will be to follow-up. Let's see what happens, God willing.

Add new comment

Restricted HTML

  • Allowed HTML tags: <a href hreflang> <em> <strong> <cite> <blockquote cite> <code> <ul type> <ol start type> <li> <dl> <dt> <dd> <h2 id> <h3 id> <h4 id> <h5 id> <h6 id>
  • You can enable syntax highlighting of source code with the following tags: <code>, <blockcode>, <cpp>, <java>, <php>. The supported tag styles are: <foo>, [foo].
  • Web page addresses and email addresses turn into links automatically.
  • Lines and paragraphs break automatically.

Metal Toad is an Advanced AWS Consulting Partner. Learn more about our AWS Managed Services

About the Author

Joaquin Lippincott, CEO

Joaquin is a 20+ year technology veteran helping to lead businesses in the move to the Cloud. He frequently speaks on panels about the future of tech ranging from IoT and Machine Learning to the latest innovation in the entertainment industry.  He has helped to modernize software for industry leaders like Sony, Daimler, Intel, the Golden Globes, Siemens Wind Power, ABC, NBC, DC Comics, Warner Brothers & the Linux Foundation.

As the CEO and Founder of Metal Toad, an AWS Advanced Consulting Partner, his primary job is to "get the right people in the room".  This one responsibility is cross-functional and includes both external business development functions as well as internal delegation and leadership development.

A UCLA alumni, he also serves in the community as a Board Member for the Los Angeles Area Chamber of Commerce, the Beverly Hills Chamber of Commerce, and Stand for Children Oregon - a public education political advocacy group. As an outspoken advocate for entry-level job creation in tech he helped found the non-profit, P4TH, an organization dedicated to increasing the number of entry-level jobs in the tech industry, and is in the process of organizing an Advisory Board for the Bixel Exchange, a Los Angeles non-profit that provides almost 200 tech internships every year.


Have questions?