Tag Archives: Leadership

A New View of Apollo 8, NASA’s Perfect Mission

Apollo 8 in 1968 was NASA’s perfect Christmas Mission that at the time awed and moved the whole world. Our forthcoming movie “Mission Control: the Unsung Heroes of Apollo” gives a new perspective on the flight from the consoles in Houston, and shows that Apollo 8 was also an extraordinary example of bold and strong leadership and remarkable teamwork.

A New Movie

In the last two years I have had the privilege to be a producer on the upcoming new Haviland Digital movie Mission Control: the Unsung Heroes of Apollo, working with director David Fairhead and producer Gareth Dodds. We were inspired by Rick Houston, an expert in space history and the author of “Go Flight: The Unsung Heroes of Mission Control”. The film should be released around the spring of 2017.

The film is about a remarkable decade of achievement by the people who worked at consoles in Mission Control in Houston. The team members were born against a backdrop of economic turmoil and global conflict. Some came from a rural lifestyle little changed from the 19th century. Others grew up in a gritty, blue-collar America of mines and smoke stacks. They ranged from kids straight out of college to those toughened by military service. But from such ordinary beginnings, an extraordinary team was born.

They were setting out on what JFK called:

“The most hazardous, dangerous, and greatest adventure upon which mankind has ever embarked”.

Through their testimony – and the supporting voices of Apollo astronauts and modern NASA flight directors – the film takes us from the faltering start of the program through the Mercury and Gemini missions, the tragedy of the Apollo 1 fire to the glories of the Moon landings.

In making the film, we had the immense privilege of spending time with these men, who had taken part in some of the greatest events of the twentieth century.

And for many, it will be a new viewpoint – a viewpoint of the space program from the ground, not the capsule.

Most of us, when thinking about that era, will come first to Apollo 11 – when Neil Armstrong and Buzz Aldrin were the first humans to walk on the lunar service. But almost universally, for those in Mission Control, their favourite mission was not the moon landing – extraordinary as that was – but the first journey to orbit the moon: Apollo 8.

1968 – A Year of Challenges

1968 was a difficult year. In the world at large, it had started with the North Vietnamese launching the Tet offensive. It was also to be the year of the My Lai massacre. In April, Martin Luther King Jr. was assassinated. There were riots in Paris and Chicago, and a sense of revolution hung coldly in the air. In June, Sirhan Sirhan shot Robert Kennedy, and in the autumn, the Soviet Union invaded Czechoslovakia.

It had also been a challenging period for NASA. In January of 1967, a fire had swept through the first Apollo capsule intended for space during a ground test. The fire was caused by a mix of bad wiring and a pure oxygen atmosphere. And because the escape hatch mechanism was clumsy, three astronauts lost their lives in horrible circumstances.

The pain of that event is still felt fifty years later. It was an avoidable and unexpected body blow for the Apollo program – one that could have easily proven fatal.

Flight Director Gene Kranz – famous for his core role in saving the Apollo 13 crew – had taken his team aside at that point and asked them to take and feel their own accountability, and then write on their blackboards the words tough and competent– a vow to do their best and strive for excellence, but also be willing to raise their hands when schedule and other pressures threatened a mission and its crew.

So, 1968 for NASA was a year of recovery and regrouping. And many – including Dr Chris Kraft, the creator of Mission Control – came to think that period of recovery proved to be necessary and essential. With the tragedy and without the cold and clear response from NASA in improving things, the moon landings may not have happened.

The main spacecraft was redesigned to a higher “Block II” standard. Flammable materials were eliminated from its interior. The hatch was made easy to open. The NASA leadership of the era passed the main test of real leadership: can you handle the bad times?

The first success of this new phase was Apollo 7, where a three-person crew tested the main spacecraft – the CSM or Command and Service Module. This flew without a real hitch in Earth orbit in October 1968.

It still wasn’t plain sailing. Apollo 6 – an uncrewed mission – had tested the mighty Saturn V rocket and it had turned out to be quite a ride. The launch was so violent that the rocket had “pogo-ed” , and any crew would have been injured or killed. The design was later changed so that helium gas was pumped into voids in the ducts leading to the F-1 engines to change the overall resonance characteristics of the vehicle. There were also issues that caused the premature shut-off of engines in the second stage, requiring another set of fixes.

And then the lunar module – the spidery and fragile craft that was meant to land on the Moon – was proving to be “a horrible piece of hardware.” It was not ready. There were too many defects to meet the schedule. It would take many weeks to fix.

And Apollo 8 was meant to test the lunar module in Earth orbit.

A Moment of Agility

The word agility is used a lot in modern business to describe approaches that can deliver results fast and handle change well. It’s a word that belongs to the 21st century.

But NASA in the 1960s remains an example of agility that still startles.

In the summer of 1968 and in a decision that would be remembered as an act of extraordinary vision and boldness, George Low, the Manager of the Apollo Spacecraft Program Office, proposed that Apollo 8 be instead sent to orbit the moon without its Lunar Module.

The risks were extraordinary.

  • This would be the first manned flight using the mighty Saturn V – a rocket that had just had its severe issues with “pogo-ing” fixed but not tested. It was a bold step indeed to use its first crewed flight to travel almost a quarter million miles to the Moon.
  • Any trip to the Moon also required intense planning and training , and the discussions had started just a few weeks before the earth orbit Apollo 7 was scheduled to fly. It was a tough schedule to meet. Would it be even possible?

Glynn Lunney, a Flight Director and one of the most important figures in NASA Mission Control during the Apollo years summarized the thought process that would typify the response of NASA senior management:

  “I went in minutes from ‘crazy’ to ‘brilliant breakthrough’, and ‘why didn’t I think of that’?”

So, the mission imagined on almost the spur of the moment rapidly gained the support of almost all NASA’s senior managers. They understood the immense morale boost it would create, and they had confidence in their vehicles. Above all, the team that had formed out of Mercury, Gemini and the early days of the Apollo program had gained immense confidence in itself. This great challenge could be met. This mission was possible. It was a Go!

Training was started in September. No public announcement was made about the real intent of the mission until November 12, less than 40 days before launch. The news of the real goal of Apollo 8 stunned and exhilarated the public. American astronauts were going to the Moon … and at Christmas.

Even those in Mission Control were shocked. John Aaron – a key figure in many flights including Apollo 13 – would think:

You’re going to do what?”

Launch

On the morning of December 21, the Apollo 8 crew – Frank Borman, Jim Lovell and Bill Anders – was awakened in the small hours, and given a traditional breakfast of steak and eggs.

As for Mission Control, it would operate 24×7 in three shifts, led by Flight Directors Charles Charlesworth, Glynn Lunney and Milton Windler. The atmosphere in Mission Control was intense. As Jerry Bostick remarks in the film, every thing was checked and rechecked.

“This no simulation … was for real”.

The countdown proceeded smoothly and at 7:51 AM, the four hold-down arms were released and the Saturn V moved slowly into the air, driven by many millions of pounds of thrust. It did not shake as violently as Apollo 6 and the crew were safe.

Astronaut Michael Collins was the CAPCOM (Capsule Communications) on duty on the ground and at 2 hours, 27 minutes and 22 seconds in the mission radioed,

“Apollo 8. You are Go for TLI.”

TLI stands for “Trans-lunar Injection”. It gave permission to the spacecraft to leave low-Earth orbit. The engine on the third and final stage of the Saturn V fired again.

Apollo 8 was now the first manned interplanetary spacecraft. And the crew would find time to take the first pictures made by humans rather than robots of the whole planet Earth.

Reaching the Moon

As they approached the moon, the crew began to prepare for Lunar Orbit Insertion or LOI. This was a particularly tense moment. It depended on a burn of the service module engine on the far side of the Moon, when the spacecraft was alone and out of contact with Earth.

After the key members of Mission Control were polled for a “go” or “no go” decision, the crew was told that they were “go” and “riding the best bird we can find.”

Mission Control had set up two countdown clocks. If Apollo 8 regained contact at the first timing point, then no burn had happened and LOI had failed. If it regained contact at the second timing point, the burn had worked perfectly. Anything else was real trouble. The craft could be heading into solar orbit or towards impact on the lunar surface.

It was at this point that Lunney – who was the flight director on duty, said:

“Okay, all flight controllers, this is a good time to take a break.

It amazed the members of Mission Control at first, but on reflection there was nothing to be done for around 20 minutes. Some of them took advantage. Eventually, the first countdown clock expired. There was no signal. Tension in Mission Control increased. Then the second clock expired. Apollo 8 radioed at that exact point

“Houston, this is Apollo 8. Burn complete.”

The engine had performed as it should. Apollo 8 was in orbit around the moon.

In Orbit

It was then that the crew could start observing another world – one of the prime purposes of the mission, and essential preparation for future landings. They would take many hundreds of photos. Jim Lovell would characterize the surface as:

“The Moon is essentially grey, no colour; looks like plaster of Paris or sort of a greyish beach sand. “

Bill Anders would add:

“Looks like a sand pile my kids have been playing in for a long time—it’s all beat up—no definition—just a lot of bumps and holes.”

These were the words of pilots and engineers. Plain, without romance. But poetry was coming.

The Genesis Reading

As Apollo 8, rounded Moon for the ninth time, they began another TV transmission. They first described the lunar surface for the people on Earth, Borman characterizing it as a “a vast, lonely, forbidding expanse of nothing.”

Then Anders said crew had a message for all on Earth. It was at that moment that each of the astronauts read a section from Genesis, about the creation of the Heaven and the Earth. It had been selected as a part of the bible with resonance across multiple religions.

“In the Beginning god created the Heaven and the Earth. And the Earth was without form and void. And darkness was upon the face of the Deep. . . . And God saw that it was Good. . . . “

