Basic Versus Developmental Facilitation

Definition

Schwarz splits facilitation into two modes on a continuum, distinguished by objective, not technique. In basic facilitation, the facilitator temporarily takes primary responsibility for managing the group's process so the group can solve one substantive problem; once solved, the group is just as dependent on a facilitator for the next problem. In developmental facilitation, the facilitator shares that responsibility with the group and deliberately teaches process skills while the substantive problem gets solved, so the group's dependence on a facilitator decreases over time.

In the Book

Table 3.3 in Chapter 3 lays the two modes side by side across client objective, facilitator role, and process outcome for the client. Schwarz is careful that this is a continuum in practice, not two discrete boxes, and he gives concrete factors that push a group toward one end or the other: whether the group has the time to invest in developing skills, whether it's a temporary body like a task force (where the investment may not pay back), whether membership is stable enough to retain any skills learned, and whether the group actually controls its own process, including its decision rule. He argues developmental facilitation is not simply "better" — it is more systemic and produces deeper learning, but it costs more and isn't warranted for a group that just needs one decision made — while noting that a group claiming to be a genuine self-directed team or a learning organization has no real substitute for it. The same distinction reappears in Chapter 8's discussion of intervention choices: basic and developmental facilitators intervene under the same conditions, but a developmental facilitator additionally intervenes, and reflects with the group, whenever doing so will build the group's own diagnostic capacity.

Why It Matters

This distinction separates two forms of help that look identical from the outside but produce opposite long-term outcomes: one that fixes the immediate problem and quietly preserves the group's dependency on the helper, and one that costs more up front but transfers the capability so the group needs the helper less next time. Any advisory relationship — consulting, coaching, parenting, technical support — faces the same fork, and naming it forces an explicit choice about which one you're actually running, since defaulting into basic mode while believing you're doing developmental work is a common, invisible failure.