Presentation given at the Designing for Digital Conference in Austin, Texas, on Monday, March 9, 2020.Teams at three libraries are using personal README files to improve communication. As README files tell you how to use software, personal README files tell you how best to interact with teammates. Presenters will share the hows, whys and benefits of incorporating personal README files into your team's practice.https://deepblue.lib.umich.edu/bitstream/2027.42/154114/1/Personal README Files- User Manuals for Library Staff.pdfhttps://deepblue.lib.umich.edu/bitstream/2027.42/154114/2/Personal README Files- User Manuals for Library Staff (with speaker notes).pdfDescription of Personal README Files- User Manuals for Library Staff.pdf : Presentation slidesDescription of Personal README Files- User Manuals for Library Staff (with speaker notes).pdf : Presentation slides with speaker note

Boyer, Josh

Brewer, Ashley

Vacek, Rachel

English

Deep Blue Documents at the University of Michigan

University of Michigan 2020-03-09 Personal README Files: User Manuals forLibrary Staff Vacek, Rachel; Boyer, Josh; Brewer, Ashley  http://hdl.handle.net/2027.42/154114Deep Blue deepblue.lib.umich.eduPersonal README FilesUser Manuals for Library StaffJosh Boyer, Ashley Brewer, Rachel VacekDesigning for DigitalMarch 9, 2020Josh BoyerDepartment Head, User Experience, NC State University Libraries@jeboyerAshley BrewerWeb Systems Librarian, Virginia Commonwealth University Libraries@loveonamixtapeRachel VacekHead of Design & Discovery, University of Michigan Library@vacekraeOutlineTraditional vs. personal README filesHow we each picked up the ideaAbout our teams and how we’re using themHow personal README files have helped usDiscussionTraditional README ﬁlesThe contents typically include one or more of the following:● Configuration instruction● Installation instructions● Operating instructions● A file manifest (list of files included)● Copyright and licensing information● Contact information for the distributer or programmer● Known bugs● Troubleshooting● Credits and acknowledgments● A changelog (usually for programmers)● A news section (usually for users) Personal / Manager README ﬁlesMolly, Tech Lead at HubSpot● My role as tech lead● Feedback● One-on-ones● Performance● My schedule● After-hours communication● A note on diversity and inclusion● If you need something● Expectations of you● My interestsExamples from README ﬁles at Tech Companies“My intent is to accelerate our working relationship with this document.”“Do not confuse my quiet with lack of engagement.”“Expected response times by communication channel…”“If I fail at any of these - especially anything that puts retaining you at risk - you would be doing me a huge favor by letting me know as soon as possible. I don't expect everyone to stick around forever, however if a departure is potentially due to something we could have done different, I would appreciate the chance to make things right first.”Use cases for README ﬁles● New employee onboarding● New team, committee, or department formation● Relationship management○ Expectations○ Personal preferences● Norm creationHow we picked up the idea of using personal README ﬁlesI stole the idea from my boss...who stole the idea from Big Tech. Already were doing semi-yearly “Write the Docs” daysMy boss shared the idea of personal READme files, and I thought they sounded like a great idea (especially because team communication was an ongoing area for improvement)We thought Write the Docs Day + Readme files = profit!How Josh started using Personal README ﬁlesRachel stole the idea from Ashley from D4D last yearMore about our teams and how we are using README ﬁlesUniversity of Michigan Library’s Design & Discovery DepartmentRobyn NessSenior UX SpecialistKen VarnumSenior Program ManagerJon EarleyUser Interface Design EngineerEllen SchlegelmilchUI/UX DesignerEliot ScottDrupal DeveloperBen HowellUser Experience & Accessibility SpecialistAlbert Bertram Web Applications Team LeaderHeidi BurkhardtWeb Project Manager & Content StrategistRachel VacekHead of Design& DiscoveryTBDFront-End DeveloperBridget BurkeFront-End Developer & Accessibility SpecialistHeymo VehseWeb Applications DeveloperD&D’s areas of focusUser experience research and designFront-end and back-end developmentProgram and project managementDigital accessibility expertiseDesign & Discovery’s SpaceDesign & Discovery’s SpaceWhy READMEs for my department?● Two departments merged into D&D● People who hadn’t previously worked together were now going to be on multiple teams together● Lots of staff change○ New positions○ Retirement○ Promotions○ Reclassifications○ People moving on/filling vacant positions● Balance of work/life● Flexibility in schedules● Renovation of space and everyone coming together● Personal preferences for interactionD&D’s README Template● Name● Title● When I started working in the Library● How I describe my work to someone unfamiliar with the type of work I do● My communication preferences:● Favorite hobbies● Favorite snacks● I am grateful for● One adjective to describe youVCUL’s Digital Engagement DepartmentErin White, Head, Digital EngagementKatie Condon, Digital SpecialistAshley Brewer, Web Systems LibrarianTodd Easter, Web DesignerCody Whitby, Web Applications EngineerStudent workers, 3-5 digitization, 1 webVCU Libraries Digital Engagement DepartmentVCU Libraries Digital Engagement READme template● About Me -- personal information, background, etc● My job -- describe your job/role in your own words ● Personal pinciples / Values  -- share some core beliefs that you think guide your work and are key to understanding where you’re coming from● Communication / Calendar -- What type of communication you prefer for what type of message, i.e. when to email vs when to call (never call) and how to interpret your calendar/drop in-ability● Feedback (how you give it and how you like to receive it) -- Communication “style” and what style and type of feedback you respond to best● Favorite foods/snacks -- for when it’s your birthday or we have something to celebrate!● Choose your own adventure!NC State University Libraries’ UX departmentNC State University Libraries’ UX departmentNC State’s README ﬁle template● Name● Title● When I started working at NC State University Libraries● My job, in my own words ● About me (personal background stuff, like where we're from, hobbies, favorite snacks, whatever is important to share)● My communication preferences (meetings, email, F2F)● My use of social media that I choose to talk about in this context● My managerial style / What I appreciate from a supervisor● What I think about noise and interruptions● I’m saying “do not disturb” when INC State’s README ﬁle template, continued● When working with me, it’s good to know that● My super power for getting things done● The primary persona I think of as the audience for my work● Other ways of describing me that may mean something to you (Myers-Briggs, Leadership frame, Hogwarts house, Enneagram, Parks and Recreation, Birth chart, etc.)● A boring fact about me● I am grateful for● [Feel free to add prompts of your own]How personal READMEs have helped usHow README ﬁles have helped Michigan ● Created an opportunity for my staff to express what's important to them as well as to learn what's important to their colleagues● Helped with onboarding and getting to know people, including those that work remotely more frequently● Increased awareness of one another’s communication styles and how they do/don’t like to be interrupted● Acknowledged people’s snack preferences, and that for most of my department, coffee IS superior to snacks (and that I shouldn’t trivialize it with such a designation)How README ﬁles have helped VCU● Bagels > donuts, not @ me!● Great onboarding tool. ● It allowed us to articulate things that are important but might be hard to say.● Gives us something to refer back to and consider● Writing them and reading each other’s helped us feel connectedHow README ﬁles have helped VCU(*Slowly backs away….*)(starts coming ‘round the corner to Ashley’s office) Hey, Ash what’s -- (Is eating. Glares.) How README ﬁles have helped NC StateAndreas Orphanides, associate department headHow README ﬁles have helped NC StateDre’s README file: “I’m very good at really big picture thinking and at nitty gritty details. I've got a bit of a blind spot between these two extremes.”How README ﬁles have helped NC StateDre’s README file: “I’m very good at really big picture thinking and at nitty gritty details. I've got a bit of a blind spot between these two extremes.”Josh’s README file: “I complement Dre with my medium-picture thinking.”How README ﬁles have helped NC State● Onboarding new staff● Allows us to say things we wouldn’t otherwise say, for example:“I advise you to build a portfolio of work that is a mix of your projects, projects that came from me and other supervisors, our team’s projects, and ones we do to support our colleagues and the Libraries.”How README ﬁles have helped NC StateHow README ﬁles have helped NC StateHow README ﬁles have helped NC StateOur boring facts:● “My favorite drink is Orangina.”● “The route I drive to work is not the same route that I drive home.”● “I don't like beets.”● “I'm pretty good at making paper snowflakes!”● “My favorite band is U2.”Discussion1. How have your you used tools like personal README files to help with communication, onboarding, team formation, or relationship management?2. What opportunities do you see with personal README files helping you, your team, or your work environment?3. What challenges do you think you might have with using personal README files in your work environment?4. What tacit understandings and misunderstandings among team members could be improved if people wrote down how they work best?5. What additional ideas do you have to add to the personal README file template(s)?Thanks!Josh BoyerDepartment Head, User Experience, North Carolina State University Librariesjeboyer@ncsu.eduAshley BrewerWeb Systems Librarian, Virginia Commonwealth University Librariesabrewer2@vcu.eduRachel VacekHead of Design & Discovery, University of Michigan Libraryrvacek@umich.edu

Personal README Files: User Manuals for Library Staff

https://deepblue.lib.umich.edu/bitstream/handle/2027.42/154114/Personal%20README%20Files-%20User%20Manuals%20for%20Library%20Staff.pdf?sequence=1&isAllowed=y

Personal README Files: User Manuals for Library Staff

Abstract

Similar works

Full text

Available Versions

Deep Blue Documents at the University of Michigan