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

Centralising the right things

Centralising the right things

Tom Booth

June 09, 2017
Tweet

More Decks by Tom Booth

Other Decks in Technology

Transcript

  1. @tombooth
    Centralising the right
    things
    Tom Booth

    View Slide

  2. @tombooth

    View Slide

  3. @tombooth
    tl;dr

    View Slide

  4. @tombooth
    Build a central team to
    empower and support
    others

    View Slide

  5. @tombooth
    Centralised
    Decentralised
    Re-centralised

    View Slide

  6. @tombooth
    Centralised
    Decentralised
    Re-centralised

    View Slide

  7. @tombooth

    View Slide

  8. @tombooth
    We weren’t one business,
    we were compe>ng func>ons

    View Slide

  9. @tombooth
    Protec>onism built through
    compe>>on

    View Slide

  10. @tombooth

    View Slide

  11. @tombooth
    Every 3 weeks, …

    View Slide

  12. @tombooth

    View Slide

  13. @tombooth
    Every 3 weeks, we had a
    wild ride of forgoHen
    changes

    View Slide

  14. @tombooth
    Opera>ons would get the
    blame for developer problems

    View Slide

  15. @tombooth

    View Slide

  16. @tombooth
    Why did their change break
    my code?

    View Slide

  17. @tombooth
    Centrally provided tools
    were very poor

    View Slide

  18. @tombooth
    GeLng features to our
    users was slow
    When we were centralised,

    View Slide

  19. @tombooth
    Change was complex
    because of poor design
    When we were centralised,

    View Slide

  20. @tombooth
    Func>onal ownership
    caused serious fric>on
    When we were centralised,

    View Slide

  21. @tombooth
    Centralised
    Decentralised
    Re-centralised

    View Slide

  22. @tombooth
    One team needs to own the
    whole service

    View Slide

  23. @tombooth

    View Slide

  24. @tombooth
    You have to embrace
    change

    View Slide

  25. @tombooth
    Deploying con>nuously is
    beHer for users

    View Slide

  26. @tombooth
    A team should own its own
    architecture and infrastructure

    View Slide

  27. @tombooth

    View Slide

  28. @tombooth
    Every team with their own
    direc>on, liHle shared

    View Slide

  29. @tombooth
    Solving the same problems,
    in the same way with
    different implementa>ons

    View Slide

  30. @tombooth
    Opera>ng at larger scale
    requires deeper knowledge

    View Slide

  31. @tombooth
    GeLng features to our
    users was slow
    When we were centralised,

    View Slide

  32. @tombooth
    Change is complex because
    of poor architecture
    When we were centralised,

    View Slide

  33. @tombooth
    Func>onal ownership
    caused serious fric>on
    When we were centralised,

    View Slide

  34. @tombooth
    The same problems were
    being solved repeatedly
    When we were decentralised,

    View Slide

  35. @tombooth
    No-one has the complete
    picture
    When we were decentralised,

    View Slide

  36. @tombooth
    We weren’t focusing on our
    users as much as we should
    When we were decentralised,

    View Slide

  37. @tombooth
    Centralised
    Decentralised
    Re-centralised

    View Slide

  38. @tombooth
    Retain ownership in the
    service teams

    View Slide

  39. @tombooth
    Iden>fy common paHerns
    in our infrastructure

    View Slide

  40. @tombooth
    Support common paHerns
    with great tooling

    View Slide

  41. @tombooth
    Always ask, how can we
    help each other?

    View Slide

  42. @tombooth
    Give teams room to
    experiment, do what’s best
    for them

    View Slide

  43. @tombooth
    Outside impressions maHer

    View Slide

  44. @tombooth

    View Slide

  45. @tombooth
    Help our owners, investors
    and auditors understand
    our services

    View Slide

  46. @tombooth
    Work together
    not apart

    View Slide

  47. @tombooth
    Work together on
    architecture

    View Slide

  48. @tombooth
    Work together on
    issues

    View Slide

  49. @tombooth
    Work together on
    bugs in produc>on at 3am

    View Slide

  50. @tombooth
    GeLng features to our
    users was slow
    When we were centralised,

    View Slide

  51. @tombooth
    Change is complex because
    of poor architecture
    When we were centralised,

    View Slide

  52. @tombooth
    Func>onal ownership
    caused serious fric>on
    When we were centralised,

    View Slide

  53. @tombooth
    The same problems were
    being solved repeatedly
    When we were decentralised,

    View Slide

  54. @tombooth
    No-one has the complete
    picture
    When we were decentralised,

    View Slide

  55. @tombooth
    We weren’t focusing on our
    users as much as we should
    When we were decentralised,

    View Slide

  56. @tombooth
    Build a central team to
    empower and support
    others

    View Slide