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

Giving back to the community through transparen...

Giving back to the community through transparency and a public handbook

Presented at the 2024 Code4libBC unconference on how transparency and a public handbook gives back to the community and profession.

Cynthia "Arty" Ng

May 14, 2024
Tweet

More Decks by Cynthia "Arty" Ng

Other Decks in Technology

Transcript

  1. GIVING BACK TO THE GIVING BACK TO THE COMMUNITY THROUGH

    COMMUNITY THROUGH TRANSPARENCY AND A TRANSPARENCY AND A PUBLIC HANDBOOK PUBLIC HANDBOOK May 16, 2024 Cynthia Ng @TheRealArty
  2. ANSWER THESE QUESTIONS ANSWER THESE QUESTIONS Do you have processes

    that need to be followed? Do you have shared workflows with other teams?
  3. ANSWER THESE QUESTIONS ANSWER THESE QUESTIONS Do you have processes

    that need to be followed? Do you have shared workflows with other teams? Do you have information that you frequently share?
  4. ANSWER THESE QUESTIONS ANSWER THESE QUESTIONS Do you have processes

    that need to be followed? Do you have shared workflows with other teams? Do you have information that you frequently share? Do you have people from other organizations ask how you do things?
  5. WHAT IS A HANDBOOK? WHAT IS A HANDBOOK? A handbook

    is a type of reference work, or other collection of instructions, that is intended to provide ready reference. - Wikipedia
  6. WHAT IS A HANDBOOK? WHAT IS A HANDBOOK? A handbook

    is a type of reference work, or other collection of instructions, that is intended to provide ready reference. - Wikipedia The handbook is the central repository for how we run the company.
  7. WHY A HANDBOOK? WHY A HANDBOOK? “Shared reality” with a

    Single Source of Truth (SSoT) Low-context communication
  8. WHY A HANDBOOK? WHY A HANDBOOK? “Shared reality” with a

    Single Source of Truth (SSoT) Low-context communication Documented workflows promote
  9. WHY A HANDBOOK? WHY A HANDBOOK? “Shared reality” with a

    measurement clarity Single Source of Truth (SSoT) Low-context communication Documented workflows promote
  10. WHY A HANDBOOK? WHY A HANDBOOK? “Shared reality” with a

    measurement clarity results standardization Single Source of Truth (SSoT) Low-context communication Documented workflows promote
  11. WHY A HANDBOOK? WHY A HANDBOOK? “Shared reality” with a

    measurement clarity results standardization worker autonomy Single Source of Truth (SSoT) Low-context communication Documented workflows promote
  12. WHY A HANDBOOK? WHY A HANDBOOK? “Shared reality” with a

    measurement clarity results standardization worker autonomy efficient onboarding / inclusivity Single Source of Truth (SSoT) Low-context communication Documented workflows promote
  13. WHY A HANDBOOK? WHY A HANDBOOK? “Shared reality” with a

    measurement clarity results standardization worker autonomy efficient onboarding / inclusivity continuous improvement Single Source of Truth (SSoT) Low-context communication Documented workflows promote
  14. WHY A HANDBOOK? WHY A HANDBOOK? “Shared reality” with a

    measurement clarity results standardization worker autonomy efficient onboarding / inclusivity continuous improvement operational scalability Single Source of Truth (SSoT) Low-context communication Documented workflows promote
  15. WHAT YOU NEED WHAT YOU NEED Buy-in Location / Version

    controlled tool Easy (enough) to use
  16. WHAT YOU NEED WHAT YOU NEED Buy-in Location / Version

    controlled tool Easy (enough) to use Reinforcement
  17. WHAT YOU NEED WHAT YOU NEED Buy-in Location / Version

    controlled tool Easy (enough) to use Reinforcement Public by default (separate internal only)
  18. WHAT YOU NEED WHAT YOU NEED Buy-in Location / Version

    controlled tool Easy (enough) to use Reinforcement Public by default (separate internal only) Start small and iterate
  19. ENCOURAGING CONTRIBUTIONS ENCOURAGING CONTRIBUTIONS Invite collaboration on changes Have guidelines

    on what level of review is required Have clear guidelines on internal-only information
  20. ENCOURAGING CONTRIBUTIONS ENCOURAGING CONTRIBUTIONS Invite collaboration on changes Have guidelines

    on what level of review is required Have clear guidelines on internal-only information Example: SAFE framework
  21. ENCOURAGING CONTRIBUTIONS ENCOURAGING CONTRIBUTIONS Invite collaboration on changes Have guidelines

    on what level of review is required Have clear guidelines on internal-only information Example: Doesn't need to be perfect, Not "set in stone" SAFE framework
  22. Harvard Business Review, March-April 2019. when people see the work

    going on behind the scenes, they value the service more. - Ryan Buell on Operational Transparency https://hbr.org/2019/03/operational-transparency
  23. WHY A PUBLIC HANDBOOK? WHY A PUBLIC HANDBOOK? Efficiency Consistency

    Collaboration Community resource Operational transparency
  24. WHY A PUBLIC HANDBOOK? WHY A PUBLIC HANDBOOK? Efficiency Consistency

    Collaboration Community resource Operational transparency
  25. WHY A PUBLIC HANDBOOK? WHY A PUBLIC HANDBOOK? Efficiency Consistency

    Collaboration Community resource Data source Operational transparency
  26. OTHER WAYS TO SHARE OTHER WAYS TO SHARE Write publicly

    Blog Article Newsletter Make resources public
  27. OTHER WAYS TO SHARE OTHER WAYS TO SHARE Write publicly

    Blog Article Newsletter Make resources public LibraryToolshed.ca