It’s not often that Game of Thrones provides a moment of insight into data exchange, but that’s what happened this week. I am just catching up with season six of the top rated HBO series; and when the “Kingslayer” Jamie Lannister walked back across a drawbridge, having failed to persuade the leader of the forces under siege in the castle to surrender, it made me think about permeable data.
In my last blog post I presented the idea that rather than trying to break down and remove the invisible walls that keep core customer data siloed and isolated in different parts and layers of the organization, we should let each group keep the keys to their (data) kingdoms, and benevolently grant access to the data to other groups and departments.
In the world of Game of Thrones, with its ever shifting alliances and loyalties, the one thing that remains constant is the need for information. That information is often delivered via messenger ravens, and occasionally through personal contact as the various characters meet and interact. On the face of it, Jamie Lannister’s interaction on the drawbridge may have been seen as a failure. Yet, the more I thought about it, the lowering of the drawbridge allowed some significant “permeable data” to flow between the two systems in play. Each commander shared a little about their intentions and reacted to information that the other one shared.
While Lannister may not have persuaded the besieged commander to surrender, he walked away with enough information to develop a way to later end the siege with relatively minimal casualties. And the commander of the castle knew more about his opponent, his strengths, and his thinking – even if he chose not to act on that information. Once that drawbridge came down, it was inevitable that data would be exchanged.
We need to lower our system drawbridges.
By making the data silo walls permeable, allowing the data to flow freely to and from the different repositories, a company can make the most out of its investment in the technology being used to garner that information, and keep the kingdom’s (data) monarchs happy at the same time. Data bridges allow the flow of information. Once enabled, the company can collect a piece of data once and share between systems, in a way that respects system ownership and allows each repository to use the data in the best possible way to fulfill its own line of business needs and tasks.
OpenText™ Experience Suite builds on this concept. It lets data flow between the various products in the Customer Experience Management portfolio, so vital information and assets can be connected from Digital Asset Management tools through to the Web Content Management and Optimization tools and on to Customer Communications and even the Call Center, where data around sentiment analysis can be fed back to the Web Content design team.
Each product can stand alone and address the needs of a particular line of business, or be an Enterprise content single source of truth. Yet by passing data between them, with other OpenText tools, or existing enterprise business systems etc., they can be the foundation of a fully connected continuous customer experience.