A couple of days ago, I attended the introduction workshop for new AI centres in Norway to present MishMash and discuss potential collaboration opportunities with the other centres. As expected, the different centres are much more focused on creating software solutions that can be used in the industry than us. We will also explore various use cases in MishMash, but we take a much more creative and exploratory approach.
As part of the discussions, the Technology Readiness Level (TRL) was mentioned. I have been briefly introduced to this concept in some other contexts, including some innovation projects we have been involved in. However, I have never taken the time to understand what it actually means. Hence, this blog post is to inform myself (and others).
What is TRL?
Technology Readiness Level (TRL) is a framework used to assess the maturity of technology development systematically. Initially developed by NASA in the 1970s, TRL has become a standard measurement tool across industries, government agencies, and research institutions worldwide. It uses a nine-point scale that tracks technology development from basic research through successful deployment. Each level represents a significant milestone in the technology’s journey from concept to real-world application. There are nine TRL levels:
TRL 1-3: Basic Research
- TRL 1: Basic principles observed and reported
- TRL 2: Technology concept formulated
- TRL 3: Experimental proof of concept
TRL 4-6: Technology Development
- TRL 4: Technology validated in laboratory
- TRL 5: Technology validated in relevant environment
- TRL 6: Technology demonstrated in a relevant environment
TRL 7-9: System Development
- TRL 7: System prototype demonstration in operational environment
- TRL 8: System complete and qualified
- TRL 9: Actual system proven in operational environment
How is TRL used?
TRL was initially designed for the aerospace and defence sector, but is now widely used in various commercial sectors. The idea is that TRL helps organisations make informed decisions about technology investments and development timelines, leading to more successful innovation outcomes.
In my experience, TRL is not used much in academic research. It is mostly those working on innovations aimed at commercialization who use it. Then it helps researchers communicate the maturity of their work to funding agencies, collaborators, and industry partners.
In my work, I primarily focus on basic research, but I also develop new hardware and software systems as part of the process. These systems typically start as prototypes—experimental implementations that demonstrate core concepts. Occasionally, some of these prototypes evolve further and mature into research products that are stable enough to be used by others in the academic community (like the Musical Gestures Toolbox). I have been involved in some development processes that have aimed for higher TRL levels, but I generally prefer to come back to prototyping instead of developing mature products.
TRL in artistic research
I have never seen TRL used in artistic research, but I think it can help explore how well a system functions. Artistic research often involves exploratory, iterative, and creative processes that do not always follow linear development paths typical in engineering or commercial innovation. However, TRL can still provide a valuable lens for assessing the maturity of technologies or tools developed within artistic projects.
For example, early-stage artistic research may correspond to TRL 1–3, where new concepts, methods, or prototypes are explored and tested in experimental settings. As these ideas are refined and validated—perhaps through performances, exhibitions, or collaborative workshops—they may progress to TRL 4–6, demonstrating functionality and reliability in relevant artistic environments. In some cases, artistic tools or systems reach TRL 7–9, becoming robust enough for widespread adoption by other artists or integration into professional creative workflows.
Way forward
Given that we will be collaborating with people from diverse backgrounds in MishMash, it makes sense to establish some common guidelines for discussing our outputs. After some reflection, I believe the TRL framework and its levels can serve as a useful system for describing the maturity of the technologies and systems we develop. Our projects will likely span the entire TRL spectrum: some researchers may focus on exploring fundamental principles and building early prototypes, while others may work towards solutions ready for deployment in classrooms, hospitals, or museums. By adopting TRL as a shared reference, we can better communicate the status and goals of our work, ensuring clarity and alignment across the team.
This text was co-written with Claude Sonnet 4 and I have used Grammarly Pro for grammar checking.