Seeing the work while doing the work: Facilitating group self-awareness for better outcomes

The team had been meeting fortnightly for three months. They were a capable group: experienced, well-informed and genuinely committed to the project they were working on. From the outside, the sessions looked productive. The agenda was covered. Actions were agreed. Progress was recorded.

But when the project sponsor asked the team to present their findings, something unexpected happened. The three sub-groups that had been working in parallel arrived at the room with recommendations that pointed in contradictory directions. Not because they disagreed, it turned out, but because they had each been solving a different version of the problem without realising it. The original brief had been interpreted three ways, none of them explicitly, and the team had been working at pace for twelve weeks on divergent foundations.

When I was brought in to help them work through this, the first conversation we had was not about the content. It was about how they had been working. We spent an hour examining not what they had produced but how they had approached the task: how quickly they had moved from brief to action, what assumptions had been made in the first two sessions and never revisited, whose questions had been left unanswered because the pace felt too urgent for anything to slow it down. The team was visibly uncomfortable. Not because the conversation was critical, but because the patterns being named were so familiar. They had been in this dynamic before, in previous projects, with different content.

By the end of that conversation, the team had a clearer picture of how their way of working had contributed to the situation they were in. More importantly, they had a shared language for what to watch for. The project recovered. But the more lasting change was in how the team began to check in on itself at the start and close of subsequent sessions — not at length, and not with any particular formality, just with enough awareness to catch the familiar patterns before they became expensive problems.

That experience captures what IAF Core Competency D2, Facilitate Group Self-Awareness About Its Task, is really asking of facilitators. It is not the most visible competency in the framework. Groups are usually focused on what they are discussing rather than how they are approaching the discussion. But it is often the how that determines whether insight deepens, decisions land and outcomes become genuinely useful rather than formally complete. Without awareness of pace, information, patterns and experience, groups can stay very busy while missing what matters most.

D2 asks facilitators to work in two spaces simultaneously: one eye on the task, one watching how the group is engaging with it. The work is not to judge or correct, but to create moments where the group can observe itself and make more conscious choices about how it proceeds. This is one of the competencies that separates facilitation as a craft from facilitation as event management.

The four strands of facilitating group self-awareness about its task

In practice, this competency involves four closely related elements:

• Varying the pace of activities according to the needs of the group
• Identifying the information the group needs and drawing out data and insight
• Helping the group make sense of underlying issues, patterns and root causes
• Assisting the group in reflecting on its experience

These are not stages to be followed in sequence. They are forms of attention and intervention that overlap and reinforce one another throughout a session. Together, they help the group remain conscious of its own work rather than being carried along by habit, momentum or the path of least resistance. When all four are present, conversations become more intentional, decisions rest on clearer understanding and learning carries forward into future work. When they are absent, groups can spend considerable time and energy producing outcomes that feel complete in the room but prove fragile in practice.

Varying the pace of activities according to the needs of the group

Groups often default to a single rhythm, either moving fast because urgency is present or circling slowly because complexity feels overwhelming. Neither pace is inherently wrong, but both become limiting when they are not chosen deliberately. Varying pace is about helping the group move at the speed the task requires rather than the speed it has become accustomed to. Exploratory work needs more space. Integrative work needs a steady rhythm. Decision-making benefits from a more contained tempo once understanding is sufficient. The facilitator’s task is to notice when the current pace is no longer serving the work and offer the group a way to adjust.

Identifying the information the group needs and drawing out data and insight

Groups frequently work with partial information without realising it. Assumptions go untested, relevant experience remains unspoken and data sits with individuals who were never invited to share it. Decisions built on this narrow base tend to be more fragile than decisions built on a fuller picture. Facilitating task awareness includes helping the group recognise what it knows, what it is assuming and what it genuinely still needs in order to proceed well. This is not about supplying answers. It is about creating conditions where knowledge, experience and perspective that already exist within the group can surface and be integrated.

Helping the group make sense of underlying issues, patterns and root causes

