Why I Give Claude a Job Title Before Every Project

← Back to all posts

You wouldn't hand a blank brief to a new hire and say "figure it out." You'd tell them their role, what decisions they own, and where the guardrails are.

I do the same thing with Claude.

What an SME Identity Actually Is

Before every stage of every workflow I run, Claude gets a short role definition. Two sentences. It names the specialization, the decisions it should make without asking me, and the domain context.

That's it. No long system prompts. No 500-word persona descriptions. Two sentences that tell Claude who it is for this task.

It Changes What Claude Pays Attention To

Without a role, Claude gives you generalist output. It hedges. It covers every angle equally. It writes like a helpful assistant who knows a little about everything.

With a role, Claude filters. A "healthcare ad compliance auditor" will catch the phrase "guaranteed results" and flag it. A generic assistant might let it slide.

It Decides What Gets Done Without Asking You

The best part of an SME Identity is the autonomy clause: "without asking." This is the difference between an AI that interrupts you with 10 clarifying questions and one that makes reasonable expert-level judgment calls on its own.

When I tell Claude it's a "brand voice architect who defines tone spectrums and editorial guardrails without asking," it stops asking me whether the tone should be warm or clinical. It reads the brand context file and decides. Like a real specialist would.

It Prevents Role Drift Across Multi-Stage Workflows

I run workflows with 5 to 12 stages. Each stage needs a different kind of expertise. The copy editor is not the SEO specialist is not the compliance auditor.

Without SME Identities, Claude starts blending roles. Your SEO pass starts rewriting copy. Your compliance check starts suggesting headlines. Everything bleeds together and you lose the sharpness of each stage.

It Makes the Output Usable the First Time

Here's the real cost of skipping this: revisions. When Claude doesn't know its role, you spend 2-3 rounds correcting the framing, the depth, the focus. When it does know its role, the first draft is usually 80-90% right.

Multiply that across dozens of tasks per week and the time savings are significant.

How I Structure Mine

Every stage file in my workflows starts with a title, then an SME Identity section. The pattern is always the same: role title, autonomous decision scope, and domain anchor.

For example, a copy editing stage might say: "Senior copy editor for medical aesthetics content; runs structural, clarity, and accuracy sweeps on procedure page copy without asking. Catches clinical terminology errors, readability issues, and brand voice violations before any optimization layers are applied."

The Bigger Point

AI tools are only as good as the context you give them. Most people focus on what they want Claude to produce. The SME Identity focuses on who Claude should be while producing it.

That distinction is the difference between output that needs heavy editing and output that's ready to use.