Future search, developed by Marvin Weisbord and Sandra Janoff, is a structured large-group planning meeting that brings the whole system into the room to find common ground and produce action commitments.

Distinctive feature among large-group methods: it is tightly designed. Unlike open-space-technology, the agenda is fixed; the content is entirely the participants'.

Evidence: Weak. Case-based, largely documented by its developers, with no controlled trials. Two design choices have independent support: getting the whole system in the room reflects the boundary-spanning finding that cross-unit contact reduces attribution error between groups, and the public admission step draws on well-established reciprocity and intergroup contact research. The three-day format and the five-task sequence are convention.

Use when: a complex issue crosses organizational boundaries, requires many parties to act, and no single party can solve it alone.

Do not use when: one organization can simply decide; when the sponsor wants a predetermined outcome; when key stakeholders will not attend.

The four conditions

  1. Get the whole system in the room. All stakeholders with Authority, Resources, Expertise, Information, and Need — the ARE IN mnemonic. Typically 60–80 people in eight mixed stakeholder groups.
  2. Explore the whole before seeking to fix parts. Global context before local action.
  3. Focus on common ground and desired futures, treating problems and conflicts as information rather than as items for action. Areas of disagreement are recorded and explicitly not worked on.
  4. Have people manage their own groups and take responsibility for their own actions.

The five tasks, over three days

Classically sixteen hours across three days, so that participants sleep twice — the overnight processing is part of the design.

  1. Review the past. Groups build timelines of the last few decades: personal, organizational, and global. Establishes shared history and shows that the present had causes.
  2. Explore the present — external trends. Build a "mind map" of forces affecting the topic, then each stakeholder group identifies which trends it is acting on.
  3. Explore the present — owning our actions. Each stakeholder group reports what it is proud of and what it is sorry about in relation to the topic. This session does the emotional work that makes day three possible, and it is the one sponsors most often want to cut.
  4. Create ideal future scenarios. Mixed groups present a future as though it already exists, in whatever form they choose.
  5. Identify common ground and plan action. Confirm shared ground publicly, record differences without debating them, then form voluntary action groups with named commitments and dates.

Why "prouds and sorries" matters

Asking each stakeholder group to state publicly what it is not proud of, in front of the others, changes the room. It converts an adversarial framing into a shared one faster than any facilitation technique, because each party has already conceded something. Skipping it — because it is uncomfortable and consumes three hours — is the most common way to hollow out a future search.

Managing conflict by not working it

The counterintuitive rule: differences are acknowledged, recorded on a flip chart, and not resolved. Groups work only on what they agree about.

The rationale: common ground is nearly always larger than expected, and it is sufficient to generate substantial action. Attempting to resolve deep conflict in a three-day meeting consumes the whole meeting and resolves nothing. This also means future search is not the right method when the conflict is the issue.

Examples by audience

  • Health care: designing an integrated care pathway with hospital clinicians, primary care, social care, ambulance, commissioners, voluntary sector, patients, and carers in one room. No single organization controls the pathway, which is exactly the condition future search is built for.

  • Software: useful for platform or standards decisions spanning many teams and business units, where a central mandate would be resisted and no team can act alone.

  • Executive: for cross-sector or ecosystem issues — regional skills, supply chain resilience, industry standards — where the executive's own organization is one actor among many.

Limitations

  • Logistically demanding: three days, 60–80 people, senior time.
  • Requires genuine stakeholder attendance; a missing party invalidates the premise.
  • Skilled facilitation is essential; the design is unforgiving of improvisation.
  • Action commitments are voluntary, so follow-through needs deliberate support in the weeks afterwards — schedule the first check-in before people leave.

See also

Organizational Development — a comprehensive practitioner's guide to OD for health care professionals, software engineers, and senior executives. Every framework says what the evidence is, and where it is weak.

Source and contributions: github.com/organizational-development. Built with the Lily Design System™.