Beyond the Better Mousetrap: Building pockets of culture where librarians make innovation stick

You do not hate innovation. You hate the ritual of buying a shiny new thing and calling that change.

Douglas Holt described the “better mousetrap” instinct as the belief that if you build a better product, people will naturally come. It is an appealing idea because it is simple, measurable, and easy to present. But in libraries, it rarely works that way. A new platform, interface, or AI tool may look impressive, yet still fail to change beliefs, habits, or identities. In higher education especially, the challenge is rarely just technical. It is cultural.

Libraries do not succeed because they offer one more feature than the next product on the market. They succeed when they help people learn differently, see themselves differently, and participate more fully in academic life. That kind of change does not happen through procurement alone. It happens through relationships, repeated practice, reflection, and trust. If the stories people tell about research, teaching, or technology do not change, then the tool may be new, but the culture around it remains the same.

That is why tech-first thinking often misfires in libraries. The real stakes are not only efficiency or convenience. They include identity, pedagogy, equity, belonging, and authority. Buying a tool does not automatically help a student see themselves as a scholar. It does not change how a faculty member teaches. It does not help a campus community think more deeply about ethical AI use, critical inquiry, or what counts as meaningful academic work. These are changes in meaning, not just function.

Holt’s work on cultural innovation is helpful because it reminds us that breakthrough value often comes not from changing what something does, but from changing what it means. Starbucks did not invent coffee. It built a new coffee culture. Blue Buffalo did not invent pet food. It reshaped how some consumers understood care and identity through pet ownership. Libraries face a similar task. The challenge is not simply to offer better services or smarter tools. It is to influence what counts as good research, what ethical engagement with AI looks like, and who gets to be seen as a legitimate contributor to academic conversations. Those shifts only take root when people can practice them in context.

This is where James Q. Wilson and Rosabeth Moss Kanter become especially useful. Wilson taught us to look for niches, those small spaces inside bureaucracies where experimentation can survive long enough to develop into a new norm. Kanter showed how innovation is often carried by people in the middle: librarians, supervisors, program leads, and project managers who define projects, build coalitions, protect experiments, and keep momentum alive. Put together, their work suggests something libraries know instinctively but do not always name: innovation is rarely imposed from the top and rarely delivered by a product alone. It is grown in the middle, in protected pockets, by people who persuade rather than command.

Imagine one small example. A librarian notices that students are treating AI as a shortcut rather than a subject for critique. Instead of launching a campus-wide initiative, the librarian begins with one faculty ally and one composition section. Students compare an AI-generated summary with a human revision and write a short reflection on omissions, authority, and bias. The team meets regularly, gathers reflections, and refines the activity as they go.

The pilot is modest. It is framed as practice, not policy. It is small enough to protect and flexible enough to revise. But that is exactly why it matters. The experiment creates a new story the institution can repeat: in this class, AI is not simply a threat or a shortcut. It is something students can examine critically as part of scholarly life. That story begins to travel. Faculty grow curious. Students use different language. Slowly, the meaning of “using AI” starts to shift from crutch or crisis to one skill among many in academic work. That is what cultural innovation looks like: small, visible, repeatable, and capable of changing meaning over time.

Design-based research strengthens these pockets of innovation by turning practice into evidence. Rather than treating a pilot as a one-off success story, design-based research places an intervention in a real setting, studies it in context, gathers both qualitative and quantitative evidence, and refines the work through iteration. In library settings, that might include short surveys, student reflections, staff observations, assignment revisions, or notes on how participants describe their own learning. This kind of documentation matters because it makes the work more than anecdotal. It makes it learnable, shareable, and adaptable.

Still, even the strongest pilot needs protection. Promising ideas often fail not because they lack value, but because they are overexposed to institutional process too early. A small experiment can easily be buried under demands for immediate scale, formal approval, or universal buy-in. That is where leadership in the middle matters most. Library leaders and middle managers can presell the idea quietly, find the right faculty partner, manage expectations, secure modest support, and shield emerging work until it has enough strength to stand on its own. They can also make sure the people doing the work receive visible credit. Students, adjuncts, staff, and collaborators should be recognized publicly so that experimentation becomes associated with learning and leadership rather than risk and extra labor.