As discussion unfolds, groups typically generate more material than they can use. Ideas accumulate, viewpoints multiply, and the conversation risks becoming fragmented. Without support, groups leave with lists rather than insight. A core part of this competency is helping the group step back and make sense of what is emerging: noticing patterns, surfacing recurring themes, identifying tensions and examining what might be driving what they are seeing. This is the move from content to meaning, and it usually requires slowing the pace deliberately, because insight rarely emerges under pressure.

Assisting the group in reflecting on its experience

Reflection is where learning consolidates. Yet it is consistently squeezed out by the pressure to complete tasks. Assisting the group to reflect on its experience helps participants not only finish the current work but improve how they work together over time. Reflection can be brief and well-targeted: what worked well in how the group approached this task, what made progress difficult, what they would do differently. When held with care and proportion, it deepens understanding without slowing momentum and prepares the ground for more thoughtful, sustainable progress next time.

Reflections on varying the pace of activities

In facilitation, pace is commonly mistaken for speed. We speak of moving faster or slowing down as if pace were primarily a matter of minutes on an agenda. But pace is not principally about time. It is about the relationship between time, attention and cognitive load. A group can move quickly and still think deeply. Another can spend hours together and make very little progress. What matters is whether the current tempo is supporting the kind of thinking the task requires in this particular moment.

Research in cognitive psychology consistently demonstrates that different types of thinking operate best under different conditions. Daniel Kahneman’s framework distinguishing fast and slow thinking, developed from decades of research in decision science, is directly relevant here. Kahneman describes System 1 thinking as fast, automatic and pattern-based, and System 2 thinking as slow, deliberate and effortful. Both are necessary. The problem arises when groups apply fast thinking to situations that require slow thinking, or when they remain in slow, exploratory mode when a decision is ready to be made. Facilitators who understand this distinction can help groups recognise which kind of thinking the current moment calls for, and adjust the pace accordingly.

Pace also carries a social signal. When a facilitator moves quickly, participants infer that efficiency matters more than depth. When a facilitator slows the room, participants sense that their thinking deserves time. Neither signal is inherently right or wrong. Problems arise when the signal conflicts with the work. A group that is being moved through a process at a pace that prevents adequate reflection will often produce decisions that feel superficially complete but carry unresolved uncertainty that resurfaces later, sometimes at considerable cost.

The practical challenge is that groups rarely self-regulate their pace well. Some groups develop a cultural habit of speed, equating momentum with competence. Others stall in the comfort of continued discussion, using exploration as protection against the commitment that decision requires. Facilitators hold responsibility for noticing these patterns and intervening without taking over the group’s sense of ownership of its own work.

The most reliable signals that pace needs adjustment come from the group itself. When conversation is skimming across issues without deepening, when agreement appears quickly but feels thin, when the same points are being revisited without new development, the group is likely moving too fast for the complexity of what it is working on. When energy is visibly dropping, when discussion is circling without integration, when detail is accumulating without moving toward meaning, the group may be stuck in a tempo that is preventing progress as much as enabling it. Both of these are observable, and both can be named neutrally and offered back to the group as information rather than correction.

Inner steadiness matters here as much as observational skill. Many pace interventions are driven less by what the group needs and more by the facilitator’s own discomfort with silence, ambiguity or the appearance of slow progress. The urge to fill silence, to move to the next activity or to summarise before the group has fully arrived at its own understanding is among the most common ways facilitators inadvertently shortchange the quality of a session. Developing the capacity to stay with the group’s uncertainty without acting on it prematurely is a discipline that grows through practice and reflective attention to one’s own facilitation responses.

Seven practices that help me vary pace in service of the group’s work

