The SWAP Signal: Founder's Broadcast - Q2 2026

The SWAP Signal: Founder's Broadcast is my quarterly broadcast. 📣

 

Welcome to the first edition of Pattern Recognition.

One of the unique privileges of my work is having a front-row seat to projects across the country. Every week, I'm in the room with architects, engineers, owners, and consultants navigating different project types, different teams, and different challenges. While every project has its own personality, I've learned that the same coordination patterns tend to surface again and again.

This quarterly letter is my opportunity to share those observations - the habits that keep projects moving, the pitfalls that quietly create delays, and the lessons that emerge from seeing hundreds of design teams work through complex problems. My hope is that these insights help you recognize the patterns on your own projects a little earlier, ask better questions, and ultimately deliver better outcomes.

Pattern Recognition Insights from the rooms where projects come together. The Pattern I'm Seeing...

Over the past few months, I've had the opportunity to facilitate planning sessions with project teams across the country. The projects have ranged from recreation and community centers, fire and police stations, and senior and youth residential centers. Different clients. Different delivery methods. Different personalities.

Yet despite all those differences, I've noticed the same coordination patterns emerging over and over again.

Not software problems.

Not staffing problems.

Not scheduling problems.

Coordination problems.

The encouraging part is that these patterns are remarkably consistent. Once you know what to look for, you can often identify them early, before they become missed milestones, late decisions, or expensive rework.

Here are three patterns I've seen repeatedly this quarter. Pattern #1: Meetings Have Become Reporting Sessions Instead of Decision Sessions

Many project teams spend valuable meeting time sharing status updates that could have been communicated beforehand. Everyone leaves informed, but very few decisions have actually been made.

The most efficient teams treat meetings differently. They arrive with updates already shared, allowing the conversation to focus on resolving conflicts, making decisions, and removing obstacles. Their meetings are shorter, more engaging, and far more productive because every agenda item is designed to move the project forward.

Question to consider: If every recurring meeting on your calendar disappeared tomorrow, which ones would actually change the outcome of your project?

Pattern #2: Projects Rarely Slip Because People Aren't Working Hard

I've yet to meet a project team that lacks commitment.

What I do see are incredibly talented people waiting on information they didn't realize someone else was responsible for providing. A structural engineer waiting on an architectural direction. An owner assuming a decision had already been made. A consultant unaware that their deliverable was driving several others.

These aren't performance issues. They're visibility issues.

When dependencies remain hidden, delays feel inevitable. When they're identified early, coordination becomes dramatically easier and teams spend less time recovering from surprises.

Pattern #3: Healthy Projects Aren't the Quietest Projects

One assumption I hear often is that a project without conflict must be a healthy project.

In reality, the strongest teams tend to have the most candid conversations.

They're willing to say:

• "We don't have enough information yet."

• "This milestone isn't realistic."

• "If this decision slips another week, it will affect three other disciplines."

Those conversations aren't signs that a project is struggling... they're signs that the team trusts one another enough to surface problems while they're still manageable.

Silence rarely means everything is fine. More often, it means uncertainty hasn't found a voice yet.

The Common Thread

If I had to summarize the biggest lesson from this quarter, it would be this:

Projects don't become predictable because people work harder.

They become predictable because uncertainty becomes visible earlier.

That's what effective coordination is really about. Not creating more meetings or bigger schedules, but helping the entire team see the same picture at the same time.

When that happens, better decisions follow naturally.

I'd love to hear what patterns you're seeing on your own projects. Some of the best ideas we've incorporated into our facilitation process (and into SWAP PM) have come from conversations with people in the field who simply noticed something worth sharing.

Heather Bemis is the Founder & CEO of SWAP Integration and the creator of SWAP PM, a cloud-based platform that brings structure and clarity to project planning in the AEC industry. A licensed architect with 18+ years of experience, she’s passionate about lean processes, team alignment, and building tools that make collaboration easier and more effective. 📨heather@swappm.com 📨hbemis@swapintegration.com