Heat maps for coupling in mobile release trains

We borrowed heat-map language from print magazines: deep ember for blocking dependencies, golden highlights for shared DTO packages that look harmless but stall trains. The exercise lives inside Service Boundaries for Mobile Release Trains, but the blog version distills the worksheet. Paragraph two covers facilitation: rotate who holds the marker every ten minutes so the loudest engineer does not own the color legend. Quiet participants often spot duplicate serializers first. The third paragraph is about follow-through: photograph the wall, transcribe hotspots into your activity log, and schedule a boundary test before the next release window. Without that step, the heat map becomes wallpaper.