Borman ended the broadcast with:

“And from the crew of Apollo 8, we close with good night, good luck, a Merry Christmas and God bless all of you – all of you on the good Earth.”

This was a hugely moving and unexpected experience for those in Mission Control. Flight controller Jerry Bostick later wrote:

“I was totally overwhelmed, and tears came to my eyes. [What could be] more appropriate than a Bible reading about creation, coming from the first people to ever leave the influence of Earth, on Christmas Eve?”

Returning Home

The next critical moment was Trans-Earth Injection, or TEI. The service module engine needed to be restarted a second time, and perform another perfect burn. Again, that would be done behind the moon.

It worked, and Lovell reported:

  “Houston … please be informed, there is a Santa Claus.”

After the long coast back to Earth, the Apollo 8 Command module re-entered the atmosphere with the fire and dreadful violence that comes from interplanetary velocities. The deceleration peaked at around 6g, as the spacecraft met the resistance of Earth’s atmosphere.

Anders would say:

“You could see the flames and the outer skin of the spacecraft glowing; and burning, baseball-size chunks flying off behind us. It was an eerie feeling, like being a gnat inside a blowtorch flame.”

At around 10,000 feet the three main parachutes slowed the Command Module, and it splashed down south of Hawaii.

Apollo 8 – In Retrospect

In the end, Apollo 8 was a genuine and complete success. It was indeed a perfect mission. Jerry Bostick would say: “It was bold, it was exciting, and it was successful.”

 Chris Kraft – who created the very notion of Mission Control – notes in his autobiography how many historic firsts it scored. It was the:

  • First manned flight of a Saturn V
  • First manned vehicle to leave earth’s gravitation field
  • First use of a computer to provide total “onboard autonomy” in navigation
  • First manned vehicle in lunar orbit
  • First close-up view of another planet
  • First exposure to solar radiation beyond the earth’s magnetic field
  • First vehicle to rocket out of lunar orbit
  • First manned vehicle to re-enter from another planet

Perhaps the impact of the Mission is best summarized by a telegram sent to Borman by an unknown citizen that stated:

“Thank you Apollo 8. You saved 1968.”

Apollo 8 as an Example of Leadership

Apollo 8 of course is also extraordinary example of bold and strong leadership and remarkable teamwork.

Coming less than two years after the Apollo 1 fire which could have halted the program, it represents true both organisational resilience and the genuine acceptance of accountability. NASA were truly “tough and competent”.

It demonstrates adaptability, creativity and agility. Apollo 8 was meant to be an Earth orbit mission. The bold and courageous mission that replaced that original intent probably shortened the path to the Moon. It was a decision made quickly and decisively.

It demonstrates the high performing team at the heart of NASA and Mission Control – who were able to create a new and complex mission plan for humanity’s first mission to another world in a matter of weeks.

Apollo 8 was also a remarkable moment in communications, in PR and marketing. At the end of a deeply troubled year, its success bound together humanity for a moment.

In summary, Apollo 8 is a perfect example of the power of vision and imagination, followed by perfect execution.

And it happened at Christmas.

Keith Haviland

This article is an extended version of an article first published in 2014. Many thanks for David Woods for insight into the Apollo 6 launch.

Keith Haviland is a Former Partner and Global Senior Managing Director at Accenture, and founder of Accenture’s Global Delivery Network. He is also a film producer and CEO of Haviland Digital – dedicated to intelligent film, TV and Digital Media.

Last Man on the Moon is now released!

“I went to the Moon. What can’t you do?” – Gene Cernan

Our film “The Last Man on the Moon”, from Mark Stewart Productions,  is now officially released. It is showing in selected cinemas in North America, is available on iTunes, and US Blu-rays and DVDs can be pre-ordered. Initial reviews have been excellent.

12027390_527051210789746_3263581701015699599_o
From left to right: Mark Craig Director; Keith Haviland Co-Executive Producer; Eugene Cernan; Gareth Dodds, Producer and Mark Stewart, Executive Producer.

The film is a feature-length biography of Eugene Cernan, astronaut, aviator, friend and family man. The core team consists of Mark Craig, Director; Gareth Dodds. Producer; Mark Stewart, Executive Producer and – of course – Commander Cernan himself. It has been a great personal pleasure and privilege to have supported this project.

Like all good films. it works at many levels. It looks and sounds beautiful. It is intensely human and at times very funny or intensely moving. The movie appeals to a wide audience, and people with little interest in spaceflight still become engrossed in its gripping story about a man, his family and his friends. The section about the Apollo 1 fire is deeply sad. Sections on Gemini 9 and  Apollo 10 recreate the drama of manned spaceflight. The treatment of Apollo 17 (the last Apollo mission to the Moon) is celebratory, and sometimes approaches the spiritual.

12792272_527055430789324_1841839854561418748_o
Gene Cernan being interviewed at the Houston premiere of “The Last Man on the Moon”.

At the heart of the story is Captain Cernan’s remarkable personal journey. From humble beginnings, he became a skilled Navy aviator. He was next accepted as an astronaut, and the film allows you to share his raw joy at that moment. During his NASA career, he faced some difficult missions, dealt with genuine tragedy, and makes his own mistakes – including a poorly timed and avoidable helicopter trash. But he retained his passion, his ambition and an absolute focus on the program. He became remarkable leader, and to this day can still light a room and inspire people with his presence.  The film expands to cover his family life, and his deepest friendships, and also manages to be one of the best histories of the golden age of the Apollo era.

The film will appear in other regions soon. To keep up with the film’s progress visit the film’s Facebook Page or its dedicated website.

Enjoy!

The-Last-Man-on-the-Moon_poster_goldposter_com_21

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 being Co-Executive Producer on “The Last Man on the Moon”. Advisor/investor for web and cloud-based start-ups.

Lost on Mars – Christmas 2003

Christmas Day 2003 was meant to be a special day for the exploration of Mars, and for a charismatic scientist named Colin Pillinger. In the end, it was the key moment of a story that involves loss and rediscovery, innovation, lessons around program management and flawed but inspirational leadership.

A probe called Beagle 2 – christened after the ship that supported Darwin’s famous voyage of exploration – was intended to land on the Martian surface in the small hours of Christmas morning, UK time.

Its destination was Isidis Planitia, a vast impact basin that sits across the border between the ancient highlands and the northern plains of the Red Planet.

Beagle 2 was a low-cost, small-scale and minimalist British spacecraft. It had, however, audacious goals to directly search for life. Colin Pillinger was its Principle Investigator.

After piggybacking across tens of millions of miles of empty space, the craft had detached from its mother ship, the European Space Agency’s (ESA) Mars Express, on 19th December 2003 where it would fall towards Mars on a relentless ballistic trajectory.

A Violent Landing

mars-express_beagle_art_atmosphereentry_1600x1078The plan was this. Beagle 2 would slam into the Martin atmosphere at 20,000 km/hour. After a violent deceleration in the Martian atmosphere, parachutes were to deploy. Then just two hundred meters above the Martian landscape, large airbags would inflate to cushion the final impact of the vehicle. The lander would bounce on the surface at about 02:45 UT on 25 December 2003, and come to a stop.

At that point the top of the lander would peal open, pushing out four solar panels. A signal would then be sent to Earth immediately after landing and another the next Martian day to confirm that Beagle 2 had survived both the landing and its first lonely and cold night on Mars.

That was a prelude to the real science. A panoramic image of the landing area would later be taken using the stereo camera. The lander arm was to dig up soil samples for analysis, and a probe nicknamed the mole would inch its way across the surface. Beagle 2 would begin to make its contribution to history.

No Signal

It didn’t happen that way of course. Instead on that Christmas Morning, there was a cold, distant silence.

A search begun. Throughout January and February, Mars Express, the American orbiter Mars Odyssey, even the great Lovell Telescope at Jodrell Bank would attempt to pick up a signal from Beagle 2. Throughout the Beagle team said they were “still hopeful” of finding a successful signal.

But every time there was no such signal, no sign of the little craft.

The Beagle 2 Management Board declared beagle 2 lost on 6th February 2004. On 11 February, ESA announced an inquiry would be held into the failure of the mission. The results of that enquiry would prove to be highly critical.

Origins

Beagle_2_e_Colin_PillingerThe voyage of Beagle 2 started within the Open University – a British distance learning institution created in the 1960s. Its scientists have been major contributors to the study of a group of meteorites blown off the surface of Mars and the suitability of the ancient Martian environment for life.

In 1997 ESA announced Mission Express with a 2003 launch date. It was then that Colin Pillinger of the Open University team, and a member of the ESA Exobiology Study Group, proposed a lander. The craft would be dedicated to looking for life and conducting chemical analysis of the Martian environment. The name Beagle 2 arose quickly, and Colin himself gave the rationale:

“HMS Beagle was the ship that took Darwin on his voyage around the world in the 1830s and led to our knowledge about life on Earth making a real quantum leap. We hope Beagle 2 will do the same thing for life on Mars.”

The journey had started.

A Very British Eccentric

Colin Pillinger was a larger-than-life figure, and had cast himself from the mould of the archetypal British eccentric scientist. He lived on a farm and possessed “mutton-chop” whiskers that always made him instantly recognizable. Personally, he could be challenging. Professor David Southwood of Imperial College would say:

“My own relationship with him in the Beagle years was stormy … Fitting the much bigger Mars Express project, as I had to, around Colin’s far from standard approach was not easy and he could be very exasperating. Nonetheless, he had genius, a very British genius”.

He could also be inspiring and inspirational. Professor Monica Grady was once one of Pillinger’s PhD student. She would say:

