Summiting Mt Kilimanjaro - A Project Management Case Study

Introductionequipment and started the hike. We had planned our
Reaching almost twenty thousand feet high, Mounttrip to come after the rainy season. The good news
Kilimanjaro is the tallest point in Africa. In Swahili,was that there wasn't much rain while we were
Kilimanjaro is translated as the "Mountain ofthere. The bad news was that we would have to
Greatness." In 2000, my brother and I decided tohike through six inches of mud. Our technology
climb this great mountain. We spent months preparingsupport (hiking poles) helped us stay upright for the
including understanding what we would need tomost part. This day was spent hiking through the
summit, designing our approach, getting the rightthick rainforest. The trail was covered in mud and all
equipment and training for endurance. We then spentwe could see in every direction (including up) was
one week executing the plan up the mountain. Sincegreen vegetation.
these are the same steps required in managing anySince we were hiking together, we could only move
project, I decided to write a case study on Projectas fast as our slowest person. We had a team
Management best practices in the context of planningmember who moved very slowly. This resulted in us
and executing our journey up the mountain.hiking into the night time on the first day. We had to
Planninguse our headlamps to see at night, which we were
Like most big projects, we had an almostplanning on using on the summit night. We would
unattainable vision; to summit the tallest mountain inhave to figure something out for light when we
Africa. We had fixed resources (our own money) andsummitted.
a fixed timeline. Historically, 80% of people who tryWe finally arrived at our camp, had some dinner, and
to summit this mountain fail for one reason orthen went to bed. We really couldn't sleep because
another. Interestingly, this is the same percentageof the excitement of the trip and the new
that experts attribute to the success of any ITexperience.
project. We had to plan for this correctly so that ourLessons Learned
goal could be achieved.* Do team-building activities to build the one team,
Be Informedone goal concept
Our first step was to gather as much information as* Learn how to say "slow American" in Swahili
possible. We wanted to understand the history of* Help the team members who are struggling, as
other attempts, the associated risks, and anythingtheir performance affects the entire team
else that might influence our project.* Be flexible with your approach as the reality
Some of our discoveries include:becomes different than the plan
* HAPE (High Altitude Pulmonary Edema) is aDay 2 - Immersion
potentially fatal condition where fluid fills the lungs ofWe woke up very early this next day and started to
a climber if they ascend to quicklyclimb again. We continued through the rainforest for
* There are several ways to get to the topsome time. We continued to hike very slowly and my
* They have a wet rainy season and a cold winterlegs began to hurt. This concerned me since it was
seasononly the second day. My shoulders had also started
* The terrain is uneven with parts that are veryhurting from the weight of my backpack.
slippery because of scree (small rocks which slideAfter a few more hours of hiking, we finally came
under your feet as you try to climb up)above the tree level. This was significant because,
* Since the summit is the highest point on theafter about fourteen hours of hiking, we could finally
continent, there is nothing to block the winds whichsee our goal. This is so important to a project
can get to forty below zerobecause we are often so focused on the steps we
We would need to use this information to prepareare taking that we rarely look up to see the goal
ourselves for the journey. This relates directly to thethat we are trying to achieve.
initiation of a project where it is important to giveWe were now at around twelve thousand feet and it
the team insight into the history and potential riskswas very cold. We had the appropriate equipment
from which a plan can be made.but nothing could prepare us for the
Hire the Expertsspider-mosquitoes (we don't know what they were,
Neither my brother nor I had ever hiked a mountainbut they looked like a cross between spiders and
of this magnitude before so we sought the advice ofmosquitoes). At the camp we noticed these critters
people who had a proven record. We collected ourall over the ground. As it got dark out, they
short list of tour companies (vendors). Based on ourdisappeared because it got very cold. We learned
vendor analysis (cost, track record, services offered,later that they all must have gone into our tent and
etc.) we came up with a partner. We selected asleeping bags. We spent the rest of the night trying
company that had a proven track record of successto get them out of our tent, bags, clothes, and
and who could organize and execute the details forpsyche.
us.Lessons Learned
The other option would have been to fly to Tanzania* Project work is painful at times, but you need to
and figure it out ourselves which would have had anwork through it
extremely low probability of success. This sounds like* Envision the goal and see the bigger picture
an easy decision, but too often companies attempt* Take care of bugs when you notice them and
to jump into projects without expert advice and thenbefore they get out of control
make the mistakes that an expert would haveDay 3 - Roller Coaster
already experienced ("those who do not learn fromWe continued hiking for another eight hours up and
history..."). For example, our tour company provideddown the mountain. There were many valleys and
us with a "bathroom tent." This was nothing morehills on the path. Since we were trying to move
than a tent containing a plastic seat with a hole andhigher, we knew that every time there was a valley
plastic bag in it. We didn't see any other hikers on thethat we went down, that we could have more
mountain with one of these and it made theground to make up to come higher. On projects,
difference between something civilized and trying tothere are always obstacles that take you away from
balance behind a rock.your ultimate goal and they have to be worked
Create a Planthrough to get you back on track.
We researched the activities that needed to takeWe camped out at the base of a wall that we would
place. We needed equipment, logistics (flights, hotels,be scaling the next day. That night, our companion
etc.), and a plan to condition ourselves. Working withwas coughing and could not breathe at the altitude. It
our partner, we laid these out into a plan that wewas 15,000 feet and she was a smoker. We would
could manage to ensure that everything was in place.decide to send her down the mountain the next day
We also mapped out a plan for the mountain. Basedsince there was little chance of her making the wall
on our risks, we had decided to ascend to thirteenand her health was deteriorating.
thousand feet and stay there for three days whileLessons Learned
we acclimatized (to avoid HAPE). The plan also* Sometimes the work takes you away from your
accounted for the timing of the climb by scheduling itgoal and you have to make up the ground
after the rainy season out and before the winter* Sometimes it's okay to change resources if they
season. We would ascend at night and reach theare not the appropriate fit and risk the end goal
summit by daybreak.Day 4 - The Wall
On projects, creating the plan is one of the mostWe had a scope change. With our companion leaving
critical activities. Once the project starts, it will costthe envoy, we had to send her down with a guide,
more time and resources to change direction, so it issome porters, and one of the two stoves used for
important to consider things carefully up front. Halfcooking. Often during projects, a critical dependency
way up the mountain, we would not have been ablegets impacted and teams have to respond
to take a different starting route.accordingly.
Define Appropriate RolesThe wall was very scary as it required a lot of
A best practice is to source work to people who areclimbing and hand-over-hand scaling up rocks. My
best suited to do the work. On our trip, the providerbrother and I are not fans of heights and there was
that we selected had agreed to provide us withnot much of an area between us and the ledge. We
people who would carry our tents and prepare thecouldn't turn back, but going forward meant more
food (I felt like a rap star with my "posse" of peopleanxiety and pain. We continued on to the next camp.
following me around). These were not things that weLessons Learned
wanted to concern ourselves with but that were* Even though you have a plan, you have to be
critical to our success. We could not climb withoutflexible to changes in scope.
eating and staying warm and carrying these* Projects often hit a wall in the middle where the
ourselves would have left us exhausted for ourteam needs to push through.
summit attempt.Day 5 - Almost There
Projects must have the same approach. CompaniesOn this day we would go up to around 16,000 feet.
do not have the resources to specialize in everyThis meant a very steep hike for the day. Upon
technical field. They need to consider sourcing specificgetting to the camp, we met a team of South
technologies to organizations that can manage theAfricans who were not able to summit because they
work and stay informed of the changes to theall had dysentery. I realized at this point that 80% of
technology.people who fail do not just fail on the last summit
Use of Technologyday but as a function of their journey through the
Another best practice is to use technology as anprocess. This holds true for project managers that
enabler of success. We learned that there would bemay make mistakes along the way, preventing them
a lot of hiking over unstable terrain and that thefrom attaining their goal.
summit was forty below zero with winds. We turnedWe laid out our special summiting gear and tried to
to technology to help us overcome these obstacles.get some sleep before the last push. Because of our
We purchased special hiking poles for stabilization andsteady pace we were able to have enough energy
special boots that would keep our feet warm at theto try the summit. Oftentimes, people may rush too
summit.much at the bottom and then not have the stamina
There is a trade-off between technology and cost,to finish. This is very relevant to projects that get
though, as we could have used a helicopter to meetbehind and then push the team hard for too long and
our goal of getting to the top, but that was notthe people cannot complete their mission.
financially feasible (not to mention it would have beenLessons Learned
cheating). Projects should consider the use of* Completing the goal is a result of the journey along
technology to enable their success, but also look atthe way and not just the last push
the costs of doing so (cost, maintenance of* Need to pace out the work. People get burnt out if
technology, obsolescence, etc.).they run for too long.
Use of PrototypesDay 6 - The Summit
Our plan was to hike other mountains that wereWe started our final push at midnight. We "deployed"
similar to Kilimanjaro. We wanted to prototype theour technology (head lamp, boots, hiking polls) and
experience and gauge the success of our training.started the trek. The "scree" (a grouping of small
Living in the United States, the best we could getrocks) was everywhere and it felt like we slid down
was in Colorado (8,000 feet lower than Kili). Weone step for every two that we took uphill. Because
learned that our technology worked and that weof our slow start on day 1, our head lamps ran out
could tolerate altitudes above ten thousand feet. Wevery quickly. Luckily we had a clear night and a full
did not want to risk testing these out for the firstmoon which reflected off of the glaciers. My legs
time when we were in Africa. Imagine our successhurt so badly, but I focused on one step at a time
rate if we had just tried on our new boots for theand after six hours, we finally made it to the top to
first time when we arrived in Africa. A woman in oursee the sun rise.
"expedition" had to descend the mountain in theAt the top, I felt very nauseous and "lost" all of the
middle of the climb because she could not handlefood that I had eaten before. At that altitude, your
altitudes anywhere near the 19,500 foot goal.body only focuses on breathing and everything else
Lessons Learnedshuts down. We took our pictures and then started
* Get as much information as possible to identifyback down again.
risks and opportunitiesIt took us another three hours to get back down.
* Have a carefully thought-out planThe scree was less forgiving when you go downhill
* Use experts and historical information to plan andand combining that with my lack of energy, I must
estimate out a projecthave slipped and fallen about ten times. The decent
* Partner with providers who have the expertise andwas difficult mentally as well because we had already
outsource that work which is not a core competencyreached our goal (to summit) and had no motivation
* Use technology to enable success, whereto continue pushing through pain.
appropriateLessons Learned
* Use prototypes to test approaches and* There is nothing like the feeling of meeting your
technologiesgoals
Execution* Once the goal is completed, there is still work that
There comes a point where the planning stops andneeds to get focus and attention
the project starts moving. Along the way there areDay 7 - Project Closure
always unplanned obstacles and challenges that comeWe continued down the mountain for another four
up. This project was no different.hours. Since we were near the base, we had to go
Day 1 - Kickoffback through the mud again. We finally finished and
We arrived in Africa in anticipation of our newwent back to the camp where we celebrated our
project. On the first day we got to meet the teamsuccess with the team. This included songs in Swahili
which was made up of tribal guides. Each person inand a lot of beer.
our team had one guide and some porters/cooks.Lessons Learned
We took a three-hour bus ride with everyone to The* Celebrate successes with the team
Mountain. The entire way no one said a word exceptConclusion
for an occasional conversation in Swahili and someMost projects have goals as aggressive as summiting
looks at us (my guess is they were betting onMt. Kilimanjaro. In order to be successful, the Project
whether we would succeed or not). There wereManager must gather as much information as possible
clearly cultural and language differences that weand make a realistic plan. This plan has to be flexible
would need to get past if we were to workto the inevitable changes that will occur. To increase
together as a team. The beginning of a project isthe probability of success, the PM should look to
always difficult because people are new to eachsource non-competency skills and use technology. I
other and are trying to figure out the relationships.would also suggest setting up a bathroom tent for
After arriving at the mountain, we unloaded ourthe team, just in case.