Tag Archives: technology

Digital Abundance, and the Second Half of the Chessboard

We live in an time where the rate of change in digital and cloud technology is exponential. The word “exponential” is used a lot,  often without rigour, but in this case the statement reflects reality closely, and the implications are perhaps staggering. We already seeing – and often taking for granted – a rate of innovation greater than any other period in digital history.

Fable of the Chess Board

To understand the extraordinary power of exponential growth, set’s start with the fable of placing rice (sometimes wheat) on each square of a chessboard, starting with one grain on square one, two grains on square two, four grains on square three and so on – doubling each time. The well known question is: how many grains of rice would be on the chessboard at the finish?  The story is often told in the form of a servant speaking with the Chinese emperor, but the tale is linked more clearly to the writings of Islamic scholars around the 10th century, or sometimes to the invention of Chess itself in India.

The final square alone would end up with 2 raised to the power of 63. That is a very large number indeed, and there would be enough rice on the board that placed end-to-end the grains would span the gap to the nearest star, Alpha Centauri, and back again.

Moore’s Law

Gordon Moore working at Intel in 1970
Gordon Moore working at Intel in 1970

The one real place in human endeavour where this type of process exists is IT. It is (of course) enshrined in Gordon Moore’s “law”, where in 1965 he predicted a doubling every one to two years in the number of components per integrated circuit.

Moore’s Law is now a cliché, mentioned in articles and on stages an untold numbers of times. It is not even a law in the normal sense, but a remarkably astute observation. But as a description of actual progress it is real, and remains real.  It also carries through to memory capacity, disk capacity, the number of pixels in digital cameras, and much more. The drum beat of progress is remarkable, sustained, even relentless.

Ray Kurzweil and the Second Half of the Chessboard

Ray Kurzweil
Ray Kurzweil

In 2001, Ray Kurzweil – computer scientist, inventor and futurist – wrote a seminal essay about the rate of change in digital tech that contained the following observations about the rice and chess parable, to illuminate the future power of the Moore’s law process.

It should be pointed out that as the emperor and the inventor went through the first half of the chess board, things were fairly uneventful. The inventor was given spoonfuls of rice, then bowls of rice, then barrels. By the end of the first half of the chess board, the inventor had accumulated one large field’s worth (4 billion grains), and the emperor did start to take notice. It was as they progressed through the second half of the chessboard that the situation quickly deteriorated …. One version of the story has the emperor going bankrupt as the 63 doublings ultimately totaled 18 million trillion grains of rice. At ten grains of rice per square inch, this requires rice fields covering twice the surface area of the Earth, oceans included. Another version of the story has the inventor losing his head.
Ray Kurzweil from “The Law of Accelerating Returns”

In other words, it is in the later phases of exponential growth that the effects become extraordinary, and beyond all common-sense models. Kurzweil uses this as part of building the case for the singularity – a predicted epoch of miraculous tech-driven change – that sits at the ragged edge of futurist thinking.

1958 – 2006

Erik Bryonjolfsson and Andrew McAfee of MIT develop the chessboard metaphor further in their excellent book “The Second Machine Age”.

They take a start point in 1958. The late ’50s were a remarkable and forgotten period of progress in tech, where many of  foundation concepts were created. 1958 also marks the moment when the first use of the term Information technology was made in the Harvard Business Journal .

Assuming a doubling of IT power every 18 months, we entered the second half of the chessboard in 2006 – a year that saw the launch of  twitter, youtube and Amazon Web Services in a form we would understand today.

Digital Resource Abundance

The point that Bryonjolfsson and Andrew McAfee are making is this: remarkable capacity is now available, and continuously increasing, for innovators, inventors and entrepreneurs. Such abundance of resources allows us to have driverless car technology,  smart phones with the capacity of high end PCs of the past, and games consoles with the capacity of former supercomputers. Digital abundance has also led to the first usable voice-based agents such as Siri, vast and responsive social networks, and robots that begin to mechanically move and act in the world like humans or animals. We have data, and potential insight, at scales that stretch our ability to describe in the current metric system. Social Commerce enterprises, like uber and Airbnb, have connected legions of customers and citizen suppliers on a scale that is breathtaking. We have arrived in the foothills of the future sooner than we were perhaps expecting.

Implications for Enterprises

For enterprises, this richness of compute and storage power allows the redundancies that make large-scale cloud computing not only feasible, but competitively essential and inevitable.  For most purposes, it is already inherently cheaper, more (potentially) agile and secure. The new technologies also facilitate new types of business model, new sources of insight on a gigantic scale and new demands from their end clients.  Immediacy in business matters more than ever. As a result, Enterprise IT has embarked on a long period of transformation and change – maybe a decade of marvels and dark dangers. Any organisation now needs to think more about tech opportunity and invention, than optimisation of the server estate, or cost per development hour.

Whether we will create true AI in the next decade, or next century, or ever remains an unanswerable question. The current rush to digital will prove to be part-bubble driven by over enthusiasm.  There will be broken promises, and conventional  challenges around service and costs. Legacy rarely dies, but grows larger.

But what is clear is that the opportunity to invent and innovate grows ever more profound as we move into the next great phase of digital history. It’s time for imagination, and for all technology practitioners to look forward.

Keith Haviland

Keith Haviland is a business and digital technology leader, with a special focus on how to combine big vision and practical execution at the very largest scale, and how new technologies will reshape tech services. He is a Former Partner and Global Senior Managing Director at Accenture, and founder of Accenture’s Global Delivery Network. 

Published author and active film producer, including Last Man on the Moon. Advisor/investor for web and cloud-based start-ups.

New Horizons and the Human Journey to the Surface of Pluto