“He was a determined and controversial figure. I crossed swords with him more than once in the 35 years I have known him. But he was enthusiastic, inspirational and never failing in his drive to promote planetary sciences and the science that would come from missions to the moon and Mars. He was one of the most influential people in my life.”

He and his team certainly had a flair for grabbing attention. To put the Beagle 2 project on the map and get financial support, they got the band blur to record mission’s call-sign was composed by the band Blur. The calibration target plate intended for testing Beagle 2’s cameras and spectrometers after landing was painted by Damien Hirst.

Pillinger raised sufficient funds to attempt the mission – although funding was always very light by international standards. A consortium was created to build the probe across the Open University, the Universities of Leicester and Wales, Astrium, Martin-Baker, Logica and SCISYS.

Mars Express launched from Baikonur on 2 June 2003, and on it sat its little disk-shaped companion: Beagle 2.

Analysis of the Failure

In May 2004 the findings of the ESA report were published in the form of 19 recommendations, many of which speak about issues that will be familiar to any student of program management.

It could – and certainly was – read as an indictment of Colin Pillinger’s leadership and management style. The Telegraph newspaper would say the report:

“is believed to criticize the management of the project and blame a lack of testing, time and money for its failure. While he is not named directly, the report is likely to be seen as critical of Professor Colin Pillinger … even before the probe left for Mars … critics of Prof Pillinger warned that Beagle 2 had not been adequately tested”

There were recommendations that covered accountability, and adequate resourcing. Others mentioned the need for appropriate systems level documentation and robust margins to cope with the inherent uncertainties of space flight.

There was also an underlying assumption that Beagle 2 had failed catastrophically. So many of the recommendations covered testing of all kinds, and especially the shocks and processes around entry and landing.

But the truth was that Beagle 2’s fate was a mystery. The probe – without landing telemetry – had simply vanished.

Aftermath

Colin Pillinger continued to display his usual spirit after the report. He said shortly after publication “It isn’t over with Beagle by any means.” He continued to push for another landing attempt, but unsuccessfully.

Then tragically, after a period of ill health, he died unexpectedly of a brain hemorrhage, just two days before his 71st birthday at Addenbrooke’s Hospital in Cambridge on 7 May 2014.

The obituaries were respectful. Just getting Beagle 2 started was seen as an achievement, and many gave him the credit for rekindling British interest in space and space flight.

But he died not knowing what had happened to the spacecraft he had conceived and build.

History is Rewritten

PIA19107-Beagle2-Found-MRO-20140629

But then history was rewritten.

On 16 January 2015, it was announced that the lander had been located intact on the surface of Mars by NASA’s Mars Reconnaissance Orbiter, in the expected landing area within Isidis Planitia. The images had been taken in 2013, but not analyzed until after Pillinger’s death.

The images demonstrated the probed had properly landed and partially deployed, with its parachute and back cover nearby. Some of the solar panel petals had deployed, but not all, preventing deployment of its radio antenna. Beagle 2 appeared to have just a few mechanical movements and one faulty motor from success.

One newspaper claimed:

The history books must be re-written to show that the Beagle 2 mission was a success after the first pictures of the probe proved that it did land safely on Mars, vindicating lead scientist Colin Pillinger.

Dr David Parker, then CEO of the UK Space Agency would comment:

“Beagle 2 was much more of a success than we previously knew. The history books need to be slightly rewritten to say that Beagle 2 did land on Christmas Day 2003.”

Conclusion

In the final analysis, Beagle 2 was a most peculiar space mission – created by a British eccentric and funded poorly. It was also perhaps poorly program managed.

However it was genuinely inspirational, becoming a project that touched people’s hearts and minds. There is no doubt it failed, but we now know  it also came within moments of absolute, joyous triumph. This little, underfunded craft almost worked. As Colin Pillinger himself once said

A little set back like a lost lander should not discourage visionaries.

Images used in this article are from ESA and NASA.

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.

Vision + Execution = Greatness

Vision is core to good leadership, and the best management. It is the essence of successful programs, the heart of effective transformation and the engine of innovation.

It is also what teams want from their leaders. James Kouzes and Barry Posner once wrote in the Harvard Business Review:

 “Being forward-looking—envisioning exciting possibilities and enlisting others in a shared view of the future—is the attribute that most distinguishes leaders from non-leaders. We know this because we asked followers.”

The Kennedy Commitment

One of my favourite examples of how an extraordinary vision can become reality is when Kennedy promised the world, before the US had even fifteen minutes of manned spaceflight experience:  “I believe that this nation should commit itself to achieving the goal, before this decade is out, of landing a man on the Moon and returning him safely to the Earth.”
The Kennedy vision is truly remarkable because it was achieved, in full. The simple promise was turned to powerful reality by the leadership, intense focus and personal commitment of 400,000 people at peak.

Vision + Execution = Greatness

So, for me the essence of real leadership is precisely this combining of vision with the ability to execute. Another leadership thinker, Warren Bennis, once said:  “Leadership is the capacity to translate vision into reality.”
This is not straightforward. Many of us will have seen corporate vision or strategy documents that are strong on the Promised Land, but not the hardships and challenges of the journey to get there. Many good ideas come to grief on the cold, sharp-edged rocks of delivery.

Example: The Global Delivery Network

My own most intense experience of combining big vision and successful execution comes from building the Accenture Global Delivery Network, and, within that, its Indian Delivery Centres. Today, the company is one of the dominant players in India-based and global delivery of technology services. In hindsight, the journey seems inevitable, almost a slam-dunk. But it wasn’t always like this.We started practical work with a small core team of India leaders, Brits and Americans in late 2000, at the request of the charismatic, global head of Financial Services. He felt the intensity of coming global competition, and had the vision to take action.

This core team would become true masters of delivery and client service. They would achieve extraordinary things in their careers. (And to give credit were it is due, we were also strongly supported by experienced leaders in the US and Spain, reflecting the already global personality of the company. They would give us resources and counsel.)

Meeting in Mumbai

The initiative and initial investment was based on creation of an initial team of just 200 people. There are now 100,000s of people in the firm’s global delivery network. At the time that would have seemed to many the purest fantasy, although some of us had a glimmer of what might be possible. However, we were starting with a small step.
By the summer of 2001 had two clients and the 200 seats in the India city of Mumbai, only partially filled with people. Our initial task was getting close to completion. But we knew that our responsibility was much greater, and it was time to plan the next stage.
So in a meeting room in Mumbai, lit brightly by sunlight, we discussed want we wanted to achieve. We needed an aspirational vision but it needed to be practical, based on specific goals and achievements that we could easily communicate.

Vision on a Whiteboard

At the end of our discussion, I drew a whiteboard diagram to summarize and took a photo for future reference. I felt that it would be important, at least as a personal memento. In fact, it would years later be published in a celebration of the Indian team’s success. Although it was formalised and turned into detailed, properly costed plans, our simple whiteboard summary turned out to be a foundation stone.
The essence of this vision was what we needed to do to catalyse growth. Unlike typical start-ups, we were blessed with a vast and impressive existing channel. We needed scale and momentum, coupled with our first core offerings. We had to convince our salesforce and then our real clients we were credible in a new market. I had an instinct that once we passed that test of credibility, our growth rates would look exponential. And so it was to be. But first we had to get started.
So, the top half of the whiteboard looked like the following. (Our financial year ran from September to August, so Q1 of FY2002 starts in September 2001).
 Slide1-001

Simple Targets

This wasn’t a conventional vision or strategy. It was stripped down to a bare minimum of supply-side metrics. But it would serve its purpose. It covered the following:
  • CMM targets that refered to the 5-level Capability Maturity Model from the Software Engineering Institute located at Carnegie Mellon University. This aims to measure the quality of software delivery processes. The true value of CMM – and its descendents like CMMi – is subject to debate. However, it does require a rigorous focus on process and quality, and was essential to competing in this new market. We had to reach the highest levels of the model fast. These targets would soon evolve into a much more profound focus on offerings and industrialisation.
  • Most importantly, the diagram showed the headcount growth we wanted to achieve in the next two years – headcount would be a vital and simple metric of our progress. The goals we put down – given we were starting from scratch – were tough. We would have to keep the people we hired busy, engaged and chargeable. We were in essence already anticipating an exponential growth curve.
  • The diagram also shows our intent to move into three cities as part of building a platform for growth. Getting support for this rapid geographic expansion would not be easy, but it would provide flexibility and scalability. In fact we opened in 2002 in Bangalore, followed by Hyderabad a little later. Bangalore was destined to become a true global hub.

Building a Team

The second half of the board contained another diagram that I have also recreated below. It shows something else we realised very early on. We need a focus on building a team for the future, not simply a collection of new resources, but a group of people – a real team – who shared a strong sense of culture and common cause. Slide2-001

Communicating the Vision

We now had goals that were hard to achieve, but inspirational for our core team, easy to measure and simple to communicate. This was also fundamental. As PeterDrucker once said: “Leadership is lifting a person’s vision to high sights, the raising of a person’s performance to a higher standard, the building of a personality beyond its normal limitations.” We needed to be able to straightforwardly tell our story and our intent to a team freshly hired, and get them to become leaders in a  long journey of transformation. We used our whiteboard goals as the anchor for that process.

Start-Up Days

Work started very practically, with the joys and stresses of any good start-up. One of team – who was destined to become a much respected Senior Managing Director – help dig the cable trenches in the tarmac outside the main building. We built our first big client meeting room the day before our first big client meeting. Recruiting was hard at first. Really hard. We hadn’t built our brand in the relevant technology talent pools. We did have a thriving local consulting practice. However, we were unknown to the people we needed for tech work. The vision helped. So did phone calls and events with candidates, their parents and families to show our intent, and the possibilities ahead. Our India leaders worked hard to sell our story, and with passion. Good people began to join us.

