liveBook · Manning

Respect for people

As explained in Build High Value Software Systems

A system property in which people closest to the work have the authority, information, and psychological safety to improve it.

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

How Build High Value Software Systems covers it

How deep it goes
Defines the system property and explains it through production-line authority and software review, design, and retrospective examples.
Examples
Uses Toyota's andon cord alongside architecture concerns, race conditions in pull requests, and deploy-process hazards.
What you can do after
Apply it by giving developers authority to improve work and responding constructively when they surface risks.
How it connects
Connects Lean and continuous improvement with psychological safety, cross-training, shared ownership, and code review.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Build High Value Software Systems. The section links point to the parts of the book it draws on.