“I thought I’d better check this third plate, which is another date, see if there’s an image there in the right place that would be consistent with the images on the other plates. That was the final proof.” – Clyde Tombaugh

Pluto was discovered on 18 February 1930 by young astronomer Clyde Tombaugh. His technique was humble, switching mechanically between photographic plates to see if one of the faint points of light appeared to move. On that day, he noticed a moving object on photographic plates taken on 23 and 29 January of that year. After the Lowell observatory had taken confirmatory photographs, news of the discovery was announced on 13 March 1930.

Clyde Tombaugh
Clyde Tombaugh

The naming process would prove complex, and human. Candidate names include Zeus, Percival and Chronos. The final choice of Pluto was proposed by Venetia Burney, an eleven-year-old schoolgirl from England, who was interested in mythology. She would earn £5 for her idea. The name would inspire Walt Disney in naming his cartoon dog, and the discoverer of the radioactive element plutonium.

Venetia Burney, who named Pluto
Venetia Burney, who named Pluto

Within months of discovery, Pluto was appearing in fiction, including the Cthulhu Mythos stories by HP Lovecraft. But the main role of Pluto in popular culture was to be a symbol of vast distance, cold loneliness and the unknowable. Even the mighty Hubble telescope would find only the barest hints of what lay on its surface, a surface that would sometimes reach temperatures as low as 33 Kelvin, within touching distance of absolute zero.

Eventually that would change.

Indeed, a Pluto flyby was a possibility for the “Grand Tour” undertaken by Voyager 1, and would have happened in the late 1980s. However, a close approach to Saturn’s moon Titan was selected instead, since it was seen as of much greater significance than tiny, remote Pluto. As a consequence of that, when Voyager 2 encountered Uranus and Neptune, Pluto became the only traditional planet whose face was unmapped and unknown.

So, in 1989, a group of scientists formed the “Pluto Underground” to promote the idea of a mission. At the heart of this alliance was a scientist called Alan Stern, who would pursue the concept of a Pluto mission with intense passion and would eventually become the Principle Investigator for New Horizons.

It wasn’t an easy process. Initial ideas were rejected, sometimes with great controversy. Then a competition was held, in which NASA would select a mission concept to fund as part of the first mission of the mid-cost New Frontiers program. New Horizons won, was rejected but then re-selected, for a mission cost of around $700m.

The probe finally lifted off from Pad 41 at Cape Canaveral at 14:00 on January 19, 2006.

New Horizons on the Launch Pad
New Horizons on the Launch Pad

The triangular New Horizons spacecraft has been compared in size and shaped to a grand piano. Unlike a piano, it is powered by a plutonium battery – more formally called a radioisotope thermoelectric generator or RTG. There’s irony here. The first probe to Pluto is powered by an element named after it.

New Horizons was the fastest spacecraft ever to leave Earth, it was accelerated even further after a scientifically valuable flyby of the Jovian system.

Jupiter and Io as seen from New Horizons
Jupiter and Io as seen from New Horizons

Almost a full decade after lift off, New Horizons reached its destination – the distant ice world of Pluto, almost exactly on the day that marked the 50th anniversary of interplanetary exploration. Because New Horizons is 4 ½ light hours away, the extraordinarily fast encounter was dark to the ground, powered by software and supported by immense pre-planning.

But shortly afterwards, and for first time in many years, we had the raw pleasure of seeing – as a connected human community – the faces of strange new worlds. We saw the cratered surface of Charon, the major moon of Pluto, cracked by a mighty canyon and marked by a mountain seemingly buried in the heart of a crater, like a giant Norman castle. On Pluto we saw a landscape of the Norgay Montes ice-mountains adjacent to a vast young plain (Sputnik Planum) fractured into polygon shapes – a landscape that is somehow active and renews itself at those temperatures of 33 kelvin.

Sputnik Planum
Sputnik Planum
Norgay Montes -  Ice Mountains on Pluto
Norgay Montes – Ice Mountains on Pluto

The triumph of New Horizons completes a story that combines the initial discovery of a very distant world, the vision of those that pursued a Pluto Mission for decades, and the gigantic contribution NASA and the US have made to this period of exploration. That story also includes the remarkable efforts of the New Horizon team, across complex planning, the spacecraft design, the construction of the science instruments and the management of mission operators.

It is of course a human story, not just a tale of achievement in technology and engineering. The probe itself carries a number of artifacts that tie it back to the beginnings of the Pluto story. Two stand out for me.

The Venetia Burney Student Dust Counter or VBSDC was built and is operated by students at University of Colorado. It measures the dust peppering New Horizons during its voyage. It is named after the little girl who named the distant world in the early 1930s.

And most moving of all is the fact that the craft contains one ounce of the ashes of Clyde Tombaugh himself, the young man who discovered Pluto and who would never know that his remains would pass close to 10,000 kilometers about the surface of the planet he was the first to glimpse.

Full disk Pluto as seen from New Horizons
Full disk Pluto as seen from New Horizons

As principal investigator and life-long Pluto advocate Alan Stern has said: “We have completed the initial reconnaissance of the solar system.” And like all such missions, for a moment it connected us all, as an example of the best we can do.

I Saw a Mash-Up of Royalty, Business and New Tech Innovation. It Worked.

Over the last two years I have been working with a small number of start-ups. These are mostly digital and cloud-based, although one is bringing innovation to large-scale consumer goods, and has built an impressive robotic production line near Cambridge. As a result, I have begun to build a classic entrepreneur’s network.

