• Library Entrepreneur in Residence: Month 1

    A few weeks ago, I landed at Boston Logan Airport and caught the free Silver Line to South Station. I then bought a CharlieTicket from the kiosk for the week. This was my third paper CharlieTicket in two months, and I was starting to wonder how sustainable this was. One day after dinner that week I was walking to the T with my boss when I shared this. He told me to hold on a moment, and walked over to the booth agent. After a quick exchange, she handed him a hard plastic CharlieCard (there’s a difference) that he handed to me before we started walking toward the exit.

    For people not from New York, Boston, San Francisco or another evolved transit hub, know that there are levels to public transit.

    It hit me that I was an outsider, and like in many parts of life, there was an entire world that I needed an insider to show me the ropes. What made this meta was an identical experience taking place in parallel during my onboarding at Boston University Libraries. Having worked as a vendor with libraries since 2010, I thought I developed an “insider’s view” into the information profession. But after a month into my appointment as an EIR at BU, it’s become crystal clear that there’s an entire world to research libraries a vendor simply isn’t privy to.

    Time to write and think is few and far in between nowadays, but I consider it a part of my work to document my experience and share learnings to people studying the future of work in libraries. Here are a few initial impressions I can’t shake after 30 days.

    I’ve learned more about the academic research enterprise and its circumstance in the past 30 days than in the past 9 years.

    It’s one thing to get glimpses of the research enterprise through a meeting with a library or listening to a presentation at a conference. It’s an entirely other thing to jump waist-deep into the raging rapid that is an ARL, AAU, R1, large research operation. Weekly meetings, committee participation, attending industry gatherings, and performing deep work associated with the organization’s future is shaping up to be an executive MBA program for aspiring library leaders.

    Working in a community rather than a market affords opportunities to innovate as opposed to iterate.

    After getting two degrees in library automation and publishing (2, 4-year stints at major vendors), I got so burned out by the bickering, finger-pointing, and showmanship symptomatic of commercial vendors that I began to question my career choices. It’s easy to lose sight of the people and work that makes you excited about libraries when constantly being tasked to out do the “bad guy”. Because you’re constantly studying the competitor’s moves, you’re never able to actually innovate – it’s just varying degrees of iteration to do something cheaper or more novel without realizing the real competitor in the room is actually in the mirror. (More on vendors competing themselves away in another post). On the other hand, it’s revitalizing to be a part of an organization where the mandate is to literally determine the best ways to serve researchers and increase their impact.

    People – not resources, collections, or programs – are a library’s most important asset.

    The debate on this point will heat up in the coming years as we see the face and age of librarianship continue to shift. But I’m quite confident in my stance that the only force multiplier research libraries have in today’s increasingly complex operating environment are its investments in the development of its people. Our primary challenge then becomes unlocking the potential of our teams by sharing the onus of the library’s evolution with everyone on board, as opposed to a handful of deputies and managers.

    A vendor’s orientation, concerns, and goals are distinct, and perhaps anti-thetical to the concerns of the 21st century research enterprise.

    Another stark realization that I haven’t been able to shake is how out of sync commercial interests are from that of the library. Of course, the utility of products and services that meet the needs of libraries makes a positive impact. But on this vendor impact spectrum, there comes a point in which the utility becomes the threat. This is because commercial vendors have lost sight of their purpose and why they were created in the first place, replacing that purpose with the profit motive. Businesses don’t exist to create profit – they create profit in order to exist. Why they exist is a different reason altogether that the profit motive has obfuscated. The victims in this of course are libraries and patrons.

    More to share, but in the meantime, there’s more work to be done.

  • Diversity Hiring in Football and Libraries

    Last week I tweeted about an HBS story unpacking leadership lessons from the recent NFL coach firing spree. In short, the NFL season concludes each year with a host of personnel changes, known by fans as “Black Monday”. The article focused on takeaways from managers on personal development and skill acquisition as strategies to protect your position within an organization. This year’s Black Monday held an irony that may have fallen on the authors of the article, given that 5 of the 8 coaches fired were Black. This prompted a conversation within the Black community about the role race and equity play in the recruitment, development, and retention of its staffers.

    Google’s knowledge graph connected search query and click data to associate coaches fired in 2019’s Black Monday. Screenshot taken on Tuesday, January 29, 2019.

    This week, a colleague shared a podcast from sports commentator Bomani Jones on the NFL firings that touched on some key themes library directors deal with when trying to develop diverse talent pipelines. Check out the podcast first, then come back and see my highlights for libraries.

    1. Peeling Back The Layers Discouraging Diverse Talent Pipelines

    An ever growing dress code for a night club.

    Bomani Jones and his guest Domonique Foxworth joked about some of the rules night clubs establish to maintain a certain type of clientele. This typically includes restricting the type of wardrobe patrons wear in order to require assimilation to a pre-defined culture to gain admission. Now, once the initial rules were adhered to by an unintended group, more rules are added. But once the additional rules were adhered to by the unintended group, the intended group no longer wants to patronize the club, creating a dilemma for the club owner: Do we keep our night club exclusive to the intended group and risk losing the business of the unintended groups? Or do we allow the unintended groups in and run the risk of losing our core business.

    The co-hosts discussed that night club owners have a decision to make on whether to “lean in” to or embrace interest from Black patrons or to create layers discouraging them. In the US, most night club owners create obstacles prohibiting Blacks from patronizing their establishments. Historically, the same has been the case in libraries, posing the same question to library administrators: are we making it easier for diverse candidates to learn about, apply for, and thrive in openings in our organization, or are we making it more difficult?

    Deans and directors can analyze the following areas when it comes to building or tearing down these 5 layers in between diverse candidates and our organization:

    1. Advertising: Does our advertising encourage Whites to apply to our jobs and discourage Blacks? 
    2. Opportunities: Are the pathways into our organization designed to attract Whites and discourage Blacks? (More on this later.)
    3. Culture: Do our norms and expectations in the workplace encourage Blacks to assimilate to White culture in order to thrive?
    4. Policies: Do our policies discourage Blacks from investing years of their career there, encouraging them to leave as soon as they find a better opportunity?
    5. Benefits: Do our benefits and perks respond to the unique needs of the community we are seeking to attract?

    2. “We Steady Tryna’ Come Up”: Developing a Right View of Black Entitlement

    Talent pipelines don’t include Black people not due to lack of interest, but due to racist infrastructure explained above. In fact, to the contrary, it is a cultural trait among Black people to desire all of the opportunities that our white counterparts have for two primary reasons: 1) We feel entitled to it due to the centuries of unpaid labor from our ancestors. 2) As Domonique Foxworth states in the podcast, it’s one of the most American traits one can have to want everything that’s possible to be had and to want more of it. This runs counter to the prevailing racist stereotype suggesting that Blacks are entitled and lazy, and highlights the fact that since our ancestors were brought over, we’ve only ever known how to work for everything we have. 

    Rare footage from an NBC interview of Dr. Martin Luther King 11 months before his assassination addresses this issue of Black entitlement, which was a myth propagated by European peasant classes after receiving various forms of aid from the government.

    And he offered more details here in this speech to NATRA 9 months later.

    As Dr. King illustrates, conflating the native Black American experience with immigrants (even African immigrants) and other minority groups is an age-old tactic to extend slavery from its now illegal origins into various legal means that continue to make the American dream unachievable. The only difference now is that what used to be out in the open is now more subtle and more difficult to detect.

    As leaders of organizations who are serious about achieving equity within our workforces, do not succumb to the lazy man’s analysis of affirmative action, the Rooney Rule, and other programs. These programs were designed to give native Black Americans boots once and for all in order to one day be able to pull the bootstraps.

    The simplest way to understand the right view of black entitlement is that when a Black person is entitled, we aren’t interested in anyone manufacturing the outcomes for us so that we are successful, creating unfairness towards anyone else, but solely interested in leveling the playing field with equal opportunities so that we have as fair of a shot at success as our white and immigrant counterparts.

    3. Early Exposure is Key to Building Diverse Pipelines

    In his most recent press conference, the NFL commissioner addressed the issue on many fans’ minds of increasing the number of black coaching and managerial staff to become more representative of the population of the players. 

    Foxworth discussed why the pipeline in the NFL is so dry, and the reasoning resonated with the way the libraries run their organizations today. Jones described a similar comfort level he had on college campus since one of his parents who was a professor exposed him to the academic environment at a young age, leading to his success in college. Like libraries, most starting jobs in the NFL are unpaid positions, giving the children of coaches a leg up over other candidates. It may be the case that the coach’s son knows more about the game than a current player. But it’s no excuse to delay rethinking the talent development practices of the league. Since Black librarians cannot afford to take unpaid positions at the same rate many our white and immigrant counterparts can, and are not exposed to the information profession at as early of ages, the pipelines must be built much earlier.

    4.  Other Non-Diversity Related Takeaways

    As mentioned, the podcast is worth listening to all the way through, especially as a manager or leader in your organization. But here are some of the other takeaways not related to diversity.

    1. “What’s your coaching tree?” Try to uncover who candidates can bring with them when they come, and who’s tutelage they were you under  in order to gain insight into their leadership style and professional biases.
    2. “What gives you the edge?” Currently high performers have to always be thinking about the future, because your competitors are constantly looking at what you’re doing and adjusting, reducing your value proposition.
    3. “Help everyone improve, not just low-performers.” Compliment your talent to make them better, not to make what’s already easy for them easier.
    4. “Leaders invest in who people are, not just what they can do.” Important to build a relationship with people in order to develop culture. Can’t just stay focused on the tactics
  • Accessibility @Skilltype Part 1: Good A11Y is Good UX

     Skilltype’s v3 tagEditor
    Skilltype’s v3 tagEditor

    At the heart of Skilltype is a spirit of inclusion. We know that information professionals – those who work in libraries, who conduct scholarly research, who manage knowledge systems in our institutions – are vital to the survival and dissemination of truth. We make tools to help these professionals do their job well, and it’s important that our tools invite, include, and serve all those who might benefit from their use. That’s why we are committed to making our software accessible to users of all levels of ability.

    The following posts describe the considerations and challenges we faced when developing with accessibility in mind, describes some architectural strategies for building accessible components in React, and then walks through accessibility implementations in two of our components, MenuBar and TagListPicker.

    We’re not Accessibility experts. We’ve read a lot of blog posts about Accessibility and looked through various standards documents, but we don’t claim to have the depth of experience of, say, an Accessibility professional. However, we weren’t going to let that be an excuse to “leave accessibility for later,” which is a tempting path [1]. Instead, we decided to approach accessibility (A11Y) the way we approach user experience (UX). None of us have degrees in UX or call ourselves UX professionals, but like most teams building apps for web and mobile, UX is a top priority in our software design and we spend a lot of time discussing and testing it.

    Thinking about A11Y as UX is not trivial but it can be intuitive. The first step in our UX design is always mining our own sensibilities as web users. We ask ourselves questions like “does this make sense?”, “what would I expect to happen here”, “is this too much information on one screen”, etc. We use those sensibilities to make some best guesses that inform our interface design and behavior. We can do the same thing with A11Y with a little extra effort – first, we have to build some sensibility around using A11Y features by using the web the way someone with disabilities would.

    We began by familiarizing ourselves with the types of disabilities some of our users may have. The A11Y Project identifies four broad categories of accessibility: Visual, Auditory, Motor and Cognitive [2]. Each has its own specific set of guidelines and considerations, but there is also a lot of overlap. For example, if keyboard interaction is well-designed on your site, it will assist users with visual impairments using standard keyboard navigation as well as motor-impaired users using special control apparati. So, for the purposes of this post, we’ll focus on a blind or visually impaired user, but many of the analyses and strategies here can inform design and development for other accessibility needs.

    The W3C Web Accessibility Initiative (WAI) site provides some useful personas for users with disabilities [3]. Here’s an excerpt from their persona for Ilya, a senior staff member (of a fictitious organization) who is blind:

    • Ilya is blind. She is the chief accountant at an insurance company that uses web-based documents and forms over a corporate intranet and like many other blind computer users, she does not read Braille.

    • Ilya uses a screen reader and mobile phone to access the web. Both her screen reader and her mobile phone accessibility features provide her with information regarding the device’s operating system, applications, and text content in a speech output form.

    We know that responsible UX/UI design must address site or app functionality in the various browsers and platforms where users will encounter our work “in the wild” (Chrome, Firefox, iOS, Android, etc), so our next step was to identify the screen readers that our visually impaired users would use on our web app. For this, we looked to WebAIM, a non-profit organization out of Utah State University that compiles data every year on screen reader usage and demographics. We learned that the vast majority (> 80%) of users with disabilities used 3 screen readers: JAWS, NVDA and VoiceOver [4]. As JAWS is a commercial product with a non-trivial pricetag ($90/year), we opted to start with the free applications.

     Source:  WebAIM Screen Reader Survey, 2017
    Source: WebAIM Screen Reader Survey, 2017

    To educate ourselves, we watched some videos of users with disabilities actually using screen readers to interact with applications like email on their computers and phones, as well as navigate and use web sites like reddit (and even playing Mortal Kombat).

    We then installed and/or activated these applications on our own computers and spent some time using our computers and phones to browse the web. At first, it’s incredibly awkward and slow to do anything, especially on the phone, where the gestural metaphors are nearly all repurposed. One vlogger on Youtube who is blind and demoing screen readers on her phone even warns, “don’t activate VoiceOver on your iPhone until you know how to use it, or you won’t be able to turn it off” [5]. But after a few hours of experimentation and Googling, you should be able to proficiently navigate a website with only your ears and the keyboard. It’s very important to reach this level of proficiency with screen readers – you must begin to build a design intuition for alternative forms of interaction; over time, as you design, build, and test accessible interfaces, this intuition will mature and, ideally, be on par with your sense for visual design and usability.

    In Part 2, we’ll look at how React is particularly well suited for architecting accessible apps.

    Paul Hine is a senior developer at Skilltype.

  • Skilltype @ ALA Midwinter 2019: Taking the Road Less Travelled

    In typical Skilltype fashion, our presence at ALA Midwinter 2019 in Seattle was non-traditional. Mainly because as a startup, exhibit hall real estate isn’t the most fiscally responsible investment. But also because brands that launch at ALA in the sea of vendors simply to fade into oblivion. Why spend all of that money to cross your fingers in hope that the right people stop by your “little booth that could”, when in actuality the people who stop by just want to know if you’re raffling off an Apple Watch.

    So instead, I saved money, called up some friends, and connected the Skilltype way.

    Thursday: Gonzaga Skilltype Kickoff

     Icy sidewalk en route to Gonzaga’s Foley Library for their official Skilltype kickoff. January 23, 2019.
    Icy sidewalk en route to Gonzaga’s Foley Library for their official Skilltype kickoff. January 23, 2019.

    Over the course of the day, we had about 40-50 people from the library and various departments across campus such as Organizational Development and HR, Office of Diversity, and the office of research attend sessions to learn about the future of work, and how Skilltype can help prepare their organizations for 2030.

    After the session, I flew back across the Cascades to Seattle, and started preparing for the weekend’s festivities.

    Friday: Skilltype Happy Hour @ Amazon HQ

     Waiting on our advisory board member at Amazon’s Oscar building. January 23, 2019.
    Waiting on our advisory board member at Amazon’s Oscar building. January 23, 2019.

    Being in Seattle, I tapped Skilltype advisory board member Julian to see what ideas he had about showing our development partners a special experience while in town. He got us passes to the Amazon Spheres – an alternative workspace for Amazon employees who need a creative boost during the week. The 5-story indoor rainforest was an inspiration of what the future of work could feel like.

     Skilltype development partners touring Amazon Spheres. January 23, 2019.
    Skilltype development partners touring Amazon Spheres. January 23, 2019.

    After the tour ended, we met up with our beta testers and some new friends to kickback. This was one of the first times our development partners connected in this context. The energy around the Skilltype movement was tangible.

     Skilltype dev partners connecting at happy hour. January 23, 2019.
    Skilltype dev partners connecting at happy hour. January 23, 2019.

     Skilltype community members connecting at happy hour. January 23, 2019.
    Skilltype community members connecting at happy hour. January 23, 2019.

    Saturday: Skilltype + BCALA

    Spent the afternoon with the BCALA delegation sharing my personal story in libraries and the road to Skilltype. Was very interesting to have my personal and professional identities converge since they usually don’t. I believe this is another tenet of the future of work – being able to bring your full self to the workplace. To model it was refreshing and nerve-wracking at the same time.

    Sunday: Skilltype Product Update

     Skilltype beta testers and working group members discussing our current roadmap. January 25, 2019.
    Skilltype beta testers and working group members discussing our current roadmap. January 25, 2019.

    On Sunday morning, we connected with our beta testers and working group leaders to get stuff done. One of the biggest decisions that came our of this talk was to approach Teams differently on the platform. Eleanor Cook commented on the difficulty of organizing department nomenclature across institutions to the platform. Every institution calls teams something different. Unlike other pieces of organizational data that are controlled with vocabularies, Bohyun Kim from recommended that other systems on campus do a good job at structuring groups of people. Skilltype can be the place where we can create ad-hoc, dynamic groups simply used for internal purposes. We immediately agreed and brought the idea back to the team to update the roadmap.

    It was also interesting to have the current and previous heads of three separate professional associations in the room discussing Skilltype’s role in the professional association landscape. I’m really excited about where this conversation will go, as there seems to be a need for something more; something different.