Tag: Human-Computer Interaction

New Paper on Why HRI Needs a Post-growth Perspective

Beyond ‘Green Growth’: Why HRI Needs a Post-Growth Perspective

The field of Human-Robot Interaction (HRI) is at a crossroad. As we design more sophisticated robots for healthcare, education, and the home, we are forced to reckon with that our technological progress is deeply intertwined with an economic model that demands perpetual growth—often at a steep cost to our planet.

In our new paper, ‘Post-growth Perspectives in HRI’, recently presented at HRI ’26 in Edinburgh, my co-authors (Mafalda Gamboa, Ilaria Torre, and Birgit Penzenstadler) and I argue that it’s time to look beyond the ‘green growth’ narrative.

The Problem with ‘Business as Usual’

Climate research has pointed out that economic growth is the root cause of environmental devastation, and the most prevalent ‘rescue narrative’ is that productivity growth will recover through new technological breakthroughs. But, this narrative rarely account for the limits to the planetary resources.

Almost all improvements in user interactions increase energy and resource consumption. The carbon emissions from training Large-Language Models is one example, and emissions from sensors and components are also mainly caused by energy consumption. All parts, both software and hardware, of the robots the HRI community are building and buying are, therefore, (somewhat) harmful to our planet. 

In parallel, we are seeing a growing graveyard of social robots, where many of the robot platforms that the field has relied on are going bankrupt due to not being able to expand and grow beyond academic buyers. We argue that HRI cannot solely rely on the unstable market of social robots and the market mechanisms that the field is deeply tied to, such as software-as-a-service and robot-as-a-service, which by many large companies is often driven by robotwashing. To tackle this, we point to self-built and low-scale robots, even though they are not exempt from the material dependencies of the broader growth paradigm. 

Introducing Post-growth for HRI

Our paper introduces a post-growth perspective to HRI, by inviting the community to shift the focus from quantitative growth to qualitative development. We reuse the metaphor of the snail (broadly used by the degrowth and slow movements) and add a new ring on the snail’s shell—a layer of automation, artificial intelligence, and robotics, built upon already complex structures. While intended to enhance efficiency and productivity, this continual layering risks creating fragility, dependence, and ecological or social imbalance. The metaphor thus warns of the limits of accumulation and invites reflection on how to achieve balance for HRI. 

To help researchers and practitioners navigate this shift, we propose three actionable steps:

  1. Ask ‘Question Zero’: Inspired by the question zero for the use of AI: ‘why AI?’, we, in our version, ask ‘why robots?’. Asking this forces criticality and more detailed motivation for why a robot is needed and for whom. Question zero can also inform research that examines real-world applications in need of critique. Beyond refusal, the question seeks to find cases in need of assessment and possible exnovation.
  2. The Post-growth Manifesto: We suggest a manifesto (see below), that comes with a glossary. Here, we list a number of conventional understandings of robots in HRI based on our reading of the field, in opposition to a list of important notions within post-growth for HRI. It can be a tool to locate, discuss, and negotiate ongoing research, and in doing so, we encourage leaning into the B side to support a post-growth orientation.  
  3. Sustainability Statements: Just as ethical and positionality statements have become standard, we propose a template for sustainability statements. These encourage researchers to reflect on the environmental, social, and economic impacts of their work.

Why This Matters

As HRI researchers, we have the power to define what the ‘future’ looks like. By embracing post-growth, we aren’t ‘anti-technology’. Instead, we are advocating for a future where robotics serves humanity and the biosphere without being tied to the destructive cycle of endless extraction.

We hope this paper serves as a call to reflexivity and criticality. It’s time to consider not just how we build and deploy robots, but for whom and at what cost.


Citation: Sofia Thunberg, Mafalda Gamboa, Ilaria Torre, and Birgit Penzenstadler. 2026. Post-growth Perspectives in HRI. In Proceedings of the 21st ACM/IEEE International Conference on Human-Robot Interaction (HRI ’26). Association for Computing Machinery, New York, NY, USA, 1388–1398.

Human-Centred Software Engineering for Sustainable Software

Unsplash Photo by Nick Fewings

As we look ahead to the future of software engineering, one thing is clear: there is an urgent need for stronger communication between software engineering (SE) and human-computer interaction (HCI) researchers. This issue was brought to the forefront during the 2030 Software Engineering Workshop, co-located with the ACM International Conference on the Foundations of Software Engineering (FSE’24), where one of the key topics was the importance of human aspects in software engineering. There is also a growing need to develop sustainable systems that are not only technically robust but also socially and environmentally sustainable. The call to bridge the gap between SE and HCI was a key theme in one of the keynote addresses at the 46th International Conference on Software Engineering (ICSE 2024), which emphasised the necessity of collaboration between these fields to achieve trustworthy AI systems by design.

Historically, SE and HCI have followed parallel paths [1], with some considering HCI a subset of software engineering, while others see it as an independent field. While software engineering tends to be functional and systematic, HCI draws from diverse areas such as psychology and ergonomics to prioritise human-centred design. This difference in focus has led to challenges in transferring knowledge between the two fields, with each speaking a different language despite working toward the same goals: creating effective, efficient, and usable software systems.

With the rise of AI, IoT, and other advanced technologies, the stakes are higher than ever. We are designing systems that increasingly touch every aspect of daily life, from healthcare to transportation to education. These systems must be trustworthy, reliable, and—most importantly—designed with the human at the center. Education plays a crucial role in addressing this gap. Today’s students are tomorrow’s software engineers, and if we want them to design systems that are both technically sound and human-centered, we need to embed human aspects into software engineering curricula. However, current frameworks like SWEBOK (Software Engineering Body of Knowledge) and curriculum recommendations consider HCI a small part of the overall software design process rather than a central theme.

Another challenge in bridging the gap between software engineering and HCI lies in the terminology each field uses. For instance, concepts like usability, user experience, and quality in use often have different meanings depending on the discipline or standard being referenced. This terminological confusion can create additional barriers to collaboration, as researchers and practitioners may believe they are discussing the same concept when, in reality, they are approaching it from different perspectives.

There are, however, promising efforts to bridge this gap. International conferences that focus on both SE and HCI, or that feature tracks dedicated to exploring the intersection of the two disciplines, are helping foster collaboration. These platforms allow academics and practitioners from both fields to share ideas, discuss challenges, and develop strategies for more integrated approaches to software design and development.

As someone who has conducted research in both fields, with a focus on requirements engineering and software quality, I’ve seen firsthand how the practical aspects of software engineering and the conceptual frameworks of HCI are complementary. Together, they broaden the perspective on challenges and opportunities, enabling the production of software that is not only functional but also provides real value to all stakeholders, including users, developers, and decision-makers.

By bridging the gap between SE and HCI, we can design solutions that meet human needs while contributing to a more sustainable, inclusive, and trustworthy digital future. The next decade offers a critical opportunity to reshape the relationship between these two fields, and in doing so, shape the future of software development for the better.

[1] Ogunyemi, A., & Lamas, D. (2014). Interplay between human-computer interaction and software engineering. In 2014 9th Iberian conference on information systems and technologies (CISTI) (pp. 1-10). IEEE.