How architects actually use Claude, not why

I keep coming back to a post I saw this week from an architect who just wrapped a book-sharing session at ARCHIDEX, one of the big architecture and design expos. What grabbed me wasn’t the event. It was the questions the room kept asking.

The author, along with coauthor Ar. June Chow, walked architects through some of the handiest ways to put Claude to work: building presentation decks, exploring design concepts, and spinning up websites. Useful stuff on its own. But the crowd didn’t want the highlight reel.

Here’s what struck me. The whole conversation skipped past the usual questions. Nobody asked why to use AI or what to use it for. Everyone wanted to know the same thing: how do you actually use it well?

The original poster shared the exact questions that came up, and honestly, they apply to way more than architecture. Designers, writers, marketers, anyone building with AI runs into these. So I broke them down.

The 5 questions every AI user eventually asks

  1. How do I make it reflect my style and my company’s DNA? This is the big one. Generic AI output is easy. Output that sounds like you takes work. The trick is feeding the tool your past projects, your tone, your rules, so it learns your fingerprint instead of a default one.
  2. How do I use AI and still be myself? The fear here is losing your own voice. The author’s framing flips it: AI is a tool you point, not a personality you adopt. You stay the source of taste and judgment. It just moves faster.
  3. How do I avoid homogenous content? When everyone uses the same tool with the same lazy prompts, everything starts to look identical. The fix is specificity. The more unique context and constraints you give it, the more your work stands apart from the sea of sameness.
  4. How do I stay the commander instead of being commanded? This one hit me. It’s easy to slip into accepting whatever the AI hands you. The expert’s point is that you set the direction, you make the calls, you reject what doesn’t fit. The moment you start following the tool, you’ve handed over the wheel.
  5. How do I not get lazy? Speed is a trap if it kills your thinking. The healthiest use keeps your brain in the loop, using AI to handle grunt work while you stay sharp on the parts that actually need a human.

Why these questions matter more than the tools

The person who shared this landed on a conclusion I fully agree with. Once AI becomes a common commodity, and it’s getting there fast, the tool itself stops being the edge. Everyone has access to the same models.

When AI becomes a common commodity, how you work with it becomes the key to success.

That’s the whole game. Two architects can use the exact same Claude setup and produce wildly different results. The difference isn’t the software. It’s the taste, the context, and the judgment each person brings to it.

How you can put this to work today

You don’t need to be an architect to steal this. Here’s how I’d apply the author’s thinking to any creative or knowledge work:

  • Feed it your voice. Before asking for anything, give the tool 2 or 3 samples of your best past work so it mirrors your style, not a generic one.
  • Set constraints on purpose. Tell it what to avoid, what tone to hit, what your brand rules are. Constraints are what make output feel custom instead of copy-paste.
  • Review like a commander. Treat every draft as a starting point, not a finish line. Cut what’s weak. Keep only what matches your standard.
  • Protect your thinking. Use AI for the heavy lifting, drafts, research, first passes. Keep the strategy and the final calls in your own head.

The reason all of this resonated is simple. We spend so much time chasing the newest tool and almost none learning how to actually work with the tools we already have. The creator flipped that script, and I think that’s exactly where the real advantage lives right now.

These are just the highlights from what the industry pro shared. The full LinkedIn post has more context from the room and the discussions that sparked it. Worth a read if you want to see how working architects are thinking about this. Go check it out.

Scroll to Top