Why Great Architects Struggle as Firm Owners

Why Being a Great Problem Solver Makes You a Struggling Architecture Firm Owner

TL;DR:

The problem-solving skills that made you a great architect can sabotage your firm's growth
Most firm owners get trapped in "Tactical Whack-a-Mole"—solving easy problems while real issues fester
Leadership isn't about solving every problem; it's about selecting which problems deserve your attention
Mike Sweebe went from 500 wrong inquiries to a 60% conversion rate by solving the right problem
Your firm needs you to evolve from problem solver to problem selector

There's a quote I came across recently from Wes Gay that stopped me mid-scroll:

"Being a problem solver is overrated... A leader's job isn't to solve problems; the job is to clarify which problems ought to be solved."

My first reaction? That's ridiculous. Problem solving is literally what architects do.

My second reaction? He's absolutely right. And it explains a lot about why so many talented architects struggle to grow their firms.

Here's the uncomfortable truth: the very skill that made you a successful architect might be the thing holding your firm back.

Let me explain.

You Were Trained for This

From day one of architecture school, you were taught to solve problems. Complex architectural problems. Elegant problems. Problems involving gravity, light, human behavior, municipal codes, difficult sites, impossible budgets, and clients who want a 5,000 square foot home on a 2,500 square foot lot.

And you got good at it. Really good.

You learned to look at a tangled mess of constraints and requirements—architectural, structural, spatial—and somehow find the solution hiding inside. You developed an almost compulsive need to fix things, to make them work, to find the answer.

This is a superpower. In design, it's everything.

But here's what nobody told you in studio: running a business presents a fundamentally different kind of problem. And the instincts that serve you so well at the drafting table can absolutely wreck you in the conference room.

Because in business, the problems never stop coming. They multiply. They mutate. They show up faster than you can solve them.

And if you try to solve all of them - the way you were trained to do - you'll exhaust yourself chasing issues that don't actually matter while the real problems quietly eat your firm from the inside.

The Problem With Problem Solving

When you're designing a building, the problem is (usually) defined for you. There's a site. A program. A budget. Constraints. Your job is to find the best solution within those parameters.

But when you're running a firm? You have to decide what the problem even is.

And that's a completely different skill—one that requires you to evolve from technician to strategist.

Most architects I talk to are drowning in problems. Not enough leads. Too many of the wrong leads. Fees too low. Scope creep eating profits. Staff members who can't seem to deliver without hand-holding. Cash flow that looks like an EKG during a cardiac event.

So what do they do? They start solving.

They redesign the website. Update the logo. Create a new brochure. Try to integrate new software systems. Tweak the proposal template. Implement a new project management system. Attend a networking event. Post more on Instagram.

Problem, solution. Problem, solution. Problem, solution.

It feels productive. It feels like progress.

It's not.

Tactical Whack-a-Mole

We have a name for this at Archmark: Tactical Whack-a-Mole.

It's when you spend all your time and energy smacking at whatever problem pops up next, without ever stepping back to ask whether it's a problem worth solving in the first place.

Here's what Tactical Whack-a-Mole looks like in the wild:

"We need a new website." Maybe. But if your messaging is unclear and you don't know who you're actually trying to attract, a new website is just a prettier version of the same confusion. You'll spend $15,000 and six months on a site that still doesn't convert because the real problem, unclear positioning, was never addressed.

"We need a better brochure." Do you really? When's the last time a client said, "I was going to hire you, but then I saw your brochure and changed my mind"? The brochure isn't why you're not closing projects. (More on what probably is in a minute.)

"We need to hire someone to handle marketing." Maybe. But if you don't know what your positioning is or who you're trying to attract, you're just asking staff to execute on confusion. The real problem isn't lack of personnel, it's a lack of strategy.

"We need to update our logo." This one's my favorite. Firms will spend months agonizing over whether the font should be a little heavier, whether the icon reads properly at small sizes, whether the color palette feels "right" - while completely ignoring the fact that nobody's actually visiting their website to see the logo in the first place.

The logo isn't the problem. Traffic is the problem. But traffic is a harder, scarier, more ambiguous problem to solve. So we fiddle with the logo instead.

This is what your problem-solving brain does when it's not pointed at the right target. It finds problems it knows how to solve, the tangible, contained, designable problems, and goes to work on them.

Meanwhile, the actual problems fester.

The Real Skill: Problem Selection

Wes Gay nailed it: A leader's job isn't to solve problems. It's to clarify which problems ought to be solved.

This is a fundamental shift in how you think about your role. You're not the Chief Problem Solver anymore. You're the Chief Problem Selector.

And here's the thing, this probably feels wrong to you. It might even feel lazy. You became an architect because you like solving problems. Sitting back and deciding which problems to solve feels... delegating? Managerial? (Four-letter word in some firms.)

