SlideShare utilise les cookies pour améliorer les fonctionnalités et les performances, et également pour vous montrer des publicités pertinentes. Si vous continuez à naviguer sur ce site, vous acceptez l’utilisation de cookies. Consultez nos Conditions d’utilisation et notre Politique de confidentialité.
SlideShare utilise les cookies pour améliorer les fonctionnalités et les performances, et également pour vous montrer des publicités pertinentes. Si vous continuez à naviguer sur ce site, vous acceptez l’utilisation de cookies. Consultez notre Politique de confidentialité et nos Conditions d’utilisation pour en savoir plus.
https://www.wrike.com/blog/10-reasons-the-death-star-failed/ - A long time ago in a galaxy far, far away… the Death Star projects failed spectacularly. Here, finally, is an Imperial insider's view into why these projects blew up — literally. Learn from the Empire’s mistakes to keep your projects from falling to the dark side. And stop by the Wrike blog at https://www.wrike.com/blog to learn everything you need to know about project management. Your Yoda, we will be!
10 Reasons the Death Star Failed: Project Management Lessons Learned
10 REASONS Pnosactstm. -.
FROM THE DEATH st AR
Here I am-_—. — a former Imperial starﬂeet
commander. Now, I'm at the bridge
of a single pathetic Star Destroyer,
stationed in some puny backwater
system. How did the once invincible
Galactic Empire come to this? If you
ask me, these are the 10 key mistakes
, , leading to the failure of the Death
Stars, and ultimately, the collapse
F0 of the Empire.
INCOMPLETE PROJECT REQUIREMENTS
The Death Star fulﬁlled every requirement
for the ultimate weapon: a super laser capable
of destroying a planet with a single blast, plus
15,000 laser, ion, and turbolaser batteries. But
plans didn't include defenses that could keep
starﬁghters from inﬁltrating & causing
Carefully consider how the completed project
will function in the real world when writing your
requirements. What situations could cause problems?
NOT RECOGNIZING RISK
No project is invulnerable, as every Imperial
office on board learned the hard way when
the ﬁrst Death Star disintegrated. If your
project has a susceptible thermal exhaust
port, you need to know — even if it is only
two meters wide.
No project is too big to fail, or too small to skirt risk. Conduct a thorough
risk assessment to identify potential threats and opportunities.
NOT MANAGING RISK
When Rebels snatched the Death Star plans and
found a weakness, the Empire didn't do anything
to mitigate the threat: no contingency plans,
evacuations, or defensive TIE ﬁghter patrols.
Tarkin was so certain in the Death Star's
invincibility that he didn't even evacuate
once it was under attack.
Be proactive with potential problems. Do what you can to prevent them,
and respond quickly if they do occur.
Ever worked under an unreasonable manager?
Imagine reporting to Vader or Tarkin! Not exactly
approachable. And they certainly didn't encourage
new ideas or collaboration.
Be available to help with questions and hangups, offer advice, and ask
for new ideas. Don't just expect people to follow your orders to a I
The Death Star's main purpose was to scare
local systems into cooperating. But wouldn't
Super Star Destroyers stationed in key systems
do the trick? Or a few garrisons of stormtroopers?
Instead of intimidating them into submission,
the Death Star inspired more star systems
to join the rebellion.
Consider all possible solutions to the problem, and only then decide
on an approach. Don't just choose the ﬁrst idea or easiest path.
NOT LEARNING FROM MISTAKES
After the ﬁrst Death Star's destruction, the Emperor
insisted on pushing full steam ahead on the second
Death Star. Although the thermal exhaust port
weakness was ﬁxed, he repeated many
of the same mistakes, believing
a bigger Death Star with more
ﬁrepower would ensure victory.
Hold a retrospective after each project What worked well? What could be
improved? Apply knowledge to future projects for constant improvement.
DIFFICU LT STAKEHOLDERS
The Emperor wanted the second Death Star operational ASAP, insisting on unreasonable timelines that Jerjerrod‘s
team could never meet. The only possible result was sloppy work & missed deadlines. And sure enough, without
Endor's protective shield, the Death Star was easy pickings for the Rebels.
When faced with unrealistic demands, present several feasible
alternatives and let the stakeholder choose the approach. Or, list
what additional resources you'll need to meet their request.
Jerjerrod simply didn't have the men he needed
to get the Death Star operational on time. When he
asked for additional resources, Vader and Palpatine
just threatened him instead of helping him.
Completed projects don't materialize through sheer willpower
Ask your team what they need, and then do your best
to provide it — or rethink your plan.
POOR TEAM MORALE
Vader believed that if your survival hinged on job
performance, you'd meet every expectation.
But by killing every admiral and captain who
slipped up, all he accomplished was constant
turnover of leadership — and stalled progress
as a result.
Did you know people are actually more productive when they're
in a good mood? (Safe to say the Empire didn't. ) Create a happy
work environment and watch your progress SOUI’.
When Vader wasn't killing key ofﬁcers or terrorizing
underlings, he was searching for Luke Skywalker.
He was so distracted, it's no wonder the project
was behind schedule!
Stay focused on the work at hand.
Multitasking is a sure-ﬁre productivity killer
Learn from the Empire’s mistakes
to keep your projects from falling
to the dark side — and stop by
Wrike. com/ blog to learn everything
you need to know about project '
management. We'll be your Yoda!
Brought to you by I
. ‘ward-ining collaboration
and projectjmanagement software
www. wrike. com