Anticipating Problems and Setting Expectations

Episode 21 of Building Better Relationships in Construction, based on Paul Schwinghammer’s chapter on Anticipating Problems and Setting Expectations, emphasizes proactively identifying and communicating potential issues to build trust and prevent surprises. Hosts Alex and Sabrina highlight anticipating problems—like septic decisions or last-minute window changes—so clients understand costs, schedule impacts, and options up front. Clear, matter-of-fact language, concrete examples, and documenting conversations reduce friction, manage expectations, and turn tense moments into “relationship deposits.” Anticipation enables contingency planning, reduces firefighting, and fosters a culture of transparency that trickles to crews and subcontractors. Practical tips include asking clarifying questions for hypothetical statements, explaining ripple effects of changes, offering written options with trade-offs and fees, and training teams to flag ambiguities. The approach improves client experience, strengthens reputation and referrals, and lessens emotional stress. Listeners are encouraged to use the checklist provided and consult Paul’s book for deeper guidance and practical implementation examples.

Transcript

SPEAKER_00 0:09

Welcome back to episode number 21 of our podcast series: Building Better Relationships in Construction. This episode is based on the book Building Better Relationships: A Guide to Enhancing the Customer Experience for Home Builders, Remodelers, and Construction Managers by Paul Schwinghammer. I'm Alex.

SPEAKER_01 0:28

And I'm Sabrina. Today we're pulling from Paul's chapter on anticipating problems and setting expectations. Lots to dig into here, and we'll try to keep it conversational and practical.

SPEAKER_00 0:40

Right. So Paul opens with a simple but powerful idea. Anticipate problems before they happen. Don't wait for surprises. When you can see potential issues coming, you can talk about them early. And that completely changes the dynamic with your client.

SPEAKER_01 0:59

Exactly. Think of yourself as a navigator, someone watching for storm clouds. If you point them out early, the client doesn't feel blindsided later. Instead of, what happened? It becomes, okay, we saw it, we talked about it, here's the plan. That's huge for trust.

SPEAKER_00 1:17

There's a great example Paul uses about septic systems. A client casually says they might handle the septic separately, maybe hire another contractor or do parts themselves. If you ignore that comment, it can come back as a surprise. Later, the client expects you to manage bills or pay fees. And then you've got friction.

SPEAKER_01 1:39

Right. So Paul's recommendation is to name that possibility right away. Say something like, I hear you might handle the septic yourself. If you keep it in the contract but want us to manage payments, we'll need to add a 15% processing fee because of the extra admin work. Want me to include that option in the agreement? Short, clear, and honest.

SPEAKER_00 2:00

That example shows how anticipation removes ambiguity. The client knows the cost and the consequence up front. No mystery fees, no hurt feelings, and even if the client decides to do it themselves, the fact you raised it makes you look proactive and trustworthy.

SPEAKER_01 2:16

There's a broader lesson there that applies outside construction too. Paul points to retail. If a store excludes TVs from a sale but there's no sign, customers feel cheated. The frustration isn't about the policy, it's about the lack of clear communication.

SPEAKER_00 2:33

So true. A simple sign, a short sentence, a heads up. Those small acts of communication prevent a lot of dissatisfaction. In construction, the complexity is higher, so the payoff from anticipating is bigger.

SPEAKER_01 2:47

Let's talk about change orders or last-minute requests. Paul talks about window changes during trim stage. A client asks to swap a window, and it sounds like a small request until you factor in rework, schedule delays, and hidden costs.

SPEAKER_00 3:02

Instead of just quoting a price, Paul suggests explaining the ripple effects. Changing this window now could require significant rework and may cost more. I want you to know that before you decide, that little pause, that honest framing, sets expectations.

SPEAKER_01 3:20

It does a few things. It sets realistic cost and schedule expectations, reduces future disappointment, and demonstrates you care about their experience, not just the quick sale. It also moves the conversation from reactive to collaborative.

SPEAKER_00 3:34

And that matters. When a client hears you thinking through consequences, they start treating you like a partner. They also start to expect transparency as the norm.

SPEAKER_01 3:44

Paul calls this expectation setting a strategic deposit in the relationship bank account. I love that phrasing. Each time you anticipate a problem and communicate it clearly, you're building trust, like putting money in an account.

SPEAKER_00 3:58

