liveBook · Manning

Silent person

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

A silent person is a participant who has difficulty expressing views or concerns and whose contributions are consequently given less consideration by the group.

A silent person has difficulty expressing views or concerns, so the group may implicitly rank their contributions lower and give them less consideration. section 6.2.2

A concern dismissed before production

In a software design discussion, a quiet participant raises a concern that the group does not take time to understand. The idea is easily dismissed, and the resulting problem becomes visible only after implementation and deployment to production. section 6.2.2

The pattern matters because it can:

  • Hide problems in the chosen design until the solution has already been implemented. section 6.2.2
  • Reduce the group’s ability to use concerns and ideas as proactive input during development. section 6.2.2

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

How deep it goes
Defines the social pattern and traces its consequence from dismissed concerns to problems discovered after production.
Examples
Uses a silent participant whose dismissed concern becomes a design problem after implementation and production deployment.
What you can do after
Evaluate design discussions for overlooked concerns before implementation and production deployment.
How it connects
Connects silent people with ranking, software design, testing, and proactive development input.

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.