Dominant Ideas

Dominant Ideas is a seven-step peer-consultation structure in which the group listens not to the presenter's situation but to the beliefs underneath it. The presenter tells briefly where they are stuck; for ten minutes the group names the assumptions it hears in the story — "a good teacher solves this alone", "if I keep asking I'm being difficult" — without advising and without judging, while the presenter listens and takes notes. Then the group lists the ideas, the presenter says which ones they recognise, everyone names one alternative way of seeing it, and the group discusses what this yields for the presenter and for the team. Made for standing groups of four to eight colleagues, and for a presenter who keeps hitting the same wall in different situations — not for a case that asks for a decision.

Check one thing before the first run: does the group understand what a dominant idea is? Not an opinion and not a mistake, but a belief that steers the thinking without being spoken — "a good tutor is always available", "conflicts get settled straight away". Say it once out loud before step 2, with an example that is not the presenter's, and add that naming is different from judging: the group says what it hears, not whether it is true.

Group size

circle of 4–8 colleagues

Duration

40–50 min per case

Level

upper secondary+ · teams

Materials

pen and paper, a board for the list

Format

one circle, one presenter per round

Goal

see the beliefs under a pattern

The flow at a glance

35 min total
the presenter speaksthe grouptogetherin silence

The minutes above are a starting point, not a script: whoever prepares the structure sets the time per step. The thirty-five minutes of steps become forty to fifty in practice, once settling into the circle and the reflection at the end are counted. One step carries the method and keeps its ten minutes: naming the dominant ideas — the second round of naming is sharper than the first, and it only comes after a silence. With four colleagues the alternatives are named in three minutes; with eight, four minutes is tight.

Step-by-step instructions

7 steps

Bringing in the case

3 minthe presenter speaks

The presenter describes their situation briefly and concretely, says where they are stuck and closes with their question to the group.

Looking for dominant ideas

10 minthe group

Participants name the beliefs and assumptions they hear in the story: "I hear: a good teacher solves this alone." No advice, no judgement — the presenter listens and takes notes.

Taking inventory

3 mintogether

The group lists all the beliefs named, on the board or on paper, and picks the two or three that matter most. The presenter may now ask clarifying questions.

The presenter responds

5 minthe presenter speaks

The presenter says which beliefs they recognise as their own, what surprises them and what they reject — no defending, there is nothing to set straight.

Formulate alternatives

4 minthe group

Everyone in turn takes one dominant idea and puts a different idea next to it: not "he must…", but "you could also see it like this". One alternative per person; the presenter listens.

Discuss the yield

5 mintogether

What does the presenter take away, and which idea does the group recognise in itself? Dominant ideas rarely belong to one person.

Evaluation

5 mintogether

The group looks back at the process, not at the case: what went well, where did it become advice after all, what will we do differently next time?

One case per round. A second presenter starts again at step 1; the player runs one round per name entered in the preparation and closes with the reflection questions.

Why does this work?

Whoever keeps hitting the same wall in different situations rarely has a problem with the situations. The problem is in what they believe about themselves and their work — and that is exactly what they cannot hear themselves, because it feels self-evident. Dominant Ideas lets the group say it out loud, and does three things to keep that safe.

Naming is different from judging

In step 2 the group says what it hears, not whether it is true: "I hear: a good teacher solves this alone". That sentence form does the work. A piece of advice ("he should really…") asks the presenter to do something, a judgement ("he is too much of a perfectionist") asks them to defend themselves; a naming asks them only to listen. Guard the form strictly — at every "he should" you ask: which belief do you hear underneath? — and let silences stand. The first round of naming is predictable; the second, after the silence, is the round the method exists for.

The presenter listens and writes, until step 4

As long as the presenter joins in, they defend: at every named belief they explain why it is justified in their case. So in step 2 they listen and take notes, and only in step 3 do they ask clarifying questions. In step 4 they do not have to judge anything for truth — the trap the player names — but only say which ideas they recognise as their own and which surprise them. Recognition is enough; agreement is not needed. Whoever hears themselves say "a good tutor is always available" once, through a colleague, does not need convincing.

