Susanna Aromaa, Päivi Heikkilä, Hanna Lammi (2024). Human-centred design of Industry 4.0 technologies in research projects. In: Ergonomics In Design. AHFE Open Access, vol. 129, pp. 34–40. https://doi.org/10.54941/ahfe1004808
Novel technologies are often developed through collaborative research projects. This increases complexity in collaboration compared to company-internal development projects and can create challenges as regards applying human-centred design (HCD) principles to the development. This paper presents two research projects in which human factors (HF) had an essential role. Although HF principles served as a useful guide in the design of technology solutions, some challenges were encountered. These challenges are outlined in this paper and suggestions regarding how to manage potential risks in collaborative projects are presented. Lessons learned from these projects can be used by HF researchers in future research projects to better manage HF activities when developing technology solutions.
Digitalisation and automation are changing industry and require workers to apply novel technologies in their work (e.g., augmented reality, robotics and artificial intelligence) (Romero et al., 2016; Kagermann et al., 2013; Kadir and Broberg, 2020). During this transformation towards smart factories, it is important to develop Industry 4.0 technologies by applying human-centred design (HCD) approaches (e.g., ISO 9241–210, 2019; Brown, 2008) and ensuring participation of users (Ehn, 1993; Muller and Kuhn, 1993). These HCD approaches are well described and can serve as a valuable guide in the development process. However, technologies are not always developed within a single company or a small development group, but rather the first versions of technology solutions may be created in collaborative research projects.
The development of technology solutions in research projects may increase complexity in collaboration and create challenges as regards implementing HCD principles. For example, in the smart construction sector, it was noted that using a design thinking approach in a research project was not a simple and straightforward task (Aromaa et al., 2022).
The goal of this paper is to understand the main challenges that can hinder the use of HCD principles during research projects aimed at technology devel- opment. This paper describes the challenges encountered in the application of HCD during two research projects. First, the paper describes the research projects and how the challenges were identified (Material and methods).
Human-Centred Design of Industry 4.0 Technologies in Research Projects 35
Then it describes the challenges encountered (Results) and how the main challenges could be managed during the projects (Lessons learned). Finally, conclusions are presented.
MATERIAL AND METHODS This section describes how the challenges were discovered and provides short descriptions of two research projects. The challenges were identified by three human factors (HF) researchers who participated in the projects: all three of them participated in the EU-funded project and two of them participated in the nationally-funded project. They all work in the same research institute, and they have over 20 years of experience in HF research in different kinds of research projects. After the projects ended, the HF experts had a workshop in which they identified challenges they had come across during the projects. To identify these challenges, they adopted the HCD process description from ISO 9241–210 (2019), which has main four steps: (1) understanding and specifying the context of use, (2) specifying the user requirements, (3) pro- ducing design solutions, and (4) evaluating the design of the approach. The HF researchers discussed challenges related to these four phases of HCD.
The first project was a four-year EU-funded project, in which 20 part- ners developed human-centric industrial applications to support modern industrial work. The partners represented research organisations, technol- ogy providers and manufacturing companies as industrial pilot organisations. There were three different partners who focused on HF research. The project was carried out from 2020–2023. The aim of the project was to find the balance between cost-effective automation and involving human workers in tasks where they create the greatest added value. The HF work focused on studying industrial requirements for the development of the new com- ponents, co-defining industrial use cases, giving human-centric design and research guidance to the partners, evaluating the developed components and co-creating ethical guidelines within the consortium.
Another project was a nationally funded co-innovation project that was conducted over two years (2021–2023). Nine companies in the fields of robotics solutions, software and B2B services, and a research institute partici- pated in the project. Researchers from the institute represented three different research areas: business, robotics and HF. The aim of the project was to study new technologies and multi-purpose robot-enabled services and busi- ness models. The scope of the project focused on autonomous, mobile service robots that are used indoors or outdoors, for instance, in last mile deliver- ies, maintenance, surveillance and customer service. Concerning HF, the focus was on the development and evaluation of the user experience and acceptance of shared, heterogeneous multi-purpose service robots and robot fleets.
RESULTS
Human factors were an essential part of both research projects assessed and beneficially affected the technologies that were developed in the projects. However, the HCD activities could have been better organised and managed
during the projects. Based on these two projects, it was found that there can be challenges in all four HCD phases when designing technology solutions in a research project. The following sections describe the challenges identified in the projects.
Challenges Identified in the EU Project This project involved 20 partners from all over Europe, three of which focused on HF topics. Therefore, it took some time in the beginning to get together with all the partners, agree on responsibilities and create a com- mon understanding of the project’s goals and the tasks that needed to be performed. Additionally, the abstraction level of the discussions was high in the beginning, and it took time to reach a precise understanding as to how to proceed in the project. At the beginning, a workshop was held in which initial requirements were ideated together, but it was challenging because there were several different development targets, such as technol- ogy solutions, support tools, pilots, use cases and a marketplace. Therefore, the requirements that were defined were general and the abstraction level was high.
In the HCD phase, in which a context of use is defined, the project faced challenges because the coronavirus pandemic restricted travel and it was not possible to see industrial contexts in real life. Additionally, during this phase, the understanding of the use cases was formed by interviewing mainly project partners and other stakeholders (and not actual end users). These interviews were also used to define the specific requirements for each use case. In some companies, the definition of use cases took time and some of the cases changed completely from the initial plan. This meant extra time was needed, and this delayed other actions, such as the planning of HF evaluations.
When the use cases and technology developments were more defined and prototype building had started, one challenge was that the requirements were not systemically reviewed and refined to support this more detailed level of prototype design. Development actions in the project were carried out by several distributed partners and, therefore, the HF experts were not able to be intensively involved in all technology development cases. This led to chal- lenges as regards following the co-design principles, and only rather general HCD guidelines were created to guide the developers.
Human factors evaluations during the project were conducted mainly on an independent basis by the pilot partners, and the HF experts only provided data collection material and received results from the pilot partners for anal- ysis. The HF experts were not able to follow the actual tests or have direct contact with end users. This also meant that only quantitative (questionnaire) data were gathered and more qualitative (e.g., observations, interviews) were not extensively obtained.
Challenges Identified in the National Project This project had similar challenges at the beginning, when seeking to redefine a common goal for the collaboration and create a shared understanding of the
Human-Centred Design of Industry 4.0 Technologies in Research Projects 37
“multi-purpose robot” concept. Another challenge was due to the fact that versatile fields of robotics were included in the project (indoors/outdoors, maintenance, delivery, surveillance, customer service) and therefore it was not possible to define common HF requirements and principles that cover all robots, e.g., in the form of heuristics. Interviews related to understand- ing the context of use were conducted by business researchers who reported the results to the project group. However, HF researchers were not involved in defining the interview questions and therefore were not able to compre- hensively gather insights important to their research. The project focused on innovating new business and service models for multi-purpose robots and actions thus focused more on technology development and service models than on the interaction with humans (end users).
The project encountered resource challenges, notably due to time con- straints on the part of the technology developers. For example, the project attracted a lot of interest in the media and among the public: demos were requested, and their design and implementation ate up resources. Conse- quently, collaborative efforts with the HF experts were limited. Another challenge was that the work was somewhat siloed because companies had their own development goals and other technology developers had theirs.
Because the project focused heavily on technology development, there was a technology feasibility study arranged. However, the planned final pilot with robots was first postponed and finally cancelled. Therefore, the HF experts were not able to evaluate the multi-purpose robots with actual end users and customers.
LESSONS LEARNED This section summarises the main challenges when applying the HCD approach identified in the two research projects presented (Table 1). Addi- tionally, it describes ways of mitigating the possibility of these challenges arising or negatively affecting the research results. One of the main chal- lenges was that there was not enough time and effort allocated to defining a common understanding of the project and its goals at the beginning. Con- sensus regarding how to collect data to understand the context of use and how to share findings should also be thoroughly planned and executed in collaboration. The definition and management of user requirements needs more attention, especially when moving forward in research projects. It is important to understand for whom requirements are defined and how to refine them during the project. When producing design solutions, collabo- ration and information exchange should be emphasised, especially between HF experts and technology developers. Final pilot evaluations can often be planned for the end of the project due to the time reserved for technology development. This is a managerial issue that a project leader should recog- nise and then take steps to ensure the timely development of prototypes or provide other ways to substitute prototype evaluations (e.g., by using Wizard of Oz method (Kelley, 1984), in which not all technology features need to be implemented). Additionally, the project leader should advance collaboration between end user companies and HF experts to ensure access to real users.
Table 1. Summary of challenges identified when implementing human-centred design in two research projects and possible ways to manage the risk of the chal- lenges arising.
Table available in the original PDF paper.
Possible Ways to Manage Risks
Main Challenges Identified
Human-Centred Design Phase (ISO 9241-210, 2019) Understanding and specifying the context of use
Defining common goals and understanding for the project
Plan data collection activities together, collect data that is important for different partners and define data sharing strategies.
When writing a project plan, allocate more time and effort to co-creative activities in which common understanding and goals can be defined. Involving all partners in understanding the context of use (gathering data and sharing information)
Specifying user requirements
Outline in the project plan how requirements are to be managed, and at what point they will be reviewed.
User requirements remain at a general/high level –requirements are not refined while going further in the project User groups are not yet known and/or access is not allowed (requirements are based only on project partners)
Try to identify users and other stakeholders at the beginning of the project. Additionally, re-define requirements during the project, when the research work becomes more defined. Producing design solutions
Design solutions are created in silos
Provide means and ways to make technology development more transparent (e.g., arrange workshops, meetings, demos while development is happening). HF experts are not involved at this stage
Include in the project plan that co-design principles should be applied throughout the project. Be clear in the beginning that HF experts need to hold discussions with solution developers. Evaluating the design
Final pilots with end users are late or cancelled (focusing only on technology feasibility)
Highlight this risk at the beginning of the project to all partners. To mitigate the risk, arrange small experiments during the development process. Additionally, plan how to use substitutive methods (e.g., Wizard of Oz method) to execute HF studies if technology is not ready. HF experts do not have access to end users
Be clear as to who the end users are and who are other stakeholders. Highlight the importance of collaborating with real users. Define alternative plans to substitute end users, if they are not available and if HF experts are not able to meet them.
Human-Centred Design of Industry 4.0 Technologies in Research Projects 39
CONCLUSION
The use of human-centred design (HCD) approaches supports the design of good usability products that are accepted by users. This paper presents two research projects in which human factors (HF) were an essential part of the development of technology solutions. Even though HF principles were successfully taken account in the development, there were some issues that hindered the HCD process. To learn from these matters, this paper identified challenges in applying HCD principles in research projects.
Key findings for HF researchers to keep in mind in future research projects are that a project leader should be well informed about the HCD process and that there should be enough time set aside at the beginning to create the basis for collaboration and common goals. Additionally, specifying user requirements at the beginning of the project is not enough; it is equally impor- tant to manage and refine them during the project. Timely evaluations are also essential in research projects, and if this is not achieved, HF researchers should have back-up plans to ensure that HF topics are addressed. These lessons learned can be used when designing human-technology interaction in collaborative projects with different stakeholders.
ACKNOWLEDGEMENT
This paper explored the challenges of applying HCD in research projects. Nevertheless, the projects executed were successful in many ways and all the project partners were helpful and participated actively in achieving the project goals. We are grateful to all the project partners for collaborating with us during the projects. This paper was supported by the Business Fin- land funded project “Intelligent Human Technology Co-agency in Process Control” (COACH).
REFERENCES
Aromaa, S., Lappalainen, I., Kaasinen, E. & Öfversten, J. “A Case Study—Applying a Design Thinking Process and User Experience Goals in Developing Solutions for a Smart Construction Site”. International Conference on Human-Computer Interaction, 2022. Springer, 93–105. Brown, T. (2008). Design thinking. Harvard Business Review, 86, 84. Ehn, P. (1993). Scandinavian design: On participation and skill. Participatory design:
Principles and practices. ISO 9241–210. (2019). Ergonomics of human-system interaction. Part 210: Humancentred design for interactive systems. Kadir, B. A. & Broberg, O. (2020). Human well-being and system performance in
the transition to industry 4.0. International Journal of Industrial Ergonomics, 76. Kagermann, H., Wahlster, W. & Helbig, J. (2013). Recommendations for Implementing the Strategic Initiative Industrie 4.0: Securing the future of German manufacturing industry. Kelley, J. F. (1984). An iterative design methodology for user-friendly natural lan-
guage office information applications. ACM Transactions on Information Systems (TOIS), 2, 26–41.
Muller, M. J. & Kuhn, S. (1993). Participatory design. Communications of the ACM. Romero, D., Stahre, J., Wuest, T., Noran, O., Bernus, P., Fast-Berglund, Å. & Gorecky, D. “Towards an operator 4.0 typology: A human-centric perspective on the fourth industrial revolution technologies”. CIE 2016: 46th International Conferences on Computers and Industrial Engineering, 2016 Tianjin, China.
LISTED IN THE AHFE DIGITAL BOOKSTORE CATALOGUE
Explore the complete digital volume
Ergonomics In Design
Read this individual research paper free through the original publisher, or explore the full digital proceedings book.
ISBN 978-1-964867-05-2
Explore this ISBN in the AHFE Bookstore ↗Listed in the July 2026 bookstore catalogue; search by ISBN to confirm current availability · Digital book purchase optional