So, a few weeks ago I received an invitation to an event called Pitch@Palace, which is exactly what its name suggests – a start-up demo-day style event that was to be held at St James Palace on November 5th (a day that traditionally – and in this case ironically – marks the Gunpowder plot of 1605 where Guy Fawkes and other conspirators attempted to blow-up the House of Lords).

Pitch@Palace is led and sponsored by the Duke of York who introduces the program on its website with:

 “British prosperity, in all its forms, is central to my work. I want to recognise and reward the people and organisations working to ensure that we have the workforce, intellectual property and entrepreneurial culture to succeed.”

I wasn’t sure what to expect. The event would be well intentioned I was sure. Worthy. But could it be connected to the technical zeitgeist, relevant, genuinely innovative?

In the end, I was simply impressed. Impressed enough, in fact, to write this little post. The event was a job well done by all those involved.

There is something about being in a proper, full-on Palace, of course. The event was held in the spectacular apartments around the throne room – with great ceilings, fine artwork, chandeliers and gilt mirrors. I managed to take my own selfie a few feet in front of the throne – the use of mobile devices being encouraged throughout the event. Pitch@Palace was very well attended and the palace was crowded and full of energy and the buzz of conversation.

It turned out that the pitch day had been supported by a process that ensured the start-ups on show were very high quality. Forty-one start-ups/entrepreneurs had been selected from a network of fourteen partner organisations – tech accelerators, and University and government sponsored schemes. During October, the Duke of York held a “Pitch@Palace Bootcamp” at Central Working Space, part of a huge accelerator facility in the Mile End Road in the classical East End of London, in partnership with Microsoft Ventures, Wayra and KPMG. A panel of judges selected 15 of the start-ups to present.

The main event was kicked-off by the Duke of York. It was the first time I have seen him speak. He gave an urbane, quietly passionate speech about the program – grounded in a real sense of business reality, and strongly encouraging those in attendance to contribute.  It was an introduction that any top flight CEO would have been proud to have made.

Then came a series of three-minute pitches (supported by additional materials available on the web). What was immensely pleasing was the breadth of innovation and ideas on show. Ideas ranged across digital and physical tech, and across the categories of consumer technology, education, environment, medicine, robotics and gaming.

There isn’t space to describe all of the fine fifteen finalists, but I liked Insignia Technologies with smart labeling to reduce food-waste, Pure Marine who aim to crack the challenges of wave energy, Terra Recovery with a mission to mine existing landfill,  Armourgel with a product that protects the vulnerable against injury, Reach Robotics that makes gaming robots, and Insane Logic that through digital apps makes speech and language therapy easily available and affordable. The winner of the vote at the end of the evening was Squirrel who aim to empower low-income employees through digital  tools to manage and save their money.

There were other strong products in the original long-list of forty-one that had their own booths spread through the Palace. I liked See.Sense that manufacture (in Northern Ireland) an intelligent bike light that shines brighter and flickers faster when an internal accelerometer detects change, and so enhances visibility at key moments.

So, part from a good event, what conclusions can be drawn from the evening?

First point: Pitch@Palace emphasizes the way that business innovation and a culture of entrepreneurship have established themselves in the UK, on a strong foundation of tech innovation. There has been a real change over the last decade. The sector appears much more mature than during the time of the original dot.com frenzy at the turn of the century. There is a way to go – some ideas require larger funding that is commonly available early in the UK, and there needs to be more support for the creation of effective channels for new companies (an ex-colleague of mine has created a fine business that does just that). But, overall, we have developed a culture and infrastructure that can create new forms of growth.

Second point: I was impressed with seeing so much hardware and physical product. And some of this was being manufactured in the UK. The UK is now very strong in media and digital production, but it needs to be stronger across all manufacturing.

Third point: Many of the ideas and products presented – by design of the Pitch@Palace process – had a strong social or environmental edge. They were uniformly good business ideas as well. The evening felt remarkably progressive.

So, last night I saw a mash-up of Royalty, business and bright, new tech innovation. It worked.

The Bifurcation of Technology and the Revolution in the IT Industry

Sometimes people start to use a phrase or word that captures a moment of change. You hear friends and colleagues using it, and it starts to crop up in the media. One such example I’ve heard several times in the last few weeks is bifurcation, as a dry shorthand for the current momentous transformation in IT and IT services. The trends I noted in an article (here) in the summer are accelerating, and fast.

A recent, excellent article in the Economist covers this well. The bifurcation is the dual-track nature of growth in IT. Services and products related to mobile and cloud are expanding, and sometimes with extraordinary growth rates. Conversely, traditional IT sectors are growing slowly or even shrinking”. The sectors under pressure include most types of hardware, traditional enterprise software, and classical IT services.

The combination of the differential growth characteristics means the IT industry overall is showing modest growth. The Economist quotes a number of 3% overall. Other commentators will give numbers even closer to zero. It is a challenging environment.

One result of this is the beginning of significant change in the corporate structures of IT suppliers. Larger companies are acquiring faster-growing companies. That is the usual cycle. More profoundly, some large companies will radically reshape themselves. As the Economist describes “HP’s recent decision to break itself up was merely the opening shot … Others will shed businesses that have become commoditised …IBM announced that it will pay Globalfoundries, a contract chipmaker, to take its semiconductor business off its hands.”

The changes in technology driving these changes in business are very real. Over the last 20 years, the relentless increase in available compute power, network bandwidth and storage capacity has moved us to a world where a wide variety of very powerful devices – not always operated by people, but increasing by other machines – can connect reliably to remote services of increasing breadth and sophistication.

And what this means is that such services can potentially take advantage of real economies of scale, and can be built and provided to the entirety of the universe of consumers and business with an ease that a generation ago would have seemed startling.