A Key Test

Then came a moment that I have written about before, but remains a pivot point of this slice of history. We had reached 500 people, and acquired more space. Overall, with a little difficultly, we had balanced demand and supply effectively. Our HR team had made a brilliant start. Now demand for people was increasing. We were beginning to see supply challenges. It was the start of the exponential growth curve I had expected, hoped for and feared, just a little. I asked our talented local leaders this: Although, it has taken eighteen months to grow to 500 peoplewe need to hire 500 people in the next five weeks. Can you do it? Those who have built and worked in start-ups know how hard an ask this was. And what the mood of that meeting, when a world of pain and hard work was opening up before us? It was tremendous – full of energy and laughter. They had a can-do, will-do attitude”  and were committed to the vision. They went for it. We hired many HR contractors, and arranged for virtual interviews across the globe. We created a large war room with white boards to record real-time status. And then we held interviews, thousands of times. By the end of the period they had made 526 offers to good candidates. This was a break through moment. The India team went to trounce all the targets in the initial strategy. They had a vision, they had executed well.  When we found a rare moment to reflect, we all felt we had shared in a period of great accomplishment.

Evolving the Vision

After that we adapted the vision and strategy on a six-monthly basis. It become a regular part of our process, both in India and globally. We looked ahead at our business challenges and opportunities, at what innovations were possible and what offerings would drive growth. We worked on horizons of now (immediate issues), three months, 12 months and 3-5 years. As a result, we drove higher levels of industrialisation, delivery innovation and accountability. We added a strong focus on business and industry skills. We opened in seven cities, and introduced ways of dealing with huge scale. We introduced offshore approaches to consulting and systems integration, beyond the normal outsourcing focus of global delivery. Throughout the focus remained on vision and execution.

Looking to the Future

What of the future? Global delivery models are now part of the fabric of IT services.  They are standard, and expected. However, as always, there is new opportunity on the horizon. This is not so much from fashionable digital business models. These are important,  but even more important is the systematic underlying change from an old world of devices and systems to a new universe of services and infinite sharing in the cloud. Agility becomes possible at scale in ways it never has before, and our connection with technology will be completely transformed. So, there is still plenty of scope for leadership that combines ambitious vision, and successful execution. There are still histories to be made.

Keith Haviland

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.

Stewardship: A Fundamental Part of Good Leadership

“The price of greatness is responsibility.”– Winston Churchill

Meetings in Hollywood and London

The meeting was over drinks in the Roosevelt Hotel in Hollywood. It was with an old friend who I had worked for in the late 1980s. He was then leading a technology start-up in London, specialising in UNIX and Open Systems. The company was a true prototype for the eCommerce and Digital start-up waves of the 21st Century. It was tech-savvy, youthful, ambitious and diverse. It had energy and pzazz.

It became a business success, and was sold in 1990. It was also a cultural success. People liked working there. Even today in 2015 there are occasional re-unions of the core team.

My friend had then moved to LA to try his luck in the world of film. Again he had successful, and now lives in a Spanish style villa in the Hollywood Hills.

We spoke about his plans, and mine. It wasn’t long before I realized that, although I hadn’t worked with him for twenty years or so, he wanted me to develop and be successful. He still felt his old loyalty to his previous team.

Cut to another scene. It is a few weeks later. I am having lunch in London with another old friend, someone I have worked for a little more recently. He had been a respected leader in both commerce and public service. Again, I felt that same sense of support, and quiet, steady belief. Here was someone who wanted others to succeed almost as a natural reflex.

Stewardship

people-297819

This led me to reflecting on what I think is one of the most essential qualities of good leaders: stewardship.

One of my alma maters is Accenture, a company who organize people on a global scale. It has a set of simple core values intended to help define its culture. To paraphrase, these include: integrity; respect for people as individuals; a focus on acting as a team; excellence and, above all, prioritizing client service.

And as an instruction to leaders, this set of values also includes the word stewardship – which means a focus on the greater good, thinking of the future, and the development of the people around you. It has been a fundamental element of that company’s long history, arising from its origins as a partnership.

Over the years, and across companies, I have had the privilege to work with many good leaders, and the best naturally adopt a stewardship style. They care about the future of both their business and their team with a natural grace and enthusiasm. Above all, they think about the motivations, development and careers of the people who work for them.

This does not need to be at the expense of being able to make tough calls. Indeed some of the best stewards are also courageous. One leader who worked for me in building the Accenture Global Delivery Network was a red-blooded operator – able to direct without hestitation, and do the hard things at scale. He is one of the masters of delivery it has my privilege to work with.  However, he also ensured that the bi-annual performance management process of a large group of people was undertaken with a huge amount of care, professionalism and objectivity. The views of his own leadership team were fully taken into account, and balanced. When it mattered, he acted as a steward. It impressed me, and a great many others, enormously.

Aspects of Stewardship

hand-173584_1920

There economic models of stewardship cultures in enterprises, and a whole literature on “servant leadership.” However, what follows is my personal definition of major attributes of stewardship, written as advice for leaders and potential leaders.

  • A combination of strong values and an inspiring vision, communicated well. The vision is essential for setting a direction. It should be adaptable, but stable enough to allow consistent execution. The values will enable you to handle change, and trouble, and create the foundations of the culture you aim to build.
  • Loyalty. By this, I mean the loyalty of leaders to their teams. Great teams can be created when people know you “have their back”, that what you say is what you mean, and you want them as individuals to progress and prosper. Loyalty is something best returned, rather than exhorted or demanded.
  • Courage. It is important to have the skills to deal with challenges and failures in a positive way. This can mean being simple and direct about bad news, or poor performance. Truth is at the heart of delivery and learning. Courage can also mean a leader constructively standing up to his own boss when poor decisions are being made – since even great people will make poor calls.
  • A relentless focus on recognition. People thrive when their achievements or hard-work are celebrated. It is a core part of what most individuals will want out of their career. And sometimes a simple thank you is plenty enough. It still amazes me how many of those in management positions don’t recognize the value of this kind of simple engagement. As with loyalty, give credit, and you earn it back.
  • An unyielding emphasis on development. If you want long-term growth, you need to develop your team, and build a flexible leadership bench for the future. You need to worry about the progress of each individual, and what skills or encouragement they each need to succeed. This is much broader than succession planning, which often has a narrow, static focus. Indeed, when a company starts treating its middle management as an economic issue that is ultimately a failure of top leadership and their stewardship foresight.
  • Forward thinking. The job of a leader is to make sure future challenges are anticipated, offerings are adapted to changing markets, and structures flex with growth. As I was building the Accenture Global Delivery Network, I made myself think frequently about horizons of 3 months, 12 months and five years. It worked well, during a long and exhilarating period of quasi-exponential growth.
  • Providing an environment in which good can be done. When I started working with people in India, the Philippines and other developing countries, I was very struck by the intense enthusiasm for supporting local communities, and for giving something back. It was humbling, and inspirational. This taught me the importance of making sure a sense of the common good was part of the cultural fabric. Such a culture will start many experiments in achieving excellence in client-service, improvements in training, initiatives in diversity, and action to help the community and environment. And some of these experiments will work.

Benefits

leaf-749929_1920

What are the benefits of stewardship?

It creates the kind of positive culture where teams want to deliver excellence in client service, and continuous improvement. It enables long-term growth because you naturally create a bench of leaders able to take your place. It creates an almost unconscious loyalty, with high levels of engagement, and lower levels of attrition. And your future leaders will develop their own sense of stewardship.

It creates open channels of communication, because people work in an atmosphere of trust. It can make a real impact on local communities through an effective corporate social responsibility program. In the end you can create a place where people aspire to work, to serve and progress.

Conversely, toxic leaders who are interested in personal position first and foremost will often do a great deal of damage, and can leave ineffective teams behind them. And even formerly respected leaders who break a bond of trust can see the morale and performance of their teams drop dramatically.

However, the final message is an immensely positive one. Stewardship cultures feel right. They also are right – bringing great benefits in culture and client-service. Above all, they bring the ability to grow, at scale and in the long-term, in a dynamic and changing world.

Keith Haviland

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.

 

 

Enduring Leadership Lessons of Apollo 13

Apollo 13 Launch
Apollo 13 Launch

Forty five years ago, astronaut Jack Lousma was acting as the ground-based Capcom (a shorthand for Capsule communicator) for the Apollo 13 mission, which was in its coast phase towards the Moon.

The mission so far had been routine. Lunar missions seemed to have become almost straightforward. Lousma asked the crew, as part of normal operations:

13, we’ve got one more item for you, when you get a chance. We’d like you to stir up your cryo tanks.

The response – initially from Command Module pilot Jack Swigert has become a modern legend:

Okay, Houston —I believe we’ve had a problem here.

There had been an explosion. The crew’s first thoughts were that a meteor might have struck the Lunar Module. In fact, an oxygen tank had exploded because of an old wiring issue inside the tank. The following image – taken in the last minutes of the flight – shows the immense damage done to the Service Module.

Damaged Apollo 13 Service Module
Damaged Apollo 13 Service Module

What followed is equally well known – a story of resilience, ingenuity, guts and adaptability. The main Command and Service Module Odyssey would be powered down, and the Lunar Module Aquarius would become an unexpected lifeboat, supporting the full crew way beyond its original design limits. The moon was lost. The rest of the mission would now have a life and death focus on managing resources and controlling the spacecraft’s trajectory. The unfolding events would grab the world’s attention in a way that was unprecedented – billions of people would care, and sometimes pray, for the Apollo 13 crew during their encounter with fate.

