Showing posts with label Evolution. Show all posts
Showing posts with label Evolution. Show all posts

Monday, November 21, 2011

Spotting the Next generation ...

For the best part of a decade I've worked on how business activities evolve from genesis through to products to commodity. As activities evolve then practices (such as management methods) that are applied also have to change which is why one size never fits all.

I've also demonstrated how this process of evolution creates a cycle, with commoditisation enabling further genesis (as in innovation of new activities) and the importance of inertia barriers in regulating this cycle.

These cycles also appear at the macro-economic scale and they're known as Kondratiev waves, however even more localised cycles (i.e. specific to an industry) tend to be associated with organisational change.

Hence with the commoditisation of the means of mass communication (i.e. the internet), new forms of organisation appeared known as Web 2.0. These companies had different activities, practices, strategies and structure to the more traditional, enterprise organisations that existed before.

In general terms, this cycle of evolution and its interaction with inertia barriers creates three economic eras - peace, war and build. During the peace era, sustaining change is particularly high, companies fight to maintain their relative position and inertia barriers to change help support the status quo.

The war era occurs when an activity evolves from one state (such as products or rental services) to another (such as commodity or utility services) and during this time disruptive change dominates whilst inertia barriers become a hindrance to survival. Companies literally are fighting to survive, often against their own internal culture and inertia to change.

So during the last IT war, caused by the evolution of the means of mass communication, these new web 2.0 organisations formed and the rate of disruptive change was high. Those traditional, more enterprise like companies that were impacted but survived the war had adapted and learnt many of the lessons of web 2.0. Today, social networking, social media, rich internet applications are the norm.

However, cloud computing - which is nothing more than the evolution of a wide range of activities from products (and rental services) to commodity (and utility services) - has initiated a new era of war.

The models predicted (and this is what we found) that there are three main forms of IT organisation in the wild - the traditional enterprise who have adapted, the web 2.0 players and a new breed of Next generation companies. The practices, activities, strategies and organisational memes of these Next generation are the ones which will tend to diffuse and dominate our industry.

The underlying framework, models and principles of how this works is part of a report I'm finishing for the LEF. Including in-depth surveys of over a hundred companies, it provides a reasonable hypothesis of organisation evolution across activities, practices and strategies. I say reasonable because it's more than postulation as there is data that demonstrates the pattern but this is not peer reviewed, the sample sizes are small and hence its only a reasonable hypothesis and requires a good dose of scepticism.

I'm not going to go through the report but I thought it might be useful to just comment on how to identify the Next generation in general terms.

If your organisation :-
  • embraces change and is acutely aware of inertia barriers
  • has primary goals based upon disruption of existing markets and growing ecosystems rather than a focus on profitability and growth into emerging geographical markets
  • views commoditisation not as a liability but an opportunity
  • operates through small, highly empowered teams building and creating services
  • builds and exploits ecosystems by enabling others to build upon its services
  • uses data analytics rather than metrics to determine action
  • continually challenges and removes processes
  • understands evolution and avoids one size fits all mentality
  • builds distributed systems designed for failure that use commodity IT where possible
  • considers itself to be as, if not more, efficient than Amazon
  • games behaviour both internally and externally
  • views culture as malleable and focuses on talent density
  • views open source as a tactical weapon
  • is seen by others to be simultaneously highly innovative, customer focused and efficient despite what Porter said on the subject
... then you're Next generation. If this isn't you, you're not. If you're not, then just hope this war doesn't stretch into your industry or that IT isn't a major barrier to entry into your space or this hypothesis is completely wrong.

I've provided a comparison between the traditional enterprise and the next generation in the following table.



Along with retail, media, travel firms and others who have already suffered in the last war - we should see software products & hosting, insurance and retail banking dragged firmly into this one.
Of course, along with this war era comes a build era, a golden age where the genesis of new activities flourishes and we see periods of frenzied growth.

The cycle is continuous, and the next major war after this one should be related to the commoditisation of the manufacturing process itself ... now, that'll be a big one. For me, this is personally important as it creates an opportunity to test the hypothesis.

What we should see as the means of manufacturing becomes more of a commodity (driven by 3D printing, printed electronics and hybrid printers) is a high degree of disruption in manufacturing industries as inertia barriers to change are broken by new entrants whose practices will be remarkably different from the existing players. The practices of these Next Next generation of company will diffuse and become the norm.

If this hold true, then I'll have enough to finally put the work up for peer review - having initial data (covering 4,000 data points), a hypothesis which describes a pattern from that initial data and has been preliminarily shown to exist in this current war through a survey (providing in total over 6,000 data points across 100 companies) and finally a pattern which is predictive.

If it doesn't and is falsified then it's back to the drawing board. The downside is I'll have to wait many years (possibly as much as a decade) before the next war starts ... if only companies were more like bacteria that I could grow in a lab.

Sunday, September 25, 2011

Strata Conference

The O'Reilly Strata Conference NYC has now finished and I have to say it was a blast. The standard of speakers, corridor chat and the general environment was exceptionally high. If you're interested in speaking, they've already opened up the request for proposals for the Feb'12 event, so get writing.

There was something magical about the event in NYC created by a convergence of people, technology and ideas. I haven't seen a conference with this much buzz and excitement since ETech. You can guess that I was truly impressed, it was O'Reilly at its finest and that's a tall order given the very high standard of their conferences. If you missed the conference, then you can find many videos from the event on the O'Reilly channel.