A new underlying industry architecture for software is forming. It includes a complex infrastructure layer that provides cloud services, which itself faces real change as the concepts of commoditized data centre and commoditized server becomes blurred. It includes a complex range of platform options that link humans and their devices to apps and cloud services. The architecture is crowned by applications and functional services – and it is the richness of these that will accelerate the change in IT. Importantly for established businesses, there is an explicit need to add an integration layer to the architecture – since we are on a decade-long transformation, and the interfaces with legacy systems will be key concerns. Overall, the concepts of Infrastructure-as-as-Service (IaaS), Platform-as-a-Service (PaaS), and Software-as-a-Service (SaaS) introduced by Gartner have served us well, but need refreshing as this form of architecture becomes dominant.

These changes in architecture also change the expectations for the delivery of software and services. New companies especially want their back-end support systems to be easily, immediately and cheaply available, and provided as elastic services that will grow with them. They do not seek uniqueness or differentiation here. Instead, they want innovation and rapid development of those services that face their customers. More generally, monolithic applications are being replaced by systems of services. This brings more architectural complexity, but it allows development to be parallelized and – if well managed – delivered in much more agile ways.

There are obvious dangers here for the providers of IT services (and you can include IT departments under this heading) who are sometimes surprisingly disinterested in the way they deliver their technology services, although this is often what clients are buying.

For example: a typical feature of large companies is operator dominance where a focus on cost becomes primary – growth in a changing world is much harder and requires fortitude. Taken to excess, the focus becomes optimization of legacy services, and too much focus on tools such as global delivery – wonderful as part of a toolkit, but most effective in combination with client-facing services that bring new technology opportunity into the heart of businesses. Indeed, the best India-based IT providers realize exactly that, and understand that conventional outsourcing now has a limited shelf life.

Another sign of dysfunctional effects are mash-ups of old and new which resemble failed experiments in genetic engineering. We all know of large projects where agile approaches have been introduced at too large a scale to deal with mad schedules, and client and suppliers try to handle this with conventional procurement approaches. Fixed-price contracts and flexible iteration can be unlikely bedfellows.

But real, sun-bright opportunity at scale also exists. An eco-system of service providers has appeared around the dynamic and fast-growing company Salesforce. Salesforce transaction volumes are in 9 figures daily, and much of these are via their platform technologies, showing people are building their own apps around its Software-as-a-Service core.

Another positive example:  I have come across one agile based company that hires the very best developers – aspiring for the top 1% – and undertakes only small projects with direct and strong business support. It seems to genuinely deliver the benefits of agile approaches, with great reliability. This emphasizes to me a coming focus on skills and expertise that can marry client need and the power of new tech. Like all times of change, smart tech-savvy people who understand clients and can integrate complexity will be at a premium.

And the growth rates of many larger consultancies are respectable, or simply plain good – reflecting client needs for advice and support in their transformations.

So, as always I end very optimistically. There are new opportunities for those technology service providers who can develop architectures and architects for the new world, and who can create app and tech services that can be reused across their clients. Good companies of the future will get to grips with better, more nimble ways of integrating, assembling and crafting solutions for clients as systems of services. They will invest in building the new skills and high-end expertise for 21st century delivery – both close to clients and in their global centres. They will create new types of career, and new types of personal opportunity.

I will be writing about these positive trends in future articles. Stay tuned.

Keith Haviland is a business and technology leader, with a special focus on how to combine big vision and practical execution at the very largest scale, and how new technologies will reshape tech services.
He is a Former Partner and Global Senior Managing Director at Accenture, and founder of Accenture’s Global Delivery Network.
Published author and active film producer, including Last Man on the Moon. Advisor/investor for web and cloud-based start-ups.

Steam, War Computers and Social Media: Representing Technology in Film

The London Film Festival is currently on – running from 8th to 17th October across 17 venues, showing over 250 films. As always, it offers an extraordinarily rich program from filmmakers across the world, in a city that has now firmly become one of the movie capitals of the world.

Film, of course, is now a truly digital business. In the last few years, digital cinema cameras like the Arri Alexa have made physical rolls of films essentially redundant, and give very high-definition results of great quality. Production activities like data wrangling and conforming are tasks centred on managing video data that will seem very familiar to anyone who has dealt with configuration management on a software project. And when films are shown in a modern cinema, they will be stored as a Digital Cinema Package or DCP – a standardised collection of digital files. Everywhere there is also experimentation with digital distribution, the art of getting content to consumers in different ways on different devices, and the web’s video services have unleashed a vast wave of low-cost creativity. Technology is transforming filmmaking.

The London Film Festival itself exploits modern technology, including live streaming of its red carpet galas to cinemas across the country and use of its own BFI player for festival related content. London overall is a place where technical skills abound in the new digital crafts around post-production, special effects and 3D.

But this article is not about the digital revolution in the making of film; it is about how technology is increasingly part of the dramatic content of film, and how technology and especially digital technology is represented. The examples are – naturally enough – drawn from the London Film Festival.

The inspiration for the article was accidental. I had booked each film I wanted to see for the normal reasons – I liked the look of the film, or respected the filmmakers, or was interested in the buzz surrounding the movie. But, as I watched each of them – usually somewhere in Leicester Square – I was struck by how often technology intruded, and how often directors tried to find ways of representing technology in general, and specifically n the digital world, on screen.

Mr. Turner

Let’s start in an unlikely place with Mr. Turner. It is a marvellous film, from director Mike Leigh. It is a biography of perhaps the greatest English painter JMW Turner (1775 to 1851) who was known as “the painter of light” and who anticipated both Impressionism and modern Abstract Art.

