Three Shifts to Talk to Claude Like a Pro

Most people treat Claude like Google, but the ones getting real results start with the problem, not the tool. Three shifts—context, outcome, and role—transform Claude from a generic answering machine into a trusted advisor that understands what you actually need.

The Communication Problem Nobody Talks About

Smart People Still Miss the Click

Being able to follow a conversation but missing the one thing that makes it click is the exact position most people are in with Claude. They're technically capable but lack the framework to communicate effectively.

Results Come From Approach, Not Smarts

The people getting real results from Claude are not necessarily smarter or more technical; they simply approach the tool differently. They start with the problem they need solved, not with what the tool can do.

Questions vs. Handoffs

Most people ask Claude questions when what it actually needs is a proper handoff. After 20 years of teaching, the speaker learned that confusion comes from people looking for answers rather than looking to understand—the same pattern appears in how people talk to Claude.

Shift 1: Add Context

The Capable Colleague Test

Before writing your request, ask: if I handed this task to a capable colleague I'd never worked with before, what would they need to know first? This reveals what context Claude is missing.

Context Transforms Generic Answers

A vague request like 'write a follow-up email to a client' leaves Claude guessing. Adding context—'I'm a business consultant, had a call yesterday about renewing a contract, they asked for 2 weeks to confirm budget'—gives Claude the foundation to produce something actually useful.

Shift 2: Define the Outcome

Describe What Good Does, Not What It Looks Like

Most people describe the format they want ('write me a paragraph' or 'summarize this document'). Instead, describe what the output needs to do: 'write a paragraph a non-technical senior manager can read in 30 seconds and understand what action they need to take.'

Role Determines How Claude Reads

If you ask Claude to read a draft as a general reader, it reads one way. If you ask it to read as a skeptical manager who's seen a hundred proposals and is deciding whether this deserves 10 more minutes, it reads completely differently. The role is the perspective you actually need.

Shift 3: Assign a Role

Role Is Perspective, Not Character

The role is not a character you invent; it's the perspective you actually need. Choose it deliberately based on the real expertise or viewpoint that would help solve your problem.

Real-World Demo: Hiring Decision

Generic Answer Without Framework

When asked 'I have two candidates for a project lead position, one more experienced but guarded, one less experienced but impressive—what should I consider?', Claude gives a reasonable but generic answer about culture fit and interview performance.

Specific Answer With Context

Adding context—'I'm a senior manager at a mid-sized marketing agency, hiring a project lead managing five people, team is under pressure, John has 8 years but was guarded, Marcus has 4 years but was engaged'—makes Claude's output immediately more specific and actionable.

Strategic Answer With Outcome

Adding outcome—'I need to defend this recommendation to leadership if challenged'—makes Claude tell you exactly what argument to make for each candidate, anticipate pushback, and identify what information you still need before Friday.

Advisor Answer With Role

Adding role—'You are a senior talent advisor who has helped executives make hundreds of high-stakes hiring decisions'—shifts Claude from analyzing candidates to analyzing your blind spots. It warns that the most common mistake is letting interview performance stand in for job performance, and tells you what to ask on reference calls.

Putting It All Together

The Three-Part Template

Use this structure for every request: 'You are [specific perspective]. I need this to [what it needs to do]. Here's the situation and the specific context that matters: [details].' This single move changes how Claude approaches your problem.

Persistent Context With System Files

Instead of rebuilding context every time, use a single file Claude reads automatically at the start of every session. Before you type a word, Claude already knows your role, priorities, and how you think.

Notable quotes

The ones getting real results are not necessarily smarter or more technical. They just approach it differently. — Cal Hyslop
What you're looking for isn't who impressed you more in a room, it's who is more likely to be functioning well 6 months from now. — Cal Hyslop
That's not a search engine answer. That's what a trusted advisor would tell you. — Cal Hyslop

Action items

  • Before your next Claude request, ask: if I handed this to a capable colleague I'd never worked with, what would they need to know first?
  • Reframe your request to describe what the output needs to do, not just its format
  • Assign Claude a specific perspective or role based on the expertise you actually need
  • Use the three-part template: You are [role]. I need this to [outcome]. Here's the context: [details]
  • Consider creating a system file with your persistent context so Claude knows your role and priorities automatically
