liveBook · Manning

Hot check-in

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

A hot check-in is a session-opening activity that immediately addresses an active conflict or contentious design question.

A hot check-in opens a session by immediately entering an active conflict or contentious design question. It can surface views on the current design, architecture, or the value of an architect, but may raise pressure rather than create understanding. section 8.3.2

Avoid adding this pressure when conflict is polarized. Directly challenging opposing sides can reinforce polarization, push people toward choosing sides, and worsen the conflict. section 8.3.2

Use a lighter alternative

Instead, center shared needs and business problems. Run short networking rounds with prompts about personal reservations and the current reservation flow; ask participants to report what they heard from someone else, encouraging listening over reaction. section 8.3.2

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

How deep it goes
Defines the move and contrasts its polarization risk with a lighter listening-oriented check-in.
Examples
Uses questions about design quality and architect value, plus reservation-flow anecdotes shared through three networking rounds.
What you can do after
Evaluate/understand it: recognize when direct conflict entry may add fuel to polarization and choose a lighter check-in.
How it connects
Connects polarization, conflict resolution, business problems, impromptu networking, and listening to understand.

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.