Insight

Insight
Home > Insight > Easyriders lead by example (Published in Computing, March 2008)

Insights

Filter insights by:


« Back to Insight

Easyriders lead by example (Published in Computing, March 2008)

The motorcycle company Harley-Davidson knows its customers. As the firm’s web site says, it is one thing for people to buy your products; it is another for them to tattoo your company’s name on their arm. But that is exactly what Harley-Davidson’s most devoted customers do.
The company interacts with customers at numerous touchpoints: by phone, in the showroom, on the road, at bikers’ conventions and in shops that sell biker clothes featuring the Harley-Davidson logo.
However, arguably the best and most comprehensive portal into the Harley-Davidson world is the organisation’s web site. The insights the site offers into how Harley-Davidson sees and strives to interact with its customers have many implications for other industry sectors.
Few organisations can boast a web site that illustrates such a seamless relationship with customers. So many firms, even successful ones, make it painfully obvious that they see their customers as completely distinct from the business.
Loyalty cards and frequent flyer clubs try to offer the impression of belonging, sometimes fairly successfully though very often, you can see the blatant marketing motive too close to the surface.
Many organisations have specialised customer clubs and even children’s book publishers have created clubs, so that members can receive special information about their literary heroes.
While plenty of companies generate customer loyalty, not many achieve the level of customer enthusiasm Harley Davidson wins.
Maybe a vital point here relates to shared brand values it is not just the product itself that attracts people to Harley-Davidson, it is the fact that they see the product as a reflection of themselves.
But why doesn’t every brand inspire the kind of loyalty Harley-Davidson wins from so many of its customers?
The real reason is that many firms too easily lose sight of who their clients are and what they really want.
How often do you really take the trouble to see your company, services and products through the eyes of customers? And how do you become more customer-centric?
Firms need to place the customer at the heart of the business and ensure everything is done with clients in mind. Best practice here can be distilled into three key principles.
First, dedicate everything you undertake to meeting your customer’s needs. Ensure your staff share a passion for delighting customers and ensure all the services you provide, through whatever channel, have the client in mind.
Second, know and understand your market and learn to love it. If you do not love your market, or are not prepared to learn to love it, why are you doing your job at all?
Third, be agile. Yesterday’s sales are history; ask yourself what your customers are looking for now. IT managers need to ensure their staff and supply base are ready and willing to adapt.
Put such lessons into practice and you will help kickstart a new momentum in the business.

This article appeared in Computing on the 20th March 2008.

Please read more about our work in Customer Centricity.

