Systemic questions: understand the pattern, not just the person

Systemic questions explore a situation through its context, relationships and recurring interactions. Instead of stopping at “this person is difficult,” they invite a closer look at what happens, how others respond and what conditions keep the pattern going. Their value is not in sounding clever. It is in helping people examine an explanation that may be too narrow.

In a workplace conversation, that might mean moving from “the warehouse never helps us” to a specific handoff: what information reaches the warehouse, what its staff do next and what the service team does in response. This does not excuse poor behaviour or make everyone equally responsible. It opens questions that a label closes down.

Begin with curiosity, not a hidden destination

There is an important distinction between asking to understand and asking someone to arrive at your preferred conclusion. “What would happen if you finally trusted the new system?” is grammatically a question, but it has already diagnosed the problem and selected the remedy.

Karl Tomm’s 1988 paper describes questions in terms of the assumptions and intentions behind them, distinguishing lineal, circular, strategic and reflexive forms. It was written for therapeutic interviewing. It provides a conceptual background, not proof that a particular question improves workplace performance.

Gianfranco Cecchin’s earlier essay revisits hypothesizing, circularity and neutrality within systemic family therapy. Its invitation to curiosity is a useful orientation, but the workplace examples here are a practical adaptation, not a clinical method or a reproduction of either author’s full framework.

Before asking, check your own position. What do you already believe? What answer would surprise you? Could you accept that your proposed intervention is unnecessary? If every possible response will be interpreted as resistance, changing the wording will not make the conversation exploratory.

You can hold a hypothesis without hiding it. “I wonder whether the timing of updates is part of the difficulty. Does that fit your experience, or am I missing something?” makes the idea available for correction. It is different from presenting the hypothesis as a fact that the other person must defend against.

Agree what kind of conversation this is

Explain the purpose, the time available and what will happen with the discussion. Ask whether exploring the situation in this way would be useful. In a management setting, be honest about authority: an employee speaking with their manager is not in the same position as a volunteer speaking with an independent facilitator.

The ICF’s 2025 competencies connect questioning with agreements, listening and respect for the client’s autonomy. They also distinguish coaching from other forms of support. For an ordinary workplace discussion, the implication is to be clear about your role and avoid drifting into personal or clinical territory.

Do not disguise a performance decision as an open exploration. If a deadline or process requirement is fixed, say so. You can still investigate how the work is experienced and where support is needed, without implying that every condition is negotiable.

If you are joining a larger change assignment, settle these expectations during contracting. A sponsor wanting a list of “difficult employees” is asking for something very different from a team wanting to understand a recurring handoff problem.

Choose a question that opens the missing part

The following groups are a practical menu, not a universal taxonomy or a sequence to complete. Choose one question that fits what the speaker has said. A simple factual question can be exactly what the conversation needs.

What you need to explore	An original workplace question	What to watch for
Context	“At what point in the order process do you usually need to call?”	A concrete situation rather than a general label
Interaction	“When the warehouse asks you to wait, what do you do next—and what happens after that?”	A sequence involving more than one response
Another perspective	“What do you imagine dispatch would say is missing from the request?”	An interpretation to check, not knowledge of someone else’s mind
Exceptions	“Think of a recent order that moved smoothly. What was different about that one?”	Conditions worth investigating, not proof of a cause
A possibility	“If the next owner were visible in the record, what would you do differently?”	A hypothetical response, not a prediction
A boundary	“What would need to stay unchanged for that experiment to be workable?”	Valuable practices or constraints a proposal could disturb

Context questions make the setting more specific. Circular questions connect perspectives or responses: one person’s action becomes part of the situation to which someone else responds. Hypothetical questions temporarily change a condition so that people can explore possibilities.

Keep those purposes distinct. Asking what dispatch might think can reveal the speaker’s assumptions, but it cannot replace speaking with dispatch. Asking about an exception can uncover a useful lead, but it does not establish that the difference caused the better outcome.

Follow one handoff through a conversation

Here is an invented conversation at the wholesaler from our contracting example. The service team calls the warehouse when it cannot explain an order delay. The aim is to understand that interaction, not to secure agreement to a predetermined training programme.

The facilitator starts with: “Could we look at one recent order where the dashboard did not give you enough to answer the customer?” The service colleague describes a delayed parcel whose status had not changed since the morning.