Set in the first half of the 19th Century, it succeeds at recreating the period with a sense of truth that is unusually powerful – through its authentic and sometimes very funny dialogue, its recreation of the manners and moral temper of the period, and its careful choice of locations.

It shows off Turner’s art of course – and is visually rich and sometimes stunning – but the film also brings to life the man himself: a successful, eccentric and harrumphing curmudgeon born outside the establishment, who then became very much part of it. Turner is vividly played by Timothy Spall, with ungainly confidence and much humour.

But one of the most unexpected parts of the film for me was the way it shows an older Turner experiencing changes in 19th century society, and especially the impact of technology. Mike Leigh successfully conveys a deep sense of the move from the Georgian to the truly industrial Victorian era.

Examples: the means of passage from London to Margate changes from steamer to train during the film. There is a wonderful, funny sequence where Turner and his mistress are photographed by an American master of this new technology. He is armed with the latest cameras and equipment, including a head brace to help with long exposures. During this process, Turner ponders on the future effects on art.

And in one of the grandest sequences of the film, Turner and a group of friends watch the tall-masted and exhausted warship The Fighting Temeraire being towed to its break-up by a steam tug. This was to inspire what is one of the most famous, reproduced and loved paintings by a British artist.

During the scene, one of Turner’s companions looks at the great tall ship and remarks melancholically: “The ghost of the past.”

Turner prefers instead to observe the blackened, low shape of the steam tug: “No,” he shouts back, “The past is the past. You’re observing the future! Smoke. Iron. Steam!”

This presentation of technology, as a set of dynamic changes and images seen through the curious eyes of an artist is highly effective. The film ends up being as much a biography of the early Victorian age – a age of steam, coal, industry and transformation, with the young Albert and Victoria putting in an appearance themselves – as it is a biography of Turner.

The Imitation Game

The Imitation Game moves us directly into the first days of the digital era. Indeed a key moment of the film, set during World War II, is when Keira Knightly pronounces the phrase “digital computer” awkwardly, as though it is being said in the world for the very first time.

The film is a biographic study of Alan Turing, played with suitable coldness and fragility by Benedict Cumberbatch. Turing was a taut, difficult personality often backwards diagnosed as autistic. He was a mathematician, cryptologist, and one of the first computer scientists, introducing many key foundations of that discipline. The name of the film itself is taken from one of Turing’s papers where he develops the concept of the Turing Test. This is a test for whether machines can ever think, and whether they could ever imitate a human mind.

It is a brilliant choice of title, since the film is about deceit at many levels – including the original Enigma codes, the hiding of the success of Allied code-breaking and the passing of false information to the Russians. Above all, there is the hidden nature of Turing’s own sexuality in a time when male homosexuality was a criminal offence.

The bulk of the film’s plot – with quite a lot of dramatic simplification- is centred on the breaking of the German Enigma code at Bletchley Park. The resulting intelligence was labelled Ultra (from Ultra Secret), and Churchill would later tell King George VI: “It was thanks to Ultra that we won the war.” The film itself repeats the common suggestion that ultra shaved two full years of the war.

In the film, the core of this process is a computer-like device – a bombe in the terminology of the time – that eventually is successfully programmed to break German encrypted messages on a daily basis. Turing’s efforts to design, build and operate the machine, and manage the team around it, occupies much of the story.

The visual and dramatic vocabulary that the film uses to describe its technology is taken straight from 1950s Science Fiction. In some ways, this is a perfect choice, since the 1940s wartime acceleration of technology would influence the world-view of the 1950s. So, we have common archetypes such as:

  • The central character of a lonely, arrogant boffin, dressed in tweed, who has a mission to save the world. Indeed, Turing is warned several times in the film to avoid thinking of himself as God.
  • Plain speaking, slight dim military men who’s job seems to be to place obstacles in the way of the hero
  • Sudden moments of inspiration where a chance remark opens the door to the instant resolution of a complex problem.
  • Diagrams and mathematical text assembled in great linked masses showing the workings of another “Beautiful Mind”
  • The great machine itself, a clunking mass of cylinders and valves that rotate remorselessly – like a vision of a Babbage difference engine. It reminded me of the whirl of mechanical computation machines in the classic “When Worlds Collide”.

The vision of technology here is cold, hard-edged and relentless – similar to Turing himself. Overall, the film succeeds – it is a good,moving and watchable piece of work, with strong performances throughout, but perhaps the plot works itself a little too mechanically, simulating the code-breaking machine at its heart.

Men, Women and Children

This film – by Jason Reitman and starring Adam Sandler, Jennifer Garner and a large ensemble cast – is completely contemporary. It is about the lives of middle-class Americans, and how modern motivations and complexities are wired together by personal and social technology. It is based on an original novel by the controversial author Chad Kultgen.

Technology is represented in two ways. Firstly, there is a sequence of digital special effect sequences of the Voyager missions to the outer solar system, narrated by Emma Thompson. The connecting link between these sequences and the rest of the film is through the use of words – at the very end of the film – that Carl Sagan wrote about the “Pale Blue Dot” photo. This famous image was taken by one of the Voyager probes of the distant Earth as a final act of observation. The sequences are beautiful, and the narration sometimes very funny, but this part of the film feels a little contrived and unnecessary.

 The second representation of technology – of websites and social media – is much more relevant and direct. This is not achieved through conventional shots of a PC or smartphone screen, but via pop-up windows on screen that represent what is being shown on a device. These appear beside the main antagonists in the film, popping in and out of existence like speech or thought bubbles. This is effective, and helps the narrative flow. It soon seems strangely natural. It is also provides opportunities for real humour, when people text what they really thinking of the person they are talking to.  

