I’ve been in this field for over twenty years now, and if there’s one thing I’ve learned about running a design practice, it’s that “good problem solver” means something different depending on who you ask. Ask a structural engineer and they’ll describe someone who works backward from constraints. Ask a client and they’ll describe someone who makes their anxiety go away. Ask another architect and you’ll probably get a completely different answer again.
The truth is, problem solving isn’t one skill. It’s a handful of distinct instincts, and the best teams I’ve worked on had a mix of them, not five people who all think the same way.
Here are the types I’ve come to recognize, both in myself and in the people I’ve hired, collaborated with, and learned from over two decades of practice – and life.
The Diagnostician
This is the person who won’t touch a solution until they understand the actual problem. Client says the kitchen “doesn’t work.” The Diagnostician doesn’t start sketching. They ask why. Is it the workflow, the light, the storage, or is it that nobody agreed on how the space should be used in the first place. In design, this instinct saves you from beautifully solving the wrong problem, which happens more often than any of us like to admit.
The Systems Thinker
Every project is really a web of dependencies. Move a wall and you’ve moved a load path, a duct run, a budget line, and possibly someone’s mood. Systems Thinkers see those connections before they become change orders. They’re the ones who catch that the “simple” window change on page twelve actually touches four other trades. If you’ve ever had a project run smoothly through construction, there was probably a Systems Thinker somewhere keeping the whole thing coherent.
The Improviser
Plans meet reality and reality usually wins. The slab is off by three quarters of an inch. The client falls in love with a fixture that’s on backorder for fourteen weeks. The Improviser doesn’t panic and doesn’t blow up the schedule looking for a perfect fix. They find the workable path forward, often on site, often on the fly. I used to think this was a personality trait. Now I think it’s a skill you build by getting comfortable with things going sideways.
The Translator
This might be the most underrated type in our field. The Translator moves fluidly between the language of design intent, the language of construction detail, and the language a client actually understands. They’re the reason a homeowner doesn’t glaze over during a value engineering conversation, and the reason a contractor doesn’t roll their eyes at a drawing set. A lot of what people call “great communication” in this industry is really just strong translation.
The Pattern Matcher
After enough projects, you start to recognize shapes. This detail always leaks if it’s not flashed a certain way. This client behavior means the budget conversation is coming. The Pattern Matcher has seen the movie before and skips straight to the part where they head off the problem. This is the type that experience builds slowly, and it’s why a seasoned project manager can sometimes solve in five minutes what takes a newer one an afternoon.
None of these live alone
Here’s the part that took me a while to really internalize: you are probably not just one of these. I lean Diagnostician and Systems Thinker most days, but throw me into a site visit with a surprise and I’ll find the Improviser in me fast. The best collaborators I’ve worked with can shift between modes depending on what the moment calls for, and the best teams have people who cover for each other’s blind spots.
CollabMind takes into account these varied ways of getting through a work day. A Systems Thinker needs to see how the pieces connect. A Translator needs a shared place where client conversations, drawings, and site notes don’t live in three different inboxes. A Diagnostician needs the full history of a decision, not just the latest version of it. Different problem solvers need different views into the same project, and giving them that has always felt like the real work of good project management software, not just another feature on a list.
So next time a project throws something unexpected at you, it might be worth asking not just “how do we solve this” but “what kind of solving does this actually need.” Sometimes you need to diagnose. Sometimes you need to improvise. Knowing the difference is half the battle.
What type are you? I’d genuinely love to hear where you see yourself, and where you think your team is missing a type they could use more of.