I was also fortunate enough to be asked to speak, the video of my talk is below. In my session I covered commoditisation, innovation and the role of big data by examining some of my new research into the evolution of organisations. As per normal, the title of the talk is my usual Situation Normal, Everything Must Change and the talk itself is different from any other previous example i.e. the title applies to the talk itself.

By the way, if you have enjoyed my talks and you're interested in helping out with my research then please take 20 minutes to complete my online survey, as that would be really appreciated.

OSCON 2010: "Situation Normal, Everything Must Change"

Thursday, August 18, 2011

Hosting Con Keynote

I was very fortunate to be asked to give the opening keynote at Hosting Con 2011 covering commoditisation, business evolution, leadership and what the various tactical plays in the cloud computing space mean to hosting companies. The audience was fantastic, I had a great time and despite using excessive numbers of slides, no-one was hurt in the process.

Continuing on the theme from my OSCON tutorial, I've uploaded a summary set of slides which are highly condensed but give a taster to what we covered.

Alas, there's no video and as per usual I'm six years into writing my book and around 30% of the way there. The subject matter keeps on giving me more areas of interest to explore, so don't hold your breath for me to finish any time soon.

Wednesday, March 19, 2008

I'll huff and I'll puff and ... ohh I like how you've painted it.

Whenever I'm mapping out the activities (for example business processes) of an organisation, I try to use colour codes for the different lifecycle stages of an activity. I find this helps me when visualising what the organisation needs to do and how it needs to change.

It's just something I do. I've provided four images to show the colour codes I use.

Stage 1 - Innovation, First Instance
(click on image for larger size)

Stage 2 - First Movers, Bespoke examples
(click on image for larger size)

Stage 3 - Transition, Products
(click on image for larger size)


Stage 4 - Commodity.
(click on image for larger size)


It's worth remembering that any activity has an effect on the organisation. In the case of a created product the effect is overall on cashflow, however you could equally have a process whose effect is on the efficiency of operations and cost reductions.

Generally, any innovation should be built upon many commodity or transitional like activities. If it's not, you need to ask yourself why not?

Componentisation of systems into activities and use of commodity components where possible is a massive accelerator for innovation. It is the reason why I advocate using Service Orientated Architectures (SOA), Software as a Service (SaaS) and Enterprise Architecture (EA) frameworks like Zachman.

The speed at which a complex system evolves is much faster if it is broken into smaller stable components and hence organised into one or more layers of stable subsystems (for more on this read up on Howard Pattee).

If you:-
  1. take a system of k elements
  2. group every s number of k elements into a new component, l
  3. group every s number of l components into new component, m
  4. keep on repeating this grouping until you can't group any more
Then, with each component being considered stable, the rate of evolution of the system will be proportional to the log to base s of k.

To show this in action, consider the three little piggies building a house. Let's say each house requires 100,000 bricks and whilst the big bad wolf can blow down an unfinished item, any stable component is too strong to be blown apart. Our three little piggies will follow different strategies:-
  • Piggy 1 : Build the house in one go with each brick being a single component.
  • Piggy 2: Build stable components, each component containing 10 sub-components. i.e. 10 bricks = a line. 10 lines = a section of wall etc.
  • Piggy 3: Build stable components, each component contain 100 sub-components.
OK, let's say on average you can put together 1,000 components before the big bad wolf returns. Then :-
  • Piggy 1 : will never be completed.
  • Piggy 2 : will be completed by the 12th visit of the wolf.
  • Piggy 3 : will be completed by the 2nd visit of the wolf.
In general: build in blocks, use small stable components.

[NB: For simplicity of explaining the analogy, I've taken the initial act of combining 100 or 10 or 1 brick(s) into one component as creating one component. If you instead treat each brick as a component, then the times are Pig 1: Never, Pig 2: 112 visits, Pig 3: 102 visits.]

It sounds obvious, but knowing the lifecycle stage of an activity along with componentising systems which can be componentised is a necessary step to increasing innovation. In other words: if someone has already built a hammer, use it and don't rebuild it.

Equally essential is to use different methodologies at different stages of an activities lifecycle (it's not agile vs six sigma or networked vs hierarchical or innovation vs efficiency - it's a mix of each, all the time). In other words: get used to living with change.

Using such an approach you can balance the innovation paradox between the order needed to survive and the disorder needed to create a future.

In summary: build in blocks, use a hammer, expect the plan to change and don't forget to add a splash of colour.

Friday, February 29, 2008

GATTACA

Last year, Google invested in 23 and me, an organisation that specialises in genetic sequencing. Apparently, the company intends to create a genetic database that people can search for both personal and scientific reasons. As they say on their site: "unlock the secrets of your own DNA, today!"

This year, Google has unveiled its personal health records service. According to Nick Carr, future partners will include a "slew of hospitals and care providers, medical testing companies, pharmacy chains, and health insurers".

For some reason, I always get nervous whenever "the secrets of my DNA", "search" and "health insurers" are mentioned in close proximity to each other.

Out of curiosity, the 15th amendment states: "The right of citizens of the United States to vote shall not be denied or abridged by the United States or by any State on account of race, color, or previous condition of servitude".

Do you think you might need to add "DNA sequence" to that as well?