How to avoid simplistic conversations about disruption?
This post is about some of the myopic views on disruption in financial services (or any other vertical for that argument), and why I am getting a bit tired of...
The second simplification of the disruption discourse is the lack of inclusion of the macro-forces. Some of the macro-forces deeply driving what’s going on are:
- Technology macro-force. Here is where inter-connectedness hits hardest. However, this is probably the easiest macro-force to deal with, as technology will take care of itself, as it always has. Open source and other collaborative models will only speed-up that self-care of technology: standards will emerge almost naturally, by natural selection, or my monopolistic interventions.
- Regulatory macro-force. Regulation is still very high on the agenda of financial institutions, and one can only expect that more is to come, especially on the area of data capitalism, handling of personal and corporate data, and even data ethics. After having digested the regulatory impact of the 2008 financial crisis, many are tempted and seduced to jump back with relief into innovation. The blockchain hype is a great excuse for claiming one is busy with the future state of things. Nothing could be further from the truth
- Geo-political macro-force: Grexit, Brexit, Terrorism, War, Surveillance, climate, and other crisis that can pop-up at any moment in time, with their potential of killing overnight all the innovation plans and ambitions.
- Eco macro-force: the acknowledgement that our organizations don’t operate in isolation, that we have to evolve from ego-businesses to eco-businesses, not only extracting value out of the ecosystem for our sole and own benefit, but that we are part of a reciprocal non-zero-sum game with an unspoken desire to save humanity.
The third simplification is the omission of the time component of evolution. I strongly recommend you discovering the work of Simon Wardley and his “situational awareness maps”.
Different values are created by different versions of different technologies and value engines, each of them evolving at their own pace on the lifecycle of emerging to commodity/utility. For big organizations – like financial institutions – it is extremely difficult to map out the current state, let’s not even mention the ability to strategically decide where one wants to head for in different time horizons in the future.
The same situational awareness is not only needed for (existing) and new technologies, but also for existing and new regulations, geo- and eco- events and ambitions.
In the past many have been concerned with the “backward compatibility” of new services and solutions. Backwards compatibility with the existing footprint and practices in the market that is.
I believe there is room today to start thinking in terms of “Forward Compatibility”.
What is Forward Compatibility? It is a capability to plan ahead for gradual adoptionby the ecosystem, taking into account the different barriers mentioned above. This is about knowing HOW to get at the new destination:
- How you rally the main stakeholders of the ecosystem into a rigorous system and process innovation? Process innovation is different from process-, datamodel-, or messaging standardization. It is not about standardizing the existing and guaranteeing backwards compatibility with the existing. It is about co-creating a new reality.
- How you promote the evolution from the current model to the future model? In the case of distributed ledger technologies for example, it is not about a tabula rasa that will eradicate the existing, but how one evolves from for example a messaging hub-and-spoke paradigm towards business objects and lifecycles in the cloud, initially probably in one central database (one node), and then evolve to a peer-to-peer networks of many distributed databases or nodes (remember the Digital Asset Grid?)
- How to bootstrap this new reality taking into account the network effects to be created and promoted in the new P2P reality.
No disruption will happen without fundamental re-design – or better re-invention – of the end-to-end business processes:
- Organizations knowing where they want to get and defining and leading that journey;
- De-risking change throughout this journey;
- Making trade-offs in the breadth ànd depth of the destination;
- Moving beyond the atomic nature of the transaction. As mentioned an nausea in previous posts, it is not good enough anymore to enable (atomic) transactions, the challenge is to enable commerce, as an end-to-end process
Startups/Scale-ups who want to be part of this endeavor, will need to know how to “scale”: they will need to learn to appreciate the mechanics of growing a startup into a corporate. This growth process (and its associated growth pains) is very well described in the post “Go Corporate or go home” around the concept of legibility of on organization. The startup organizations – whether they like it or not – will need to become more legible, more predictable. The author makes a very solid argument why hierarchies are needed.
“The smaller a company is, the less they need to formalize anything, and the less the three levels — chain of command, business process, and culture — differ.”
As they grow, they will have to synchronize how they transform these three levels (chain of command, business process, and culture). It’s not only from small self-sufficient team into hierarchies; it is also growing into professional business processes, and evolving the social fabric and conventions.
Although startups, scale-ups, and corporate innovation sandboxes mimicking the startup culture “love to have and keep the flexibility, the cost of growth is scale, integration, and profitability.”
In this context, it is probably worth having a look at the post about the Transferwise culture (I could have taken any other scale-up for that matter) “We inspire smart people and we trust them”, and especially the comment on that post that talks about KPIs, product-level empowerment, about focusing on growth more holistically, actually removing bottlenecks and silos, empowering teams at the product level, and instrumenting themselves to be able to actually get granular feedback.
If possible – assuming you want to spend some quality time – read that post and comment after you have read “Go corporate of go home”.
So next time, when I hear you pitch about disruption, the end of banks/banking, collaboration/co-operation, or one or the other technology solving world hunger, please make sure you have an answer on how to get to your new destination. I would suggest you keep forward compatibility in mind.
(Post image: Joshua Nguyen on flickr)