Elite Leadership Tips

687 views

Published on

Published in: Business, Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
687
On SlideShare
0
From Embeds
0
Number of Embeds
8
Actions
Shares
0
Downloads
15
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Elite Leadership Tips

    1. 1. Elite
Leadership
Tips José
Teixidó Joesys@gmail.com @joesys
    2. 2. Background• Guby
Network
 (Grippo,
Achei,
Brújula,
Yagua,
 Conexcol,
Mexico
Global)• Amnisty
InternaJonal• abc
Digital• Keegy
/
SmowJon• Mazda
USA• Sabre
Holdings
    3. 3. Background• Licemil
1
“Acosta
Ñú”
Military
Academy• ARIOS
(Jungle
Ops
InstrucJon
Area)• CIMOE
(Special
OperaJons
Command)• Military
parachuJst• Silvio
PeJrossi
 Para
Regiment
    4. 4. Tech
Company
Warfare• Small
teams
operaJng
in
adverse
condiJons
in
 unstable
situaJons• “Operators”
usually
in
charge
of
more
than
one
 essenJal
task• Absolutely
everybody
counts• PotenJal
lack
of
“SituaJonal
awareness”
    5. 5. The
(lack
of)
Leadership
Problem• De
facto
teams• Team
Leads
usually
chosen
based
on
pure
 technical
seniority
or
years
in
service
for
the
 company• Leaders
with
“I
am
legend”
complex
    6. 6. Redefining
Leadership• Boss
Vs.
Leader: – Boss:
Dictates
 – Boss:
Commands – Boss:
Inspects – Leader:
Involves
and
inspires• Horde
or
Mob
Vs.
Team Difference
is
just
a
thin
line
 made
of
respect
and
coordinaJon
    7. 7. Tip
#1 CulJvate
the
characterisJcs
 of
a
true
leader:• DedicaJon• Integrity• Technical
competence• Self‐confidence• Devoted
to
the
objecJves
that
are
entrusted
to
 him
but
also
to
his
people
    8. 8. Tip
#2 Own
your
team
• Values:
There
is
no
“team”
unJl
everybody
 understands
the
team
“colors”• MoJvaJon:
Find
out
what
moves
your
team,
 personally
and
professionally
• DevoJon:
Leading
is
a
full
Jme
job
    9. 9. Tip
#3 Lead
by
example• “First
to
fight
&
last
to
flee”
aetude• Make
sure
you
commit
to
your
own
rules
and
 deadlines• Respect
your
team
and
you
will
be
respected

    10. 10. Tip
#4 Provide
support
 and
develop
your
team• “Sergeant”
comes
from
the
french
“Servant”...
he
who
serves
 the
troops• Facilitate
and
remove
roadblocks• Pareto
principle:
ideally
20%
of
new
tasks
or
non
maintenance
 development• Create
a
weekly
space
for
the
team
to
share
its
views
on
 technology
or
projects,
even
if
they
are
personal
    11. 11. Tip
#5 Create
a
dependable
structure
&
 trust
it• Avoid
“nobody
in
command”
and
“hide
the
bomb”
situaJons• Implement
high
standards
without
a
“zero
defect”
aetude• Share
the
burden
of
command
and
delegate
process
 inspecJons
    12. 12. Tip
#6 Define
“Success”• The
“problem”
defines
the
“goal”• Clear
and
realisJc
objecJves• Measure
progress
using
always
the
same
metrics• Just
like
in
combat,
keeping
a
“defensive”
aetude
for
long
 periods
of
Jme
drains
teams
moral
    13. 13. Tip
#7 “Debrief”
each
mission• Analyze
what
went
well
and
what
could
be
improved
aier
 every
release• Encourage
feedback
over
the
work
done
on
the
previous
 release• Making
a
mistake
is
human,
making
the
same
mistake
twice
is
 stupid
(and
potenJally
deadly)
    14. 14. Tip
#8 Reward
and
punish
 with
respect• Reward
and
scold
should
last
no
more
than
a
few
minutes• Scolding
should
be
personalized
but
never
personal• Should
be
done
as
soon
as
possible
aier
the
offense,
and
 should
be
done
in
person
with
good
eye
contact
    15. 15. Tip
#9 Stand
up
and
take
the
hit• Decide
and
execute
when
there
is
conflict.
Never
let
coworkers
 argue
for
too
long
waiJng
for
them
to
decide
who
“wins”• Hence,
even
if
your
decision
is
not
popular
the
affected
party
 will
focus
frustraJon
on
you
and
not
on
coworkers.
Remember
 keeping
the
team
oiled
and
operaJve
always
comes
first.• Is
bejer
to
make
a
bad
decision
than
taking
none
    16. 16. Tip
#10 Shut
up
and
learn!• Being
a
leader
doesn’t
mean
you
should
know
everything,
that
 is
why
you
have
competent
people
reporJng
to
you• A
good
listener
is
a
good
decision
maker• Avoid
using
your
personal
experience
as
your
only
aid
when
 analyzing
a
situaJon
    17. 17. Q&A Thank
you! José
TeixidóJoesys@gmail.com @joesys

    ×