Alternative ideas, not an action plan

Step 5 puts a different idea next to each dominant one — "you could also see it like this: a good teacher knows when to ask for help" — and no step-by-step plan. That is not half-heartedness but the point: whoever swaps a belief changes their own behaviour in ten situations at once, while an action plan solves one. And because dominant ideas rarely belong to one person, step 6 pulls it wider than the case: which idea does the team recognise in itself? The most interesting insight of a round usually lies in what the whole group turns out to believe.

When it fits, when it doesn't

When it fits

  • When someone keeps hitting the same wall. Three different classes, three times the same irritation; three parents, three times the same conversation that gets stuck. When the situations differ and the pattern stays, the problem is rarely in the situation — and that is exactly what this method looks for.
  • With a presenter who has already tried everything. Whoever says "I have really tried everything" has tried everything within one belief. Advice does not help them any more; a different idea does.
  • In a team that wants to examine itself. Step 6 asks which idea the group recognises in itself. A team that has done three cases has its own dominant ideas listed — "we solve it ourselves", "we don't bother each other" — and that is worth more than three pieces of advice.
  • In a standing peer-consultation group that can already listen. Ten minutes of naming without advising asks for a group that already knows the Gossip Method or trio advice. The structure is not harder than those two, but the discipline of step 2 is new.
  • With a case without a clear incident. "I can't get my team on board, however I explain it" has no moment and no ending, so it does not fit the Incident Method. Here it is a perfect case: the belief sits in the sentence itself.

When it doesn't

  • When a decision is needed. The method yields other ways of seeing, not a choice and not steps; the presenter decides afterwards what to do with it. If the team is stuck on one concrete moment and wants to know what to do then, take the Incident Method — it ends with alternatives and a decision.
  • With one isolated incident. One student who slammed the door once carries too few beliefs to name for ten minutes; the group will start inventing. Ask the presenter whether it happens more often and in other forms — if so, it is a pattern and the structure fits; if not, the Incident Method is the better choice.
  • With a question of values. "May I promise a student something I am not sure of?" is not about an unconscious assumption but about a conscious weighing, and that asks for inquiry rather than naming. The Socratic conversation is made for it: the same group, and the four virtues as a language.
  • With a group that has only just met. Hearing which beliefs colleagues hear in your story takes a trust that is not there yet in a first meeting; the group then names only what is safe. Start such a group with trio advice, and come back here after two or three sessions.
  • Without explaining beforehand what a dominant idea is. A group that does not know the concept names behaviour in step 2 ("he is strict") or gives advice. Say it once before step 2, with an example that is not the presenter's: a dominant idea is a belief that steers the thinking without being spoken — and the group says what it hears, not whether it is true.

Examples by context

Teaching team"I can't get my team on board with the new approach, however I explain it" — the case from the preparation screen. The group hears: if I explain it well, they will come along. That is where the conversation starts.
Form tutors and pastoral careA tutor who wants to solve every student's problem personally and is burning out. Named: a good tutor does not refer on. Alternative: a good tutor knows when to refer on.
School leadershipA head of department who wants to settle every conflict immediately and notices the team avoiding them. The group hears: calm in the team is my responsibility. Step 6: does the whole leadership team believe that?
Health and social careA youth worker who stays too long with every family. Named: if I leave, I abandon them. The same seven steps; the alternatives are about boundaries, not about this family.
Vocational and higher education placementsA student who never asks a question on placement. The group hears: a good trainee already knows. One of the dominant ideas of every training programme — and step 6 makes that visible.
Coaches and trainersA trainer who experiences every quiet group as a failure. Named: energy is my responsibility. Alternative: silence is work.

Variations