1. I monitor engagement rather than the clock. Absorption and restlessness are more reliable indicators of whether to continue or shift than the time an activity has been running. I use both as data, and I let purpose rather than minutes determine transitions.
2. I name the type of work the group is doing at key moments. Saying “we are in an exploratory phase here, so I want us to resist the pull toward conclusions for a little longer” gives the group a frame for understanding why the current pace feels as it does.
3. I use silence deliberately. When a significant question has been posed, I hold the silence longer than feels comfortable rather than filling it. The thinking that emerges from held silence is often qualitatively different from the thinking that emerges from continuous speech.
4. I resist rushing exploration to protect convergence. When I sense that the group is not yet ready to move toward decision, I say so rather than allowing an artificial convergence that will need to be undone later.
5. I notice and name my own urge to intervene prematurely. When I feel the pull to move things along, I pause before acting and ask whether the impulse is responding to the group’s need or to my own discomfort with the current state of the room.
6. I offer the group choice at pace transitions. Rather than simply moving to the next phase, I sometimes ask whether the group is ready to move on or whether it needs a little more time with the current question. This keeps the group’s agency in its own process.
7. I debrief pace explicitly when it seems to have been a factor. At the close of a session, asking “how did the rhythm of today feel?” surfaces learning about the group’s relationship to pace that can inform future design.

Reflections on identifying the information the group needs and drawing out data and insight

One of the most consequential facilitation errors is allowing a group to work at length on an incomplete or distorted picture of its situation. This happens more often than groups realise, and it rarely announces itself. The conversation feels productive. People are engaged. Ideas are forming. But beneath the surface, something important is missing: a perspective that has not been invited, a data point that is known to one member and unknown to others, an assumption that everyone holds and no one has named. Decisions built on this foundation are more fragile than decisions built on a fuller, more honestly tested picture of reality.

Karl Weick’s work on sensemaking in organisations offers a useful theoretical frame here. Weick argues that organisational actors do not simply receive information and respond to it. They actively construct the situations they find themselves in, selecting certain cues from the environment and ignoring others, building a coherent narrative that makes action feel possible. This process is necessary but it is also limiting, because the narrative that enables action also excludes certain kinds of information from consideration. Weick’s concept of enactment, the idea that organisations partly create the environments they then perceive themselves to be operating in, suggests that groups working on complex problems are always working with a partial and actively constructed picture of reality, not an objective one. The facilitator’s role, in this frame, is to help the group notice what it is selecting in and selecting out, and to create conditions where a broader range of information can enter the picture.

In practice, this means attending to three distinct types of information that groups frequently leave on the table. The first is experiential knowledge: what participants have directly seen, heard or encountered in their work that is relevant to the question being explored. This knowledge often sits with the people in the room but is not brought forward because the conversation has not created space for it. A question as simple as “what are you observing in practice that bears on this?” can surface data that shifts the entire direction of a discussion.

The second is emotional or relational information: how confident people feel about a decision, where commitment is fragile, what concerns are being held privately because the environment has not signalled that they are welcome. This is not soft information. It is among the most practically important information a group working toward durable decisions can have. A decision made without surfacing fragile commitment is a decision that will face implementation problems the group did not prepare for.

The third is structural information: what the group does not yet know and needs to find out before it can proceed well. Groups sometimes move toward decisions before they have identified the gaps in their knowledge base. Part of the facilitator’s task is to help the group distinguish between what it knows, what it is inferring and what it genuinely still needs to establish. Naming this distinction creates a more honest picture of the group’s actual epistemic position and helps it make more proportionate decisions about what to act on now and what to hold until better information is available.

Drawing out this range of information requires a combination of deliberate questioning and structural design. Open questions that invite experience rather than opinion tend to surface richer and more specific information than questions that invite abstract argument. Going around the room in a structured round ensures that information held by quieter or less senior participants is surfaced before the conversation has been shaped by the most vocal voices. Anonymous input methods, whether digital or written, can surface concerns that participants would not voice in the plenary, particularly in groups where hierarchy creates performance pressure around contribution.

Seven practices that help me identify and draw out the information a group needs

