I've Been Frustrated by It Too

Last November, I was in a Beijing café racing a two -hour proposal deadline. I asked the AI to help me write "reb uttals for clients who refuse to renew" — and it handed me a paragraph starting with "First, we need to understand the client's concerns… " I nearly threw my laptop. In that moment, I felt like the thing had zero idea how urgent my situation was.

I figured it out later: the AI wasn't d umb. I just had no idea what it had been designed to be .

Anthropic Just Made the "Manual" Public

Anthropic — the company behind Claude — recently published a rare piece explaining exactly how they designed Claude's personality and behavior: why it " asks clarifying questions before answering," why it refuses to directly write certain things, why it sometimes feels like it's "lecturing" instead of "just helping."

Reading it felt like one of those aha moments. Like using a piece of software for six months and suddenly stumbling on the product manager's original design doc — all those "weird" behaviors suddenly made sense.

I have a friend named Xiaowen (she runs a personal fitness coaching business) who kept complaining that AI-generated course outlines were "too generic, no personality." I sent her the design article . After reading it, she ran the same request again — this time adding to her prompt: "My students already have a fitness foundation; don 't start from scratch." The output was completely different. Her words: "So it's been guessing who I am. I just needed to tell it first."

What You Can Do Today — and What It Actually Costs

Money: Claude has a free tier that's enough to get a real feel for it. If you're using it more than a dozen times a day, the paid plan runs around $20 /month.

Time: Reading Anthropic's design article takes about 15 minutes. (Here 's the core takeaway I'd highlight: the underlying logic is "get clear on who you are and what outcome you want — then say that at the start of the conversation.")

Technical barrier : Zero. It's just a normal browser chat interface. Nothing to install.

First step: Open Claude, and before your next question, add one line of context — something like "I'm an independent consultant, my clients are mostly small business owners, and I need help with…" Just that one change , and you'll notice the answer quality shift.

This isn't something everyone needs to go deep on. If you're only using AI occasionally to ask random questions, feel free to ignore all of this for now.

Where Are You Right Now? My Take Differs by Stage

If you're just starting out and don 't have stable clients yet: I'd suggest doing exactly one thing — before every AI conversation, use one sentence to say who you are and what you're working on. No technique required. That single habit alone shifts AI responses from "generic" to "closer to what you actually need." No need to study design philosophy right now. Come back to this article when you start feeling like the AI keeps missing the point.

If you already have one or two clients and are using AI for day-to-day work: I'd spend those 15 minutes reading the Anthropic piece. You'll almost certainly hit one or two "oh, THAT'S why" moments, and then naturally adjust how you talk to it. That's exactly how Xiaowen stopped wasting so much time going back and forth.

If you're scaling up and AI is already embedded in your daily workflow: The value of this article for you is understanding " where the limits are." Know what Claude was designed to do, and you'll know which tasks are worth the effort of careful prompting — and which ones are faster to handle with a different tool or just do yourself. I've burned time on this mistake: using AI for a lot of things it genu inely isn't good at. Once I understood the design logic, I re-divided my workflow and saved real energy.