The Brick: Styles let you bring more than one perspective to the same piece of work. It's the simplest change most professionals haven't made yet.
Walk into your next team meeting and announce that this time, you only want to hear from one person. Just one perspective. The rest of you, please do not speak. That meeting wouldn't survive ten minutes, and yet that's how most professionals run every Claude conversation.
When you start a chat without a Style applied, you get one collaborator: the default. It's capable, but it's one perspective. Most professionals I've worked with have used Claude for months without ever opening the Styles drawer. They've explored Skills, Projects, Cowork, Schedules. But never Styles.
It's the simplest change you can make, and it's the one most professionals haven't made yet.
What Styles Actually Are
A Style is a saved instruction set that shapes how Claude approaches a conversation. It sits one layer above the prompt you type. You set it, and Claude carries it through every turn until you change it.
There are five presets built in:
- Normal: Claude's default, no adjustments applied
- Learning: Claude asks questions and guides you towards an outcome
- Concise: Short answers, no elaboration
- Explanatory: Detailed, thorough responses that walk you through the reasoning
- Formal: Professional tone, polished language
You can also build your own, either by pasting in writing samples for Claude to model, or by writing the instructions yourself. Your custom styles live in the same drawer, one click away.
The preset list is fine for everyday use. What changes the game is understanding what happens when you switch the lens mid-work.
What Changes When You Switch The Lens
A Style doesn't make Claude smarter. What it does is change how Claude approaches the conversation: the voice it takes, the structure it uses, the perspective it brings.
That might sound like a small thing. It isn't.
When you're in a room with your team, the challenge is rarely finding an answer. It's reading the same situation through different lenses to make a better decision. Your project manager's read isn't your account director's read, which isn't your finance lead's read, which is never the same as your sales manager's.
The room gets smarter because the lenses differ.
Styles are the closest thing in Claude to seating different collaborators around the table. The model is the same, but the lens changes.
How To Use Styles
Starting with the presets:
- Learning: Working through a problem, picking up a new skill, getting your head around a new concept
- Concise: Summarizing call transcripts, building playbooks, internal comms
- Explanatory: Translating onboarding docs, reviewing a technical spec
- Formal: Writing a work memo, presentation copy, writing an email to the Royal family
Custom styles are where it gets more interesting. Think about your own environment. Your company might have:
- A decision-making framework you use consistently, like SWOT or RICE
- Brand and voice guidelines for external communications
- A sales methodology like SPIN or SNAP
- A stakeholder who needs complex ideas simplified before they'll engage with them
Each of those is a custom style waiting to be built. Take the RICE example. Without a style set, Claude might walk you through the same decision using a completely different framework. With a style that tells Claude how your team thinks, what framework you use, and how you like responses structured, the output fits your actual process.
That's a different conversation entirely.
Run a Test
Take something you're about to send. A client proposal, a board update, a difficult Slack message, a hiring decision memo. Run it past Claude three times, with three different Styles.
First, your default. See what Claude reads in the work overall.
Second, create a style called "Skeptical Operator" with these instructions:
You are a senior operator who has seen this kind of work fail before. Read for the assumption that turns out to be wrong, the dependency that has not been named, and the stakeholder whose reaction has not been considered. State concerns plainly.
Third, create a style called "First-Time Reader" with these instructions:
You are reading this for the first time, with no context about the project, the company, or the relationships. Tell me what is unclear, what feels assumed, and what would land differently if you knew nothing about this beforehand.
You'll get three different reads on the same draft. The trap is treating every flag as equally important and trying to action all of them. That's just busywork spread across three rounds.
The signal is in the overlap. When only one lens raises a concern, weigh it but hold off. It might be that lens's bias showing through. When two of the three flag the same paragraph, sentence, or assumption, even if they describe it differently, that's the edit you actually need to make.
Where To Start
Most of what you do with Claude is alignment work, not knowledge work.
Drafting. Reviewing. Sharpening. Communicating. Deciding.
These are exactly the tasks where Styles compound. Skipping them isn't a small efficiency loss. It's a choice to bring one perspective to work that would be better with three.
The defaults are there when you need a quick shift. The custom styles are there when your work has specific enough requirements that a generic lens won't cut it. Both take less time to set up than most people assume.
Start with one piece of work this week. Run it through two Styles. See what the second read surfaces that the first one missed.