Architecture Decision Records (ADRs) have been characterized as a lean documentation technique, but this overlooks their cultural impact: writing ADRs can also help developers evolve into architectural thinkers. ADRs accomplish this by subtly influencing developers to change four key behaviors: improved appreciation of design’s value, increased design participation, better follow through on decisions, and stronger design engagement. These four complementary behaviors nudge developers to see themselves as software architects, which in turn transforms the team’s culture.