With the list on the board have one group member write down every naming in step 2 immediately, visible to everyone. Step 3 is then half done, and in step 4 the presenter sees five readings of their situation side by side — that overview is often the moment they recognise their own idea.
The presenter takes notes give them a sheet in step 2 with two columns: I recognise, surprises me. Writing keeps the hands busy at the moment the reflex to respond is strongest, and their response in step 4 becomes more concrete.
With a second naming round after the first five minutes of step 2, half a minute of silence, and then: what are we not hearing yet? The second round is almost always sharper — the player says so too — and the silence is what makes it possible.
As a team inquiry three cases from three colleagues in three sessions, and the lists from step 3 kept. At the third session the group lays the three lists side by side: what comes back? That is the team's own list of dominant ideas, and the yield of step 6 writ large.
Short, in a team meeting set the steps to 2-7-2-3-3-3-3 and the round fits in half an hour. Shorten the short steps, not the naming: that is the method, and under seven minutes the second round does not come.
With the live link with the player on one screen, every group member follows the same step, the same time and the case text on their own screen through the live link. Handy in step 2, for re-reading the presenter's sentences without asking them anything.

By age

Primary and lower secondary. Not for this age. The structure asks the group to hear the beliefs under a story — abstractions about what a good student or a good friend is "supposed" to do — and asks the presenter to hear those about themselves without responding. That abstraction is not there yet, and the presenter is too exposed. To talk about such beliefs in class, take Four Corners with statements like "a good student never asks for help": the class picks a corner and defends its choice, and nobody has to put their own story on the table.
Upper secondary (16+). Possible, in a tutor group that has been together for a while, with three conditions: the presenter volunteers, the case is about a situation — a part-time job, a placement, a project that got stuck — and you sit in the circle to guard step 2. Explain beforehand what a dominant idea is with an example from their world ("a good student does everything alone"), keep the naming to five minutes and have the presenter take notes.
Vocational and higher education, teacher training. The strongest use in education, because every training programme has its own dominant ideas and students absorb them unnoticed — "a good trainee already knows", "asking questions is weakness". A case from a placement brings them to the surface, and step 6 shows the group that the idea is not the presenter's alone. Groups of five or six, three quarters of an hour, the list on the board.
Adults: teams and peer consultation. The setting the structure was made for. The hardest part here is step 2: professionals hear a problem and want to solve it, and "he should really…" is the first sentence to fall. At every piece of advice ask which belief sits underneath, let silences stand, and use step 6 for what the method yields most in a team: what does the whole team turn out to believe?

Common mistakes

Advice instead of naming. "He should really…" is the sentence that derails step 2 most often. Ask: which belief do you hear underneath? — and the adviser names after all. After twice the group does it themselves.
Naming behaviour instead of beliefs. "He is strict" is not a dominant idea; "I hear: without strictness I lose the class" is. The sentence form "I hear: …" helps: what follows has to be something the presenter could believe.
The presenter judges every idea for truth. "No, that's not right, because…" — and the response becomes a defence. Ask instead: which of these steers you the most? Recognition is enough, agreement is not needed, and what they reject they may reject without explanation.
The first silence gets filled. After three minutes of naming it goes quiet, and the facilitator moves to step 3. The second round, after that silence, is the sharp one — let it stand and ask: what are we not hearing yet?
The alternatives become an action plan. "So first he has to…" does not belong in step 5. An alternative is a different idea — "you could also see it like this" — not a step. If a plan comes anyway, ask which belief sits underneath it.
The yield stays with the presenter. Step 6 also asks what the group recognises in itself. Whoever skips that question misses the insight the structure yields most in a team: that the presenter's belief turns out to be the team's belief.
The list does not get written down. Five namings in the air are forgotten after step 3. Write them on the board: a list shows that one situation gets read in five ways, and the presenter chooses from what they see, not from what they remember.

Frequently asked questions

What exactly is the Dominant Ideas method?

