Four goals for the data-driven telco

Becoming a data-driven telco

There have been many case studies over the last five years demonstrating the disruption caused by “data-driven businesses”, i.e. those using insights to understand customers, automate processes, change their business models and drive new revenues. In the future, this concept will become an integral part of what it takes to compete successfully, allowing organisations to understand and run all parts of their operations, work with their customers and partners and take part in external activities in new ecosystems. This applies to telecoms operators as much as any other industry.

This research builds on a range of reports STL Partners has previously published on strategic topics related to telcos’ use of data, including:

This research turns to the practical topics of delivering on these strategic goals. The diagram below offers an overview of the drivers and barriers affecting delivery areas such as telco data management and machine learning (ML) in the short and longer term.

Drivers and barriers to being a data-driven telco

Source: STL Partners

Enter your details below to request an extract of the report

What capabilities should telcos develop?

Telcos are reasonably sophisticated users of data, but their particularly complex web of legacy systems requires a good deal of work around data management and governance to enable the extraction of data sets to give 360-degree view of the customer – and increasingly to provide training data for algorithms.

In the mid-term, telcos that are successful in selling IoT and becoming ecosystem players will require new A3 to deal with the increasing number of services, devices, price points and parties involved in providing service to a customer. Our research suggests that there is a range of new A3 technologies that can provide the automation and intelligence for this, as well as for the underlying data management processes.

In the longer-term, A3 will speed up decision making, impacting company strategy, new product and service creation, and customer experience. Humans will increasingly be supported by AI-, ML- and automation-powered tools in their decision-making. A similar progression will occur among competitors in telecoms, and in adjacent markets, increasing the complexity and speed of doing business. Besides integrating A3 into human workflows, working at increasing speed will depend on getting richer insights out of the available data with techniques such as small data and creation of synthetic data.

Capabilities for a data-driven telco

Source: STL Partners

 

Table of contents

  • Executive Summary
    • Capabilities telcos should develop over the medium term
    • What will telcos focus on in the mid-term?
    • Next steps
  • Becoming a data-driven telco
    • Short term drivers
    • Barriers in the short term
    • Long term drivers
    • Barriers in the long term
  • Availability of data
    • Use of data fabrics
    • Better data labelling
    • Rise of synthetic data
    • More intelligent data selection
    • Telco strategies for cloud usage
  • Equipping people
    • Augmented analytics and business intelligence
    • Decision intelligence
  • Work on governance
    • Governance across the telco
    • Agility in governance
    • Governance for AI and machine learning
    • Ethical governance
    • Improved measurement of governance
    • Governance in ecosystems
  • Index

Big data analytics – Time to up the ante

Introduction

Recent years have seen an explosion in the amount of data being generated by people and devices, thanks to more advanced network infrastructure, widespread adoption of smartphones and related applications, and digital consumer services. With the expansion of the Internet of Things (IoT), the amount of data being captured, stored, searched and analysed will only continue to increase. Such is the volume and variety of the data that it is beyond traditional processing software and is therefore referred to as ‘big data’.

Big data is of a greater magnitude and variety than traditional data, it comes from multiple sources and can be comprised of various formats, generated, stored and utilised in batches and/or in real-time. There is much talk and discussion around big data and analytics and its potential in many sectors, including telecommunications. As Figure 1 shows, analysis of big data can give an improved basis upon which to base human-led and automated decisions by providing better insight and allowing greater understanding of the situation being addressed.

Figure 1: Using Big Data can result in richer data insights

Source: STL Partners

This report analyses how telcos are pursuing big data analytics, and how to be successful in this regard.  This report seeks to answer the following questions:

  • When does data become ‘big’ and why is it an important issue for telcos?
  • What is the current state of telco big data implementations?
  • Who is doing what in terms of intelligent use of data and analytics?
  • How can big data analytics improve internal operational efficiencies?
  • How can big data be used to improve the relationship between telcos and their customers?
  • Where are the greatest revenue opportunities for telcos to employ big data, e.g. B2B, B2C?
  • Which companies are leading the way in enabling telcos to successfully realise big data strategies?
  • What is required in terms of infrastructure, dedicated teams and partners for successful implementation?

