Couldn’t agree more on the references part—those glossy portfolios can be pretty misleading. I’ve found that even the most impressive designers sometimes gloss over the day-to-day communication or how they handle pushback. I get that professionals have experience and might know pitfalls I don’t, but there’s a difference between offering advice and steamrolling your preferences.
One thing I’ve learned: if a designer can’t explain *why* something’s “not standard” in a way that makes sense for your specific situation, it’s usually just their personal taste or habit talking. I had one try to talk me out of a mudroom because “nobody does that anymore.” Turns out, it’s my favorite part of the house.
At the end of the day, you’re the one paying and living there. If they can’t respect that, it’s probably time to move on.
At the end of the day, you’re the one paying and living there. If they can’t respect that, it’s probably time to move on.
Nailed it. Here’s how I look at it—building a home is way more personal than people think. It’s not just about trends or what’s “in” right now. You want a mudroom? That’s your call, not theirs.
Here’s how I’d break down the hiring process:
- **Interview more than one designer.** Don’t just go with the first person who wows you with a slick portfolio. Ask about their process, how they handle disagreements, and what they do when a client wants something unusual.
- **References matter, but dig deeper.** When you talk to past clients, ask about communication style, flexibility, and whether the designer respected their vision. Did they push back constructively or just bulldoze?
- **Ask for stories, not just pictures.** “Tell me about a time you disagreed with a client and how you handled it.” That’ll tell you way more than any staged photo.
- **Insist on explanations.** If someone tells you something’s “not standard,” make them explain why it doesn’t work for *your* situation. Sometimes there’s a legit reason (budget, code, logistics), sometimes it’s just their own preference.
- **Get everything in writing.** Scope, fees, timelines, revision process—if it’s not clear up front, it’ll bite you later.
One thing I’ll add: sometimes designers see pitfalls you don’t, but the good ones will walk you through it instead of just saying “no.” I had a client who wanted a laundry chute in a spot that would’ve been a nightmare for plumbing. We talked through options and ended up finding a better spot together. It’s all about collaboration.
At the end of the day, your home should fit your life—not just someone else’s idea of what’s cool or current. Trends come and go... but you’re the one walking through that mudroom every day.
WHERE DO YOU EVEN START WITH HIRING SOMEONE TO DESIGN YOUR HOUSE?
Couldn’t agree more—if you’re not being heard, it’s a red flag. I’d add: don’t underestimate the value of site visits with your designer before you sign anything. Sometimes what looks good on paper just doesn’t work with the land itself. Had a project where the “perfect” plan ignored a killer view... total waste. You want someone who’ll walk the lot with you and actually listen to what matters most. That’s how you end up with a place that feels right, not just looks trendy.
Couldn’t agree more about the site visits—there’s just no substitute for seeing how a design fits the actual land. I’d also say, don’t get too caught up in flashy portfolios. I’ve seen designers with stunning renderings who just don’t “get” the practical stuff, like drainage or sun exposure. Sometimes the less glamorous details make or break a project. If they’re not asking about things like utilities or local zoning, that’s another warning sign. It’s not just about the look, it’s about how the house actually works on your lot.
WHERE DO YOU EVEN START WITH HIRING SOMEONE TO DESIGN YOUR HOUSE?
I hear you on the practical details, but I wouldn’t write off a strong portfolio either. Sometimes those “flashy” renderings actually reveal a designer’s ability to communicate ideas clearly. Had a client once who picked someone with only technical chops—great with code requirements, but the end result was bland and didn’t really feel like home. There’s a balance to strike, I think... you want both vision and practicality.