A peer-consultation method for a standing group of four to eight colleagues, in seven steps around one case. The presenter briefly describes their situation and the question they are stuck on (three minutes); the group names which beliefs and assumptions it hears in the story, without advice and without judgement, while the presenter listens and takes notes (ten minutes); the group lists all the ideas named and picks the two or three that matter most (three minutes); the presenter says which ones they recognise as their own and which surprise them (five minutes); everyone in turn names one alternative idea (four minutes); the group discusses the yield for the presenter and for the group (five minutes); and the group looks back at the process (five minutes). The second step is the method: the group says what it hears, not what the presenter should do.

What is a dominant idea?

A belief that steers thinking and action without being spoken — and usually without you hearing it yourself, because it feels self-evident. "A good teacher solves this alone." "If I keep asking I'm being difficult." "Calm in the team is my responsibility." Such ideas are not wrong; they are invisible, and that is the problem: whoever keeps hitting the same wall in different situations acts from the same idea in all of them. The group does hear it, because the idea sits in the wording of the story — in what the presenter takes for granted, in what they do not consider. The sentence form the method uses, "I hear: …", is deliberate: what follows has to be something the presenter could believe, not a description of their behaviour.

How long does a round take?

The seven steps add up to thirty-five minutes with the default times: 3, 10, 3, 5, 4, 5 and 5. With settling into the circle, the transitions and the reflection questions at the end, one case comes to forty to fifty minutes in practice — plan it as the whole subject of a session. Whoever prepares the structure sets the time per step; the player counts down. One step carries the method and keeps its ten minutes: the naming. The short steps around it can be tighter, and with four colleagues the alternatives are named in three minutes. Two cases in one session are an hour and a half with a break.

How big should the group be?

Four to eight, in one circle. Below four the group hears too few different ideas in the same story — and that variety is the point of steps 2 and 3; above eight the naming becomes a string of separate remarks and the alternatives round lasts longer than it stays sharp. The player allows three to twelve so that a group just under or over the mark can still run, but the method is made for four to eight. Split a larger team into two circles, each with its own case.

What does the presenter do during the naming?

Listen and take notes, and not respond — not even when a naming seems unfair to them. The moment they explain why a belief is justified in their case, they are defending, and the group stops naming and starts asking questions. In step 3 they may ask clarifying questions about the list, and in step 4 they say which ideas they recognise as their own, which surprise them and which they reject — without explanation. The trap, the player says, is that they start judging every idea for truth; ask instead which idea steers them most. Recognition is enough; agreement is not needed.

How do you facilitate the Dominant Ideas method?

Three things carry the round. One: the explanation beforehand. Before step 2, say in one sentence what a dominant idea is, with an example that is not the presenter's, and that the group says what it hears and not whether it is true. Two: the line in step 2. At every "he should really…" you ask which belief sits underneath; at every description of behaviour ("he is strict") you ask what he believes then. And let the silence stand: the second round of naming only comes after half a minute of nothing, and is sharper than the first. Three: the list. Write the namings on the board, pick two or three together in step 3, and use step 6 for the question that makes the method yield most in a team: which idea does the group recognise in itself? The player does the rest — and as the facilitator, do the structure once as the presenter yourself.

What if the group only gives advice?

That is the standard mistake of step 2, and it has one remedy: the question "which belief do you hear underneath?". A piece of advice always contains an idea — whoever says "he should ask for help" hears "a good teacher solves this alone" — and after converting twice the group does it themselves. If that does not help, give the first example in the right sentence form yourself: "I hear: if I explain it well, they will come along." And say beforehand that the advice has its place in step 5, in the form of a different idea: whoever waits in step 2 gets their turn in step 5.

What is the difference from the Gossip Method?

In both the presenter listens for a step to what the group says about their situation, but the group says something different. In the Gossip Method the group talks freely about the case — what stands out, what we would do — and the yield is an honest mirror of the situation. In Dominant Ideas the group names only beliefs, in one sentence form, and the yield is a mirror of the thinking behind it. Rule of thumb: Gossip Method for one situation that chafes; Dominant Ideas for a pattern that returns in different situations.

What is the difference from the Incident Method?

