When I saw Cooper Hewitt present its new interactive Pen at Museums and the Web in 2015, I had recently come through the complexity of developing a much smaller museum interactive myself. The scale of what Cooper Hewitt had attempted was startling. These were my notes from that presentation, revisited now as a case study in what happens when an interactive device becomes an institutional system.

Cooper Hewitt reopened its renovated Carnegie Mansion in December 2014 with a new digital platform connecting collections, galleries and visitor systems. The Pen launched in early 2015 as the most visible part of that environment: visitors could save objects by touching NFC-enabled labels, draw and create on interactive tables, and later retrieve what they had collected through a unique web address printed on their ticket.

The Pen was not really a Pen project

What became clear in the presentation was that the Pen touched almost every part of the museum. Object labels needed current location data and NFC tags. Ticketing had to communicate with the museum’s API so every visit could receive a unique identifier. Pens had to be paired, distributed, returned, cleaned and maintained. Interactive tables had to receive collections from the device. The website had to preserve the visit afterward. A handheld object that looked simple to the visitor depended on a large chain of collections data, software, physical infrastructure and human workflows.

That is why one of the most important statements in my original notes was: “This is not just a tech project—it affects everything the museum does.”

Prototype before polish

The team described a long development process involving multiple versions of the Pen, working electronic prototypes, industrial design, manufacturing constraints, radio-frequency problems, power and networking limitations, software development, and repeated testing. The line I wrote down in bold was their advice for building institutional momentum: build “the dumbest, dirtiest prototypes ever.” The point was not aesthetic. Cheap, imperfect prototypes made ideas tangible enough for people across the institution to react to them before too much money, prestige or technical complexity hardened the design.

The published design history reinforces that approach. Cooper Hewitt created storyboards and videos of anticipated interactions, produced 3D prototypes, built working electronic versions and tested practical scenarios ranging from collecting objects to returning the Pen and changing its battery. The team was trying to test not only whether the object worked, but whether the surrounding experience worked.

The visible object depended on invisible capacity

My conference notes repeatedly return to capacity: bring technology knowledge inside the institution; build the collections website and API; avoid one-off digital spectacles; share code; hire people; sustain the sector; and do not overdesign for the platforms of the present.

That last point feels especially durable. Social platforms were changing quickly even in 2015. Cooper Hewitt made sharing possible through ordinary web URLs rather than binding the visitor experience too tightly to any one social network. The technology was ambitious, but the larger architecture was built around museum-controlled collections data and web infrastructure.

What happened

The system saw substantial use. Five weeks after launch, Cooper Hewitt reported more than 400,000 acts of collection with the Pen and described post-visit logins as strong. By 2019, the museum reported that an average of about 21 percent of Pen users had logged in after their visit to review what they collected, with a high near 30 percent. The Pen remained in use from 2015 to 2020.

But success also made the system harder to change. By 2019, Cooper Hewitt described the Pen and its underlying systems as so pervasive that evolving individual parts of the visitor experience had become difficult. As the technology approached the end of its life, the museum created an Interaction Lab to step back and rethink questions of scale, dependence and sustainability rather than immediately replace the Pen with another large system.

What I see differently now

In 2015, the Pen itself was what blew my mind. Looking back, the more important achievement was the capability that had to exist around it. The object visitors held was only the interface to a network of collection systems, APIs, ticketing, gallery infrastructure, manufacturing, maintenance, staff practices and post-visit web access. The Pen eventually ended. The institutional lesson was that ambitious digital experiences become durable only when the organization can support the system behind the visible technology.

That is why another line from my notes now reads differently: “Before this we had nothing; now we have something and we’ll figure the rest out later.” It sounds casual, but it describes a useful posture toward institutional experimentation. Build enough real infrastructure to learn from. Then keep learning.

Cooper Hewitt continues to preserve extensive documentation of the project, including Designing the Pen, technical documentation of how the Pen interacted with the museum API, and the museum’s broader record of the interactive visitor experience.