Cutting to the present day, It was my privilege to attend a Forty-Fifth anniversary celebration of the mission at Cape Canaveral last Saturday. The highlight was a panel discussion with the surviving astronauts (Jim Lovell, and Fred Haise), mission directors (Gene Kranz, Glynn Lunney, Gerry Griffin) and the Capcom team (Vance Brand, Jack Lousma and Joe Kerwin). The discussion was both entertaining and hugely inspiring. We sat in front of real history.

Again it struck me again how perfect Apollo 13 is as a modern parable: a parable of leadership; of how to take action in a moment of complex crisis; of teamwork, and of engineering excellence. I have often used it in my own thinking, and teaching.

In no particular order, here are just some of the lessons Apollo 13 can teach us.

The Power of Teamwork. The film Apollo 13 centres on Jim Lovell and Gene Kranz. It has to, in order to present a complex real-life drama with the confines of the movie format.

But it was not for nothing that the panel at the celebration event consisted of multiple astronauts and flight directors. And every member of that panel emphasised the importance of teamwork, and how they themselves represented the efforts of 1000s.

Indeed, before cell phones and modern communications, without asking and within a short period after the incident, Houston Mission Control and many other NASA centres were filled with NASA members and supporting contractors. People would be at their desks for days, dividing up an immensely complex problem into solvable pieces. NASA and its suppliers pulled together to save the three astronauts as they swung around the moon.

The Power of Responsible Leadership in a Crisis. One of the key moments for the flight directors managing the crisis occurred when they – represented by Glynn Lunney and Gerry Griffin – went to brief NASA leadership, who would themselves have been under a great deal of hard-edged public pressure. The flight directors went through five complex recovery scenarios, and made their recommendation out of that five.

Given the importance of the decisions being made, the Flight Directors were ready for challenge. The challenge that came delighted them

We have just one question. How can we help?

Those of you who have worked in major problem resolution and crisis management will recognise the importance of this. As a leader, if you have the best people, and good procedures, then your role is to let them act, and give them the resources and support they need.

The Power of Professionalism. The crew of the mission, and the people that supported them, had been selected on the basis of character and ability. They had been well trained. As Ron Howard, director of the film Apollo 13, once pointed out to Jim Lovell , it was hard to hear a problem when listening to the original tapes from the time of the initial explosion. The response to immense problems was calm and measured – in both the spacecraft and in Mission Control.  It was focused on making revised plans, and working those plans. In fact throughout the crisis, there was little doubt and little fear. The NASA team believed it could save the astronauts, and worked carefully to that goal.

The Power of Preparation, Rehearsal and Testing.  Although the Apollo 13 was an extreme incident, NASA’s careful preparation paid off. They had rehearsed using the lunar module to control the full “stack” on Apollo 9. NASA’s detailed, existing procedures proved to be highly adaptable to the new set of problems. The wiring on the Command and Service Module was made to an extraordinarily high standard – a reaction to the tragedy of the Apollo 1 fire. That meant that the dampness inside the hibernating spacecraft did not create issues when it was brought back to life for re-entry.

So, after forty-five years, the story of Apollo 13 – of NASA’s successful failure – still endures, and inspires. Above all, it can teach.

Mission Control celebrates the recovery of the Apollo 13 crew
Mission Control celebrates the recovery of the Apollo 13 crew

Keith Haviland

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.

Failure is an Option

Things will always go wrong, but excellent preparation and strong leadership can turn failure into a kind of success.

The story of Apollo13 is a parable of gritty resolve, technology excellence, calm heroism and teamwork. For anyone focused on leadership, operations and program management it is absolutely the purest of inspirations.

The film of Apollo 13 centres around the phrase Failure is Not an Option,” invented post the original drama in a conversation between Jerry Bostick – one of the great Apollo flight controllers – and the filmmakers. It summarises a key part of the culture of Apollo era NASA, and it has found its way onto the walls or desks of many a leader’s office. It is part of the DNA of modern business culture, and of any sizeable delivery project.

Damaged Apollo 13 Service Module
Damaged Apollo 13 Service Module

Lessons from the Space Program

But one of the reasons that the crew was recovered was this: throughout its history, NASA and mission control knew that failure was precisely an option, and they designed, built and tested to deal with that simple truth. The spacecraft systems had – where physically possible – redundancy. The use of a Lunar Module as a lifeboat had already been examined and analyzed before Apollo 13. In the end, a old manufacturing defect caused an electrical failure with almost catastrophic consequences. It was precisely because Mission Control was used to dealing with issues that Apollo 13 became what has been called a “successful failure” and “NASA’s finest hour.”

The ability to respond like this was hard earned. The Gemini program – sandwiched between the first tentative manned flights of Mercury, and the Apollo program that got to the moon – was designed to test the technologies and control mechanisms needed for deep space. It was a very deliberate series of steps. Almost everything that could go wrong did: fuel cells broke, an errant thruster meant that Gemini 8 was almost lost, rendezvous and docking took many attempts to get right and space walks (EVAs in NASA speak) proved much harder than anybody was expecting. And then the Apollo 1 fire – where three astronauts were actually lost on the launch pad – created a period of deep introspection, followed by much redesign and learning. In 18 months, the spacecraft was fundamentally re-engineered. The final step towards Apollo was the hardest.

But, after less than a decade of hard, hard work – NASA systems worked at a standard almost unique in human achievement.

So, with near infinite planning and rehearsal, NASA could handle issues and error with a speed and a confidence that is still remarkable. Through preparation, failure could be turned into success.

Challenges of a Life More Ordinary

All of us have faced challenges of a lesser kind in our careers. I was once responsible for a major software platform that showed real, but occasional and obscure issues the moment it went into production, expensively tested. We put together an extraordinary SWAT team. The problem seemed to be data driven, and software related and simply embarrassing. I nick-named it Freddie, after the Nightmare on Elm Street movies. It turned out to be a physical issue in wiring – which was hugely surprising and easily fixed. The software platform worked perfectly once that was resolved.

Another example: In the early days of Accenture’s India delivery centres, we had planned for redundancy and were using two major cables for data to and from the US and Europe. But although they were many kilometres apart, both went through the Mediterranean. A mighty Algerian earthquake brought great sadness to North Africa, and broke both cables. We scrambled, improvised, maintained client services, and then bought additional capacity in the Pacific. We now had a network on which the sun never set. It was a lesson in what resilience and risk management really means.

Soon enough, and much more often than not, we learnt to handle most failures and problems with fluency.  In the Accenture Global Delivery network we developed tiered recovery plans that could handle challenges with individual projects, buildings, and cities. So we were able to handle problems that – at scale – happen frequently. These included transport issues, point technology failures, political actions and much more – all without missing a single beat. Our two priorities were firstly people’s safety and well being,  and secondly client service, always in that order.

Technology – New Tools and New Risks

As technology develops, there are new tools but also new risks. On the benefit side, the Cloud brings tremendous, generally reliable compute power at increasingly low cost. Someone else has thought through service levels and availability, and invested in gigantic industrialized data centres. The cloud’s elasticity also allows smart users to side step common capacity issues during peak usage. These are huge benefits we have only just started to understand.

But even the most reliable of cloud services will suffer rare failures, and at some point a major front-page incident is inevitable. The world of hybrid clouds also brings new points of integration, and interfaces are where things often break. And agile, continuous delivery approaches means that the work of different teams must often come together quickly and – hopefully – reliably.

The recent Sony incident shows – in hugely dramatic ways – the particular risks around security and data. Our technology model has moved from programs on computers to services running in a hybrid and open world of Web and data centre. The Web reflects the overall personality of the human race – light and dark – and we have only just begun to see the long-term consequences of that in digital commerce.

Turning Failures into Success

What follows is my own summary view of those key steps required to handle the inevitably of challenges and problems. It is necessarily short.

1. Develop a Delivery Culture – Based on accountability, competence and a desire for peerless delivery and client service. Above all, there needs to be an acknowledgement that leadership and management are about both vision and managing and avoiding issues. Create plans, and then be prepared to manage the issues.

2. Understand Your Responsibilities – They will always be greater in number that you think. Some of them are general, often obvious and enshrined in law – if you employ people, handle data about humans, work in the US, work in Europe, work in India and work across borders you are surrounded by regulations. Equally importantly, the expectations with your business users or clients need to be set and mutually understood – there are many problems caused by costing one service level, and selling another. Solving a service problem might take hours or days. Solving a problem with expectations and contracts may be the work of months and years.

3. Architect and Design – Business processes and use cases (and indeed users!) need to account for failure modes. The design for technical architectures must acknowledge and deal with component and service failures – and they must be able to recover. As discussed above, cloud services can solve resilience issues by offering the benefits of large-scale, industrialised supply, but they also bring new risks around integration between old and new. Cloud brings new management challenges.

4. Automate – Automation (properly designed, properly tested) can be your friend. Automated recovery and security scripts are much less error prone than those done by people under stress. There are many automated tools and services that can help test and assess your security environment. Automated configuration management brings formal traceability – essential for the highest levels of reliability. Automated regression testing is a great tool to reduce the costs of testing in the longer term.

5. Test – Test for failure modes in both software and business process. Test at points of integration. Test around service and service failures. Test at, and beyond, a system’s capacity limits. Test security. Test recovery. Test testing.

6. Plan for Problems – Introduce a relevant level of risk management. Create plans for business continuity across technology systems and business processes. Understand what happens if a system fails, but also what happens if your team can’t get to the office, or a client declares a security issue.

7. Rehearse Invest in regular rehearsals of problem handling and recovery. Include a robust process for debriefing.

8. Anticipate and Gather Intelligence – For any undertaking of significance, understand potential issues and risks. Larger organisations will need to understand emerging security issues – from the small, technical and specific to more abstract global threats. Truly global organisations will need to sometimes understand patterns of weather – for example: to determine if transport systems are at threat. (I even once developed personal expertise in seismic science and volcanism.)