1. I ask for observation before interpretation. Inviting participants to describe what they are directly seeing or experiencing before moving to conclusions helps the group build a shared factual ground before interpretation begins, and often reveals significant differences in what people actually know.
2. I create structured rounds before open discussion. Going around the room before the conversation opens ensures that less vocal participants contribute their information before the discussion has been shaped by the first few voices. This is one of the highest-leverage structural choices available to a facilitator.
3. I name the distinction between what is known, inferred and still needed. Helping a group see these three categories separately is often enough to slow premature decision-making and create a more honest assessment of what the group actually has to work with.
4. I surface emotional and relational information explicitly. A direct question such as “where does commitment to this direction feel strong, and where does it feel uncertain?” treats confidence and concern as legitimate information rather than as reactions to be managed.
5. I invite experience rather than opinion. “What have you seen that bears on this?” tends to produce more specific and useful information than “what do you think about this?” The first grounds the conversation in reality. The second opens it to abstraction.
6. I notice when information seems to be held by one part of the room. If a pattern emerges where certain people seem to know things that others do not, I create space to surface that information explicitly rather than allowing it to remain with a subset of the group.
7. I use anonymous input when the environment creates barriers to honest contribution. In groups where hierarchy, interpersonal dynamics or cultural norms make certain information difficult to voice in the plenary, written or digital anonymous input can surface what the open conversation cannot.

Reflections on helping the group make sense of underlying issues, patterns and root causes

Groups rarely struggle because they lack insight. More often, their thinking moves too quickly from experience to conclusion. Observations, interpretations and judgements collapse into a single statement delivered with certainty. When this happens, disagreement centres on competing opinions rather than on how those opinions were formed, and the conversation becomes progressively harder to move without someone conceding ground.

A core task of facilitation is to slow this leap just enough for the group to see its own reasoning. This begins with separating what is being observed from what is being assumed, and with helping the group distinguish between facts, opinions and guesses. Facts are observable and verifiable. They include data, behaviours, events and direct experience. Opinions sit one step above: they reflect interpretation, judgement and belief. Guesses occupy the least stable ground: they are assumptions about causes, intentions or future outcomes that have not yet been tested. When facilitators invite participants to notice which of these they are speaking from, the fog that often surrounds difficult group discussions begins to lift. Conversations slow. Curiosity replaces certainty. The group becomes more able to test its thinking rather than defend it.

One of the most practically useful tools for supporting this kind of sensemaking is the ORID method, developed by the Institute of Cultural Affairs as a focused conversation framework. ORID stands for Objective, Reflective, Interpretive and Decisional, and its value lies in the discipline it enforces: preventing the group from collapsing observation, reaction, interpretation and decision into a single undifferentiated conversation.

At the objective level, the group is invited to name what it knows for certain: what has happened, what data exists, what has been observed repeatedly. This stage often feels deceptively simple, yet it is frequently rushed. Taking time here surfaces gaps, inconsistencies and assumptions about what the group “knows” before interpretation has begun. Groups regularly discover at this stage that what seemed like shared factual ground is more varied than expected.

At the reflective level, the group names its reactions: what concerns it, what energises or unsettles it, what surprised or frustrated it. This is not therapy. It is a way of preventing emotion from leaking unacknowledged into later analysis. When reactions are surfaced early, discussions about meaning and action tend to be clearer and less charged.

At the interpretive level, patterns and root causes begin to emerge. Because facts and reactions are already visible, the group is better placed to explore what might be driving what it is seeing: what themes recur, what tensions have not been resolved, what underlying dynamics might be shaping the surface behaviour. Questions at this level focus on meaning rather than on blame or premature solution.

Only then does the group move to the decisional level, where it considers what to do next. At this point, decisions tend to feel more grounded because they rest on shared understanding rather than on the partial views and unspoken concerns that typically shadow conversations that have skipped the earlier stages. I was personally trained in ORID by the ICA, and I would recommend this investment to any facilitator who works regularly with groups navigating complex sensemaking.

Peter Senge’s work on mental models, developed through the systems thinking tradition and most accessibly presented in The Fifth Discipline, offers a complementary lens. Senge argues that groups are rarely limited by the complexity of their situation but by the mental models through which they perceive it: the deeply held assumptions and images through which they make sense of experience. When these models remain invisible, groups repeat the same patterns regardless of the content they are working on. Making mental models visible, whether through the Ladder of Inference, assumption mapping or structured sensemaking conversations, is among the most powerful things a facilitator can do to help a group break out of a pattern that is limiting its effectiveness.