The Incident Method examines one moment with a choice in it: the incident is told without its ending, the group analyses and writes alternatives, and it ends with what the presenter did or will do. Dominant Ideas examines not a moment but a pattern, and ends not with action but with a different way of seeing. Choose the Incident Method when the team wants to know what you do in such a moment; Dominant Ideas when the presenter has already tried everything and it still keeps coming back.

Can the method be used in class?

In upper secondary it can, in a tutor group that knows each other, with three conditions: the presenter volunteers, the case is about a situation outside the classroom, and you sit in the circle to guard step 2 — with an explanation beforehand of what a dominant idea is, in their own world. From vocational education onwards and in higher education it is one of the strongest peer-consultation structures for placements, because every training programme has its own dominant ideas and students absorb them unnoticed. Younger than upper secondary it does not fit: hearing the beliefs under a story requires an abstraction that is not there yet. For the class, Four Corners with statements about such beliefs does the same work without putting anyone on the chair.

Does the method work online?

Yes, and the list of step 3 is even easier online: have everyone type their namings in step 2 into the chat in the form "I hear: …", then the list is already there when step 3 starts, and the presenter sees all the readings side by side. The presenter mutes their microphone in step 2 — listening without responding is easier online than in a circle — and unmutes in step 3. Share the player's screen or give everyone the live link, so every participant has the step, the timer and the case text in front of them.

Where does the Dominant Ideas method come from?

The method comes from Dutch peer-consultation practice (intervisie) and is described in the Praktijkboek Intervisie by Monique Bellersen and Inez Kohlmann, alongside the Gossip Method and the Incident Method. The idea behind it — that people act from beliefs they no longer hear themselves, and that a group can hear those beliefs in the way someone tells their story — has two sources outside intervision: Peter Senge's mental models, the taken-for-granted assumptions that determine how an organisation sees and acts, and the work of Michael White and David Epston on dominant stories, the way one reading of your own situation makes all the others invisible. The form of the method — naming, not judging; alternative ideas, not an action plan — translates those two into a conversation of three quarters of an hour.

Which peer-consultation method do you pick?

StructureGoalGroupDurationWhen it fits
Dominant Ideasname the beliefs under a pattern and put others next to them4–840–50 minpresenter keeps hitting the same wall
Gossip Methodhear honest feedback without defending4–835–45 minpresenter is quick to defend themselves
Incident Methodanalyse one incident blind, to alternatives and a decision5–840–50 minteam doesn't know how to act in one moment
Socratic conversationfind a wise stance through perspective-taking and the four virtues4–830–90 minquestion of values, team wants depth
Trio advicequick advice from two colleagues, in parallel trios3 per group15–20 min per caseeveryone has a question, little time
Pair Coachcoaching questions in pairspairs10–20 mina task instead of a case, in class too

Sources

  • Monique Bellersen & Inez Kohlmann, Praktijkboek Intervisie (Boom) — the Dominant Ideas method as an intervision method in seven steps, with the naming without judgement and the alternative ideas this structure is built on.
  • Jeroen Hendriksen, Intervisie bij werkproblemen (Nelissen) — the ground rules of intervision: standing group, one presenter per round, and why the presenter stays silent while the group speaks about their case.
  • Erik de Haan, Leren met collega's. Praktijkboek intervisie (Van Gorcum) — the difference between examining a case and judging a presenter; the ground under the sentence form "I hear: …".
  • Peter Senge, The Fifth Discipline (1990) — mental models: the taken-for-granted assumptions that determine how a team sees and acts, and why they only change once they have been spoken; the ground under step 6.
  • Michael White & David Epston, Narrative Means to Therapeutic Ends (1990) — dominant stories: how one reading of your own situation makes the others invisible, and why an alternative idea changes more than a piece of advice.

Compiled by Oksana Oliinyk · Last updated 15 September 2026

Was this page useful?

After your answer we ask three short questions — half a minute, and it really helps us.

Log in to leave a comment.

No comments yet. Be the first!