9. Respond – But finally acknowledge that there will be major issues that will happen, and such issues will often be unexpected. So, a team must focus on:

  • Simply accepting accountability, focusing on resolution and accepting the short-term personal consequences. It is what you are paid for.
  • Setting-up a management structure for the crisis, and trigger relevant business continuity plans
  • Setting up an expert SWAT team, including what is needed from suppliers.
  • How to report diagnosis and resolution – be accurate, be simple, avoid false optimism and be frequent
  • How to communicate with stakeholders in a way that balances information flow and the need for a core team to focus on resolution
  • How to handle media, if you are providing a public service
  • And after the problem is solved and the coffee machine is temporarily retired, how does the team learn

And finally a Toast …

In previous articles, I have acknowledged the Masters of Delivery I have come across in my varied career.

In this domain covered by this article, I have worked with people in roles such as“Global Asset Protection”, “Chief Information Security Officer” and teams across the world responsible for business continuity, security and engineering reliable cloud services. They work on the kind of activity that often goes unacknowledged when things go well – but in the emerging distributed and open future technology world, they are all essential. To me, these are unsung “Masters of Delivery.” Given this is the start of 2015, let’s raise a virtual glass in celebration of their work. We all benefit by it.

Keith Haviland

This is a longer version of an article originally posted on linkedin.  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.

30 Alternative Quotes on Success to Celebrate New Year, 2015

A large part of the Western workforce will be returning to work, after celebrating New Year. It’s a time of New Year’s resolutions, and general thinking about renewal and the future. Or at least exercise.

And there seems to be no shortage of Internet-seved inspirational quotes and messages for this New Year of 2015 – as part of the vast, modern literature on self-improvement and leadership excellence. Much of this is based on the premise that success is ultimately about self-belief.

This actually represents a very old trade in ideas. Virgil was a 1st century BC Roman poet who completes with Shakespeare for the times he is quoted. One quote is “Possunt quia posse videntur,” which roughly translates as “They can, because they believe they can.”

But success is more than about denying doubt, it is about preparation, planning, effort and working with other people. It is managing issues and dealing with error. So, to celebrate the arrival 2015, I have assembled a few alternative quotes on success and leadership for the year, some with a little edge, and all hopefully a little truth.

Oh, and a Happy and Very Successful New Year to you all.

1. Success consists of going from failure to failure without loss of enthusiasm – Winston Churchill

2. As a general rule, the most successful man in life is the man who has the best information. – Benjamin Disraeli

Benjamin Disraeli
Benjamin Disraeli

3. Strive not to be a success, but rather to be of value. – Albert Einstein

4. I don’t look to jump over seven-foot bars; I look around for one-foot bars that I can step over. – Warren Buffett, investor

5. Success depends upon previous preparation, and without such preparation there is sure to be failure. – Confucius

6. The test of success is not what you do when you are on top. Success is how high you bounce when you hit bottom. – George S. Patton

George S. Patton
George S. Patton

7. Success is dependent on effort. – Sophocles

8. The supreme quality for leadership is unquestionably integrity. Without it, no real success is possible, no matter whether it is on a section gang, a football field, in an army, or in an office. – Dwight D. Eisenhower

9. As I’ve progressed in my career, I’ve come to appreciate – and really value – the other attributes that define a company’s success beyond the P&L: great leadership, long-term financial strength, ethical business practices, evolving business strategies, sound governance, powerful brands, values-based decision-making. – Ursula Burns

Ursla Burns
Ursla Burns

10.Failure comes only when we forget our ideals and objectives and principles. – Jawaharlal Nehru

11. Never was anything great achieved without danger. – Niccolo Machiavelli

12. Ultimately, leadership is not about glorious crowning acts. It’s about keeping your team focused on a goal and motivated to do their best to achieve it, especially when the stakes are high and the consequences really matter. It is about laying the groundwork for others’ success, and then standing back and letting them shine.- Chris Hadfield, astronaut

13. Anticipating problems and figuring out how to solve them is actually the opposite of worrying: it’s productive. – Chris Hadfield, astronaut

14. Everyone who’s ever taken a shower has an idea. It’s the person who gets out of the shower, dries off and does something about it who makes a difference. – Nolan Bushnell

15. In fact, researchers have settled on what they believe is the magic number for true expertise: ten thousand hours. – Malcom Gladwell, Outliers: The Story of Success

16. First, have a definite, clear practical ideal; a goal, an objective. Second, have the necessary means to achieve your ends; wisdom, money, materials, and methods. Third, adjust all your means to that end. – Aristotle

Aristotle
Aristotle

17. Expect problems and eat them for breakfast. – Alfred A. Montapert

18. Whenever you see a successful business, someone once made a courageous decision. – Peter F. Trucker

19. Stay hungry. Stay foolish. – Steve Jobs

20. People do not decide to become extraordinary. They decide to accomplish extraordinary things. – Edmund Hillary

21. To succeed in life, you need two things: ignorance and confidence. –Mark Twain

Mark Twain
Mark Twain

22.We had risen to probably one of the greatest challenges in history, put a man on the moon in the decade. We’d created incredible technologies. But what was most important, we’d created the teams, what I call the human factor. People who were energized by a mission. – Gene Kranz, Flight Director

23. There are three things that matter. The first is competence — just being good at what you do, whatever it is, and focusing on the job you have, not on the job you think you want to have. The second one is confidence. People want to know what you think. So you have to have enough desirable self-confidence to articulate a point of view. The third thing is caring. Nothing today is about one individual. This is all about the team, and in the end, this is about giving a damn about your customers, your company, the people around you, and recognizing that the people around you are the ones who make you look good. – Bill Green, former Accenture CEO

24. I attribute my success to this: I never gave or took any excuse. –Florence Nightingale

Florence Nightingale
Florence Nightingale

25. The best time to plant a tree was 20 years ago. The second best time is now. – Chinese Proverb

26. The world is changing very fast. Big will not beat small anymore. It will be the fast beating the slow –Rupert Murdoch

27. A leader is one who sees more than others see, who sees farther than others see, and who sees before others see — Leroy Emis

28. The best executive is one who has sense enough to pick good people to do what he wants done, and self-restraint enough to keep from meddling with them while they do it.— Theodore Roosevelt, American President

Teddy Roosevelt
Teddy Roosevelt

29. A leader is a dealer in hope. – Napoleon Bonaparte

30. If at first you don’t succeed, try, try again. Then quit. There’s no point in being a damn fool about it. – W.C. Fields

wc fields 1934 - by paul hesse

Christmas and NASA’s Perfect Mission

Apollo 8 was NASA’s perfect Christmas Mission, which moved the human spirit. It was also an extraordinary example of bold and strong leadership, remarkable teamwork and commitment, agile and rapid program management, and brilliant, authentic communications and marketing. Apollo 8 represents leadership at its best.

I’ve always been fascinated by the great cycles of humanity’s festivals – and their links to the patterns of our solar and lunar years, and to each other. I’ve often sent greetings that search for the meanings of such festivals.

We are now a few days away from Christmas and its secular cousin of the New Year. For Christians, Christmas is of course a very direct celebration of the religion and its origins. But its date was set by Roman clergy from the 350s, and maybe earlier, to connect it to the ancient festivals of the Winter Solstice – which are in the end also about renewal and rebirth. For some Romans, the date of December 25st was the birthday of the sun god Sol Invitictus. In the north of Europe, people celebrated the pagan festival of Yule, which became synonymous with Christmas from the tenth century onwards. Many traditions linked with the non-spiritual side of Christmas – from greenery and trees from the North forest, through gift giving and feasting, to the miraculous powers of a bearded, benevolent godlike figure – have their ancient origins in these pagan festivals.

But this year I wanted to celebrate Christmas with a modern twist, and look for a story that underpins some of the themes of Christmas, and resonates with my own interests and future plans – a story that would also be an inspiration.

For me the choice is an obvious one: the Christmas flight of Apollo 8 in 1968 – the first time that humans would orbit and return from the Moon, and NASA’s perfect flight.

It is a flight seen by many who took part in Apollo as the golden moment of America’s journey to the Moon – and perhaps its greatest mission. It is a story that covers vision, teamwork, renewal and a moment of spiritual reflection, looking down upon the Moon and the Earth.

1968 – A Year of Turmoil

1968 overall was an extraordinarily challenging and difficult year for the US and the West. It started with the North Vietnamese launching the Tet offensive at Nha Trang. It was also the year of My Lai. In April, Martin Luther King Jr. was assassinated. There were riots in Paris, and a sense of revolution hung coldly in the air. Later, there were riots in Chicago. In June, Sirhan Sirhan shot Robert Kennedy, and in the autumn, the Soviet Union invaded Czechoslovakia with a vast army, strangling the Prague Spring. It seemed an inauspicious year.

Delays in Apollo

The Apollo program also faced its own complex challenges as the deadline set by President Kennedy closed in. First had come the tragedy of the Apollo 1 fire in 1967, which had killed astronauts Gus Grissom, Ed White and Roger Chaffee.

The defects in the Command and Service Module (CSM) spacecraft had been fixed remarkably quickly, and Apollo 8 was intended to test the Lunar Module or LM in low Earth orbit in December 1968.

But the first lunar module turned out to be broken. When it arrived at Cape Canaveral, there were too many defects to meet the schedule. It would take many weeks to fix.

A Flight to the Moon is Born

In a decision that would be remembered as an act of extraordinary vision and boldness, George Low, the Manager of the Apollo Spacecraft Program Office,  proposed that Apollo 8 be instead sent to orbit the moon without its Lunar Module.