Seven practices that help me support sensemaking about underlying issues and patterns

1. I separate observation from interpretation explicitly. When I invite the group to name what it has directly observed before offering its interpretations, the quality of the subsequent sensemaking conversation almost always improves. The factual ground becomes shared rather than assumed.
2. I introduce the facts-opinions-guesses distinction when conversations are stuck. Asking “is that a fact, an interpretation or a guess?” is rarely received as a correction. It tends to land as a clarifying question that the group finds useful.
3. I use ORID as a sensemaking structure when the group needs to work carefully through complexity. Moving from objective to reflective to interpretive to decisional prevents the premature problem-solving that consistently shortchanges the quality of analysis in groups under time pressure.
4. I ask about patterns rather than causes. “What do we keep coming back to?” and “Where does this issue seem to show up again and again?” tend to surface systemic understanding more effectively than “why is this happening?”, which often produces defensive answers rather than genuine inquiry.
5. I slow the pace deliberately at the interpretive stage. Insight rarely arrives quickly. I build in time for the group to sit with what it is noticing before moving to conclusion, and I hold the space when that sitting feels uncomfortable.
6. I help the group notice its own assumptions about root causes. Asking “what do we have to believe for this explanation to make sense?” helps the group examine the foundations of its analysis rather than simply debating the conclusions.
7. I invite the group to name what it has not yet looked at. “What might we be avoiding, or what angle have we not yet considered?” regularly surfaces the most significant insight of the sensemaking conversation, because it is precisely the thing the group found it easiest not to name.

Reflections on assisting the group in reflecting on its experience

Groups learn far less from what they do than from what they take time to notice. Meetings are full of activity, decisions and discussion, yet without deliberate reflection much of the learning remains implicit or is lost entirely. Assisting a group to reflect on its experience is therefore not an optional closing ritual. It is a core facilitation practice that turns participation into insight and activity into intention.

Research on experiential learning, most comprehensively developed by David Kolb, demonstrates that experience alone does not produce learning. What produces learning is the cycle of experience, reflection, conceptualisation and experimentation that Kolb’s model describes. Groups that act without reflecting, or that reflect without connecting their reflections to changed practice, are completing only a fraction of the learning cycle. The facilitator who creates deliberate space for reflection at the right moments is not slowing the group’s progress. They are completing a cognitive process that experience alone leaves unfinished.

Roger Greenaway’s Four Fs model, developed through outdoor and experiential education, offers a practically useful structure for leading reflection that honours the full complexity of the group’s experience. The four stages, Facts, Feelings, Findings and Future, are not a checklist. They are a sequence of inquiry that ensures different kinds of information are given their proper place before the group moves to conclusions or commitments.

Reflection begins with facts, because groups rarely share the same picture of what actually happened. Memory is selective, attention uneven and meaning is added quickly. Inviting participants to name observable events, decisions, moments that shifted the direction or energy of the work, establishes a shared reference point and often surfaces quiet differences in perception that are important data in their own right. Questions at this stage focus on what happened, what was said or decided, what moments stood out.

From facts, the conversation moves to feelings: the emotional responses that shaped how people experienced the work. These are frequently present but unspoken, and when they remain unspoken they distort later sensemaking and commitment. Surfacing feelings is not about therapy or disclosure for its own sake. It is about recognising emotional data so it does not operate invisibly in the conversation that follows. Asking how the process felt at different points, or where people felt energised, uncertain or frustrated, normalises reaction and reduces defensiveness in the subsequent interpretive work.

Only once facts and feelings are visible does the group turn to findings: the interpretive heart of the reflection, where meaning begins to form. Here, facilitators help the group notice patterns across what happened and how it was experienced. Assumptions are surfaced, dynamics named and early explanations tested. Questions at this stage ask about patterns, recurring themes, what might be driving what the group experienced. This stage benefits from slower pacing because insight tends to emerge gradually rather than through quick analysis, and because it requires the group to stay with uncertainty long enough for something genuinely new to surface.