The themes covered are those social issues generated or amplified by technology. One example plotline: the character Tim Mooney (played by Ansel Elgort) is a schoolboy football player of real talent. But he quits the sport – to the vast disapproval of his father Kent (Dean Norris) – to obsessively play online games. He also learns of his absent mother’s new marriage via Facebook. Increasingly alienated, he finds solace in a relationship with intellectual, book-reading teenager Brandy Beltmeyer (Kaitlyn Dever).

Her mother Patrica (played with steel by Jennifer Garner) is one of the strongest characters in the film. Her obsession is the Internet life of her daughter, which she monitors, restricts and controls with total authority before she finds out that her daughter has a secret and rebellious alternative web identity. This sets up a near tragic incident, where Patrica impersonates her daughter to persuade Tom that their relationship is over. As a consequence, Tom takes an overdose that he barely survives.

Another examples of the film’s threads include a teenager so corrupted by pornography he cannot form a normal relationship, a married couple who organise parallel infidelities via websites, a teenager who damages her life chances by putting too racy images on the web, and another – borderline anorexic – who gets advice on extreme dieting from virtual friends on the web.

There is much humour, especially at the beginning, but in the end the film takes a grim view of humanity. However, the representation of the technology works well, and allows parallel threads of plot and meaning to be shown on screen. It is a successful recreation of people’s abstract virtual lives.

Dearest and Rosewater

Both these films are reconstructions of real stories, where technology is part of the story, but not the prime driver. Both were – for me – unexpectedly moving, and illuminated very different cultures.

“Dearest” is a Chinese film, directed by Peter Chan, which covers the sensitive subject of child abduction in China. Although fictionalizsed, it is based on a true story that Chan came across in a TV documentary. It is well acted, humane and gives real insight into the social world of modern China.

Tian Wenjun (Huang Bo) and his ex-wife Lu Xiaojuan (Hao Lei) lose their child PengPeng through abduction. They spend three years searching – using the web as a means of communicating across the vastness of China, and connecting with others in their situation. Eventually, they locate their son in a remote village. The film then – remarkably and successfully – switches its point of view entirely to the heartbroken woman Li Hongqin (Zhao Wei) who has been looking after the abducted child.

In Dearest, the technology dimension is treated entirely conventionally, with the focus always on the actors. It is well made, and a delightful film, but rooted in traditional filmmaking.

“Rosewater” is the story of London-based journalist Maziar Bahari (played by Gael García Bernal) who was detained in Iran for 100 days, while his British and pregnant girlfriend waited for him in London. It was written and directed by Jon Stewart, who was connected with the case.

The film starts with Bahari getting increasingly involved in the events around the Iranian presidential elections, and their violent aftermath. He is arrested and spends four months in solitary at Evin Prison, being interrogated by a “specialist”. Since he is blind-folded, his experience of the interrogator is through the scent of rosewater that surrounds him.

Technology threads itself through the film in two ways. It is shown as one of the motors of change in Iran, with the opposition fluent in use of the web and internet. TV news has also connected Iranian youth to the wider world. At one point, Bahari is introduced to a “university” that is simply a vast array of satellite dishes, hidden from the security forces. The last scene in the film is of a small boy filming the destruction of the nest of dishes by police. He is using a smart phone.

There is also a sequence that starts with Bahari in the depths of despair. He is convinced that the world has forgotten entirely about him. He has been told that his girl-friend has not contacted the Iranian authorities. But then a security guard mentions that Hilary Clinton has been talking about him. In that instance, he realises he absolutely has not been forgotten, and he is actually famous and the subject of much outside debate. That awakening is captured in the use of an animation sequence that shows information and keywords spreading around the world. It is out of kilter with the naturalistic feel of the rest of the film, and reminded me of the use of maps to show travel and the passing of time in films from the 40s and 50s. But it is effective, and a compact means of making the point.

Conclusion

Technology, and a sense of technical change and opportunity is everywhere in society, and everywhere in the world. That is influencing the mirror of film – only one of the films above was directly about the use of technology, but technology pervades all of them. This presents filmmakers with a challenge – especially when the technology is digital. How we represent the drama and rhythm of lives that are part virtual becomes an interesting and essential question. Soon I suspect someone will make a breakthrough film which tackles and answers that question head-on.

I look forward to it

 

Masters of Delivery, Episode 2 : Ten Commandments for Successful Program Delivery

This article provides guidance for those leading or working in a large program. Its original name was WB and the Tablets of Stone until I went for something more directly informative. We’ll see why in a moment.

Let’s introduce WB first.

WB is another Master of Delivery I am privileged to know – a natural results-driven program manager, who can instinctively drive the largest projects and programs to completion. He has a flair for action, for handling scale and a gritty humour. He is a kind of Indiana Jones or Hans Solo of program management. So, in a galaxy a not so long time ago …

Context

We faced two years of hard work on a major program across much innovative software development, and data conversion of records covering the activities of millions of people. This would be followed by re-casting business processes from customer billing to how a set of large call centres operated. As many will know, a large call centre quickly goes off the rails with any system problem. Even with good fallback procedures, work queues can build rapidly and customers will hang on the phone for what seems like interminable periods.

In short, the new system would drive almost the entirety of our client’s business. It was high risk. And to create and deploy it, we would assemble a large team – around 400 at peak – across technologists, business people, operations and executives. It was a team of teams.

Defining Goals, Culture and Behaviour

WB and I wanted a simple way of defining and communicating our goals, and the culture and behaviours we wanted. As WB would put it, ‘the job of leadership is to create an environment in which people can succeed’, and the ten commandments became one of the major vehicles for achieving this.