This would be the first manned flight using the mighty Saturn V – a rocket that had just had severe issues with “pogo-ing” fixed. It was a bold step indeed to use its first manned flight to travel almost a quarter million miles to the Moon.

Any trip to the Moon also required intense planning and training flight, and the discussions had started just a few weeks before the earth orbit Apollo 7 was scheduled to fly. It was a tough schedule to meet. Would it be possible?

Glynn Lunney, one of the most important figures in NASA Mission Control during the Apollo years summarized the thought process that would typify the response of NASA senior management “I went in minutes from ‘crazy’ to ‘brilliant breakthrough’, and ‘why didn’t I think of that’?”

So, the mission imagined on almost the spur of the moment rapidly gained the support of almost all NASA’s senior managers. They understood the immense morale boost it would create, and they had confidence in their vehicles. Above all, the team that had formed out of Mercury, Gemini and the early days of the Apollo program had gained immense confidence in itself. This great challenge could be met. This mission was possible. It was a Go.

Training was started in September. No public announcement was made about the real intent of the mission until November 12, less than 40 days before launch. The news of the real goal of Apollo 8 stunned and exhilarated the public. American astronauts were going to the Moon.

Crew

The crew consisted of Frank Borman, Jim Lovell and Bill Anders. For Borman and Anders, this was to be their last spaceflight. Lovell would be the commander of Apollo 13. They were a good crew admired by those who supported them, and became well prepared at short notice for a mission of an entirely new kind.

Mission Control would operate 24×7 in three shifts, led by Flight Directors Charles Charlesworth, Glynn Lunney and Milton Windler.

Apollo 8 Crew
Apollo 8 Crew

Launch

On the morning of December 21, the Apollo 8 crew was awakened in the small hours, and given a traditional breakfast of steak and eggs. The countdown proceeded smoothly and at 7:51 AM, the four hold-down arms were released and the mighty Saturn V moved slowly into the air, driven by many millions of pounds of thrust.

Astronaut Michael Collins was the CAPCOM (Capsule Communications) on duty and at 2 hours, 27 minutes and 22 seconds in the mission radioed, “Apollo 8. You are Go for TLI.” The engine on the third and final stage of the Saturn V fired, and pushed out of Earth orbit.

Apollo 8 was now the first manned interplanetary spacecraft.

Apollo 8 Lift Off
Apollo 8 Lift Off

Reaching the Moon

As they approached the moon, the crew began to prepare for Lunar Orbit Insertion or LOI. This was a particularly tense moment. It depended on a burn of the service module engine on the far side of the Moon, when the spacecraft was alone and out of contact with Earth.

After the key members of Mission Control were polled for a “go” or “no go” decision, the crew was told that they were “go” and “riding the best bird we can find.”

Mission Control had set up two countdown clocks. If Apollo 8 regained contact at the first timing point, then no burn had happened and LOI had failed. If it regained contact at the second timing point, the burn had worked perfectly. Anything else was real trouble.

It was at this point that Lunney – who was the flight director on duty, said: “Okay, all flight controllers, this is a good time to take a break.”. It amazed the members of Mission Control at first, but on reflection there was nothing to be done for around 20 minutes. Some of them took advantage.

Eventually, the first countdown clock expired. There was no signal. Tension in Mission Control increased.

Then the second clock expired. Apollo 8 radioed at that point “Houston, this is Apollo 8. Burn complete.”

The engine had worked as it should. Apollo 8 was in orbit around the moon.

 

Lunar Surface from Apollo 8
Lunar Surface from Apollo 8

In Orbit

It was then that the crew could start observing another world – one of the prime purposes of the mission, and essential preparation for future landings. They would take many hundreds of photos.

Jim Lovell would characterize the surface as follows:

“The Moon is essentially grey, no color; looks like plaster of Paris or sort of a grayish beach sand. “

Bill Anders would add:

“Looks like a sand pile my kids have been playing in for a long time—it’s all beat up—no definition—just a lot of bumps and holes.”

But it was not the Moon that was to get the most attention.

The First Human Earthrise

One of the key moments of the flight, and indeed all of history, came as the craft emerged from behind the Moon for the fourth time. The crew witnessed “Earthrise” for the first time – the crescent of our plant rising above the limb of the moon’s broken surface. Borman noticed first, and called in excitement to the others, taking a black and white photo as he did so. Anders took another, now famous color photo, later selected by Life as one of its 100 photos of the century.

The sense of wonder, and unity, at seeing all of Earth and all of humanity from the vastness of space was a common experience shared by many of the Apollo astronauts. Anders would go on to say:

“We came all this way to explore the Moon, and the most important thing is that we discovered the Earth”

Earthrise in Black and White
Earthrise in Black and White

The Christmas Eve Reading of Genesis

As Apollo 8, rounded Moon for the ninth time, they began another TV transmission. They first described the lunar surface for the people on Earth, Borman characterizing it as a “a vast, lonely, forbidding expanse of nothing.”

Then Anders said crew had a message for all on Earth. It was at that moment that each of the astronauts read a section from Genesis, about the creation of the Heaven and the Earth.

“In the Beginning god created the Heaven and the Earth. And the Earth was without form and void. And darkness was upon the face of the Deep. . . . And God saw that it was Good. . . . “

They had chosen Genesis since it was from that part of the Bible that had meaning across several major religions. Borman ended the broadcast with:

“And from the crew of Apollo 8, we close with good night, good luck, a Merry Christmas and God bless all of you – all of you on the good Earth.”

This was a hugely moving and unexpected experience for those in Mission Control. Flight controller Jerry Bostick later wrote:

“I was totally overwhelmed, and tears came to my eyes. [What could be] more appropriate than a Bible reading about creation, coming from the first people to ever leave the influence of Earth, on Christmas Eve?”

Returning Home

The next critical moment was Trans-Earth Injection, or TEI. The service module engine needed to be restarted a second time, and perform another perfect burn. Again, that would be done behind the moon.

It worked, and Lovell reported “Houston … Please be informed, there is a Santa Claus.”

After the long coast back to Earth, the Apollo 8 Command module re-entered the atmosphere with the dreadful violence that comes from interplanetary velocities. The deceleration peaked at 6g, and – as planned – the spacecraft bounced like a skipping stone before falling to the Pacific Ocean.

Anders would say:

“You could see the flames and the outer skin of the spacecraft glowing; and burning, baseball-size chunks flying off behind us. It was an eerie feeling, like being a gnat inside a blowtorch flame.”

At around 10,000 feet the three main parachutes slowed the Command Module, and it splashed down south of Hawaii.

Apollo 8 Command Module being recovered after splashdown.
Apollo 8 Command Module being recovered after splashdown.

Apollo 8 – In Retrospect

In the end, Apollo 8 was a genuine and complete success. It was indeed a perfect mission.

Jerry Bostick would say: “It was bold, it was exciting, and it was successful.”

Chris Kraft – who created the very notion of Mission Control – notes in his autobiography how many historic firsts it scored. It was the:

  • First manned flight of a Saturn V
  • First manned vehicle to leave earth’s gravitation field
  • First use of a computer to provide total “onboard autonomy” in navigation
  • First manned vehicle in lunar orbit
  • First close-up view of another planet
  • First exposure to solar radiation beyond the earth’s magnetic field
  • First vehicle to rocket out of lunar orbit
  • First manned vehicle to reenter from another planet

Perhaps the impact of the Mission is best summarized by a telegram sent to Borman by an unknown citizen that stated: “Thank you Apollo 8. You saved 1968.”

Apollo 8 as an Example of Leadership

Beyond the magnificence of the technical achievements, there are many leadership lessons.

Apollo 8 is a perfect example of the power of vision and imagination, creating a new mission of historic importance out of issues.

It would not have been possible with the preparation already undertaken, and the intense commitment and teamwork of the extraordinary team that had formed around mission operations.

Apollo 8 was also a remarkable moment in communications, in PR and marketing. At the end of a deeply troubled year, its success bound together humanity for a moment as would Apollo 11 and Apollo 13 in coming months.

And perhaps most importantly, each of those who witnessed Apollo 8 through the media of the day got to see our fragile home from afar.

Jim Lovell Suiting-Up for Apollo 8
Jim Lovell Suiting-Up for Apollo 8

The Final Word

Apollo 8 was NASA’s perfect mission. It shows the value of imagination and bold vision. It was founded on teamwork. It enabled all of us to look at ourselves in a different way.

And it happened at Christmas.

Merry Christmas and a Happy, Bold and Successful New Year to all of you.

Or as Borman said: ”Good night, good luck, a Merry Christmas and God bless all of you – all of you on the good Earth.”

Keith

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.

When Speed and Agility Matter: Moving with the Lightning

Episode 3 of the Masters of Delivery

 The Problem of Time

I’ve spent much of my career focused on how to plan and manage one of the most precious and complex resources: time – and especially how time relates to project scale and complexity.

In software development and technology-driven business projects, one of the clearest and most dramatic trade-offs is between speed and cost. There is a simple rule: the shorter the schedule, the bigger the total effort, and associated cost. The dynamics of organizing and connecting people around common processes will become increasingly stressed when time is tight. The scope for error and rework increases significantly.

Indeed, there are schedule and scale combinations that are simply impossible to achieve, for which – to coin a phrase from the great Fred Brooks – there is no silver, magic bullet. Rome, an Olympic stadium, and even average size software projects cannot be built in a day.

 When faced with demands for impossible schedules, where the balance of scope and schedule simply do not fit, I normally take people through the complex dynamics of time and teams. I stress the need for a proper amount of time to understand a business and develop a design, and the option of delivering function in iterations so that some benefit can be gained earlier.