This report discusses implementations of big data and examines how the market will develop as telco awareness, understanding and readiness to make use of big data improves.  It provides an overview of the opportunities and use cases that can be realised and recommends what telcos need to do to achieve these.

Contents:

  • Executive Summary
  • Big data analytics is important
  • …but it’s not a quick win
  • …it’s a strategic play that takes commitment
  • How is ‘big data analytics’ different from ‘analytics’?
  • Opportunities for telcos: typically internal then external
  • Market development and trends
  • Challenges and restrictions in practice
  • What makes a successful big data strategy?
  • Next steps
  • Introduction
  • Methodology
  • An overview of big data analytics
  • Volume, variety and velocity – plus veracity and value
  • The significance of big data for telcos and their future strategies
  • Market development and trends
  • Challenges and restrictions
  • Optimisation and efficiency versus data monetisation
  • Telcos’ big data ecosystem
  • Case studies and results 
  • Early results
  • Big data analytics use cases
  • Examples of internal use-cases
  • Examples of external use cases
  • Findings, conclusions and recommendations

Figures:

  • Figure 1: Using Big Data can result in richer data insights
  • Figure 2: The data-centric telco: infusing data to improve efficiency across functions
  • Figure 3: Options for telcos’ big data implementations
  • Figure 4: Telco’s big data partner ecosystem
  • Figure 5: The components of a telco-oriented big data

The ‘Agile Operator’: 5 Key Ways to Meet the Agility Challenge

Understanding Agility

What does ‘Agility’ mean? 

A number of business strategies and industries spring to mind when considering the term ‘agility’ but the telecoms industry is not front and centre… 

Agility describes the ability to change direction and move at speed, whilst maintaining control and balance. This innate flexibility and adaptability aptly describes an athlete, a boxer or a cheetah, yet this description can be (and is) readily applied in a business context. Whilst the telecoms industry is not usually referenced as a model of agility (and is often described as the opposite), a number of business strategies and industries have adopted more ‘agile’ approaches, attempting to simultaneously reduce inefficiencies, maximise the deployment of resources, learn though testing and stimulate innovation. It is worthwhile recapping some of the key ‘agile’ approaches as they inform our and the interviewees’ vision of agility for the telecoms operator.

When introduced, these approaches have helped redefine their respective industries. One of the first business strategies that popularised a more ‘agile’ approach was the infamous ‘lean-production’ and related ‘just-in-time’ methodologies, principally developed by Toyota in the mid-1900s. Toyota placed their focus on reducing waste and streamlining the production process with the mindset of “only what is needed, when it is needed, and in the amount needed,” reshaping the manufacturing industry.

The methodology that perhaps springs to many people’s minds when they hear the word agility is ‘agile software development’. This methodology relies on iterative cycles of rapid prototyping followed by customer validation with increasing cross-functional involvement to develop software products that are tested, evolved and improved repeatedly throughout the development process. This iterative and continuous improvement directly contrasts the waterfall development model where a scripted user acceptance testing phase typically occurs towards the end of the process. The agile approach to development speeds up the process and results in software that meets the end users’ needs more effectively due to continual testing throughout the process.

Figure 5: Agile Software Development

Source: Marinertek.com

More recently the ‘lean startup’ methodology has become increasingly popular as an innovation strategy. Similarly to agile development, this methodology also focuses on iterative testing (replacing the testing of software with business-hypotheses and new products). Through iterative testing and learning a startup is able to better understand and meet the needs of its users or customers, reducing the inherent risk of failure whilst keeping the required investment to a minimum. The success of high-tech startups has popularised this approach; however the key principles and lessons are not solely applicable to startups but also to established companies.

