Process consultation — Organizational Development

Edgar Schein's process consultation is a stance rather than a technique. Its definition: "the creation of a relationship with the client that permits the client to perceive, understand, and act on the process events that occur in the client's internal and external environment in order to improve the situation as defined by the client."

The consultant's expertise is in process — how work is done, how people interact, how decisions are made — not in content. The client keeps ownership of the problem.

Evidence: Weak as research, strong as practitioner consensus. No controlled evidence that the process consultation stance outperforms expert or doctor-patient consulting. It is endorsed near-universally in the OD literature, and its central claim — that solutions the client owns survive longer than solutions delivered to them — is consistent with the participation and internalized motivation literatures. Treat it as a well-argued professional stance rather than a demonstrated method.

Use when: the client's diagnosis may be wrong; when the solution must be owned locally; when previous expert recommendations were accepted and not implemented.

Do not use when: the client genuinely needs specialist content expertise and knows it — a legal opinion, a security assessment, a clinical protocol.

Schein's three models of helping

Expert / purchase of expertise. The client defines the problem and buys an answer. Works only if the client diagnosed correctly, communicated accurately, and the expert's answer is implementable in their context. Three fragile assumptions.
Doctor-patient. The client presents symptoms; the consultant diagnoses and prescribes. Fails when the client will not reveal the real symptoms, will not accept the diagnosis, or will not take the medicine. The most seductive model for consultants and the most commonly resisted by clients.
Process consultation. The consultant helps the client diagnose and solve their own problem. Slower to satisfy, more durable in effect, and the only model that builds client capability.

All three are legitimate. The error is defaulting to model 1 or 2 when the situation calls for 3 — which happens because 1 and 2 feel like value delivery and 3 feels like doing nothing.

Principles of humble inquiry

Schein's ten principles, condensed to the ones that carry the weight:

Always try to be helpful. Helping is the purpose, not being right.
Always stay in touch with the current reality. Yours and theirs.
Access your ignorance. The most useful question is the one you genuinely do not know the answer to. Questions you know the answer to are advocacy in disguise, and clients can tell.
Everything you do is an intervention. There is no neutral observation. The first question you ask changes the system.
It is the client who owns the problem and the solution. You will leave.
Go with the flow. Work with the client's energy and readiness, not your plan.
Timing is crucial. The same intervention lands or fails depending entirely on when it is offered.
When in doubt, share the problem. Admitting uncertainty to the client is a legitimate move, and it models the behavior you want.

Humble inquiry in practice

Four kinds of question, in descending order of usefulness for this stance:

Humble inquiry: minimally prompting, maximum curiosity. "Tell me more." "What happened next?"
Diagnostic inquiry: steering attention. "How did you feel about that?" "What do you think caused it?"
Confrontational inquiry: inserting your own idea as a question. "Could it be that the deadline is the problem?" Useful, but it is your content now.
Process-oriented inquiry: turning attention to the interaction itself. "What's happening between us right now?" The most powerful and the most easily mistimed.

Group process observation

What a process consultant watches while a group works:

Who speaks, for how long, and after whom.
Who is interrupted, and by whom.
How decisions actually get made: consensus, default, silence, or the loudest.
What topics produce a change in energy, humor, or pace.
What is raised and dropped without response.
What is discussed in the corridor and not in the room.

Feeding these observations back — descriptively, without interpretation — is often the entire intervention.

Examples by audience

Health care: a team asks for "communication training". Process consultation observes three handovers first, and reports what it saw: the handover is conducted standing in a corridor, interrupted four times, with no structured format and no read-back. That description does more than a course.
Software: a team asks for an architecture review. The process consultant notices that three architecture decisions have been made and reversed, always after the same person's objection, always outside the meeting. The content question is not the problem.
Executive: an executive team asks for a strategy facilitator. The observable process finding — that the CEO speaks first on every item and the discussion converges within ninety seconds — is more valuable than any strategy framework, and much harder to deliver.

Limitations

Slow, and easily read as passive or evasive by clients expecting answers.
Requires the practitioner to tolerate not being the expert, which is professionally uncomfortable.
Contract for it explicitly at entry, or you will be pulled into the doctor role by week three. See entry-and-contracting.