Finally, the reflection turns toward the future: ensuring that learning does not remain abstract. The aim is not to generate long action lists but to translate insight into intention. Groups consider what they want to carry forward, what they might do differently and what they need to pay attention to next time. Questions here anchor reflection in practical commitment without overwhelming it with obligation. One or two clear intentions tend to have more lasting impact than an exhaustive improvement plan.

Beyond the task-level reflection that the Four Fs supports, there is a deeper layer of learning available to groups that is easily missed: process-level learning about how the group itself functions. Groups typically focus their reflection on content, what was decided and what needs to happen. Process learning by contrast asks how the group arrived at its decisions, what conditions helped it think well, which patterns appeared again that have appeared before. This kind of learning travels: it shows up in future sessions under different topics and different pressures. When facilitators create space for it, they are not adding a layer of complexity. They are building the group’s capacity to work more effectively without requiring a facilitator to be present every time.

Seven practices that help me assist groups to reflect on their experience

1. I build reflection into the session design rather than treating it as something that happens if time permits. Reflection that is planned for is qualitatively different from reflection that is squeezed into the last five minutes. I protect time for it as I would protect time for any other essential phase of the work.
2. I use the Four Fs sequence when the group needs to reflect on a significant experience. Moving through facts, feelings, findings and future in order prevents the collapse of these different kinds of information into a single undifferentiated conversation, and consistently produces richer and more actionable learning.
3. I begin with facts to establish shared ground. Before the group reflects on what an experience meant, I invite it to describe what happened. This reduces the divergence in interpretation that occurs when different people’s experiences of the same event have never been compared.
4. I create space for feelings before interpretation. A brief round naming how the process felt, without analysis or justification, prevents emotional residue from contaminating the sensemaking that follows.
5. I keep future commitments proportionate. One or two clear intentions that the group genuinely believes it will act on are worth more than a long list of improvements that will not survive the demands of the week ahead.
6. I create space for process-level reflection as well as task-level reflection. Questions about how the group worked together, what helped it think well, what patterns it noticed in itself, produce learning that travels beyond the current session and builds collective self-awareness over time.
7. I frame reflection as inquiry rather than evaluation. The purpose of reflection is to learn from experience, not to judge performance. The questions I use and the tone I bring to reflection signal this distinction clearly, and it shapes how openly the group is willing to engage.

The payoff

When groups become genuinely aware of how they are engaging with their task, the quality of their work changes in ways that are visible and lasting. Conversations become more intentional. Decisions rest on clearer understanding of what the group actually knows and what it is assuming. Outcomes feel more honest because the process that produced them was more honest.

Facilitating group self-awareness does not slow things down unnecessarily. It prevents wasted effort. It helps groups choose their pace rather than being driven by habit. It surfaces the information that incomplete conversations leave on the table. It creates the sensemaking that turns content into insight. And it builds the reflective capacity that allows groups to learn from their experience rather than simply accumulate it.

The lasting payoff is capability. Groups that have worked with a facilitator who consistently holds D2 begin to internalise its practices. They start to notice their own pace, check their own assumptions and create their own moments of reflection without prompting. Meetings become less about managing information and more about doing purposeful work together. The group becomes more able to see the work while doing the work, and that doubled awareness is one of the most reliable foundations for sustained high performance.

Frequently asked questions about IAF Core Competency D2: Facilitate group self-awareness about its task

What does IAF Core Competency D2 actually mean in practice?
D2 is about helping a group notice how it is approaching its work while the work is still in motion. This includes awareness of pace, participation, information flow, assumptions, emotional tone and emerging patterns. The facilitator does not analyse the group from the outside or correct behaviour. Instead, they create moments where the group can observe itself and make more conscious choices about how to proceed. It is the competency that transforms a technically competent facilitation into one that builds the group’s own capacity.