Rather than asking why the colleague distrusts the dashboard, the facilitator asks: “What could you see at that point, and what did you still need to know?” The colleague says the screen showed where the order was, but not who was dealing with the delay.

The next question follows the action: “When you called dispatch, what happened?” Dispatch said it was waiting for an update. The service colleague called again later because the customer had called again. Now the conversation has a sequence, not just two departments accusing each other of poor communication.

The facilitator asks: “How do you think the second call looks from dispatch’s side?” The colleague guesses that it feels like pressure to provide information dispatch does not yet have. The facilitator marks that as a guess: “What would we need to ask them to find out?”

This is the crucial move. A possible perspective becomes a question for another participant, not an explanation imposed on an absent group. Stakeholder mapping can help identify whose account is still missing, especially when the people least represented in meetings do essential operational work.

Finally, the facilitator asks about a smoother case. The colleague remembers an order where a named person had agreed to call back. That suggests investigating whether visible ownership and a dependable update time matter. It does not prove the dashboard needs another field, or that an additional notification would solve the problem.

Listen long enough for the answer to change your next question

A prepared list can help you begin, but reading through it can turn a conversation into an interview obstacle course. If the speaker names a constraint you did not anticipate, stay with it. Ask for clarification, summarize what you understood and allow a correction.

There is a useful counterweight in Heard, Seen, Respected, a Liberating Structures practice built around attentive listening without immediately fixing or judging. You do not need to run that whole activity to recognize the discipline: another question is not always the most helpful next contribution.

In the fictional conversation, the colleague might say that the difficult part is promising a callback while covering the desk alone. Jumping immediately to “What would an ideal future look like?” would miss the capacity issue they have just offered. A better response is to check the meaning: “So an owner field would not help unless someone had time to act on it—is that what you mean?”

Give people space to decline or redirect an unhelpful question. If a perspective-taking question feels like being asked to justify another team’s behaviour, return to observable events. If someone is unsure, do not reward a confident guess over an honest “I don’t know.”

Repair questions that contain an accusation

Some questions sound open while narrowing the acceptable answer. “How can you become more positive about this change?” assumes attitude is the problem. Try asking what is workable, what is difficult and which recent example would help you understand the difference.

“Why do you always escalate?” combines a generalization with a request for justification. Ask which situations lead to escalation and what happens when the person does not escalate. That does not remove accountability; it makes the discussion more precise.

“What are you doing to keep the problem alive?” can become blame disguised as systems thinking. A safer starting point is to trace everyone’s actions, including management decisions and your own contribution. Do not assume that the person with the least authority has the power to change the pattern.

Nor is the word “why” inherently wrong. “Why is that step important to the customer?” can be a straightforward request for meaning. Judge the intention, context and response instead of following a rule that bans one word and treats every “what” question as respectful.

Turn a new view into a check, not a verdict

End by separating three things: what was described, what you now think might explain it and what remains unknown. In our example, repeated calls were described; uncertainty about ownership is a possible explanation; dispatch’s perspective and the timing of updates still need checking.

Ask what the participants want to do with that understanding. They might agree to trace a few recent orders with dispatch, compare a smooth and a difficult handoff, or test a small clarification within their authority. Name the owner and a review point. Do not turn a reflective conversation into a new assignment for somebody who was not present.

Sometimes the conversation raises a deeper rule: perhaps response speed is rewarded while ownership of unresolved orders remains unclear. That can lead into double-loop learning, where the question concerns the governing assumption as well as the immediate action.

Boundaries and evidence

These questions are useful when people want to explore an ambiguous situation and have room to reconsider their account. They are not a replacement for a direct instruction in an urgent incident, an appropriate investigation of misconduct or a decision that a responsible manager must make.

Do not use relational language to distribute blame equally in cases of harassment, discrimination or abuse of power. A pattern can involve several people without giving them equal responsibility or equal freedom to act. Use the appropriate organizational support and reporting route rather than reframing a serious concern as a shared communication puzzle.

The cited early papers provide conceptual roots in therapy, while the coaching standards and facilitation practice offer professional guidance. They do not establish that this workplace question menu produces a particular outcome. The examples are original and illustrative. Use the approach with humility: a useful question helps people notice something worth checking, and a useful listener is willing to be changed by the answer.