One Year Vs. Five Years

Conversely, as Peter Drucker once said: We greatly overestimate what we can accomplish in one year. But we greatly underestimate what we can accomplish in five years.”  

Five years or more gives enough time for big change, enough time to create a business or even a market.

One personal example of that is when I was part of the team that founded Accenture’s India Delivery Centres in 2001. We had a short-term plan focused on 200 people, but I also drew out a longer-term plan on a whiteboard that spanned three to four years and would get us to 10,000 people in multiple cities. It captured our strategic intent. We would meet both plans.

Moving with the Lightning

However, there are times when magic will work, when external events demand a schedule that is improbably short and – even more remarkably – the right team with the right motivation and the right support achieves that timescale. Such moments can create real belief in a program or team, leading to greater success at ever larger scales. The insights learned from these experiences can also help people think through agility, an increasing demand from many senior leaders in our hyperactive era.

So, it is those moments when teams move with the lightning, when great things are done fast, that I want to explore in what follows. Let’s start with the inspiration for this article – a spaceship.

America’s First Spaceship

I was researching the history of NASA Mission Control. This was for a potential film project, and also out of simple curiosity about how the great and mighty NASA machine of the 1960s and early 70s was created.

One of the key sources is the book Flight: My Life in Mission Control by Christopher Kraft who conceived and built the first versions of NASA mission control. It is a book that tells the human and organizational story of the space program, and one I would recommend to any student of delivery.

The following sequence jumped out at me, around the Request for Proposal or RFP process for America’s first manned spacecraft – the Mercury capsule.

It was this:

  • 1st October 1958, NASA created
  • 7th November 1958, RFP Published and RFP conference
  • 12th January 1959, contract awarded to McDonnell Aircraft Corporation
  • Early February 1959, McDonnell sign contracts

By today’s standards, this is extraordinarily fast. It is genuinely astounding. This is not the RFP for an IT system, or office supplies. It is an RFP for a spaceship.

In a matter of weeks, the direction for America’s first manned space program had been set and a partner selected. The Mercury program had initial challenges – such as an infamous unmanned flight that reached a height of 4 inches – but overall it succeeded completely, and with the knowledge and expertise created America would reach the moon less than 11 years after NASA was created.

Kraft himself summarizes the spirit of the times with That can-do, will-do attitude preceded us everywhere we went.”

This incredible example demonstrates some of the themes we will explore later in the article: strong mission, strong leadership, great skills and motivation.

Above all it shows that there are times when great things can indeed be done quickly.

The Move: 3 Weeks and 300 Very Busy People

This example is not nearly so grand. It didn’t change broad history, but it did help create a major technology delivery centre, and a new business. It was, by normal corporate standards, a magnificent achievement.

We had started our new business in a charming, worn art-deco style building beside the Thames. We were in the midst of a major software development, with 300 people designing, developing and testing releases of a major software product. The work in total was tens of thousands of days. Testing in particular is very sensitive to environment – the software configurations, networks, workstation and server technology need to be absolutely correct, and the physical space needs to support intense teamwork on the grand scale.

Although the building faced the river, it was cheap to rent. And the reason it was cheap – which I didn’t know at the time – was that there was a one-month notice period in the lease.

Our facilities people had deemed it unlikely to happen. Their judgement was usually faultless, but this time they were wrong. The owner wanted to rebuild, and start demolition soon.

So, one day we faced just over 3 weeks for a move – with no target future building and no plan, and 300 people working hard on a tough schedule for multiple clients. As we expanded, we would develop true business continuity and would be able to handle loss of a facility with ease, but this was early in our history.

We had an immense problem.

The first task was not to panic, or analyse quite why we were where we were. As we have seen in previous articles, status is to be understood with blunt honesty, and issues are there to be managed.

As for the next task, I asked a true Master of Delivery – “RK” – to plan and execute the move. RK had an exceptional grasp of the full technology stack – from the wires to the complex distributed software environment. He also understood what an objective meant, and would work with enormous passion towards that.

I asked him to target just one day – the move day – of down time for the team. RK smiled.

Key Strands

So, we created a plan around a number of parallel strands that RK would operate with complete authority.

Strand 1 was creating the mission, and instilling a sense of belief about the date. We wanted people to feel that their efforts would help make a little corporate history.

Strand 2 was about people. We staffed key roles immediately with some of our best, taking a short term hit on other activities. We chose those who had general management skills, and precision, since we needed delegation to be effective. We would expect everyone to be hands-on – acting much like people do in start-ups.

Strand 3 was a search for a suitable empty space. We looked in what in London is called mid-town, between the West End and the City. It was less fashionable then than it is these days, and we found three spaces of the right scale and cost. Two were dreadful – cramped spaces in out-dated concrete buildings, that would require much work. One, however, was acceptable. This was the key piece of luck we needed. We had found our future home – an Edwardian building near London’s legal district.

Strand 4 was design. We established the minimum design around building layout, furniture, a LAN, working servers and wide area communications. That was placed under firm control. Any change would be reviewed carefully.

Strand 5 was to focus on logistics with true military precision. We analysed lead times, placed orders – leased and borrowed equipment that wouldn’t arrive on time – and asked our suppliers to make the extra effort to support us.

And then, came the daily grind of execution. We met the deadline, and had people working effectively on the first day of operation of the new building. We lost only a few hours of productive work.

And it turned out that the technology design was not only effective … it was near perfect. RK had poured all his knowledge into the design, and we had no time for the usual compromises.

“500 in 5”

This is an example that I come back to repeatedly in my thinking, a key moment in my experiences in creating large delivery centres in India, and a lesson in how to get teams to do incredible things.

We had been in operation for around 18 months, reaching 500 people. This had required sustained effort since our business was then not widely known among our target talent pool. We had worked hard with candidates, even explained ourselves to their families, and organized dedicated training and conference days to attract people to apply. Overall, with a little difficultly, we had balanced demand and supply effectively. Our HR team had made a brilliant start.

Now things were changing and demand was increasing. We were beginning to see supply challenges.

I wanted to understand trends – I always want to understand trends since part of any leadership role is looking ahead – and went through the data in detail.

The reason for the new demand for people was a large, recent increase in active and potential clients. We had established a successful business. We were seeing the early days of a much larger future increase – the work at each new client would likely grow, and need more people.

Exponential Change

We had reached a tipping point. Roughly speaking, we were seeing the beginnings of an exponential, non-linear trend. Most people will naturally plan around linear and steady change, but with positive feedback, human enterprises can go through remarkable and fast changes – creating echoes of the growth of the Internet, the progress of a hit single, or viral video. The topic of exponential, human change is a topic I will be returning to in later articles.

The good news was that we had what seemed to be the start of a tremendous opportunity. The bad news was that we needed a non-linear response.

Setting the Goal

We had a talented local leader who was strong, charismatic and a true business builder. Our local HR lead was one of the most positive and dedicated professionals I have ever had the privilege to work with. They had been carefully chosen, and in their different ways they were both Masters of Delivery. They would go on to make very major contributions.

I asked them this. Although, it has taken eighteen months to grow to 500 people, we need to hire 500 people in the next five weeks. Can you do it?

Those who have built and worked in start-ups know how hard an ask this was. Talent is the key resource and often the key constraint.

And the mood of that meeting? When a world of pain and hard work was opening up before us. It was tremendous – full of energy and laughter. They had that can-do, will-do attitude” Chris Kraft had seen at NASA.

They went for it. We briefed the team … making it their moment of making history. We hired good contractors to support the core professionals. We arranged for virtual interviews from people across the globe. We created a large war room, dotted with white boards to record real-time status.

And then we filtered CVs and held interviews, thousands and thousands and thousands of times.

By the end of the period they had made 526 offers to good candidates. They had beaten the target. 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, eventually capable of hiring many thousands a month.

General Principles

So, what general threads can we pull out of my three very different examples? When can a leader or business ask for remarkable efforts in a remarkable short time frame?

My conclusions are as follows (although I would also be delighted to hear your thoughts). They are similar to the Ten Commandments we saw in Episode 2 of Masters of Delivery, but tuned completely to very rapid execution.

  1. This cannot be business as usual. Remarkable effort should be reserved for times of remarkable need. The examples we have looked it where against the background of the space race, or clear, urgent, business challenges.
  2. But in such times, it will sometimes pay-off enormously to have ambition and the courage to ask for that remarkable effort.
  3. Judgement is essential to make sure the undertaking has the right characteristics to succeed. Suitable examples include:
  • The work can be undertaken by a small number of experts. For example, it was possible to create a high-level spacecraft design in weeks. Building the spacecraft would take another two years (superb in itself).
  • Or the work can be scaled and duplicated across people and teams – as in our recruiting example.
  • It is self-contained, with few external dependencies.
  1. There must be a clear mission, a worthwhile purpose. This must be communicated to everybody. And people enjoy doing great things; enjoy making their own pieces of history – so communicate to inspire.
  2. The mission must be understood, valued and supported by the team. It’s hard to ask people to work long hours. It is much easier and much more effective to ask them to work for a goal.
  3. Assign the best team. It is remarkable how many projects fail, even mission critical ones, because hard choices about resources are not made. When timescales are fundamental, staff your best people and clear their decks. Less urgent issues will wait.
  4. And “best team” means people with experience – in every one of our three examples,the teams were led and staffed by people who had prior experience of great relevance.
  5. Above assign a qualified leader – a leader and subject matter expert – and concentrate authority in that person.
  6. Create a simple plan, simple reporting – whiteboards can be the most powerful tool for management – and a simple decision making process for issues and changes.
  7. Look after the team – get the key stakeholders or senior executives to spend time with them, deal with food and transport issues generously, give them support staff without hesitation.

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