How is D2 different from general process management?
Many facilitation activities support the task indirectly by managing time, structure or content. D2 is distinctive because it focuses explicitly on the group’s awareness of its own working. Rather than directing content or managing transitions, the facilitator draws attention to how the group is engaging: when it is rushing, circling, avoiding a topic or relying on untested assumptions. D2 is less about directing and more about helping the group see what is already happening so it can make a more conscious choice about whether to continue.

How do I apply D2 without slowing the group down too much?
D2 does not require lengthy pauses or extended meta-discussion. Effective interventions are usually brief and well-timed. A single observation, a well-placed question or a moment of structured silence can be enough to shift awareness and adjust the group’s trajectory. When done well, D2 prevents the wasted effort that comes from working confidently in the wrong direction. It tends to save more time than it uses.

What if the group resists reflection or finds meta-discussion frustrating?
Resistance usually reflects pressure, fatigue or concern about time rather than opposition to the underlying value of reflection. In these situations, D2 interventions need to be tightly connected to the task and framed in practical rather than reflective terms. “What do we need to pay attention to if we want this decision to hold?” tends to land better than an invitation to open-ended reflection. As the group experiences the practical benefit of brief awareness interventions, resistance tends to reduce.

How do I know when to offer a D2 intervention?
The most reliable signals are shifts in energy, repetition without learning, apparent agreement that feels thin, visible disengagement or a conversation that has been circling the same point without development. These signals suggest that the current way of working is no longer serving the task as well as it could. The intervention is not triggered by the facilitator’s preference but by what the group is showing. Observational judgement improves significantly with practice and with the habit of reviewing one’s own facilitation responses after sessions.

What is the most useful thing I can do when a group seems stuck?
Slow the conversation and help the group notice where it is. Stuck groups are often trying to move forward without a shared picture of what they are working with. A brief sensemaking pause, using facts-opinions-guesses or the objective level of ORID, regularly reveals that the group has different understandings of the same situation. Naming this explicitly almost always creates movement, because the group stops trying to resolve a disagreement it did not know it was having.

Does D2 apply in technical or expert environments?
Yes, and often with greater impact than in generalist groups. In technical or expert environments, assumptions can go unchallenged precisely because everyone in the room shares similar frameworks and training. D2 helps surface the assumptions that expertise makes invisible. It supports better judgement, reduces the risk of collective blind spots and improves decision quality without undermining the expertise the group depends on.

How does D2 build long-term group capability?
When groups regularly experience facilitation that supports self-awareness, they begin to internalise these habits. Over time, they notice their own patterns earlier, adjust pace more deliberately and create their own moments of reflection without needing a facilitator to prompt them. The group becomes less dependent on external guidance and more able to regulate its own working effectively. This shift, from event support to capability building, is one of the most significant contributions a facilitator can make to an organisation’s long-term functioning.

How do I use ORID without it feeling formulaic?
ORID becomes formulaic when it is applied mechanically regardless of what the group needs. Its power lies in the discipline of sequence, not in the rigid use of four named stages. In practice, I often use ORID invisibly: structuring my questions so that the conversation naturally moves from observation to reaction to interpretation to decision, without ever naming the framework to the group. When the framework serves the conversation rather than constraining it, it feels like a particularly good conversation rather than a technique.

What is the difference between reflecting on content and reflecting on process?
Content reflection asks what the group produced, what was decided and what needs to happen. It is necessary but it does not tend to change how the group works. Process reflection asks how the group arrived at its decisions: what helped it think well, what patterns appeared, what conditions supported or hindered its best work. Process reflection travels: it shows up in subsequent sessions under different topics and pressures. When facilitators make space for both, they give groups the learning that lasts beyond the outcomes of any single session.

What has helped you create moments of group self-awareness without disrupting the flow of the work?

How do you help a group slow down enough to notice what it is assuming, when the pressure to move forward is strong?

What small reflection practices have made the biggest difference to how a group works over time?

Thanks for reading!

Explore IAF Core Competency D: Guide group to appropriate and useful outcomes

This article is part of a three-part series on guiding groups to results.

• D1: Guide the group with clear methods and processes
• D2: Facilitate group self-awareness about its task (You are here)
• D3: Guide the group to consensus and desired outcomes