The larger point is simple: libraries do not need more benches in the plaza. They need more places where people can gather, experiment, reflect, and reshape meaning together. A tool can support that work, but it cannot substitute for it.

Seven ways libraries can make innovation stick

If libraries want innovation to last, they need to stop treating change as a product rollout and start treating it as a cultural practice. That means creating conditions where people can experiment, reflect, and learn together. These seven strategies can help.

1. Start with one small, protected pilot
Do not begin with a campus-wide initiative. Start with one class, one service point, one workflow, or one partnership. Small pilots are easier to adapt, easier to assess, and easier to protect while the work is still taking shape.

2. Build with people, not for them
Innovation sticks when the people affected by it help shape it. Bring faculty, students, staff, and collaborators into the design of the experiment early. Shared ownership builds trust and helps the work reflect local needs rather than abstract priorities.

3. Frame the work as practice, not policy
People are far more willing to try something new when it is presented as a limited experiment rather than an institutional mandate. Framing a pilot as practice gives participants room to test, reflect, and revise without the pressure of immediate institutionalization.

4. Treat every pilot as a form of research
Use a design-based research mindset. Gather reflections, short surveys, observations, and examples of changed behavior. A pilot should not only create enthusiasm. It should also produce evidence that others can learn from and adapt.

5. Protect the experiment from premature bureaucracy
Strong ideas often get smothered by too much process too soon. Library leaders and middle managers can help by quietly building support, managing expectations, and shielding the work from unnecessary procedural weight in its earliest stages.

6. Reward the people doing the work
Give visible credit to students, adjuncts, staff, and partners. Recognition matters because it signals what the organization values. If experimentation is invisible, people learn to avoid it. If it is recognized, others are more likely to participate.

7. Tell the story as a change in meaning
When sharing results, do not focus only on tool adoption or service launch. Explain how the work changed the way people think, learn, collaborate, or participate. That is the real marker of cultural innovation.

How do you know this kind of change is happening? Usually not from a dashboard alone. You see it in the stories people begin to tell. Faculty ask if they can try something similar. Students describe their work differently. Colleagues begin to talk less about products and more about inquiry, ethics, collaboration, and participation. Behavior shifts, but so does language. That is often the clearest sign that meaning has started to move.

Buying a tool is like placing a new bench in the plaza. It may be useful. It may even be attractive. But it does not, by itself, create street life. Cultural innovation is closer to building a small bazaar of practice: a place where people gather, exchange ideas, test possibilities, and develop new rituals together. A bench stays still. A bazaar changes how people inhabit the space.

That is the work in libraries. Start with one small experiment. Protect it. Study it. Share the story not as a technical win, but as a shift in meaning. Over time, those pockets of culture can do far more than any shiny new tool alone. They can change how people learn, how they work, and how they understand their place in academic life.

Further reading

Douglas Holt, How Brands Become Icons (2004)
A foundational text on cultural branding and the way meaning and identity shape value.

James Q. Wilson, Bureaucracy (1989)
Useful for thinking about niches and the small protected spaces where experimentation can take root.

Rosabeth Moss Kanter, “The Middle Manager as Innovator,” Harvard Business Review (2004)
A practical piece on how people in the middle build coalitions, define projects, and move innovation through organizations.

Clayton M. Christensen, The Innovator’s Dilemma (1997)
Helpful as a contrast, particularly for readers thinking about disruption from a more traditional innovation perspective.

Design-Based Research Collective, “Design-Based Research: An Emerging Paradigm for Educational Inquiry” (2003)
A strong starting point for readers interested in turning local experimentation into evidence-based institutional learning.

Peter Senge, The Fifth Discipline (1990)
Useful for thinking about how learning organizations support lasting cultural change.

Rosabeth Moss Kanter, The Change Masters (1983)
A deeper exploration of how managers in the middle can support systemic change over time.