Gaffer Tape and First Drafts: The HCI 2009 Demonstration Floor as Primary Source
Photo: retro computer prototype demonstration conference table cables 2000s, via i.pinimg.com
Conference archives tend to privilege the settled artefact. The paper is bound, the talk is timetabled, the proceedings are indexed. The demonstration, by contrast, arrives with cables, apologies and a warning that the wireless may not hold. At HCI 2009 in Cambridge, the demonstration sessions ran alongside the formal programme, and the archive’s surviving demo material still carries a different kind of evidence: not what the authors concluded, but what they could hold together in public.
A parallel programme with exposed seams
The demonstration abstract is a peculiar genre. It is part claim, part instruction manual and part confession. It must explain what the system does, what the visitor should do, what table space is required and what might go wrong. Formal papers can smooth the labour of design into a narrative of method and finding. A demo cannot. The borrowed laptop, the external monitor, the printed label and the roll of gaffer tape are all part of the argument, whether the authors intended them to be or not.
Read in sequence, the HCI 2009 demonstration entries show a field working in public. Some prototypes were clearly near completion; others were sketches made tangible for the purposes of conversation. That mixture is not a defect in the archival record. It is the record. The demo room was where the UK interaction design community tested not only systems but also the claims that surrounded them. A paper can describe a system as if it arrived complete. A demonstration has to survive being handled.
The material record of improvisation
The archive’s demo material should be read as material evidence. Equipment lists, photographs of table layouts and the short descriptions of interaction sequences reveal the conditions under which research was made. A prototype that required a laptop underneath the table is not an embarrassment; it is a datum. It tells us about budgets, lab equipment, wireless reliability and the craft of making an idea legible to a passing visitor.
This is where the demonstration floor differs from the poster floor. Posters invite reading; demos invite touching, leaning, pointing and occasionally breaking. The visitor becomes a tester, a critic and a collaborator in quick succession. In 2009, before rapid prototyping became a routine phrase in UK UX practice, the demo room was already a workshop with an audience. Its habits were improvisational: borrow, adapt, label, explain, observe. Those habits are part of the intellectual history of research through design, even when they never appear in a formal acknowledgements section.
From the demo table to rapid prototyping
By 2026, prototyping has become institutionalised. Design sprints, hack labs, Arduino and Raspberry Pi kits, 3D printing and AI-assisted code generation have lowered some barriers and raised others. The tools are different, but the demo-room virtues remain recognisable: material honesty, public testing and a tolerance for the unfinished. UK researchers now speak readily of provotypes, boundary objects and research-through-design. In 2009, those terms circulated unevenly, and much of the work was done through demonstration rather than declaration.
The comparison is not a story of simple progress. Rapid prototyping can produce polished artefacts that conceal their assumptions as effectively as any conference paper. The 2009 demo floor offers a corrective. It shows that the most useful prototype is often the one that admits its dependencies: the sensor that drifts, the screen that flickers, the script that needs a demonstrator to stand in the right place. Such admissions are not failures of rigour. They are evidence of the relationship between an idea and its materials.
What the archive should do with a demo
If demonstrations are to have equal archival status, they need equal description. Demo abstracts should be catalogued alongside papers, with metadata for hardware, software, room layout, power requirements and known failure modes. Oral histories from demonstrators would add what photographs cannot: the visitor question that changed the next iteration, the component borrowed from another lab, the moment when a prototype stopped being a diagram and became a shared object of concern.
This is not an argument for treating every demo as a masterpiece. Many were modest, and some were probably forgettable. But the archive should not confuse modesty with insignificance. The paper says what authors think; the demo shows what they can hold together. For historians of UK technology and for UX researchers in 2026, that difference matters. The demonstration floor was not the fringe of HCI 2009. It was one of the places where the conference actually thought.