But think about it in design terms.

The best architectural projects you've ever done didn't happen because you solved every problem thrown at you. The project that actually worked, that felt resolved, that made clients cry happy tears at the final walkthrough happened because you identified the real problem, the core constraint. The thing that, if solved correctly, would make everything else fall into place.

Your firm works the same way.

Somewhere in that mess of challenges you're facing, there's a keystone problem. A linchpin issue that, if addressed, will unlock solutions to a dozen other things that are currently keeping you up at night.

But you'll never find it if you're too busy redesigning your business card.

The Wrong Leads Problem (That Wasn't Actually About Leads)

Let me tell you about Mike Sweebe.

Mike runs Sweebe Architecture, a residential firm in Montclair, New Jersey. When we first connected, Mike was drowning, but not in the way you might expect.

He was getting plenty of leads. About 500 inquiries a year, in fact.

The problem? They were almost all wrong.

Nail salons. Corporate interiors. Commercial fit-outs. Project after project that had nothing to do with the single-family custom homes Mike actually wanted to design. His phone was ringing off the hook with opportunities he had zero interest in pursuing.

So what was Mike doing? Exactly what any good problem solver would do: he was solving the problem in front of him.

He was taking those calls. Responding to those emails. Having those conversations. Politely explaining, over and over, that no, he doesn't do nail salons. No, commercial interiors aren't really his thing. No, he's probably not the right fit for that project.

Five hundred times a year.

Mike couldn't do his actual work because he was too busy saying no. His website was a shingle, not a filter. It announced that he existed but did nothing to attract the right people or repel the wrong ones.

Now, a problem-solver's instinct here might be to get better at saying no faster. To create an email template. To bring on staff to screen calls. To solve the problem of too many wrong inquiries.

But that wasn't the real problem.

The real problem was that Mike had never clarified who he was actually for. His positioning was vague. His website spoke to everyone (which means it spoke to no one). The wrong leads weren't a bug, they were a predictable outcome of unclear messaging.

So instead of solving the "too many calls" problem, we helped Mike solve the positioning problem.

We got specific about who he serves. What he does. And just as importantly, who he doesn't serve and what he won't do. We helped him integrate qualification systems directly into his website - not to reduce inquiries, but to filter them before they ever became conversations.

The result?

In the first half of 2024, Mike had 20 consultations. He converted 12 of them into projects.

That's a 60% conversion rate, up from roughly 5% before (20 projects from 500 inquiries, for those keeping score at home).

Fewer leads. But the right leads. The leads that were actually worth his time.

As Mike put it: "Archmark didn't just help me target my ideal client, they helped me better understand myself and the firm I want to build. They helped me set up guardrails to protect my time. And how to put those guardrails not just on the clients, but also on myself."

Now Mike spends his time designing homes instead of explaining why he doesn't do nail salons.

Same architect. Same talent. Same market. Completely different problem being solved.

Funnel diagram: Over 500 leads filtered, resulting in a small set conversion; navy blue background.

How Architects Can Stop Solving and Start Selecting

So how do you make this shift? How do you go from reflexively solving whatever marketing or business problem is in front of you to strategically choosing what deserves your attention?

A few thoughts:

1. Get Suspicious of “Easy” Marketing Problems

If a problem has an obvious, designable solution - new logo, new website, new brochure - that should be a yellow flag, not a green light.

These aren't necessarily wrong things to do. But they're often attractive distractions from harder, more important work. Your problem-solving brain loves them because they are specific and limited. Contained. Finishable.

Ask yourself: Is this the real problem, or is this just a distraction from a bigger problem I need to address first?

2. Follow the Frustration Upstream

When something's frustrating you,bad leads, scope creep, low fees, clients who don't value your work, resist the urge to solve it at the point of impact.

Instead, trace it backward. Why is this happening? And why is that happening? And why is that happening?

Usually, by the time you've asked "why" three or four times, you've arrived at something much closer to the root cause. That's the problem worth solving.

Mike's frustration was "too many wrong leads." But the upstream cause was "unclear positioning that attracted the wrong people." Solving the first would have been a band-aid. Solving the second transformed his practice.

3. Ask What Solving This Would Unlock

Before you commit time, money, or mental energy to solving a problem, ask: If I solve this, what else gets easier?

If the answer is "not much" - if solving this problem is isolated, contained, a one-off fix - it's probably not your keystone problem.

But if solving a problem would create cascading benefits, you’re onto a solution that will lead to fewer wrong conversations, higher fees, better clients, more time for design, improved team morale, and healthier cash flow.

4. Accept That Some Projects aren’t your Problems to Solve

This is the hardest one for architects.

Some problems aren't worth solving. They should be ignored, eliminated, or designed around entirely. Not everything that presents itself as a problem deserves your attention.

That nail salon inquiry? It's not a problem to be solved. It's noise to be filtered out before it ever reaches you.

The scope creep on that nightmare project? Maybe the real solution isn't better scope management, maybe it's not taking clients like that in the first place.

The best problem solving is often not solving the problem at all. It's building a firm where that problem doesn't exist.

Silhouette of person with scattered shapes overhead vs. silhouette with a red square above.

The Architecture Firm You Actually Want

Here's what becomes possible when you stop solving every problem and start selecting the right ones:

You stop redesigning your logo for the fifth time.
You stop chasing tactics that don't move the needle.
You stop explaining your value to people who were never going to pay for it.
You stop taking calls from nail salons.

And you start building a firm that attracts the right clients, repels the wrong ones, and lets you spend your time doing what you actually became an architect to do: design beautiful, meaningful work for people who value it.

That's not a pipe dream. It's what happens when you finally identify and solve the problems that actually matter.

The firms that thrive aren't the ones solving every problem—they're the ones that evolve beyond reactive problem-solving to strategic problem selection.

Mike did it. So have hundreds of other architects who made the shift from problem solver to problem selector.

It's not about working harder. It's not about becoming a marketing expert. It's about stepping back far enough to see which problems are worth your attention - and having the discipline to ignore the rest.

One Problem Worth Solving

If you're reading this and recognizing yourself - the Tactical Whack-a-Mole, the attractive distractions, the exhausting cycle of solving problems that don't seem to move the needle - you're not alone. And you're not doing anything wrong. You're doing exactly what you were trained to do.

But you might be ready to evolve your approach.

At Archmark, we help architects identify the real problems hiding beneath the surface-level symptoms. The positioning issues masquerading as website problems. The messaging gaps showing up as low conversion rates. The clarity problems creating chaos throughout your firm.

If you're curious whether there's a keystone problem in your firm that's creating all these downstream effects, we'd love to talk.

Book a free Clarity Call - it's a no-pressure conversation where we'll help you see your firm from the outside and identify what might actually be worth solving.

Because you didn't become an architect to spend your days playing Whack-a-Mole.

You became an architect to solve problems worth solving.

Let's figure out what those are.

Frequently Asked Questions

Why do successful architects struggle with running their firms?
Architecture school trains you to solve complex design problems, not business problems. The problem-solving instinct that makes you excellent at design can actually hurt you in business—because you'll try to solve every problem that appears instead of selecting which problems actually matter. Most architects learn business management on the job, without formal training, which leads to reactive decision-making rather than strategic leadership.
What is "Tactical Whack-a-Mole" in architecture firm management?
Tactical Whack-a-Mole is when firm owners spend all their time solving whatever problem pops up next—updating the logo, tweaking the website, implementing new software—without asking whether these are the right problems to solve. It feels productive because you're always busy, but it rarely moves the needle on growth, profitability, or attracting better clients. The real issues (unclear positioning, poor lead qualification, weak messaging) continue festering while you're distracted by easy-to-solve surface problems.
How do I know which problems in my firm are worth solving?
Ask yourself three questions: First, is this the real problem or just a symptom? (Follow the frustration upstream to find root causes.) Second, if I solve this, what else gets easier? (The right problems unlock cascading benefits.) Third, is this an easy problem I know how to solve, or a hard problem that actually matters? The problems worth solving are usually uncomfortable, ambiguous, and strategic—like clarifying your positioning or building qualification systems—not tactical tasks like redesigning your brochure.
Why am I getting so many unqualified leads for my architecture firm?
Wrong-fit leads are usually a positioning problem, not a volume problem. If your website and marketing speak to everyone, they attract everyone—including people you don't want to work with. When Mike Sweebe was getting 500 inquiries a year (mostly for nail salons and commercial interiors he didn't want), the issue wasn't his marketing reach—it was that his messaging didn't filter for his ideal clients (custom residential). Once he clarified his positioning and integrated qualification into his website, his conversion rate jumped from 5% to 60%.
What's the difference between being a problem solver and a problem selector?
Problem solvers react to whatever issue appears and try to fix it. Problem selectors step back and decide which problems deserve attention in the first place. As a firm owner, your job isn't to solve every problem—it's to identify the keystone problem that, once addressed, makes everything else easier. This requires evolving from technician (solving what's in front of you) to strategist (choosing what matters most). It's the difference between playing Whack-a-Mole and building a firm where the wrong problems don't exist.

Ready to identify the real problems holding your firm back? Apply for your free Clarity Call and let's figure out which problems are actually worth solving.