insta_photos – shutterstock.com
Monday morning, sync meeting: The backend team reports “feature complete” from the team perspective, the frontend is blocked by a missing API adjustment and the department is pushing for the release. Although all partial results are available, integration is delayed. Such situations are typical for virtual collaboration. The problem is rarely a lack of competence, but rather that work statuses combine too late to form a common picture.
In face-to-face teams, this coordination often happens incidentally, for example through short questions. These small correction loops keep the system synchronous. It is precisely this informal coordination that is missing in virtual space. Communication is more planned and documented, but less checked. Assumptions remain invisible and perspectives separate for longer. The consequences only become apparent late: decisions have to be corrected, work is done twice and responsibility is formally distributed, but not lived in a coordinated manner in everyday life.
An obvious reaction to this is to create more structure through additional reports, stricter specifications and more frequent meetings. This provides short-term overview, but does not replace real synchronization. The opposite often happens: there is more communication without increasing understanding.
The real problem is not a lack of communication, but rather an insufficient coordination in the work process. What is important is not how often teams communicate, but rather how they replace what happens in person.
Create connection through better questions
If synchronization no longer occurs automatically, it must be initiated consciously. An effective lever lies in the type of questions asked. This is where systemic issues come into play. They are not aimed at individual tasks, but at the interaction behind them.
So it’s about the connections, dependencies and assumptions that shape decisions. This makes different perspectives visible and related to one another at an early stage. This creates a common picture across team boundaries – not through more coordination, but through better questions at the right moment.
1. Circular questions
Virtual IT teams often optimize locally without sufficiently considering the upstream and downstream steps. This is exactly where circular questions come in by specifically including other perspectives, for example: “How would our customer describe this decision in the current setup – and what would irritate him most about it?”
Such questions promote systemic thinking across team and functional boundaries, so that dependencies become visible at an early stage, rather than only in the company or during an incident. This makes decisions more robust, the effort required for rework is reduced and feedback loops are noticeably shortened. Especially in complex architectures, a common understanding of the entire system is created, which is what enables speed in the first place.
2. Resource-oriented questions
The focus of virtual communication is often on disruptions: incidents, delays, escalations. This is necessary, but quickly leads to a one-sided problem perspective. Resource-oriented questions can deliberately set a counter-emphasis here – for example, “Which decisions or behaviors enabled stability in the last sprints?” or “Which of these can be specifically reproduced or amplified?”.
Such questions draw attention to working solutions and the patterns behind them. This allows teams to specifically reuse successful approaches instead of solving each problem anew. This increases predictability in delivery and strengthens stability. The knowledge is not only documented, but actively used.
3. Scaling issues
In many votes it is not a lack of information, but rather a lack of clear assessments. Assessments remain implicit, delaying decisions. Scaling questions make this uncertainty tangible, for example: “How resilient is our release plan currently on a scale of one to ten?” and “What would be the first visible difference between a six and a seven in everyday life?”
This makes subjective assessments comparable and compatible. Instead of vague discussions, concrete next steps emerge: What is missing? Where is the risk? In this way, decisions can be made more well-founded because ambiguities are not ignored but clarified in a structured manner.
4. Hypothetical questions
In complex systems, alternatives are often not sufficiently thought through because the focus is heavily on the current solution. Hypothetical questions specifically open up this thinking space. An example is the question “If we were to start from scratch today, which of our current assumptions would we likely reject?”
Such mind games are not a theoretical exercise, but a pragmatic tool for improving decisions. Teams recognize options for action and their effects at an early stage. This supports prioritization, reduces wrong decisions and strengthens the ability to develop viable solutions even under uncertainty.
5. Paradoxical questions
When discussions go around in circles, it is rarely due to a lack of arguments, but rather due to stable thought patterns. Paradoxical questions start right there by deliberately irritating these patterns, for example with questions like “What would we have to do to guarantee that this project will fail?” or “How could we make our voting even more inefficient?”.
This change in perspective often has an immediate effect: implicit assumptions, contradictory behaviors or dysfunctional routines suddenly become visible. Teams recognize their own contribution to the problem and that is exactly the prerequisite for actually changing established ways of working instead of just further optimizing them.
The actual lever
The added value of systemic questions lies in the change of perspective. Problems are no longer viewed in isolation, but rather as the result of interactions. Especially in virtual environments, frictional losses rarely arise from a single cause, but rather from many small ambiguities at interfaces, in assumptions and expectations.
Systemic questions make these ambiguities visible without the need to introduce additional processes. They create clarity in the system, which in turn is the prerequisite for speed, stable delivery and reliable collaboration.
Virtual teams therefore rarely require tighter control, but rather more precise communication. Systemic questions are not a “soft” instrument, but rather an operational lever that reduces rework, speeds up decisions and increases the commitment to implementation.
Those who ask better questions make better decisions – and that is exactly what is crucial for the performance of virtual teams. (fm)
This article was published as part of Foundry’s German-speaking expert network. Would you like to join in? Apply now!
