Featured on this episode:

• Join The Designers Edge here
• Grab Your Free Script Guide here
• Access the full video interview with Elana Steele of Steele Appliance here

What you will learn from this episode:

• The five most common reasons construction projects feel harder than they should
• Why that low hum of unease on a project is information, not noise
• Exactly what the early conversations look like 

---

I want to start by asking you to think about a project.

It might be a current one. It might be one you finished recently. One where something felt hard from the beginning, not catastrophically hard, but harder than it should have been. Where your energy felt heavier than the scope of work warranted, or where you were working hard and things still felt slightly uphill.

The conventional wisdom around it is basically: some projects are just like that. Some clients are difficult. Some contractors are a headache. Some jobs are just complicated. So we push through, we deliver, and we move on.

There’s truth in that. Not every hard project is preventable. But here’s what I want to say directly, especially to the designers who have been doing this for a long time: a lot of the projects that feel hard from the start didn’t have to. They feel hard because of a handful of small moments that went unaddressed. And by the time the hardness is undeniable, those moments where you could have done something are long past.

The Cost of Managing Through

Designers who have been in this business for ten, fifteen, twenty years know this feeling well. They’ve also gotten very good at managing through it. The stamina, the professional composure to deliver a hard project without it ever being visible to the client, that competence is real and it’s earned.

But being able to manage through a hard project is not the same thing as knowing how to prevent one. And the cost of consistently managing through hard projects, in energy, in time, in that quiet depletion that never shows up on any invoice, that’s what I want to examine today.

Because those early moments are decision points. And most of us blow past them without recognizing them as such.

The Five Reasons Construction Projects Feel Harder Than They Should

In my experience, the reasons tend to cluster into recognizable patterns. And once you can name them, you start to see them much earlier and much more clearly.

1. A Scope of Work That Wasn’t Fully Defined Before Work Began

I know I’m a broken record about scope of work. There’s a reason for that. This one is so common it almost goes without saying, and yet it keeps happening — even to experienced designers who genuinely know better.

A project starts with enthusiasm and momentum and a general sense of what’s involved. The detailed scope conversation gets deferred because everyone’s excited and slowing down to get specific feels like a momentum killer. And then the project is underway, and the specifics start revealing themselves, usually in the form of things nobody accounted for. Decisions that need to be made that nobody budgeted time for. A client who has a different picture in their head than the one you’re working from.

Experience can actually work against us here. We’ve navigated enough undefined scopes successfully that we trust ourselves to figure it out as we go. And we’re right, we can. But figuring it out as you go has a cost that shows up in your time and energy, even when it doesn’t show up in the outcome.

2. Expectations That Weren’t Set Clearly at the Beginning

What does your role actually include on this project? What decisions is the client making, and what decisions are you making? What does the contractor expect from you in terms of communication and availability, and what do you expect from them?

When those conversations happen clearly and early, everyone is working from the same map. When they don’t happen, or when they happen vaguely, in passing, without anyone landing on a shared understanding, the project runs on assumptions. And assumptions on a construction project collide at some point. Usually loudly and uncomfortably.

3. The Right Conversations Happening Too Late

The client who needed to understand the full construction timeline before they committed to the project, but that conversation happened after they signed. The contractor walkthrough that should have happened before the proposal was built, but happened afterward. The budget conversation that needed to be frank and specific, but stayed polite and general because it felt too early to push.

These aren’t failures of intent. They’re failures of sequence. The information was available. The conversation was necessary. It just happened at the wrong point in the process, which meant the decisions it should have informed had already been made.

4. Early Signals About a Client Relationship That You Ignored

This is the hardest one to talk about, because it requires acknowledging that sometimes we see a signal and choose not to act on it.

The client who couldn’t make a clear decision in your discovery call, and you told yourself they’d be more decisive once things got real. The one whose questions in early meetings had a little edge to them that you explained away as thoroughness. The one who mentioned what the last designer got wrong in a way that left you quietly uneasy, but you filed it away, thinking it was the designer’s fault, not the client’s pattern.

Those signals are information. Not verdicts — information. And a designer with the right process knows what to do with that information rather than setting it aside and hoping the project smooths itself out.

For experienced designers, this pattern is particularly worth examining. The more experience you have, the more confident you are in your ability to manage a difficult client relationship. The signals you might have heeded earlier in your career start feeling more manageable than cautionary. That confidence is earned, but it can also be expensive.

5. Project Complexity That Was Underestimated Before Anyone Signed Anything

Construction projects have a way of looking simpler from the outside than they turn out to be from the inside. The renovation that was supposed to be straightforward until the walls came down. The scope that seemed contained until the contractor started asking questions that revealed how much hadn’t been accounted for. The timeline that seemed reasonable until the lead times came back.

Complexity isn’t always visible up front. But the variables that contribute to it often are, if you slow down long enough to look for them before you commit to a number, a timeline, and a scope of work.

How Designers Respond to That Feeling (And Why None of Them Work)

Here’s the thing about all five of those patterns: they don’t announce themselves as problems. They arrive as a feeling. A hunch. That low hum that something’s a little off and you’re not quite sure what.

And what most designers do with that feeling falls into a few predictable responses.

The first is to push through and hope it smooths out. 

The project is underway. The client is engaged, the contractor’s on site. Stopping to address something you can’t fully articulate feels like you’re creating a problem rather than solving one. So you keep moving and tell yourself it’s going to work itself out.

The second is to decide it’s a people problem rather than a process problem. 

That client is just high maintenance. That contractor is just disorganized. People problems feel like something you can manage through personality and patience, through your ability to read the room and handle difficult relationships, rather than something you address through structure. This framing is especially common for experienced designers because we are genuinely good at people management. It works often enough that it becomes our default response.

