Branding your Lexus OSS

It’s one thing to be a ahead of your time. It’s another to change the future.”
Lexus
.

Do telcos need differentiated prestige brands, in much the same way as Lexus is to Toyota? Do they need to differentiate their bit and byte businesses from solution integration and again from apps/content, etc?

Telcos tend to be trusted providers of bit and byte and all manner of other carrier services that are unfortunately (or fortunately??) commoditising. Naturally enough, the telcos want to move up the value-chain into services such as solution integration, managed services, content provision, etc.

Being highly generalistic here, telcos don’t tend to have the same trusted name in delivering solution integration (SI) for customers as they do for leased lines for example. Even when they acquire respected SI’s, they tend to get subsumed under the umbrella brand and the respect gets diluted.

Each of these services that step up the value chain require different business models and skill-sets and cultures. Just as Toyota realised they couldn’t sell premium product under the Toyota brand and spawned Lexus, I wonder whether telcos need to lose the attachment to providing higher-value services under the umbrella brand?

With each of these differentiated brands, the requirements from their OSS and BSS tools also change. Sounds like an fascinating dilemma to me!

Read the Passionate About OSS Blog for more or Subscribe to the Passionate About OSS Blog by Email

2 thoughts on “Branding your Lexus OSS

  1. Hi Ryan,
    You’ve made an interesting point – I wonder then does having very different OSS requirements across a large telco business mean that different OSS systems should be utilised? Probably the practical answer today is ‘yes’, but maybe that’s not the best approach going forward? Appreciated the internal silo problem is significant but perhaps changing market pressures will drive them towards taking much more advantage of their large ongoing investments into OSS – it will be interest to watch!

Leave a Reply

Your email address will not be published. Required fields are marked *