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

Power, Influence and Authority in Engineering Leadership - Dinosaur.js

Power, Influence and Authority in Engineering Leadership - Dinosaur.js

Leadership opportunities are available at all levels of an organization, but some are more evident or clearly defined than others. Helping an organization achieve its goals may require us to step up as engineering leaders. As individual contributors, we may be able to support our team in negotiating the scope of a feature, facilitating a meeting or looking into that part of our codebase everyone shies away from. How about improving processes, helping define the culture or even the career journey of an organization? Do we need to be managers to have explicit authority to be agents of change? Maybe ... or maybe not

This talk explores different challenges that engineering teams have through the lens of power, influence or authority from the perspective of engineers or managers. If you've ever wondered if you should step into management, this talk can give you some insight into the right tool or role needed to be an agent for positive change. After this talk, you should have a better idea of whether making the management career change can give you the tools you need to grow and help others in the process.

Juan Pablo Buriticá

June 21, 2018
Tweet

More Decks by Juan Pablo Buriticá

Other Decks in Technology

Transcript

  1. !
    Power, Influence and Authority
    in Engineering Leadership
    @buritica

    View Slide

  2. View Slide

  3. View Slide

  4. "Juan, I think I want to go
    into Engineering
    Management"
    — an engineer

    View Slide

  5. Why?

    View Slide

  6. "I would like to help my
    team move forward"
    — same engineer

    View Slide

  7. Why would management allow
    you to make change?

    View Slide

  8. "Because I would have
    authority"
    — same engineer

    View Slide

  9. !
    Not so fast

    View Slide

  10. What kinds of change are you
    looking for?

    View Slide

  11. View Slide

  12. View Slide

  13. View Slide

  14. View Slide

  15. Authority

    View Slide

  16. Authority
    the power or right to give orders,
    make decisions, and enforce

    View Slide

  17. View Slide

  18. !
    Authority

    View Slide

  19. Authority
    the power to influence others,
    especially because of one's
    commanding manner or one's
    recognized knowledge about
    something.

    View Slide

  20. !
    Authority

    View Slide

  21. What authority does
    an engineer have?*
    * in a "healthy" org

    View Slide

  22. Authority
    Conventionally, authority is
    legitimate

    power

    View Slide

  23. By hiring
    you confer legitimate power over
    a technical domain

    View Slide

  24. Authority of an IC
    function individualContributor () {
    let authority = ['technical-domain']
    }

    View Slide

  25. Authority
    is not static

    View Slide

  26. Experience
    can modify authority

    View Slide

  27. Autonomy of an IC
    function individualContributor () {
    let authority = ['technical-domain']
    if (experienced) {
    authority.push('own-time')
    }
    }

    View Slide

  28. Experience as a modifier
    • JR IC: little authority over their time
    • Sr Eng: some authority over their time and other's time
    • Staff Eng: full authority over their time and some over
    other's

    View Slide

  29. Modifiers vary depending on
    company, org, team, and even
    manager

    View Slide

  30. So I can change all the softwares?

    View Slide

  31. Maybe...

    View Slide

  32. How much does your team trust
    you ...

    View Slide

  33. ... and what is your scope of
    influence?

    View Slide

  34. Everytime you make decisions
    you trade on trust

    View Slide

  35. Architectural decisions
    require higher trust than
    implementation ones

    View Slide

  36. What authority does a
    manager have?

    View Slide

  37. Authority of a manager
    function manager () {
    let authority = ['people, processes']
    if (experienced) {
    authority.push('strategy')
    }
    }

    View Slide

  38. Autonomy of a manager
    function manager () {
    // ...
    let autonomy = authority.indexOf('own-time')
    authority.pop(autonomy)
    }

    View Slide

  39. So I can change all the peoples
    and processes?

    View Slide

  40. Maybe...

    View Slide

  41. How much does your team trust
    you ...

    View Slide

  42. What is your scope of influence?

    View Slide

  43. or might I say, closure?

    View Slide

  44. Management has authority over
    software through people &
    process

    View Slide

  45. Authority Closures
    function vp() {
    function director() {
    function manager() {
    function individualContributor(){
    // software
    }
    }
    }
    }

    View Slide

  46. Management authority isn't
    enough all the time ...

    View Slide

  47. View Slide

  48. ... also, authority closures don't
    tend to work the other way
    around

    View Slide

  49. Authority Closures
    function individualContributor() {
    function manager() {
    function director() {
    function vp(){
    const compensation = '$$$'
    const process = 'waterfall'
    }
    }
    }
    }

    View Slide

  50. But sometimes, there is hope!

    View Slide

  51. View Slide

  52. We all have the opportunity to
    step up as leaders

    View Slide

  53. * Disclaimer leadership takes
    time, effort and patience.

    View Slide

  54. But most importantly
    trust

    View Slide

  55. Authority Closures
    function individualContributor() {
    function manager() {
    function director() {
    function vp(){
    const onCall = 'rotation'
    }
    }
    }
    }

    View Slide

  56. Building trust can
    help you pierce your
    closure

    View Slide

  57. Authority Closures
    function vp() {
    let oncall = 'rotation'
    function director() {
    function manager() {
    function individualContributor(){
    onCall = 'team owned'
    }
    }
    }
    }

    View Slide

  58. View Slide

  59. "Juan, I think I want to go
    into Engineering
    Management"
    — an engineer

    View Slide

  60. "So you're saying I don't
    need to be a manager"
    — an engineer

    View Slide

  61. Not entirely ...

    View Slide

  62. I want to encourage you to be a
    leader

    View Slide

  63. The intent of leadership is to
    deliver outcomes for the greater
    good

    View Slide

  64. We're part of an industry that has
    an abnormal amount of power to
    cause change in the world

    View Slide

  65. View Slide

  66. Working in
    technology gives you
    authority over the
    future of people at a
    never before scale

    View Slide

  67. Knowing about your "authority
    closures" may give you the ability
    to focus change

    View Slide

  68. Stepping into management is a
    career change

    View Slide

  69. But stepping up as an IC leader is
    a lower risk way of getting
    experience

    View Slide

  70. .. and building trust

    View Slide

  71. View Slide

  72. ... so that you can eventually
    make the change you want

    View Slide

  73. We need more and better
    engineering managers

    View Slide

  74. No matter how hard you try
    you will be someone's worst boss

    View Slide

  75. But it will all be worth it
    when you become someone's
    best boss

    View Slide

  76. And accept you can't change it all

    View Slide

  77. View Slide

  78. Thanks
    @buritica

    View Slide

  79. Photo Credits
    ESMAD

    View Slide