Despite the fact that (most of) these methodologies or philosophies have existed for a long time, they have not been adopted consistently across all industries. The digital or internet industry was built on these ‘agile’ principles, whereas the telecoms industry has sought to emulate this by adopting agile models and methods. Of course these two industries differ in nature and there will inevitably be constraints that affect the ability to be agile across different industries (e.g. the long planning and investment cycles required to build network infrastructure) yet these principles can broadly be applied more universally, underwriting a more effective way of working.

This report highlights the benefits and challenges of becoming more ‘agile’ and sets out the operator’s perspective of ‘agility’ across a number of key domains. This vision of the ‘Agile Operator’ was captured through 29 interviews with senior telecoms executives and is supplemented by STL analysis and research.

Barriers to (telco) agility 

…The telecoms industry is hindered by legacy systems, rigid organisational structures and cultural issues…

It is well known that the telecoms industry is hampered by legacy systems; systems that may have been originally deployed between 5-20 years ago are functionally limited. Coordinating across these legacy systems impedes a telco’s ability to innovate and customise product offerings or to obtain a complete view of customers. In addition to legacy system challenges, interview participants outlined a number of other key barriers to becoming more agile. Three principle barriers emerged:

  1. Legacy systems
  2. Mindset & Culture
  3. Organisational Structure & Internal Processes

Legacy Systems 

One of the main (and often voiced by interviewees) barriers to achieving greater agility are legacy systems. Dealing with legacy IT systems and technology can be very cumbersome and time-consuming as typically they are not built to be further developed in an agile way. Even seemingly simple change requests end in development queues that stretch out many months (often years). Therefore operators remain locked-in to the same, limited core capabilities and options, which in turn stymies innovation and agility. 

The inability to modify a process, a pricing plan or to easily on/off-board a 3rd-party product has significant ramifications for how agile a company can be. It can directly limit innovation within the product development process and indirectly diminish employees’ appetite for innovation.

It is often the case that operators are forced to find ‘workarounds’ to launch new products and services. These workarounds can be practical and innovative, yet they are often crude manipulations of the existing capabilities. They are therefore limited in terms what they can do and in terms of the information that can be captured for reporting and learning for new product development. They may also create additional technical challenges when trying to migrate the ‘workaround’ product or service to a new system. 

Figure 6: What’s Stopping Telco Agility?

Source: STL Partners

Mindset & Culture

The historic (incumbent) telco culture, born out of public sector ownership, is the opposite of an ‘agile’ mindset. It is one that put in place rigid controls and structure, repealed accountability and stymied enthusiasm for innovation – the model was built to maintain and scale the status quo. For a long time the industry invested in the technology and capabilities aligned to this approach, with notable success. As technology advanced (e.g. ever-improving feature phones and mobile data) this approach served telcos well, enhancing their offerings which in turn further entrenched this mindset and culture. However as technology has advanced even further (e.g. the internet, smartphones), this focus on proven development models has resulted in telcos becoming slow to address key opportunities in the digital and mobile internet ecosystems. They now face a marketplace of thriving competition, constant disruption and rapid technological advancement. 

This classic telco mindset is also one that emphasized “technical” product development and specifications rather than the user experience. It was (and still is) commonplace for telcos to invest heavily upfront in the creation of relatively untested products and services and then to let the product run its course, rather than alter and improve the product throughout its life.

Whilst this mindset has changed or is changing across the industry, interviewees felt that the mindset and culture has still not moved far enough. Indeed many respondents indicated that this was still the main barrier to agility. Generally they felt that telcos did not operate with a mindset that was conducive to agile practices and this contributed to their inability to compete effectively against the internet players and to provide the levels of service that customers are beginning to expect. 

Organisational Structure & Internal Processes