This is a common management pattern. Many projects summarize their approach in ten bullet points. Indeed, I once informed a very capable member of a Quality Team that there was a typo in the ten commandments of Quality they had just published – there were just nine. That document was republished fast.

Good Ideas Get Reused

Our “commandments” were to strike an unusual chord with the team, who liked them, and bought into the aspiration they represented.. They are distinctive in their focus on team behaviour. They push control and issue resolution into the team (although ultimate accountability must still reside with program leadership).There is nothing on method, process or technique, although these were important in the background. In essence, these commandments were about creating a mission, a team and a driven culture of success, at scale.

As is often the case with things that work, our ten commandments become viral across a wide community. They have been used, with scant modification, on many projects. They are still being used.

And the reason for the sub-title of WB and the Tablets of Stone is that we came very close to having them engraved on real stone tablets. We had got our mad scheme costed, and we had chosen the shape of the tablets. We thought this little bit of theatre would help get the message across. In the end, we decided we were getting a little too impressed with ourselves, and went for a more portable presentation.

The Ten Commandments

These were the ten commandments:

  1. Meet Your Promises
  2. Act as One Team.
  3. Aim to be Exceptional, Exceed Targets
  4. Understand and Report True Status
  5. Finished Means Finished – Never Leave Problems Unresolved
  6. Take Full Ownership. Ask, Escalate, Push
  7. Be Ready for Change
  8. Learn
  9. Take Pride. Have Fun. Celebrate Success.
  10. Meet Your Promises

Let’s look at each one in detail.

  1. Meet Your Promises

We wanted a huge focus on what the client needed, what would make them successful and what had been agreed. Our promises were therefore the target scope, the schedule and the cost budget. We wanted that to be in the thoughts of our team, every minute of every hour of every hard-working day.

I think this is fundamental. It is the foundation principle for all good delivery.

Scope, schedule and budget eventually become commitments, and not eternal items of negotiation. Indeed base-lining is a key management skill. Program leaders will always have to handle change, but must keep the baseline in mind. And they should instill that can do mentality in their teams. That attitude builds client or business trust, and so makes easier the hard times when tough decisions are necessary. In fact, we shared the ten commandments with our clients. We wanted them to be part of the mission.

As part of this, all programs need a purpose that is easy to understand and communicate. Every individual team-member should understand the promises they are supporting. At one level a Concorde is hundreds of thousands of precision components. The simple goal however was to fly passengers supersonically and safely. Any worthwhile program should be easily summarizable. The fine details should also be communicated. Understanding scope, and the basics of any contract, should be a goal for each individual.

  1. Act as One Team.

A team of teams automatically means boundaries. These boundaries can be complex – within a software development team, between the dev team and the business, between a business and its suppliers, between a team and services operated in a cloud, or simply between physical locations.

The challenges that result include: simple blame games, high politics, schoolchild howler style misunderstandings, Everest-sized integration issues, subtle cultural problems and more.

One of my great insights was running a leadership team that consisted of good individuals – actually great individuals – who simply did not function as a team. Boundaries became patrolled borders. With enormous reluctance, I had to change things.

We will look at some of these situations in later articles. Things that will bind a team together include:

  • A simple set of goals (like the ten commandments!)
  • A decent scope definition
  • A good architect who understands links between teams
  • A plan that may be hard, but is believable
  • Good management
  • Good connections with the business
  • Dealing with personality and ego issues, especially in leadership roles
  • Creating a community, and celebrating success

Above all, the aim should be for a culture that encourages the building of trust. It always has to be earned via praxis, but must always be expected.

  1. Aim to be Exceptional, Exceed Targets

 We wanted people to aim high for themselves, and for the team. We especially wanted to avoid the kind of foggy ennui you can find on large programs.

Part of premise is this. Setting specific goals generates higher levels of performance than general goals, and the higher the target the more a person will do to reach that target [this comes from the research of Edwin Locke at the University of Maryland.]

One of my best personal examples of this comes from elsewhere, from my experiences in creating large delivery centres in India. It took our team eighteen months to grow to 500 people. Then potential demand started to increase exponentially. We could have gotten away with continued moderate growth, but I asked the team to aim very high and recruit the next 500 people in the next five weeks. Importantly, I let them go away to think about it.

They went for it. They worked almost 24×7 for five weeks, with a short break for an important cricket match.

By the end of the period they had made 526 offers to good candidates. They had made their own piece of history. And after that, the team knew what they were capable of, and created one of the best large-scale recruiting engines in India. We will return to this example in a future article.

  1. Understand and Report True Status

To this, we added the text:

Good News = +2 points

Bad News = -1 point

Wrong News = – 1 billion points

 This usually raises a smile. It is meant to. Gentle humour is one of the best ways of communicating. But the point it makes is deeply serious. In any team of teams, responsibility and control should be distributed. That is the most effective approach, and it requires transparency and trust.

Good progress is always good. But bad news is useful because something can be done about a known problem. Bad news will also often uncover systematic issues – in the design, the development process, or similar. As we saw in Episode 1 of Masters of Delivery, all programs are about forming a plan and then managing the issues.

 It is wrong news that is poisonous to a large program, and wrong news can be generated by a good team, proud of what they are doing, who want to fix their issues before they become visible.

The test of a team and its management is always through tough times – times I once described as when the sky is dark with the wings of headless chickens coming home to roost.

So, WB and I spent time building this culture of No Surprises, and creating a sense of accountability for knowing status, being transparent and feeling able to report trouble. Above all we wanted people to have the courage to ask for help.

