Skip to main content

When designing an operating model for digital, keep an eye on your cadence

A non-trivial amount of the work we do in Digital Strategy at the moment is focused on the design of digital operating models. I don’t particularly like the name, but the sentiment is about designing a business fit for the New Machine Age. As I’ve mentioned before, this philosophically means that it ultimately needs to become outcome- rather than process-centric. Making that happen means applying some new organisational and operational concepts to the business, one of which is an idea we’re beginning to talk about a lot: cadence.

Cadence basically means the rate at which you do things. Businesses always have them. They’re part of the culture. In a PLC, they are quarterly to match the reporting cycle. In the public sector they’re often annual. In digital startups they could be as fast as weekly, to correspond with the tempo of an agile delivery ethos. Usually though a business has a natural speed and struggles to operate outside of it. The public sector struggles to act outside of the annual plan; startups struggle to think even as far ahead as a year.

This is problematic because even if you are able to design work to have the right combination of people, the processes that surround the work operate at the typical speed (and thus precision and robustness) of the rest of the business. So the formal or ad-hoc design of the route to an outcome is compromised.

What we do to solve this issue is pretty self-explanatory. We build teams that are designed to operate at a particular cadence, then we build functions around them that are designed to operate around them at that cadence, so that the finance and procurement teams that surround an agile digital development team can operate at the same rate rather than trying to cram a monthly or weekly request for resources into an annual budgeting process. This is a development of something I’ve talked about here before – the necessity to break up functions like finance and HR into their functional components, rather than assuming that because they deal with ‘money’ or ‘people’ they should all have the same reporting line.

Clearly you can’t have endless fragmentation of speeds. Two or three is probably right to start with. We usually go for something annual to deal with things like infrastructure; something monthly to deal with iteration of the business and the build of new initiatives at a relatively small scale (this is the majority of the business) and then something multi-annual that looks at the horizon for new innovations, acquisitions, strategic repositions and the like. The latter is important as my observation of my clients is that many have lost the ability to do real strategy as the requirements to report to markets and create financial plans have grown.

Which brings me to another cadence-related issues. The need to produce anodyne quarterly reports for investors is a costly and disruptive blight on listed businesses. Perhaps we’d be better moving to a world where businesses are transparent about their numbers to their investors on a daily basis (letting them know as they do so that there is a degree of imprecision in the numbers) and that they’ll reconcile everything annually?

Controversial, I know… we’re probably not adult enough as an industry to adopt it. Ah well.

Comments

Popular posts from this blog

Impacts of a handset leasing model on mobile telcos

Following yesterday's post, here's some related thinking on the impacts on operators of handset leasing. Handset sales represent around 25% of operator revenues in a typical European market, but generate only around 5% of margin. It may therefore be the case that the scenario described would lead operators to a more profitable structural model than exists today. Oil companies are consistently and acceptably profitable, despite being (literally in some cases) the ‘dumb pipe’ that operators are so desperate to avoid becoming. One of the reasons for the oil majors sustained profitability is clear focus on their role in the value chain – to supply the fuel that enables transportation, relying primarily on location, then brand and finally product innovation to compete. BP or Shell do not need to subsidise the purchase of a car in order to drive consumption of fuel because consumers are ‘hooked’ on it (it gets them from place to place) and there are many credible car manufacturers an

Value drivers for telecoms retail

I've been doing a really large number of driver trees recently - we've taken to using them on every project to get really into the guts of value creation for businesses and thus decide where to focus initiative development (How To Win, if you're keeping score). Anyhow, I had to pause for thought recently to work out how to represent the subscription aspect of telecoms retail for a client. Since it took me a minute, I thought I'd share... its lack of elegance suggests that its not quite right, although it was enough to demonstrate that there was a certain lack of coverage in the initiatives that my client was pursuing and thus spark a debate. Enjoy.

Chief Strategy Officers II - Career Development

Here's a follow up to my earlier post on the starting point of Chief Strategy Officer (CSO) careers in the FTSE 100 and S&P 500 companies - a visualisation of two steps in their careers: their first employer or job and the job they had before they got their current position. Lots of work went into this... so any insights that you glean from the visualisation would be great to hear about :). The CSO is a crucial strategic role on the executive (!) and the owner of the tone and philosophy of decision making across much of the business, knowingly or unknowingly. Scrutiny of their experience in defining the process and language of strategic management is therefore appropriate not just amongst their executive peers, but in my view amongst shareholders. The days when being very smart and able to analyse large amounts of data were enough to be a CSO are basically gone... has the profession moved on enough to cope?