Last week both Serco and Capita announced their interim results. Not only did the two companies show a widening gap in terms of financial performance, but they also highlighted diverging business strategies.

Firstly, their financial performance in H2 2014 to date was very different:

Operating margin:

  • Capita has managed to stay on track to achieving at least 8% organic growth, net of attrition, for the full year 2014 (2013: 8%). It also stated that it expects to maintain its operating margin in the range of 12.5% to 13.5% for the foreseeable future
  • In contrast, Serco announced that the 2% organic growth in H1 2014 has turned into a mid-single digit decline in H2. This has been primarily due to reductions in volume of work in the Australian immigration contract but also due to contract losses and reduced volumes elsewhere. Serco expects to shrink significantly by 2016, with revenue reaching a nadir of £3 billion to £3.5 billion from a forecasted adjusted revenue of £4.8 billion in 2014. It expects to return to growth in 2017
  • Serco also announced a proposed equity rights issue of up to £550 million in the first quarter of 2015 to strengthen its capital structure
  • Capita announced that it has secured £1.63 billion of major new deals to date in 2014 (nine months). This is down by £1.27 billion year-on-year (largely accounted for by the signing of the £1.2 billion O2 mega deal in 2013). At £4.1 billion the bid pipeline is also lower on a sequential basis compared with £5.7 billion announced in July 2014. However Capita reports a strong win rate of one in two
  • Serco reported £900 million of contract awards since the half year to date. It also said that its current pipeline and win rate are considerably weaker than before

Secondly, the strategic directions of the two companies are diverging:

  • With its strategic review still ongoing, Serco announced that it is going to focus entirely on business to government (B2G) in the areas of justice and immigration, defense, transport, citizen services, and healthcare
  • In contrast, Capita aims to grow its private sector business and in particular in the customer management services (CMS) arena. Like Serco, it made a number of CMS acquisitions in the past few years including Ventura and parts of Vertex. Another growth target is its burgeoning legal business with the acquisition of Eclipse Legal Systems. It is also expanding its presence beyond its UK stronghold to countries such as Ireland and Germany
  • Serco will be divesting a number of businesses that are now non-core to its strategy. These include the Environmental and Leisure businesses in the UK, Great Southern Rail business in Australia, and the majority of its private sector BPO business which are mostly CMS businesses delivered by two companies that it acquired in recent years: Intelenet and The Listening Company
  • Capita has made 13 acquisitions to date in 2014 for £285 million, with more likely as it continues to expand or enhance its capabilities

Interestingly, both companies have also announced changes to their boards:

  • Alastair Lyons, Serco’s chairman has resigned
  • Capita’s CFO Gordon Hurst is stepping down following a 27-year stint at the company

Serco’s tale of woe began in 2013 when the British government discovered that it had been overcharged by Serco for offender tagging services to the Ministry of Justice (MoJ). The company is still recovering from the fallout more than a year after the issue first came to light, and having repaid more than £68 million of fees and gone through several reviews and management changes. It is ironic that Serco’s new board has chosen to focus on B2G services only, given that the troubles began in a government contract. That said, front line government services is and has always been at the core of the company’s business.

Serco has suffered from failures of governance and risk management. As it rebuilds itself, it will seek to enhance these significantly. In terms of business strategy, it will target growing opportunities in the government sector, as the pressures from aging populations and rising demand for services pushes governments to outsource more. Serco will seek to differentiate itself with its international approach, as part of which it will give its businesses a portfolio of services to go to market within specific regions of the world, to share experience and expertise.

Capita boasts of robust financial and governance structures and highly selective approach to opportunities that it pursues. Robust governance is highly needed given Capita’s aggressive acquisition strategy that has seen it take over more than a dozen companies a year for many years. Even with robust governance problems can still occur. For example, in its eagerness to win more government clients, in 2012 Capita acquired Applied Language Solutions (ALS), which had been awarded responsibility for courts interpreter services in England and Wales. For a while service delivery was less than smooth leading to the MoJ withholding fees in some instances and bad publicity in the press. Overall though Capita has benefited from many niche and strategic acquisitions that it has fully internalized, and which have largely created value and revenue.

Serco and Capita

There are lessons to be learnt from the performance of the giants of UK outsourcing. Today, one thing that is common to both is the belief that bid and governance structures have to be robust and maintained at all times.

Tagged with:
 

The state of today’s enterprise mobile apps industry is akin to the dark side of a jungle: a dense forest and tangled vegetation, inhabited by hundreds of largely unfamiliar animals and plants that rely on its delicate ecosystem to survive, perhaps to thrive. This is creating frustration among stakeholders including the CIO, CFO, CMO, and CEO, who believe they might have over-invested in mobility initiatives.