That also requires a certain generosity in management who equally need to view bad news as useful. I would go further: the primary job of management in execution is to help their team with issues

  1. Finished Means Finished – Never Leave Problems Unresolved.

Any team-based process, and certainly any large program, is a series of queues as work moves through the hands and minds of team members. So, any hold-ups have knock on effects. The trick to managing schedule is to get issues resolved fast, so work moves through the system as planned.

A team I once adopted on another project had been stuck in functional design for more than a year. Everything was work in progress. As so often is the case, the team was good. The issue was that there was no systematic connection with the users or key business sponsors, and rather than fix that, every time a design got stuck, new work was started. To resolve the issue, we built bridges and followed a systematic closedown plan in a defined sequence. It worked.

Another well-known aspect is phase containment. Larger projects will almost always consist of releases divided into phases – such as design, build, and test. Problems and gaps in design or requirements will be ruthlessly punished in later testing.

The essence of all of this is to avoid the 90% complete syndrome. The implied remaining 10% is most often the hard, expensive stuff to fix. To quote a British advertising slogan, “Finished” should mean “what it says on the tin.”. Finished should mean finished, completed, done.

Fixing hard problems when they are discovered is almost always the fastest and cheapest tactic.

  1. Take Full Ownership. Ask, Escalate, Push

 With the sub-text: Email alone does not count

 WB and I faced a tough schedule. Our plans were achievable, but they were also hard. We needed a dynamic culture, and a positive buzz in our team. In particular, we wanted people to:

  • Feel they owned their own work fully, and were responsible for completing it
  • Have a sense of reasonable urgency, not to be passive or overly patient in an ‘awaiting’ status.

We especially wanted to avoid seeing the sending of an email as a significant action, or as introducing an allowable delay. We also wanted people to feel free to use management when a decision was needed, – without that seeming an issue between peers. Debate and differences are not conflict, but part of any large team.

This an important topic in a globalizing world where sub-teams will be routinely located in different places, shifted by many time zones. Each sub-team has to take direct responsibility for its own work – but also work hard on interacting effectively with other teams in other locations.

  1. Be Ready for Change

 Change is universal – we cannot escape the second law of thermodynamics. Larger programs are prone to being impacted by change, because they will run for months and years. Change can include:

  • Passionate support for new requirements
  • Unexpected changes in the business, which can result in new work, reduced budgets or cancellation
  • Regulation changes
  • Sponsors getting replaced with people with different ideas

There is much modern thinking around Agile development, which embraces change, and creates cross-functional teams that work in short iterations. This suits certain types of problem, at a certain scale, but there will always be larger projects with a different rhythm.

The key message in this commandment is be ready. It is a job of a project manager or program leader to handle issues and change well, and not let change become mindless, infinite churn. Projects can plan for change via contingency and specific change windows in projects with multiple releases.

The level of engineering of any approach to handle change depends on project scale, but the following will always be required.

  • An anchor – a baseline – from which the impact of change can be judged
  • Adaptability and resilience in program leadership
  • Contingency and change windows
  • A process for tracking and making decisions about change understood by business sponsors
  • An architect or architect team who can assess impacts across a whole system
  1. Learn

 What did we mean by this? One part was personal. We wanted team members, and the client people we worked with to be successful, and to learn from the experience.

Again, the team dimension was critical. WB and I had three releases ahead of us. We needed the team to learn as a whole so we could:

  • Apply insights to improve business functionally
  • Innovate around tools and environments
  • Understand and avoid the first time through issues with Release 1
  • Gather actual metrics against estimates to improve future planning and set productivity and quality improvement targets.

Learning also gives the chance for senior members of the team to demonstrate stewardship by coaching, and handing on their own experience and insights.

The phrase Continuous Improvement captures some of this, but it is dry, implying process improvement. I prefer the more human notion of a learning team, learning collectively and at individual level.

  1. Take Pride. Have Fun. Celebrate Success

 Any team becomes a community. Any large team is likely to be a young community, given the way such teams are built-up, capable of great energy and commitment.

Building a team “brand” around the purpose of a program, and its attitude and results is one step in accessing that energy. Communication of clear goals, and creating that sense of making history will help here.

A healthy level of having fun, of good social interaction also helps make a good team, and although it doesn’t have to be managed, it needs to be recognized as important and supported. It is particularly necessary in today’s global teams, and I would recommend starting any distributed relationship with physical meetings where people can get to know each other, and allow time for social events.

The third element in this commandment is about recognition. Those familiar with Maslow’s hierarchy of needs will remember than esteem and recognition rank highly. People thrive on doing good work, which is noticed and celebrated.

Celebration can be real time. Testing management requires a unique approach, and one talented leader I know used a bell to mark when a test pass had been successful. As a result, applause rippled through his team several times a day. On the last day of testing, the final ring of the bell generated a standing ovation – including from our clients.

Celebration can be personal – public and deserved notes of praise or thanks go a long way. It can be a formal event to mark a major team success.

Create the right spirit, and the rewards are long-term – team-members will work with each other again and again. Such self-sustaining communities, especially if they are open, are powerful, and valuable.

10. Meet Your Promises

 We end where we started. Any program is about a set of promises: to your client or business users, your own team if you have one, and your own management. Great delivery is about meeting all these promises, and learning a little something yourself.

 Get something done, and make a little history, today.

 

 

Keith Haviland is a business and technology leader, with a special focus on how to combine big vision and practical execution at the very largest scale, and how new technologies will reshape tech services.
He is a Former Partner and Global Senior Managing Director at Accenture, and founder of Accenture’s Global Delivery Network.
Published author and active film producer, including Last Man on the Moon. Advisor/investor for web and cloud-based start-ups.

Writings from Keith Haviland