Why I Started the Constructrr Podcast

When I started the Constructrr Podcast in 2016, its mission was clear: help property owners feel more certain about the decisions they make during construction.

In my early schedule work, I saw plans change and communication break down somewhere along the way.

The first episode was my attempt to explain why that problem mattered to me. Project certainty is not created by a plan alone. It grows from the way people, information, and expertise come together when a decision needs to be made.

I kept seeing the gap between the plan and the work

Early in my construction career, I reviewed planned schedules, progress updates, as-built schedules, and delay schedules for a major public program. Rarely did everything go exactly as planned. That is not surprising. Construction is full of changing conditions, dependencies, and decisions.

The episode connected changes in the plan with a breakdown in communication.

In the episode, I called my rough estimate of how often I saw that pattern a guesstimate. The exact percentage matters less than the question it prompted: where does a project lose continuity between evidence, interpretation, and action?

A schedule may show the intended sequence without explaining where communication broke down when the plan changed.

That is why project communication is more than sending another message. It is the design of the handoff.

Project certainty lives in the handoffs

Owners need more than information. They need a dependable path from what the team knows to what someone will do next.

A useful handoff connects what changed from the plan, where communication broke down, whose expertise was missing, and whether the tool fits the project need.

Those connections bring the plan, communication, expertise, and technology into the same discussion.

Certainty does not mean pretending the original plan will hold. It means examining what changed before deciding what the project needs next.

Construction technology needs a specific job

My interest in technology was another reason I started the podcast. I had worked with engineering, design, scheduling, document-management, and collaboration software. The question that kept pulling me in was which tool best fit what a particular project needed to do.

The episode offers a useful way to evaluate construction technology: start with the project need, not the platform.

Ask what work the project needs the tool to support and why that tool fits better than the alternatives.

The right technology should make a recurring decision easier to understand and act on. Its value depends on the context in which people use it.

Trust improves the quality of project information

The founding episode also focused on collaboration. In that conversation, I argued that people need to feel valued and trusted if a team expects them to contribute their expertise.

If people do not feel valued, trusted, respected, and encouraged to contribute, the team loses part of what their expertise could add.

Trust affects what people are willing to say. What they say affects what the team can see. What the team can see affects the quality and timing of the decision.

That is why builders should be involved while design choices can still be shaped, and why the people performing the work should have a meaningful voice in how it is planned. Their knowledge is part of the system, not a soft addition to it.

Start with one decision, not a platform rollout

If this pattern is familiar, choose one recurring project deviation and trace the handoff from first evidence to final decision.

For that recurring deviation, ask:

• What changed from the plan?
• Where did communication break down?
• Whose expertise was missing?
• Does the tool fit the project need?

If an answer is unclear, it may point to a communication gap worth exploring.

Clear handoffs still depend on the people carrying them forward. In the first episode, I said, “Relationships drive this industry.” Relationships do not replace process. They make it possible for concerns, corrections, and expertise to move through that process when they are needed most.