However, this is far from the truth. Mobile apps have a long way to go in enterprise. Yet, to avoid the earlier pitfalls, enterprises and technology providers need to be fully aware of the following dangers in the mobile apps jungle:

  1. Business process transformation: Few enterprises or technology providers even consider that enforcing mobile access to an existing business process may be a poor idea. Making the end-user consume the same business process albeit through a different, perhaps “cooler,” app is not true mobility. User interest will not last if the business process is itself unsuitable for mobile. At the same time, not all business processes require this change. Enterprises must be selective in changing business processes while undertaking the mobility journey. Consultants, vendors, and others with vested interests will always extol the virtue of business process transformation for mobility, but enterprises should be very wary of this aggressive spiel.

  2. Line of business collaboration: In their desire to be the first movers, many line of business managers are creating all kinds of mobile apps with little collaboration with other business units. Given the increasing influence of non-CIO budget centers to approve technology funding, the tried and tested processes of application development are being compromised under a convenient, self-pleasing argument that mobile apps do not require a structured or “traditional” approach.

    Will this ad-hoc development blow up in our faces? I think it will. Can we prevent this? Unfortunately not. Business users are happy getting the needed application functionality on mobile devices, yet no one is thinking about the mobile application lifecycle. A long-term technology adoption framework is an unthinkable thought for these budget owners. They do not believe collaboration is their mandate or their responsibility. Their KPIs are linked to business outcomes, not to channelizing or seamlessly introducing mobile technology, and thus they will rarely ever have an incentive to create the needed structure.

  3. Cost of mobility: Enterprises and technology providers need to understand that while business agility, flexibility, and access is all good, the cost of these should not outweigh the rewards. Therefore, enterprise mobility should be viewed in its entirety to understand whether the incremental business has come at a greater cost of management and complexity. Yet the existing mechanisms across enterprises, where different unconnected lines of businesses are creating their noodly soups of mobile apps, does not engender great confidence that they will take a view of the broader picture any time soon.

  4. Mobility governance: It is fashionable these days to ignore any advice from someone who wants to instill structure or a governance model on enterprise mobility. Governance is perceived as “anti-growth” and “uncool.” Given this perception, few technology managers, despite their strong opinions, express any sentiments against the ad-hoc enterprise mobile strategy. This is a recipe for disaster.

So what can enterprises do to quash the mobile apps jungle’s beastly flora and fauna?

  1. Be selective about changing/transforming the underlying business process while mapping to mobile apps
  2. Create an environment that incentivizes lines of businesses to collaborate rather than compete in creating the next “cool” mobile app
  3. Adopt a lifecycle management approach to mobile apps
  4. Balance the growth objectives with the cost implications of enterprise mobility
  5. Incorporate an “eagle eye” to govern mobility projects

If you are undertaking an enterprise mobile application initiative and want to share your experiences and perspectives, please comment below or reach out to me directly at yugal.joshi@everestgrp.com.

Cloud-based services are distinctly different from traditional outsourcing not only because of the obvious cost and agility benefits but also because they fuel the need for a different kind of management of the services. From a management perspective the governance is transformational because it allows the governance team to change their focus on how they manage the services.

The distinction between managing cloud-based services and traditional outsourced services is critical to the outcomes and value achieved from the service.

In traditional outsourcing, the customer has a lot of say, particularly up front, in terms of designing the solution. The solution often starts with taking over what the customer currently has and then moves into a transformation journey. The customer is responsible for defining how the service components fit together and also is responsible for managing the use of those components.

But this tends to lead customers to overbuy. For example, in infrastructure the customer tends to buy more service space and more storage than is needed at any particular point in time just to ensure coverage for peak usage times and volume growth. Because it is cumbersome to contractually change the volumes, the customer ends up buying usage in step changes with the net result of overbuying.

But the real issue is how much time and effort it takes to manage this traditional kind of service. The governing cost in time and effort can overshadow the benefits of the service.

In contrast, the fundamentals of cloud-based or next-generation services are usage-based pricing combined with bundling. The customer buys bundled services rather than discrete components, and this impacts service management. For example, in traditional outsourced services, the customer manages how much capacity is needed for storage, how many licenses to purchase, etc. In the newer service models, the customer manages a few metrics around usage rather than managing the components that allow utilizing the service. The newer models enable customers to avoid the trap of overbuying.

But more importantly, cloud-based and next-gen service models profoundly change the governance aspect in the following ways:

  • Governance is much simpler and communication with the vendor or service provider is much simpler.
  • Governance efforts focus on how the organization consumes the services and on spending time helping the business units to better use the service for more value outcomes instead of managing the vendor or provider.
  • Governing demand management is much easier and reduces the complexities of billing and invoicing to keep track of usage.

