In the world of studying how groups of people work together, there is a method called Action Research. Unlike a scientist who stands far away from a forest to count trees, an Action Researcher steps into the forest to help the trees grow while also learning how they grow. This approach is built on a simple but powerful idea: to truly understand a complex problem within an organization, you must work alongside the people facing it, trying out solutions, watching what happens, and adjusting your plan as you go. It is a cycle of doing, watching, and thinking that happens over and over again. For decades, textbooks have described this process as a neat, orderly loop, suggesting that if you follow the steps carefully, you will solve problems and create new knowledge at the same time. But anyone who has tried to lead a large team or manage a complex project knows that real life rarely follows a perfect loop. People get busy, priorities shift, and the problems we think we are solving often change shape before we even finish the first step.

This is the reality that Hanna Pfeiffer and Olivier Fuchs, researchers from TH Köln, set out to explore. They did not just study a theory; they lived inside a long-term research project called CIRCLE, which was designed to help three different companies improve how they communicate and lead while working remotely. Their goal was to see how digital tools could support leadership in a world where teams are spread out across different locations. As they worked through the years, they realized that the messy, difficult parts of keeping the research alive were just as important as the formal steps of the study. They found that the true work of this kind of research happens in the spaces between the official cycles, where researchers must constantly rebuild trust, negotiate access, and adapt to a world that refuses to stay still.

The project began with a clear plan. The researchers wanted to observe how digital communication worked in real time, rather than just asking people later about what they remembered. They set up a system to record and transcribe online meetings and conversations, hoping to capture the natural flow of work. They invited three organizations to join them, expecting that these partners would provide access to their digital channels and participate in workshops to discuss findings. The plan was to follow a standard pattern: observe the work, reflect on what was seen, try out a new way of doing things, and then observe again. It sounded straightforward, but as soon as the work began, the researchers found that the problems the organizations faced were not the same problems they had planned to study.

In one of the partner organizations, the team arrived ready to analyze how digital tools affected leadership. However, the people they met were not worried about leadership communication; they were struggling with a much more immediate issue. Field workers were sending information about their hours and materials too late, which caused delays in billing and administration. The researchers quickly realized that their original research question was not useful to these people. To be helpful, they had to pivot. They helped the organization design a new system using artificial intelligence to record and translate field data in multiple languages. This was a huge practical success for the company, but it meant the researchers had to step away from their original topic. They had to constantly decide when helping the organization solve a problem was still part of the research, and when it had become just a consulting job. They learned that in a long-term project, the thing you are studying can change faster than your research plan can keep up.

Access to the people and data they needed was another hurdle that did not disappear once the project started. The researchers had formal permission to study the organization, but that permission was not a one-time ticket. They found that while they could easily record large, formal meetings, they could not get access to the one-on-one conversations where the most important trust and conflict actually happened. People were afraid to be recorded in private chats. Furthermore, as the months went by, the enthusiasm of the employees began to fade. The organization had about 400 people, and the researchers could not build a deep relationship with all of them. When the researchers asked for more time or data, they were met with the reality that the employees were busy with their actual jobs. The researchers realized that participation is not something you get at the start; it is something you have to earn and re-earn every single day. If you stop nurturing the relationship, the access stops.

The act of watching the work also changed the work itself. When people know they are being recorded or observed, they often act differently. The researchers noticed that the mere presence of their project influenced how people spoke and behaved. This is not a mistake in the method; it is a fact of life when you are inside the system you are studying. The researchers had to accept that they were part of the story they were telling. They could not pretend to be invisible observers. Instead, they had to think carefully about how their own presence was shaping the reality they were trying to understand. In one case, an organization seemed to want the research to prove that working in an office was better than working from home, even though the researchers had started with an open mind. The researchers had to navigate these hidden agendas, realizing that the organization was not just a passive subject but a group of people with their own strong beliefs and desires.

Perhaps the most surprising discovery was the sheer amount of invisible work required to keep the research going. The formal steps of the study—collecting data, holding meetings, writing reports—were only the tip of the iceberg. Beneath the surface, the researchers were spending enormous amounts of time explaining the project to new people, fixing technical glitches, reminding busy employees to participate, and traveling to different sites just to keep the relationships alive. This work did not produce data directly, but without it, there would have been no data at all. The researchers found that maintaining the conditions for the study was a massive, ongoing labor that is rarely mentioned in textbooks. It is the relational glue that holds the project together when the formal plan starts to fray.

The authors conclude that these difficulties are not signs that the method is broken. On the contrary, they are proof that the method is working as intended. By staying in the messy, unpredictable reality of the organizations, the researchers were able to see things that a distant observer would have missed. They saw how problems evolve, how trust is built and broken, and how real change happens in fits and starts. The neat, circular diagrams found in textbooks describe the ideal, but the real work happens in the gaps between those circles. It is in those gaps that researchers must negotiate, adapt, and persist. The value of this kind of research lies in its willingness to stay engaged with the messiness long enough to learn something true. The study suggests that to do this work well, we must stop pretending that research is a clean, controlled experiment and start recognizing that it is a deeply human, relational effort that requires constant care and attention.