The third is to work harder. 

More communication, more availability, more of yourself poured into the project to compensate for whatever is creating the friction. This is the response that gets projects delivered on time and produces clients who say glowing things about you. And you are depleted in a way that has nothing to do with the scope of work you agreed to.

What nobody does in that moment — and this is what I really want you to sit with — is recognize that these are all decision points. That low hum, that sense that something’s off, that hunch? The project is telling you that something needs to be addressed. Not eventually. Now. While there is still time to address it cleanly, before it compounds into something that’s much harder to untangle.

That feeling is not a problem to manage through. It is information to act on.

What It Actually Looks Like to Act On It

It starts with recognition, not just of the feeling, but of what the feeling is pointing to.

A designer with the right process doesn’t just note that something feels off. She asks: what specifically is creating this? Is it a scope of work that wasn’t fully defined and needs to be? An expectation set loosely that needs to be made explicit? A conversation that hasn’t happened yet but clearly needs to? A client dynamic that’s been present since the beginning that you’ve been managing around rather than addressing?

Taking that inventory, even a quick one, even just asking yourself that question, changes what’s possible. A vague feeling of unease is very hard to act on. A specific identified gap in the scope or a specific conversation that needs to happen is completely actionable.

The Language That Gets a Project Back on Track

Knowing how to have the conversation is where a lot of designers, even experienced ones, feel less equipped. Not because they lack communication skills — they don’t. But because the conversations that get a project back on track have a specific quality to them. They need to be direct without being alarming. They need to surface a potential problem without framing it as a crisis. They create alignment without creating anxiety, and they happen early enough that they feel like professional diligence rather than damage control.

Here’s what that actually sounds like.

Let’s say you’re two weeks into a project and the client is making decisions slowly, keeps reopening things that feel settled, and you can feel the timeline starting to compress. The instinct is either to push harder on the decisions or to say nothing, nudge gently, and absorb the delay.

But the conversation that actually needs to happen sounds something like: “Mrs. Smith, I want to check in with you on these open decisions. Not because anything is urgent today, but because I want to make sure we stay ahead of the timeline and you don’t feel rushed later. Do you have time this week to work through them together?”

That’s it. Not alarming. You’re not implying they’re doing anything wrong. You’re a designer managing the project proactively and inviting the client into that process with you.

Or let’s say you’re in early conversations with a contractor you haven’t worked with before and you’re noticing their communication is looser than you’re used to. Things are getting answered eventually, but not on the timeline you need. Rather than waiting until that becomes a real problem, the conversation sounds something like: “John, I really want to set us up for success on this project. I find things run more smoothly when we establish a rhythm early. Can we talk about how we prefer to communicate and what our timelines look like for decisions and updates? Can we take a look at the schedule together and define the milestones?”

Professional and direct. You’re not accusing anyone of anything. You’re building a structure before the absence of one creates the problem.

Both of those conversations are completely natural one or two weeks into a project. Neither requires a confrontation. Both simply change the course of what’s coming next.

That specific combination of directness and reassurance is a skill. It’s not a personality trait. It develops with practice and with having a clear sense of what you’re trying to accomplish in the conversation before you start it.

The Willingness to Slow Down in Order to Go Faster

I know that sounds counterintuitive on a construction project where momentum and consistency matter and everyone is watching the timeline.

But the designer who pauses at that first signal and addresses it — who says, before we go any further, I want to make sure we’re all on the same page — that’s the designer who doesn’t lose three weeks at the back end of the project untangling something that could have been resolved in a twenty-minute conversation in week one.

What’s on the Other Side

When you have a framework for recognizing those signals and acting on them early, when you’re not relying purely on instinct or stamina to get through hard parts, something shifts in how you show up on construction projects.

Those projects don’t become effortless. Construction is inherently complex and unpredictable, and there will always be moments that require you to pivot and adapt. But the quality of the difficulty changes. Instead of that low-grade heaviness that runs underneath everything from the start, the hard moments become specific and addressable. You know what you’re dealing with. You have somewhere to put it and the language and the process to handle it, rather than constantly absorbing it.

And your client relationships change, too. Clients can feel the difference between a designer who is managing through difficulty and one who is leading through it. Managing through something looks like everything getting handled somehow, with effort that isn’t always visible. Leading through a project looks like clarity, confidence, and a professional who knows exactly what to do next.

For experienced designers, especially, this is where the shift shows up most meaningfully. Not in whether you can get through a hard project, we already know you can. But in whether you have to. And in what you could do with the time and energy you’re currently spending compensating for problems that a cleaner process would have caught earlier.

The Goal Isn’t to Never Have a Hard Project

The goal is to know when a project starts to feel hard, know exactly what to do about it, and do it early enough that the project has a chance to become something different.

That’s what process gives you. Not a guarantee, a way through. And more than that, it gives you the ability to build a construction practice in your firm that is genuinely sustainable. One that doesn’t depend on your ability to push through indefinitely. One where hard moments are the exception rather than the story of every project. One where you finish a project and the fee reflected the work, because the work was what it was supposed to be, not what it became because several small moments went unaddressed at the start.

That version of this business is completely possible. It is not reserved for designers with a particular personality type or a particular level of experience. If anything, the more experience you have, the more work it sometimes takes to unlearn the habits that have gotten you this far but are quietly costing you.

The process is learnable. And it is far more available to you than most designers realize.

Like this episode?

Be sure to check out Episode #278: Why Your Construction Projects Feel Like You Worked for Free

Be sure to check out Episode #274: The 4 Moments Interior Designers Cross from Consultant to Construction Manager

Be sure to check out Episode #272: The Conversations Designers Avoid with the Hot Young Designers Club