Yes, and that deposit pays dividends when real problems happen. You've already established credibility. Clients are more likely to accept inconvenient news because they've seen you be honest before.

SPEAKER_01 4:10

It also reduces firefighting. If you've mapped out likely issues, you can build contingencies into the plan. So when things go sideways, because they will, you're not improvising in front of a client. You're executing a known plan.

SPEAKER_00 4:24

There's also the team and culture angle Paul highlights. When leaders anticipate and communicate, subs and crews pick up that mindset. It becomes the way you operate. Transparency trickles down.

SPEAKER_01 4:36

Which is essential. Imagine a field crew that keeps surprises to themselves. The office gets blindsided, but if the culture is to raise potential problems early, the project runs smoother.

SPEAKER_00 4:48

Let's give a couple of quick practical phrases people can use on the job. Paul encourages language that's matter-of-fact and kind. For example, I want to flag something that could affect schedule and cost. Or a heads up. If we change this now, here's what it will do to timeline and budget.

SPEAKER_01 5:07

Another one.

SPEAKER_00 5:20

And when you don't know the full outcome yet, say so. I don't have the exact number today, but I want to flag the potential for extra cost and give you a ballpark. Clients appreciate honesty over certainty when certainty isn't possible.

SPEAKER_01 5:35

Paul also reminds us that expectation setting isn't just about avoiding negative surprises, it strengthens brand reputation. Clients who experience that level of candor are more likely to refer you, come back for future work, and speak positively about your business.

SPEAKER_00 5:52

There's a loyalty component. People don't just remember that the job finished. They remember how they felt during the process. Did they feel informed, respected, heard? Those feelings drive repeat business.

SPEAKER_01 6:06

Another practical point. Document these conversations. If you've anticipated a problem and offered options, capture that in writing an email, a note in the project management system. So everyone has the same reference.

SPEAKER_00 6:19

Good point. Documentation prevents memory-based conflicts later. If it's written, it becomes part of the project's roadmap.

SPEAKER_01 6:27

One more behavioral tip from Paul: train your team to look for ambiguous statements. Clients will often speak hypothetically. We might want to do X. Teach your team to follow up with clarifying questions. If you mean to keep that in the scope but want us to manage it, would you want us to add our processing fee to cover administration? That small follow-up avoids the we assumed problem.

SPEAKER_00 6:52

To sum up, anticipation, clarity, documentation, and a culture of transparency. Those are the core actions Paul recommends. They're deceptively simple, but they require discipline.

SPEAKER_01 7:03

Discipline. Clients prefer honesty. They'd rather know the truth than be surprised.

SPEAKER_00 7:18

Let's be real. This isn't just about protecting margins. It's also emotional labor. When you anticipate and explain, you're managing the client's emotional experience. You're reducing stress for them. That's part of customer service.

SPEAKER_01 7:33

And that emotional management is a differentiator. Most builders focus on schedules and specs. Those who also manage feelings and expectations stand out.

SPEAKER_00 7:43

Nearing the end here, one practical checklist for listeners to use on their next project. One, ask clarifying questions when clients make hypothetical statements. Two, offer options with clear trade-offs. Three, put potential fees or consequences in writing. Four, train your team to flag ambiguities. Five, celebrate the relationship deposits when you do this well.

SPEAKER_01 8:10

That's a useful list. And remember, this approach isn't about being defensive, it's about being service-oriented. It's saying, we see what could go wrong, we'll help you decide, and we'll be transparent about costs and time.

SPEAKER_00 8:26

Before we close, Sabrina, I know you wanted to include Paul's availability note for listeners.

SPEAKER_01 8:32

Yes. Remember, you can purchase your copy of the groundbreaking book, Building Better Relationships, a guide to enhancing the customer experience for home builders, remodelers, and construction managers by author Paul Schwinghammer on Amazon and Barnes Noble in multiple formats.

SPEAKER_00 8:48

Great. Final thought. Your job really isn't about you, it's about your client's experience. Anticipate problems, set expectations, and you'll build stronger relationships and smoother projects.

SPEAKER_01 9:00

That's it for episode 21. Thanks for listening. If you found this useful, tell a colleague and let us know what you want us to cover next.

SPEAKER_00 9:08

See you next time. And remember to check out Paul's book for more practical guidance.

SPEAKER_01 9:13

Bye for now.