liveBook · Manning

Double signal

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

A set of conflicting signals in which spoken words do not align with tone, actions, or other nonverbal cues.

A double signal appears when spoken words conflict with tone, posture, eye contact, actions, or other nonverbal cues. Treat the mismatch as evidence that something important may be unspoken. section 5.1.1

A downplayed back-office problem

A department head says the back office only needs minor improvements and should not be a priority. Their tense posture and avoidance of eye contact suggest otherwise. Frequent system downtimes, delayed customer responses, and clerical errors strengthen the signal that a significant problem remains unaddressed. section 5.1.1

Use the mismatch as a prompt for investigation:

  • Compare stated opinions with tone of voice, posture, eye contact, and actions. section 5.1.1
  • Look for concrete evidence rather than treating reassurance as the complete account. section 5.1.1
  • Consider whether fear of repercussions, judgment, or conflict is making the issue unsafe to discuss. section 5.1.1

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

How deep it goes
Defines the mismatch, illustrates it through posture and eye contact, and connects it to safety without prescribing a full intervention.
Examples
Uses a COO meeting, downplayed back-office issues, tense posture, avoided eye contact, downtimes, delays, and clerical errors.
What you can do after
Diagnose hidden concerns by comparing words, tone, body language, and concrete operational evidence before accepting reassurance.
How it connects
Connects nonverbal communication with psychological safety, conflict, and operational problems.

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.