Glimpse.
Cal Hyslop
10 min video
3 min read
Three Shifts to Talk to Claude Like a Pro
You just saved 7 min.
The big takeaway
Most people treat Claude like Google, but the ones getting real results start with the problem, not the tool. Three shifts—context, outcome, and role—transform Claude from a generic answering machine into a trusted advisor that understands what you actually need.
The Communication Problem Nobody Talks About
Smart People Still Miss the Click
Being able to follow a conversation but missing the one thing that makes it click is the exact position most people are in with Claude. They're technically capable but lack the framework to communicate effectively.
Results Come From Approach, Not Smarts
The people getting real results from Claude are not necessarily smarter or more technical; they simply approach the tool differently. They start with the problem they need solved, not with what the tool can do.
Questions vs. Handoffs
Most people ask Claude questions when what it actually needs is a proper handoff. After 20 years of teaching, the speaker learned that confusion comes from people looking for answers rather than looking to understand—the same pattern appears in how people talk to Claude.
Shift 1: Add Context
The Capable Colleague Test
Before writing your request, ask: if I handed this task to a capable colleague I'd never worked with before, what would they need to know first? This reveals what context Claude is missing.
Context Transforms Generic Answers
A vague request like 'write a follow-up email to a client' leaves Claude guessing. Adding context—'I'm a business consultant, had a call yesterday about renewing a contract, they asked for 2 weeks to confirm budget'—gives Claude the foundation to produce something actually useful.
Without context
Write a follow-up email to a client
With context
I'm a business consultant. Call yesterday about contract renewal. They asked for 2 weeks to confirm budget. Need warm follow-up that gives space but keeps momentum.
Same task, completely different foundation
Shift 2: Define the Outcome
Describe What Good Does, Not What It Looks Like
Most people describe the format they want ('write me a paragraph' or 'summarize this document'). Instead, describe what the output needs to do: 'write a paragraph a non-technical senior manager can read in 30 seconds and understand what action they need to take.'
Role Determines How Claude Reads
If you ask Claude to read a draft as a general reader, it reads one way. If you ask it to read as a skeptical manager who's seen a hundred proposals and is deciding whether this deserves 10 more minutes, it reads completely differently. The role is the perspective you actually need.
Shift 3: Assign a Role
Role Is Perspective, Not Character
The role is not a character you invent; it's the perspective you actually need. Choose it deliberately based on the real expertise or viewpoint that would help solve your problem.
Real-World Demo: Hiring Decision
Generic Answer Without Framework
When asked 'I have two candidates for a project lead position, one more experienced but guarded, one less experienced but impressive—what should I consider?', Claude gives a reasonable but generic answer about culture fit and interview performance.
Specific Answer With Context
Adding context—'I'm a senior manager at a mid-sized marketing agency, hiring a project lead managing five people, team is under pressure, John has 8 years but was guarded, Marcus has 4 years but was engaged'—makes Claude's output immediately more specific and actionable.
Strategic Answer With Outcome
Adding outcome—'I need to defend this recommendation to leadership if challenged'—makes Claude tell you exactly what argument to make for each candidate, anticipate pushback, and identify what information you still need before Friday.
Advisor Answer With Role
Adding role—'You are a senior talent advisor who has helped executives make hundreds of high-stakes hiring decisions'—shifts Claude from analyzing candidates to analyzing your blind spots. It warns that the most common mistake is letting interview performance stand in for job performance, and tells you what to ask on reference calls.
1
Generic: What should I consider?
2
With context: Specific output about the actual situation
3
With outcome: Strategic arguments and what you still need
4
With role: Advisor identifies your blind spots and what matters in 6 months
How each shift transforms Claude's response
Putting It All Together
The Three-Part Template
Use this structure for every request: 'You are [specific perspective]. I need this to [what it needs to do]. Here's the situation and the specific context that matters: [details].' This single move changes how Claude approaches your problem.
1
You are a specific perspective
2
I need this to [what it needs to do]
3
Here's the situation and specific context that matters
Template for every Claude request
Persistent Context With System Files
Instead of rebuilding context every time, use a single file Claude reads automatically at the start of every session. Before you type a word, Claude already knows your role, priorities, and how you think.
Worth quoting
"The ones getting real results are not necessarily smarter or more technical. They just approach it differently."
— Cal Hyslop, at [1:00]
"What you're looking for isn't who impressed you more in a room, it's who is more likely to be functioning well 6 months from now."
— Cal Hyslop, at [8:42]
"That's not a search engine answer. That's what a trusted advisor would tell you."
— Cal Hyslop, at [8:42]
Try this
Before your next Claude request, ask: if I handed this to a capable colleague I'd never worked with, what would they need to know first?
Reframe your request to describe what the output needs to do, not just its format
Assign Claude a specific perspective or role based on the expertise you actually need
Use the three-part template: You are [role]. I need this to [outcome]. Here's the context: [details]
Consider creating a system file with your persistent context so Claude knows your role and priorities automatically
Made with Glimpse by Wozart
glimpse.wozart.com/v/lnngn61y
Share this infographic

More like this