1. INTRODUCTION
Application Integration is the biggest cost driver of corporate IT. While it has been popular to
emphasise the business process integration aspects of EAI, it remains true that data integration is a
huge part of the problem, responsible for much of the cost of EAI. You cannot begin to do process
integration without some data integration.
Data integration is an N-squared problem. If you have N different systems or sources of data to
integrate, you may need to build as many as N(N -1) different data exchange interfaces between them –
near enough to N2. For large companies, where N may run into the hundreds, and N2 may be more
than 100,000, this looks an impossible problem.
In practice, the figures are not quite that huge. In our experience, a typical system may interface to
between 5 and 30 other systems – so the total number of interfaces is between 5N and 30N. Even this
makes a prohibitive number of data interfaces to build and maintain. Many IT managers quietly admit
that they just cannot maintain the necessary number of data interfaces, because the cost would be
prohibitive. Then business users are forced to live with un-integrated, inconsistent data and fragmented
processes, at great cost to the business.
The bad news is that N just got bigger. New commercial imperatives, the rise of e-commerce, XML
and web services require companies of all sizes to integrate data and processes with their business
partners’ data and processes. If you make an unsolved problem bigger, it generally remains unsolved.
Users and software vendors have devoted huge efforts to tackling the N2 data integration problem.
The solutions available today can be grouped into four main levels of increasing sophistication and
power:
1. Hand coding of data interfaces
2. Source-to-target mapping and translation tools
3. Integration hubs and brokers
4. Full model-based integration
This article discusses the costs and benefits you can expect at each level.
1. INTRODUCTION
Application Integration is the biggest cost driver of corporate IT. While it has been popular to
emphasise the business process integration aspects of EAI, it remains true that data integration is a
huge part of the problem, responsible for much of the cost of EAI. You cannot begin to do process
integration without some data integration.
Data integration is an N-squared problem. If you have N different systems or sources of data to
integrate, you may need to build as many as N(N -1) different data exchange interfaces between them –
near enough to N2. For large companies, where N may run into the hundreds, and N2 may be more
than 100,000, this looks an impossible problem.
In practice, the figures are not quite that huge. In our experience, a typical system may interface to
between 5 and 30 other systems – so the total number of interfaces is between 5N and 30N. Even this
makes a prohibitive number of data interfaces to build and maintain. Many IT managers quietly admit
that they just cannot maintain the necessary number of data interfaces, because the cost would be
prohibitive. Then business users are forced to live with un-integrated, inconsistent data and fragmented
processes, at great cost to the business.
The bad news is that N just got bigger. New commercial imperatives, the rise of e-commerce, XML
and web services require companies of all sizes to integrate data and processes with their business
partners’ data and processes. If you make an unsolved problem bigger, it generally remains unsolved.
Users and software vendors have devoted huge efforts to tackling the N2 data integration problem.
The solutions available today can be grouped into four main levels of increasing sophistication and
power:
1. Hand coding of data interfaces
2. Source-to-target mapping and translation tools
3. Integration hubs and brokers
4. Full model-based integration
This article discusses the costs and benefits you can expect at each level.
1. INTRODUCTION
Application Integration is the biggest cost driver of corporate IT. While it has been popular to
emphasise the business process integration aspects of EAI, it remains true that data integration is a
huge part of the problem, responsible for much of the cost of EAI. You cannot begin to do process
integration without some data integration.
Data integration is an N-squared problem. If you have N different systems or sources of data to
integrate, you may need to build as many as N(N -1) different data exchange interfaces between them –
near enough to N2. For large companies, where N may run into the hundreds, and N2 may be more
than 100,000, this looks an impossible problem.
In practice, the figures are not quite that huge. In our experience, a typical system may interface to
between 5 and 30 other systems – so the total number of interfaces is between 5N and 30N. Even this
makes a prohibitive number of data interfaces to build and maintain. Many IT managers quietly admit
that they just cannot maintain the necessary number of data interfaces, because the cost would be
prohibitive. Then business users are forced to live with un-integrated, inconsistent data and fragmented
processes, at great cost to the business.
The bad news is that N just got bigger. New commercial imperatives, the rise of e-commerce, XML
and web services require companies of all sizes to integrate data and processes with their business
partners’ data and processes. If you make an unsolved problem bigger, it generally remains unsolved.
Users and software vendors have devoted huge efforts to tackling the N2 data integration problem.
The solutions available today can be grouped into four main levels of increasing sophistication and
power:
1. Hand coding of data interfaces
2. Source-to-target mapping and translation tools
3. Integration hubs and brokers
4. Full model-based integration
This article discusses the costs and benefits you can expect at each level
1. INTRODUCTION
Application Integration is the biggest cost driver of corporate IT. While it has been popular to
emphasise the business process integration aspects of EAI, it remains true that data integration is a
huge part of the problem, responsible for much of the cost of EAI. You cannot begin to do process
integration without some data integration.
Data integration is an N-squared problem. If you have N different systems or sources of data to
integrate, you may need to build as many as N(N -1) different data exchange interfaces between them –
near enough to N2. For large companies, where N may run into the hundreds, and N2 may be more
than 100,000, this looks an impossible problem.
In practice, the figures are not quite that huge. In our experience, a typical system may interface to
between 5 and 30 other systems – so the total number of interfaces is between 5N and 30N. Even this
makes a prohibitive number of data interfaces to build and maintain. Many IT managers quietly admit
that they just cannot maintain the necessary number of data interfaces, because the cost would be
prohibitive. Then business users are forced to live with un-integrated, inconsistent data and fragmented
processes, at great cost to the business.
The bad news is that N just got bigger. New commercial imperatives, the rise of e-commerce, XML
and web services require companies of all sizes to integrate data and processes with their business
partners’ data and processes. If you make an unsolved problem bigger, it generally remains unsolved.
Users and software vendors have devoted huge efforts to tackling the N2 data integration problem.
The solutions available today can be grouped into four main levels of increasing sophistication and
power:
1. Hand coding of data interfaces
2. Source-to-target mapping and translation tools
3. Integration hubs and brokers
4. Full model-based integration
This article discusses the costs and benefits you can expect at each level.
« Back to Insight