liveBook · Manning

Self-fulfilling prophecy

As explained in Collaborative Software Design: How to facilitate domain modeling decisions

A process in which an expectation influences behavior in ways that cause the expected outcome to occur.

A self-fulfilling prophecy occurs when an expectation shapes behavior until the expected outcome becomes more likely. In collaborative modeling, assumptions about a group’s needs, biases, or preferred tools can influence facilitation and reinforce the original assumption. section 7.3.1

When a modeling tool is not used

During an EventStorm session, participants returned to private discussion instead of visualizing their ideas. Without more structure, the group stayed with traditional methods, which could confirm an expectation that the new tool was unsuitable. Later, facilitators used lessons from that experience to anticipate bias and add nudges during an Example Mapping session at BigScreen. section 7.3.1

Avoid the cycle by treating collaborative tools as aids rather than complete solutions: provide structure, guidance, and support; question assumptions about the group; and examine the facilitator’s own biases. section 7.3.1

Figure 7.4 An example of how an Example Mapping looked at BigScreen. The groups are divided and are using index cards on the table to collaboratively model and discover new scenarios and acceptance criteria.

Use the Example Mapping arrangement to see how divided groups use index cards to discover scenarios and acceptance criteria collaboratively. section 7.3.1

How Collaborative Software Design: How to facilitate domain modeling decisions covers it

How deep it goes
Explains the risk through EventStorm and Example Mapping experiences, then recommends structure, guidance, support, and nudges.
Examples
Uses an unsuccessful EventStorm session and a later BigScreen Example Mapping session with structured nudges.
What it assumes
Assumes familiarity with collaborative modeling tools while emphasizing that facilitators must not assume they understand group needs or biases.
What you can do after
Apply it via bias-aware facilitation that structures tool use and challenges assumptions about group needs.
How it connects
Connects cognitive bias with collaborative modeling, Example Mapping, EventStorm, facilitation, and acceptance criteria.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Collaborative Software Design: How to facilitate domain modeling decisions. The section links point to the parts of the book it draws on.