Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Influence Without Authority

Influence Without Authority

This workshop is designed for employees at all levels who are interested in creating positive change in their work environment or whose role requires them to gain buy-in from others, including people in power, direct reports and cross-functional teams.

Created in collaboration with Paloma Medina.

Lara Hogan

May 04, 2020
Tweet

More Decks by Lara Hogan

Other Decks in Education

Transcript

  1. Influence Without
    Authority
    Lara Hogan, Coach + Trainer
    In collaboration with Paloma Medina
    Copyright 2020

    View Slide

  2. We all care about
    different things.

    View Slide

  3. Long road: convince them to see
    your point of view.
    Short road: see it from their
    point of view.

    View Slide

  4. Influence vs.
    Manipulation

    View Slide

  5. Influence Manipulation
    Agree with you or go along with your idea
    Disclose relevant
    information
    Hide or lie
    about relevant
    information

    View Slide

  6. Intentional influence

    View Slide

  7. COURAGE
    CONSIDERATION
    ● Doormat
    Innovative Jerk ●
    Ethical Influence ●
    ● Mean and boring

    View Slide

  8. The 3 Rules of
    Ethical Influence

    View Slide

  9. 1. Know What Matters (to
    the People who Matter)

    View Slide

  10. Identify stakeholders.

    View Slide

  11. Blocker
    Decision-
    Maker Ally
    People whose help you’ll need ▢ ▢ ▢
    Departments ▢ ▢ ▢
    Passionate people ▢ ▢ ▢
    Leaders in general ▢ ▢ ▢
    Influencers ▢ ▢ ▢
    Super experienced people ▢ ▢ ▢
    People who will be impacted ▢ ▢ ▢

    View Slide

  12. Blocker
    Decision-
    Maker Ally
    People whose help you’ll need ▢ ▢ ▢
    Departments ▢ ▢ ▢
    Passionate people ▢ ▢ ▢
    Leaders in general ▢ ▢ ▢
    Influencers ▢ ▢ ▢
    Super experienced people ▢ ▢ ▢
    People who will be impacted ▢ ▢ ▢

    View Slide

  13. Get to know
    stakeholders’ currencies.

    View Slide

  14. Our core needs
    as currencies

    View Slide

  15. 1. What feels most important to you about this?
    2. What challenges are you most concerned with?
    Or—in an ideal world—how would we move this forward?
    3. What one thing do you wish you could change about this?
    4. I have an idea I need your advice on [share idea] - what do you think I need to do to get
    others on board? Or—What key concerns or goals do you think I should keep my eye on
    for this project?
    5. If you were me, how would you handle _________?
    Tell me more about what made you choose that route?
    6. Who would you recommend I talk to to learn more about the history/background on this
    issue?
    7. If _______ happens, how would that impact you/ your crew?
    8. If I have more questions, would you mind if I follow up via email you or coffee?
    9. What can I do to make this easier/ more likely to happen?

    View Slide

  16. Resistance is data.

    View Slide

  17. We’ll need to adapt these
    tools based on who we are,
    and who our audience is.

    View Slide

  18. 2. Be a Builder

    View Slide

  19. View Slide

  20. Builders are
    solution-oriented,
    not problem-oriented.

    View Slide

  21. Facts + Impact → New Idea

    View Slide

  22. Facts + Impact → New Idea
    “There are currently no Engineering
    principles defined for how teams
    should be building new features.
    This means that there are very few
    shared components, and feature teams
    have to reinvent the wheel each time.”
    ”I vote we create a
    working group to
    define 3-4 shared
    Engineering team
    principles.”

    View Slide

  23. Facts + Impact → New Idea
    “There are currently no Engineering
    principles defined for how teams
    should be building new features.
    This means that there are very few
    shared components, and feature teams
    have to reinvent the wheel each time.”
    ”I vote we create a
    working group to
    define 3-4 shared
    Engineering team
    principles.”

    View Slide

  24. Facts + Impact → New Idea
    “There are currently no Engineering
    principles defined for how teams
    should be building new features.
    This means that there are very few
    shared components, and feature teams
    have to reinvent the wheel each time.”
    ”I vote we create a
    working group to
    define 3-4 shared
    Engineering team
    principles.”

    View Slide

  25. Facts + Impact → New Idea
    “There are currently no Engineering
    principles defined for how teams
    should be building new features.
    This means that there are very few
    shared components, and feature teams
    have to reinvent the wheel each time.”
    ”I vote we create a
    working group to
    define 3-4 shared
    Engineering team
    principles.”

    View Slide

  26. ”I vote we create a
    working group to
    define 3-4 shared
    Engineering team
    principles.”
    Make sure
    your idea takes
    into account
    key currencies.

    View Slide

  27. Tips for coming up
    with new ideas

    View Slide

  28. Influence is about ideas.
    Builder statements:

    View Slide

  29. Do your research about
    the facts and solutions.
    Builder statements:

    View Slide

  30. Avoid negative labels.
    Don't insult people or
    their "babies".
    Builder statements:

    View Slide

  31. View Slide

  32. View Slide

  33. “Our current vacation policy is
    outdated”
    ✓ “A new vacation policy could
    attract more talent”

    View Slide

  34. “Our parental leave policy is sexist”
    ✓ “An updated parental leave policy
    could help us walk the talk of
    inclusion”

    View Slide

  35. “We’re making a huge mistake if
    we go with that idea”
    ✓ “We could avoid X, Y and Z if we
    go with this other idea”

    View Slide

  36. I know you care about [currency].
    Here’s how [idea] can help with that.

    View Slide

  37. Start with winnable
    experiments.

    View Slide

  38. We’ll test ______________________________________________
    your proposed change
    for ______ months with __________________________________.
    number audience for experiment
    Our success metrics will be _______________________________.
    1-3 metrics
    We’ll report back our findings to ___________ and ___________.
    stakeholder stakeholder

    View Slide

  39. We’ll test ______________________________________________
    your proposed change
    for ______ months with __________________________________.
    number audience for experiment
    Our success metrics will be _______________________________.
    1-3 metrics
    We’ll report back our findings to ___________ and ___________.
    stakeholder stakeholder
    3
    a new mentorship + sponsorship program
    12 recent new hires in Product
    quarterly peer feedback results
    HR Product leads

    View Slide

  40. We’ll test ______________________________________________
    your proposed change
    for ______ months with __________________________________.
    number audience for experiment
    Our success metrics will be _______________________________
    ______________________________________________________.
    1-3 metrics
    We’ll report back our findings to ___________ and ___________.
    stakeholder stakeholder
    1.5
    a working group to define 3 eng principles
    1 representative from each team
    each team feels heard, and
    Eng Leads all of eng
    the principles can be applied to current + planned work

    View Slide

  41. 3. Iterate, Iterate, Iterate

    View Slide

  42. View Slide

  43. Prepare to improve
    at least 30% of your idea
    by seeking feedback along
    the way, iterating as needed.

    View Slide

  44. How

    View Slide

  45. How
    Designers +
    PMs build
    fast-loading
    features

    View Slide

  46. How
    Goal/
    Core Need
    Designers +
    PMs build
    fast-loading
    features

    View Slide

  47. How
    Goal/
    Core Need
    Designers +
    PMs build
    fast-loading
    features
    Usable website
    for people on
    slower/outdated
    infrastructure

    View Slide

  48. How
    Goal/
    Core Need
    Be flexible about
    your how

    View Slide

  49. How
    Goal/
    Core Need
    Be flexible about
    your how
    Be firm about
    your goal
    (core need)

    View Slide

  50. Get good at
    feedback-seeking.

    View Slide

  51. Resistance → Data
    BONUS MATERIAL!

    View Slide

  52. Most common responses
    when a threat is detected
    BONUS MATERIAL!

    View Slide

  53. 1. Doubt
    2. Avoid
    3. Fight
    4. Bond
    5. Escape-route
    }Data
    BONUS MATERIAL!

    View Slide

  54. Knowing and addressing
    someone’s core needs is a
    shortcut to making them feel
    understood and valued.
    BONUS MATERIAL!

    View Slide

  55. How do we recover when
    we amygdala-hijack
    someone?
    BONUS MATERIAL!

    View Slide

  56. BONUS MATERIAL!

    View Slide

  57. BONUS MATERIAL!

    View Slide

  58. Have a back-pocket script:
    Eject button + next step
    BONUS MATERIAL!

    View Slide

  59. There might be an
    inherent power dynamic
    BONUS MATERIAL!

    View Slide

  60. “I wanted to get your thoughts on
    my email last week.
    What did you read in it?
    What could I have said better?”
    BONUS MATERIAL!

    View Slide

  61. With your mouthwords:
    ● Acknowledge the power dynamic
    (if you’re a manager/leader)
    ● Acknowledge whenever you’ve messed
    something up
    BONUS MATERIAL!

    View Slide

  62. “Here are some avenues to
    give me feedback; choose
    whichever feels most
    comfortable”
    BONUS MATERIAL!

    View Slide

  63. “What I learned…”
    “What I’ll do…”
    BONUS MATERIAL!

    View Slide

  64. “I see now that when ______
    happened, we messed with
    ______. What if next time, we
    instead try ___________?”
    BONUS MATERIAL!

    View Slide

  65. Caveat
    The goal is not 100% consensus
    100% of the time
    BONUS MATERIAL!

    View Slide