Respect for People

REGISTER! 07/16 WEBINAR: Introduction to Lean Project Delivery

REGISTER! 07/22 WEBINAR: LCI A3 Thinking: Continuous Improvement in Action

Home / Respect for People

What Respect for People is and What It Is Not

In the AEC industry, Respect for People is frequently misread as a call to be polite, positive, or conflict averse. It is not. It is a disciplined practice of building conditions, both operational and cultural, where people can do their best work, raise problems early, and grow in capability over time.

This requires two things working together:

Culture: the daily human behaviors that shape how people are treated, heard, and included.
Operations: the systems, processes, and workflows that either support or undermine the people doing the work.

Fixing a broken handoff process, eliminating unnecessary wait time, or clarifying who owns a decision are all acts of Respect for People. When the work is improved, the worker is respected. Lean teams pursue both continuously, because a healthy culture cannot survive broken systems, and better systems mean nothing without the behaviors to sustain them.

Why It Matters: The Research

The AEC industry carries real mental health risk. Construction workers represent only 7.4% of the U.S. workforce but account for more than 17.9% of deaths by suicide. Adversarial relationships, unclear expectations, and siloed information do not just create friction. They produce measurable harm to the people doing the work and to the projects themselves.

surveying AEC workers across trades, disciplines, and regions found:

More than 1 in 3 workers reported their job was more stressful than they ever imagined.
Nearly 1 in 3 feared that job stress could make them physically or mentally ill.
56% reported little interest or pleasure in doing things over the past month, a clinical indicator of depression risk.
46% reported feeling down, depressed, or hopeless during the same period.

The same research found that specific Lean practices produced measurably different outcomes. When teams used tools regularly, 93% of workers felt valued by their team compared to 63% who never used them. When workers strongly agreed that regular took place, 100% felt a sense of belonging. When management visibly committed to health and safety, workers who feared job stress would make them ill dropped from 71% to 24%.

These numbers make the case clearly: how work is organized and led directly shapes whether people feel safe, connected, and capable of contributing.

Respect for People is not a substitute for clinical mental health support, and Lean practices do not replace professional help. However, it directly influences the environment where people spend most of their time, affecting whether they feel valued, included, and safe enough to speak up. This matters immensely in the AEC industry, where mental health challenges and suicide risk remain serious, complex issues with many causes. While leadership cannot diagnose or solve clinical mental health struggles, they can influence daily stress levels by improving the quality of communication, teamwork, and baseline respect.

If someone on your team may be in crisis: Encourage them to call or text 988 (U.S. and Canada) for free, confidential, 24/7 support.

The Four Pillars: What It Looks Like Daily

LCI’s Four Pillars translate Respect for People from a value into observable daily behaviors.

Pillar	What It Looks Like in Practice
Attentiveness & Empathy	Giving your full attention while actively listening; genuinely understanding and caring about your own and others’ feelings.
Integrity & Candor	Honoring your words, owning your actions, and communicating with clarity, courage, and kindness.
Equity & Trust	Inspiring inclusion, honoring diversity, and empowering all by embracing each person’s uniqueness.
Empowerment & Impact	Equipping individuals to take ownership, contribute intentionally, and drive meaningful influence on people and projects.

The Operational Side: Improving the Work and the Worker

The cultural side cannot stand alone. Operational systems must also reflect Respect for People by removing the obstacles, waste, and uncertainty that make work harder than it needs to be. Improving the conditions of work is itself an act of respect.

Operational Element	What It Looks Like in Practice
Continuous Improvement (Overarching)	Every person at every level is expected to identify problems, surface them without fear, and participate in making the work better. Improvement is not a department; it is a daily responsibility.
Flow of Work	Resources, information, and work itself move without unnecessary interruption or waiting. People have what they need, materials, decisions, drawings, when they need them, so work can proceed as planned.
Standardized Work	The current best-known method is documented and followed consistently. This creates a stable baseline from which problems become visible and improvements can be measured.
Improving the Work	Teams regularly examine how work is done and eliminate waste, rework, and friction. When a process is broken, the process is fixed, not the person working within it.
Improving the Worker’s Capability	People are given training, feedback, and opportunities to grow in skill and judgment over time. Developing people is treated as an investment in the work, not a cost.

Respect for People Across Three Levels

Respect for People looks different depending on where decisions are made. Here is what it requires, and what its absence looks like, at each level.

Production Level

What it looks like:
A design change is identified mid-project. Rather than the architect issuing a revision without consulting downstream stakeholders, the team brings together the owner, engineers, and trade partners to discuss the impact before the change is formalized. Concerns are raised, trade-offs are weighed, and the decision accounts for the whole project, not just one discipline’s preference.

Without it:
Changes are made in isolation. Downstream teams absorb the disruption, work around it, and stop raising concerns because experience has taught them it will not change the outcome.

Organizational Level

What it looks like:
A recurring breakdown is identified at the handoff between design and construction documentation. Rather than each side blaming the other for incomplete information, leadership from both firms maps the handoff together, identifies where coordination breaks down, and redesigns the process. The fix addresses the system, not the individuals caught in it.

Without it:
Departments and firms operate in silos. When errors surface at handoff, the instinct is to find who dropped the ball, not to examine the process that made the breakdown likely.

Enterprise Level

What it looks like:
Before rolling out a new enterprise project management platform across all offices and project types, leadership holds listening to sessions with project managers, field leads, designers, and owner representatives. They learn that several teams are mid-project and cannot absorb a system change without disrupting active work. The rollout is phased accordingly, protecting both the people and the projects.

Without it:
The platform launches on a fixed timeline regardless of project load. Teams comply on paper and maintain workarounds in practice. Leadership is surprised when adoption fails and blames user resistance rather than examining how the rollout was handled.

Start This Week

Respect for People does not start with a training or a kickoff meeting. It starts with the next decision you make, the next problem that surfaces, and the next conversation you have. Here are four concrete actions you can take immediately, regardless of your role.

Action	What to Do
Map Who Is Missing	Identify one decision currently in progress on your project or in your department. List everyone affected by it. If anyone is missing from the conversation, bring them in before the decision is finalized.
Find One Friction Point	Ask your team: where do you waste the most time waiting, searching, or redoing work? Pick one recurring breakdown and commit to addressing the process behind it rather than working around it.
Create One Opening	In your next team meeting, explicitly invite dissent. Ask: “What are we not seeing?” or “What concern has not been raised yet?” Then listen without defending.
Separate the Person from the Problem	The next time something goes wrong, before assigning blame, ask: “What about our system or process allowed this to happen?” Document what you find.