Breadboarding maps logic, not layout. The strength is that it keeps the review focused on whether the system makes sense before anyone responds to how it looks. Once you introduce layout, people respond to the layout: spacing, visual weight, type choices pull attention away from structure. [[Stop spending time on wireframing]] describes exactly this trap. A breadboard shows how parts connect and what happens when a user takes an action, without triggering the visual response that derails the structural conversation.
Starting with a breadboard defers visual decisions until the logic is settled. [[Look for rabbit holes]] is easier at this stage, when everything is still provisional and edge cases can be followed without undoing polished work. [[Fat-marker method]] is the physical version of the same constraint, and [[Use your hands to think]] is the practice behind both: working by hand introduces a resistance that keeps thinking at the structural level before the visual decisions close it down.