Making It Work Is the Work: Engineering Maturity as Epistemic Work
Abstract
Many HCI$\times$fabrication systems are compelling as prototypes but remain difficult to reuse, extend, or transfer beyond their original publication. A common explanation is that adoption simply takes time. We argue that the issue is more fundamental. The knowledge needed to make fabrication systems transferable, namely how they behave across different materials, machines, and users, usually does not exist at the time of publication because the work required to generate this knowledge is rarely incentivized or rewarded. Drawing on engineering epistemology and prior debates in systems-oriented HCI, we reframe engineering maturity as epistemic work: sustained engineering effort that produces knowledge which prototyping alone cannot reveal. We propose six dimensions, Fab-ilities, as a vocabulary to describe what aspects of fabrication artifacts have become established and what knowledge remains tacit: (1) buildability, (2) executability, (3) reliability, (4) maintainability, (5) transferability, and (6) scalability. We describe five of our own projects (JigFab, StoryStick++, Silicone Devices, LamiFold, and PaperPulse), where varied attempts at dissemination, such as commercialization, spin-offs, and market exploration, each exposed different gaps between what we published and what transfer actually required.
CCS Concepts
- Human-centered computing~Human computer interaction (HCI)
1 Introduction
HCI $\times$ fabrication research has become particularly good at producing compelling prototypes. We build novel tools, demonstrate new interaction techniques with physical matter, and validate them through scenarios or user studies. Yet many of these systems remain difficult to reuse, extend, or transfer beyond the original scientific contributions. This reflects a mismatch between what our community primarily values and rewards and what fabrication systems require to operate outside the lab. We argue that we need a more nuanced way to value "making it work" as part of scholarship. In todayâs publication culture, characteristics of good engineering work: reliability, reproducibility, maintainability, scalability, manufacturability, documentation, are structurally disincentivized. These characteristics are often treated as implementation details, secondary to the contribution and its evaluation. As a result, engineering characteristics, though essential for the real-world utility and potential producability of the result, are often not prioritized and dismissed during research. In fabrication research, engineering decisions are not merely implementation details. They often generate the knowledge needed to build, operate, and adapt the system beyond the initial prototype.
The sustained work of making a system function reliably produces knowledge that others need to build, run, and adapt it. This includes genuinely novel knowledge about transferability, reliability, and economic viability, but it typically emerges only through sustained practice that pushes systems beyond their first demonstration. This realization points to a structural problem. If we want systemic change in how HCI$\times$fabrication research contributes beyond publication, we must look inward and be critical about how we evaluate our papers. HCI has strong traditions of valuing concepts over execution [1]. In many HCI venues, a novel idea demonstrated through a prototype, supported by a scenario and a focused study, is treated as sufficient. But if fabrication research aims for broader useâwhether through replication, extension, pedagogy, partnerships, or other forms of uptakeâthen the engineering work that makes systems reproducible, reliable, and legible to others cannot remain an afterthought.
We argue that engineering maturity should be valued as epistemic work, alongside conceptual contributions. The community needs to better recognize and reward the work required toward real-world adoption, treating these engineering challenges as legitimate research outcomes. This would move the field closer to producing systems that can survive outside the lab. We makes three contributions in this paper:
- (1)We reframe engineering maturity in HCIĂfabrication as epistemic work, grounded in engineering epistemology and prior debates in systems-oriented HCI.
- (2)We propose a six-dimensional vocabulary "Fab-ilities", for describing the maturity of fabrication artifacts: buildability, executability, reliability, maintainability, transferability, and scalability.
- (3)We reflect on five fabrication projects to illustrate recurring gaps between systems that can be published at a scientific venue, and systems that can be transferred to practice.
2 Engineering Maturity as Epistemic Work
Concerns that HCI ideas often fail to move beyond the laboratory are longstanding. One common interpretation is that such systems are simply premature. Buxtonâs Long Nose of Innovation describes how influential ideas may take decades before reaching widespread adoption, suggesting that the path from invention to impact is inherently long [2]. However, the Long Nose perspective assumes that the knowledge required for adoption already exists and only awaits the right timing or market conditions. In practice, much of the knowledge required for transfer, such as how systems behave across materials, environments, infrastructures, and user groups, does not yet exist at the time of publication. This knowledge often emerges only through sustained engineering, deployment, and iteration beyond the initial research prototype.â In HCI$\times$fabrication, the knowledge required to make a system transferable (how it behaves across materials, machines, and users) typically does not yet exist at publication time, because the work that would generate it was never incentivized. When this work is treated as mere implementation, the knowledge it produces remains tacit. As a result, it becomes harder for the community to verify claims, compare approaches, and build cumulative knowledge.
The philosophy of engineering has long recognized that engineering practice is itself a form of knowledge generation. Vincenti showed that engineering knowledge is not simply applied science [3]: it includes practical knowledge from building and testing, functional knowledge about how components behave, and knowledge about what it takes to make systems work reliably. This knowledge emerges from confronting what doesnât work: from understanding constraints through building against them. HCI has grappled with related questions: technical HCI has argued that systems cannot be evaluated solely through usability studies [4], and that system qualities such as flexibility, expressive leverage, and scalability should be considered evaluation criteria [5]. Community voices have articulated how review practices can discourage the submission of systems work [6], and Greenberg and Buxton caution that premature usability evaluation can harm early-stage innovations [7]. Together, these research lines motivate a reframing. In fabrication research, engineering maturity is not a postscript to the real contribution. It is often an essential part of the contribution. We therefore propose treating engineering maturity as a legitimate research outcome. It is the knowledge that enables others to build, run, and transfer a system. We treat engineering maturity as epemistic work that produces new knowledge. It is systematic engineering that creates transferable know how about how and why a system works, how it fails, and how others can adapt it. This work turns hidden lessons into shared evidence, so others can check claims, compare systems fairly, and build on prior results, instead of treating the effort as a secondary implementation detail.
2.1 Dimensions of Engineering Maturity
To make engineering maturity actionable, we introduce a set of Fab-ilities as a starting vocabulary for describing maturity in fabrication systems. Specifically, we sketch six dimensions (Table 1) that capture what a contribution makes buildable, runnable, and transferable beyond the original lab setting. This framing is inspired by a prior workshop focusing on an Interaction Engineering Glossary and a Repository for interactive software "Fab-ilities" [8], which aimed to elicit reference properties for assessing the quality of engineered HCI products. Our Fab-ilities are not a checklist or a compliance target. They are descriptors for articulating what kind of maturity a contribution achieves, what remains unresolved, and what that maturity enables for others. We do not claim these dimensions are exhaustive or final. We offer them to make maturity discussable and reviewable, and to prompt a broader conversation about what fabrication research in HCI should value beyond novelty.
| Dimension | Definition and typical evidence |
|---|---|
| Buildability | Others can reconstruct the artifact: bill of materials, fabrication files, tolerances, assembly instructions, and notes on substitutable parts or fragile dependencies. |
| Executability | Others can operate the system without heroic effort: installation instructions, dependencies, calibration procedures, and a ``known good'' pipeline or test case. |
| Reliability | Behavior is characterized under variability: documented failure modes, sensitivity to materials and environment, and mitigation strategies. |
| Maintainability | The artifact can survive time: modular structure, versioning, documented assumptions, and clear limitations that prevent misinterpretation. |
| Transferability | Guidance exists to adapt the system: what must remain fixed vs.\ what can change; porting notes across machines, materials, and workflows. |
| Scalability | Cost structure & manufacturing complexity are characterized: bill of materials with pricing, and identification of cost-sensitive components affecting viability at different scales. |
Buildability asks whether others can physically reconstruct the artifact. Materials vary between suppliers and regions; components get discontinued within months of publication. The open-source hardware community has developed practices to address this [9]. Buildability requires identifying which specifications are critical, which components can be substituted, and which assembly sequences contain implicit constraints that only surface when someone else attempts reconstruction.
Executability asks: can someone who did not build the system actually operate it? A system may be reconstructable yet still require its original creators, because calibration is undocumented, error recovery depends on tacit knowledge, or the workflow assumes internalized expertise. This spans software (environment setup, dependency conflicts, implicit build assumptions) and physical operation (material placement, focus adjustment, speed/power tuning). The two interact: fabrication systems involve software controlling hardware, and failures can occur anywhere in that chain.
Reliability concerns behavior under real-world variability, for example: humidity affects adhesion, temperature influences curing, tool wear accumulates. Characterizing what fails first under what conditions requires sustained observation exceeding typical paper timelines. Recent work on FEDT [10] highlights that such characterization experiments are performed inconsistently, tools that support systematic experimental design offer one path forward.
Maintainability asks whether the system can be maintained without its original authors. Software engineering treats maintainability as first-class [11]; fabrication research does not. Yet physical systems face additional challenges: components wear out, materials degrade, and suppliers discontinue parts. A system that cannot be maintained becomes frozen at publication and is unable to evolve or adapt when dependencies change.
Transferability asks whether the system can travel to new contextsâdifferent machines, materials, or usersâand what must remain fixed. This is distinct from robustness: a system may be robust locally yet fail completely elsewhere. Replication studies show how contextual factors invisible to authors determine success in new settings [12]. Answering transferability questions requires systematic experimentation with variations.
Scalability confronts economic realities that prototypes leave unexamined. What does it cost to build ten versus a hundred? Research prototypes use components chosen for convenienceâhand-soldered connections, expensive development boards, specialty materialsâobscuring whether the contribution could ever leave the lab. Understanding which cost drivers dominate at volume, which steps need automation, and which choices trade convenience against viability is itself valuable knowledge.
3 Lessons from Disseminating HCI$\times$Fabrication Systems
We pursued multiple dissemination pathways for our fabrication research projects. In each case, we found gaps between what we had published and what was needed to move to the next stage. All projects listed below produced functional prototypes that were used beyond the specific demonstrations reported in their publications.
3.1 Cases of valorisation attempts
JigFab [13] (Figure 1) was developed in close collaboration with Fablab Genk, an open access makerspace run by one of the authors. We worked with woodworkers, hobbyists, and engineering students who use the lab daily. The system helps users design and fabricate custom woodworking jigs using digital fabrication tools. When we pursued commercialization, we filed a patent application and engaged an external marketing agency to identify potential industrial markets, but we found little traction. Prospective commercial users wanted a more mature system. They asked for clearer failure modes, stronger documentation, and behavior that remained reliable across different machines, materials, and workflows. In addition, the project involved multiple universities, which made intellectual property valorization more complex. Shared ownership introduced additional coordination, legal constraints, and procedural barriers that effectively raised the threshold for moving from a research prototype to a commercial product.
StoryStick++[14] (Figure 2) is a phone clip on that guides measuring and marking with minimal reliance on numbers, units, or mental arithmetic. This reduces common errors. StoryStick++ is currently in market research. We repeatedly see the same pattern. Companies understand what the system does, but they struggle to imagine a finished product based on the bare bones prototype we can provide. The gap is therefore not conceptual. The gap is practical and economic. The knowledge needed to build, run, and adapt the system to their context is not written down and remains in the heads of the developers. As a result, basic questions about cost structure, manufacturing complexity, and market viability remain unanswered.
Silicone Devices[15] (Figure 3) presents a DIY workflow that uses a CO2 laser cutter to fabricate stretchable electronic devices in cast silicone with embedded liquid metal traces, computation, and sensors. To support replication, we published a step by step tutorial as an Instructable [16]. In practice, the workflow requires careful execution, so workshops at our university and at the University of Chicago were facilitated by one of the authors. The project also received national valorization funding to attempt to set up a spin-off company on stretcheable electronics. We received funding for a two year trajectory to translate the technique into an industrial process. During that trajectory, the focus shifted from the original HCI goal of democratizing fabrication toward industrial applications, where it faced strong competition from established manufacturing techniques. The track ended when the lead researcher moved into a different role. The work, however, continues to inform research in both materials science and HCI.
PaperPulse [17, 18] (Figure 4) enabled non-experts to produce interactive paper devices using printed conductive traces. We explored commercialization together with a professional partner and investigated patenting options, including prior-art checks with an external intellectual property firm. However, the upfront costs and the uncertainty about a viable market path made it difficult to justify continuing the trajectory. The core novelty of PaperPulse aligns naturally with consumer oriented (B2C) markets, which are particularly difficult to sustain in Europe. This experience exposed a broader lesson. Many HCI system contributions are designed around specific user groups and contexts of use. When they are repositioned for different domains, such as expert, education or industrial users, the original contribution often loses relevance. This contrasts with general purpose techniques in materials science, in this case printed electronics, that tend to transfer more easily across application areas.
LamiFold [19] (Figure 5) exposed a different facet of the maturity gap, namely reproducibility. LamiFoldâs lamination workflow selectively cuts and glues stacks of sheet material to embed functional mechanisms. In practice, the process is highly sensitive to machine and material parameters. Laser power, cutting speed, kerf width, and material thickness interact in ways that are hard to describe in general terms. Calibration settings that yield reliable results on one laser cutter often fail on another. As a result, the knowledge required to make LamiFold work reliably across different setups remained largely undocumented and stayed tied to hands on experience rather than transferable instructions.
3.2 Barriers to Uptake Beyond Publication
One pathway has worked consistently. Our projects have repeatedly influenced the classes we teach on designing and building interactive systems, as well as fabrication and prototyping, so the research spreads through education. The systems are complex, broad in scope, and deep in technical detail, which makes them difficult to master and therefore well suited as training material for students. However, that same complexity is also a barrier to use outside the lab. What is acceptable as open ended exploration in research and education becomes hard to operationalize in practice, where users expect stable behavior, clear procedures, and predictable costs.
When we pursued other pathways such as commercialization, licensing, spin offs, and other types of market adoption, we encountered various barriers that prevented uptake. The reasons differed across projects, but the pattern was similar. Reliability was not characterized, operational know-how remained undocumented, cost-benefit models were missing, designs were tightly bound to a specific (lab) context and did not transfer well to real life usage, and the documentation needed for others to continue the work was often absent.
4 Conclusion
HCI$\times$fabrication has developed a comfortable hypocrisy. We regret that our prototypes do not reach the real world, yet we systematically devalue the very work that would make them travel. We publish the demo and call it done. We move on to the next novelty, only to wonder why nothing sticks. The engineering work we dismiss as "mere implementation" is not overhead â it is where much of the knowledge lives. What breaks, what varies, what costs, what transfers. This is precisely what we and others need to build on or disseminate our contributions. We argue that engineering maturity is epistemic work, not implementation overhead.
We proposed six Fab-ilities dimensions: buildability, executability, reliability, maintainability, transferability, and scalability. The Fab-ilities serve as a vocabulary for articulating what fabrication artifacts have consolidated and what remains tacit. We included five illustrative projects that show a consistent pattern. Once we moved beyond publication and tried to translate the work into sustained use, we encountered barriers that the paper contributions had not resolved. If we are serious about real-world impact, and not only about stating that we value it, then the field must change what it rewards. Engineering maturity is epistemic, knowledge-producing work. It is time we evaluate and credit it as such.
Acknowledgements
We would like to thank Mieke Haesen and the Tech Transfer Office of UHasselt for their continuous support. We also gratefully acknowledge the Industrial Research Fund (IOF) of UHasselt for funding and supporting several valorization trajectories related to this work, and for helping to explore pathways toward societal and economic impact. This work was partially supported by Flanders Make, the strategic research center for the manufacturing industry in Flanders. Kris Luyten is supported by the Flemish Government under the âOnderzoeksprogramma ArtificiĂ«le Intelligentie (AI) Vlaanderenâ program, R-13509.
References
- Jacob O. Wobbrock and Julie A. Kientz. 2016. Research contributions in human-computer interaction. Interactions 23, 3 (2016), 38â44. https://doi.org/10.1145/2907069
- Bill Buxton. 2008. The Long Nose of Innovation. Accessed: 2025-01-15.
- W.G. Vincenti. 1990. What Engineers Know and How They Know It: Analytical Studies from Aeronautical History. Johns Hopkins University Press. https://books.google.be/books?id=5XNTAAAAMAAJ
- David Ledo, Steven Houben, Jo Vermeulen, Nicolai Marquardt, Lora Oehlberg, and Saul Greenberg. 2018. Evaluation Strategies for HCI Toolkit Research. In Proceedings of the 2018 CHI Conference on Human Factors in Computing Systems. Association for Computing Machinery, New York, NY, USA, 1â17. https://doi.org/10.1145/3173574.3173610
- Dan R. Olsen. 2007. Evaluating user interface systems research. In Proceedings of the 20th Annual ACM Symposium on User Interface Software and Technology. Association for Computing Machinery, New York, NY, USA, 251â258. https://doi.org/10.1145/1294211.1294256
- Jofish Kaye. 2009. I Give Up on CHI/UIST. Accessed: 2025-01-15.
- Saul Greenberg and Bill Buxton. 2008. Usability evaluation considered harmful (some of the time). In Proceedings of the SIGCHI Conference on Human Factors in Computing Systems. Association for Computing Machinery, New York, NY, USA, 111â120. https://doi.org/10.1145/1357054.1357074
- Stéphane Chatty, Emmanuel Dubois, Laurence Nigay, and Jean Vanderdonckt. 2015. Towards an Interaction Engineering Glossary and a Repository for Interactive Software "-ilities".
- Open Source Hardware Association. 2012. Open Source Hardware (OSHW) Definition 1.0. Accessed: 2025-01-15.
- Valkyrie Savage, Harrison Goldstein, N\âora PĂŒsök, Jia Yi Ren, Bhaskar Dutt, Chandrakana Nandi, and Lora Oehlberg. 2025. FEDT: Supporting experiment design and execution in HCI fabrication research. In Proceedings of the 38th Annual ACM Symposium on User Interface Software and Technology. Association for Computing Machinery, New York, NY, USA, https://doi.org/10.1145/3746059.3747739
- Martin Fowler. 1999. Refactoring: Improving the Design of Existing Code. Addison-Wesley, Boston, MA, USA.
- Max L. Wilson, Ed H. Chi, Stuart Reeves, and David Coyle. 2014. RepliCHI: the workshop II. In CHI â14 Extended Abstracts on Human Factors in Computing Systems. Association for Computing Machinery, New York, NY, USA, 33â36. https://doi.org/10.1145/2559206.2559233
- Danny Leen, Tom Veuskens, Kris Luyten, and Raf Ramakers. 2019. JigFab: Computational Fabrication of Constraints to Facilitate Woodworking with Power Tools. In Proceedings of the 2019 CHI Conference on Human Factors in Computing Systems. Association for Computing Machinery, New York, NY, USA, 1â12. https://doi.org/10.1145/3290605.3300386
- Stig Konings, Maties Claesen, Danny Leen, Mannu Lambrichts, Xander Vaes, and Raf Ramakers. 2026. StoryStick++. In Proceedings of the 2026 CHI Conference on Human Factors in Computing Systems. ACM,
- Steven Nagels, Raf Ramakers, Kris Luyten, and Wim Deferme. 2018. Silicone Devices: A Scalable DIY Approach for Fabricating Self-Contained Multi-Layered Soft Circuits using Microfluidics. In Proceedings of the 2018 CHI Conference on Human Factors in Computing Systems. Association for Computing Machinery, New York, NY, USA, 1â13. https://doi.org/10.1145/3173574.3173762
- Instructables. Silicone Devices. https://www.instructables.com/Silicone-Devices/
- Raf Ramakers, Kashyap Todi, and Kris Luyten. 2015. PaperPulse: An Integrated Approach for Embedding Electronics in Paper Designs. In Proceedings of the 33rd Annual ACM Conference on Human Factors in Computing Systems. Association for Computing Machinery, New York, NY, USA, 2457â2466. https://doi.org/10.1145/2702123.2702487
- Raf Ramakers, Kashyap Todi, and Kris Luyten. 2015. PaperPulse: An integrated approach for embedding electronics in paper designs. In Special interest group on computer graphics and interactive techniques conference, SIGGRAPH â15, los angeles, CA, USA, august 9-13, 2015, studio. ACM, 3:1. https://doi.org/10.1145/2785585.2792694
- Danny Leen, Nadya Peek, and Raf Ramakers. 2020. LamiFold: Fabricating Objects with Integrated Mechanisms Using a Laser cutter Lamination Workflow. In Proceedings of the 33rd Annual ACM Symposium on User Interface Software and Technology. Association for Computing Machinery, New York, NY, USA, 304â316. https://doi.org/10.1145/3379337.3415885