Organisational structure and internal processes are closely linked to the overall culture and mindset of an organisation and hence it is no surprise that interviewees also noted this aspect as a key barrier to agility. Interviewees felt that the typical (functionally-orientated) organisational structure hinders their companies’ ability to be agile: there is a team for sales, a team for marketing, a team for product development, a network team, a billing team, a provisioning team, an IT team, a customer care team, a legal team, a security team, a privacy team, several compliance teams etc.. This functional set-up, whilst useful for ramping-up and managing an established product, clearly hinders a more agile approach to developing new products and services through understanding customer needs and testing adoption/behaviour. With this set-up, no-one in particular has a full overview of the whole process and they are therefore not able to understand the different dimensions, constraints, usage and experience of the product/service. 

Furthermore, having these discrete teams makes it hard to collaborate efficiently – each team’s focus is to complete their own tasks, not to work collaboratively. Indeed some of the interviewees blamed the organisational structure for creating a layer of ‘middle management’ that does not have a clear understanding of the commercial pressures facing the organisation, a route to address potential opportunities nor an incentive to work outside their teams. This leads to teams working in silos and to a lack of information sharing across the organisation.

A rigid mindset begets a rigid organisational structure which in turn leads to the entrenchment of inflexible internal processes. Interviewees saw internal processes as a key barrier, indicating that within their organisation and across the industry in general internal decision-making is too slow and bureaucratic.

 

Interviewees noted that there were too many checks and processes to go through when making decisions and often new ideas or opportunities fell outside the scope of priority activities. Interviewees highlighted project management planning as an example of the lack of agility; most telcos operate against 1-2 year project plans (with associated budgeting). Typically the budget is locked in for the year (or longer), preventing the re-allocation of financing towards an opportunity that arises during this period. This inflexibility prevents telcos from quickly capitalising on potential opportunities and from (re-)allocating resources more efficiently.

  • Executive Summary
  • Understanding Agility
  • What does ‘Agility’ mean?
  • Barriers to (telco) agility
  • “Agility” is an aspiration that resonates with operators
  • Where is it important to be agile?
  • The Telco Agility Framework
  • Organisational Agility
  • The Agile Organisation
  • Recommended Actions: Becoming the ‘Agile’ Organisation
  • Network Agility
  • A Flexible & Scalable Virtualised Network
  • Recommended Actions: The Journey to the ‘Agile Network’
  • Service Agility
  • Fast & Reactive New Service Creation & Modification
  • Recommended Actions: Developing More-relevant Services at Faster Timescales
  • Customer Agility
  • Understand and Make it Easy for your Customers
  • Recommended Actions: Understand your Customers and Empower them to Manage & Customise their Own Service
  • Partnering Agility
  • Open and Ready for Partnering
  • Recommended Actions: Become an Effective Partner
  • Conclusion

 

  • Figure 1: Regional & Functional Breakdown of Interviewees
  • Figure 2: The Barriers to Telco Agility
  • Figure 3: The Telco Agility Framework
  • Figure 4: The Agile Organisation
  • Figure 5: Agile Software Development
  • Figure 6: What’s Stopping Telco Agility?
  • Figure 7: The Importance of Agility
  • Figure 8: The Drivers & Barriers of Agility
  • Figure 9: The Telco Agility Framework
  • Figure 10: The Agile Organisation
  • Figure 11: Organisational Structure: Functional vs. Customer-Segmented
  • Figure 12: How Google Works – Small, Open Teams
  • Figure 13: How Google Works – Failing Well
  • Figure 14: NFV managed by SDN
  • Figure 15: Using Big Data Analytics to Predictively Cache Content
  • Figure 16: Three Steps to Network Agility
  • Figure 17: Launch with the Minimum Viable Proposition – Gmail
  • Figure 18: The Key Components of Customer Agility
  • Figure 19: Using Network Analytics to Prioritise High Value Applications
  • Figure 20: Knowing When to Partner
  • Figure 21: The Telco Agility Framework