Does Your Project Have a Story Your Team Can See Themselves In?

There is a research laboratory project that Jason Schroeder returns to again and again when he talks about culture. Not because the schedule was perfect or the budget was untouched, but because every single person on that site, from the superintendent to the laborer, believed the same thing about who they were and what they were building. The story was simple: they were the safest, cleanest, and most remarkable project in Arizona. They were delivering to an owner who genuinely cared about their workers. They were better than what the rest of the industry settled for. And they believed it. Not because it was posted on a wall. Because it was said out loud in the morning, every morning, until it became true.

That is what culture actually is. Not a set of values a company wrote in a conference room. A story a group of people believes about themselves.

What Culture Code Gets Right

Jason was revisiting Daniel Coyle’s book The Culture Code when this episode came together, and a concept he had encountered before landed differently this time. The insight is straightforward: culture is the common beliefs and actions of a group. And those beliefs and actions are shaped by the story the group tells about itself. When the story is clear and compelling and repeated consistently, the culture holds. When there is no story, the culture becomes whatever the loudest or most disruptive voice on the site decides it is.

This is why Jason told that research laboratory team the same story every single morning. Not because they had forgotten it overnight. Because repetition is what transforms a statement into a belief. He told them they were better. He told them the owner cared. He told them the industry disrespected people like them but on this project that was not the case. He told them what the end looked like before they were halfway through. And because they heard it every day in the morning huddle, it became the lens through which they made decisions, enforced standards, and held each other accountable.

Five times on that project, a worker approached a visitor who was not following site protocols and, with no supervisor around, said: we do not do that on this job. Five separate incidents. Unprompted. That is what a story that has taken hold looks like in the field.

Why People Join a Story

Jason made a comparison in this episode that is worth examining honestly. People join gangs not because they want the consequences but because they want to belong somewhere. They want significance, certainty, connection, and variety. They want to be part of something that gives them an identity and a role that matters. The gang provides all of that, packaged in belonging and purpose, however destructive the surrounding circumstances.

A construction project can provide the same four things without the destruction. Significance: you are an essential part of something worth doing. Certainty: you know the plan, the end date, and what success looks like. Connection: you are part of a crew that holds itself to a standard and takes care of each other. Variety: you are building something, solving problems, and being recognized when you do it well.

When a project superintendent creates a story that delivers all four of those things, the crew does not need to be managed toward the right behaviors. They already know what the right behaviors are because the story has defined them. The morning huddle is not a meeting. It is a rehearsal of the identity.

Five Elements That Make a Story Work

Jason outlined what has to be true for a project culture to actually take hold and stay held. The story cannot just be spoken once. It has to be embedded across every layer of how the site operates.

What the team does has to be clear. Everyone needs to know not just what their individual task is but what the project is trying to be and how their work connects to that outcome.

What the team does has to be visual. The story has to show up in the environment. A clean, organized, well-lit site tells a different story than a chaotic one. The physical conditions of the project are the culture made visible.

What the team does has to be incentivized. People who live the story need to see that it benefits them. Recognition, appreciation, and visible acknowledgment that the standard is being met all reinforce the behaviors the story is calling for.

What the team does has to be enforced. Not through punishment but through consistency. When someone behaves in a way that is outside the story, the group addresses it. The standard does not move for the convenience of one person.

What the team does has to be made famous. Tour people through the project. Let the workers tell the story. When a foreman explains to a visitor what the site standard is and why, that foreman has just become a character in the story rather than a bystander. That is when culture takes hold at the individual level.

Here are the three enemies of project culture Jason named, the conditions that kill a story before it can take root:

• No connection, meaning no morning huddle, no shared language, no group identity
• No future, meaning workers cannot see where the project is going or what success looks like 
• No emotional safety, meaning people cannot speak up, flag problems, or be honest without consequences

Remove any one of these three and the story collapses. A team that has no future cannot be motivated by one. A team that is not emotionally safe will not enforce the standard on each other. A team with no connection has no group to belong to.

Do Not Let a Crisis Go to Waste

One of the most practically useful points in this episode is Jason’s instruction about what to do when something goes wrong on the project. A crisis is not a threat to the story. It is the most powerful opportunity to make the story real.

When a crisis hits, the leader who stays calm, names the challenge clearly, rallies the crew, and calls on the identity of the group is the leader whose culture survives the pressure. That is when the morning huddle pays off. That is when all those repetitions of who we are and where we are going become operational. The team already knows what the standard is. They know how to respond because the story has already told them.

The leaders who skip the huddles and the daily culture rituals because things are going smoothly are the same ones who have no story to call on when things go wrong. The culture only holds in a crisis if it was rehearsed before the crisis arrived.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

The Challenge

Write down your project story in two or three sentences. Not a mission statement. A story. What is this project trying to be? What does success look like before the end date arrives? What does it mean for the workers to be on this site rather than somewhere else? Then say it out loud in your morning huddle tomorrow. And the day after that. And the day after that. Sixty days from now, you will not have to say it anymore because the crew will already know it. That is when the culture has arrived.

“Culture eats strategy for breakfast.” Peter Drucker

On we go.

FAQ

What makes a project story different from a mission statement?

A mission statement describes an organization. A story gives people a role to play inside something that is happening right now. It answers: who are we on this project, what are we building together, and what does winning look like before we get there?

Why do morning huddles matter for culture?

Because culture is built through repetition. Beliefs do not form from a single conversation. They form from the same message delivered consistently until the group internalizes it. The morning huddle is where the story gets rehearsed every day.

What are the three things that kill project culture?

No connection, no shared future, and no emotional safety. Remove any one of these and the story cannot take hold, regardless of how good the leader’s intentions are.

How does a crisis strengthen culture if the story is already in place?

Because the crisis tests whether the story is real. A team that has rehearsed its identity knows how to respond when things go wrong. The values they have been practicing become the behaviors they default to under pressure.