Improvement practices stall when people closest to the work lack the knowledge, safety, or authority to act. Respect for people is the system property that gives them the authority, information, and psychological safety to improve the work. section 13.0 section 13.1
In software, this means making it possible to raise concerns in design reviews, pull requests, and retrospectives—and responding with gratitude and action rather than defensiveness or dismissal. The response teaches people whether speaking up helps improve the system or whether silence is safer. section 13.1
Look for structural signs that respect is built into the work:
- People can follow shared work practices, and cross-training prevents critical knowledge from depending on one person. section 13.1
- Developers have authority to surface problems and influence outcomes; shared ownership distributes knowledge, though it adds coordination overhead. section 13.1 section 13.9
A software andon moment
A developer flags a subtle race condition during code review. A constructive response treats the warning as useful information and acts on it; dismissal teaches the developer not to raise the next concern. section 13.1