The real issue of simplicity in governing cloud-based and next-gen services carries both good and bad news. The good news is that the simplification of management tasks means the customer will need a smaller management team. The bad news: The team will need a different set of skills. Instead of skills in managing vendors, purchasing, and invoice tracking, the governance team needs skills in change management, project management and business transformation.

At CloudConnect 2012, Everest Group’s Marvin Newell moderated a lively panel discussion on next generation IT governance. The panelists included Thomas Barton, Global Enterprise Architect at Novartis Pharmaceuticals; Jeromy Carriere, Chief Architect at X.commerce; and Erik Sebesta, Chief Architect and Technology Officer at CloudTP.

The panel focused on the governance concept of holding on loosely but not letting go. Though executive buy-in is important for cost-efficient and holistic migration to the cloud, the business unit knows operations and needs the best.

In the third CloudConnect video interview of the series, Erik Sebesta answers the question: How does one balance the decision-making between the executive team and the business unit?

In case you missed the first blog, this is the second video interview of a series we taped at CloudConnect 2012 in Santa Clara. Everest Group’s Scott Bils chaired the Organizational Readiness track and enlisted an impressive lineup of speakers.

Watch the first video, featuring Francesco Paola of Cloudscaling.

Watch the second video, featuring Simon Wardley of the Leading Edge Forum.

Watch the last video, featuring Clayton Pippenger of Quest.

In mid-February, I have the opportunity to join a great group of executives to debate how cloud computing will – nay IS – changing the way we need to think about IT governance. As you may know, Everest Group is chairing a track at CloudConnect in Santa Clara, CA, on Organizational Readiness. One of the sessions is slated to include Neal Sample of eBay, Bates Turpen of IHG, Thomas Barton of Novartis, and me discussing governance issues of today and tomorrow. We conducted a prep session last week, and I thought I’d share some of the topics we anticipate debating at CloudConnect.

  • Standards. One of the key pillars of capturing the value of cloud computing is the use of standard services to meet your needs. This raises the stakes for making the “right” choices early in your solution design and requires strong governance to ensure erosion of adherence to the standards is stopped in its tracks. Whether our discussion will start or end with a battle over the right approach to standards is unclear! What is the “half life” of standards decisions and how should you manage the balance of business and technical considerations that you will need to live with for some time?

  • Hybrid IT environments. Most agree that large enterprises will evolve to IT environments that include non-cloud and cloud components. The cloud landscape will also likely include internal (private) cloud environments and external cloud environments (virtual private clouds, public clouds, and Software-as-a-Service solutions). Controversy will be apparent on how big an enterprise should bet on cloud as THE focus of its go-forward plan. How should you balance the governance needs of these diverse environments?
  • Governance intensity. Cloud environments create the opportunity (nightmare?) for independent initiatives to be executed quickly and out-of-sight of centralized governance processes.  Some think these pockets of innovation and initiative are central to leveraging the full power of the cloud; others suggest this is a step onto the slippery slope toward anarchy in terms of IT governance.  What is the right approach?

  • Leadership. Who should take the lead in IT governance. There is a camp that suggests detailed technical decisions are shaped by governance decisions, so architects need to be in the middle of governance. Others argue that the business must set the vision and follow through to allocate resources consistent with those broad objectives or you’ll end up with disconnects that erode value from the outset. Sorting out these issues will be more than a sidebar skirmish! While most enterprises are likely to end up somewhere in the middle, how should you decide what decisions lean which way?

  • Management paradigm shift. Many governance processes have been established for IT approaches that are driven by capital budget management; i.e., large, lengthy projects are the centerpiece of how resources are allocated and policy is set and administered. Cloud computing services turn that paradigm on its end as easy-on/easy-off solutions that require little/modest capital come to the forefront. This fight will extend far beyond IT, encompassing the CFO and BU leaders. How does this fundamental shift in the underlying economics and what needs to be managed change the governance requirements?

  • Pace of change. The IT landscape has always been characterized by rapid change and short innovation cycles. However, cloud computing is accelerating this pace even more. With lower switching costs and innovation that presents opportunities to unlock ever-increasing value, the likelihood of opportunities to change directions increases with each service innovation. Risk takes on a whole new meaning in ways that will reveal fundamental differences of opinion that will light up the stage. How should an enterprise assess these opportunities? What must change in IT governance to accommodate the breathless pace of change inherent in the cloud?

With these topics in mind, the governance panel discussion at CloudConnect is certain to be lively and cover an array of challenging, if not controversial, issues.

If you have a particular area on which you’d like the panelists to share views, post a note to this blog and we’ll consider adding it to the list.

Page 1 of 212