Your first promotion.
Unit 1 gave you the map. This unit walks you across the first rung — the single biggest, easiest, highest-leverage move you will ever make with Claude.
If you finished Unit 1, you know where Phase 1 and Phase 2 sit on the journey. You probably also know — quietly, honestly — that you live somewhere between them. You write decent prompts, but you also dash off a lot of short questions and accept generic answers.
Unit 2 is going to fix that. Not by giving you a clever trick or a list of templates. By giving you a new thought process — one that costs nothing, takes seconds to adopt, and changes the quality of your output the first time you use it.
What you'll walk out with
A new mental model for every prompt you write. A four-ingredient framework you can apply in under 60 seconds. Two complete worked examples you can copy. And two hands-on briefs you'll write yourself — with a model answer to compare against.
What Unit 2 covers
- The Phase 1 trap — the symptom every stuck user shares.
- The mindset shift — from "asking Claude" to "briefing Claude."
- The four ingredients of a brief — Role, Context, Task, Constraints. (RCTC.)
- Two worked examples — same task, weak prompt vs. strong brief, side by side.
- Three Phase 2 mistakes — and the specific fix for each.
- Two hands-on briefs — you write, then compare against a model answer.
- The Phase 2 ceiling — why even great briefs eventually stop scaling, and what comes next.
The Phase 1 trap.
Almost every stuck Claude user has the same symptom — and once you see it in your own work, you can't unsee it.
You open Claude. You type a short question or a short request. You get a competent, perfectly written answer. You read it, take what's useful, and move on. The whole interaction took 20 seconds.
You feel productive. You were productive — a little. But you also got the same answer that anyone else who asked that same question would have gotten. Which means you got a fraction of what Claude could have given you if it had known anything about your work.
Three signs you're stuck in Phase 1
1. Your prompts are shorter than your tweets.
"Write a follow-up email." "Help me prep for the meeting." "Summarize this." If you wouldn't accept this kind of instruction from your boss, you shouldn't be giving it to Claude either.
2. The answer is technically right but feels off-the-shelf.
It addresses what you asked. It doesn't address what you needed. If a stranger gave you the same answer you just got, would you be impressed — or would you be slightly disappointed? Phase 1 answers are stranger-quality answers.
3. You quietly edit Claude's output a lot.
You change the tone. You add the names. You rewrite the opening line because it's too formal (or too casual). You're doing the work Claude should have done — because you never told Claude what "your work" sounds like.
The honest part
None of this is Claude being limited. All of it is the predictable result of asking strangers for advice without telling them about your life. Same Claude. Tell it more. Get more.
Reflection · 2 minutes
Open Claude. Look at the last five prompts you wrote. How many of them are tweet-length? That number is your Phase 1 score.
Stop asking. Start briefing.
This is the sentence to keep in your head every time you type. It is the only mental shift you need to escape Phase 1 — and it is permanent once it lands.
Asking and briefing feel similar. They are not. They produce wildly different outputs because they come from wildly different postures.
Asking
Asking is what you do when you assume the other party already understands the situation. You ask a coworker who's been on the project for six months, "should we push the launch?" You ask a friend, "do you think I should take the job?" Those questions work because the listener already has the context to answer them well.
When you ask Claude a Phase 1 question, you are treating Claude like that coworker — like Claude has been in the meeting, read the doc, met the customer. Claude has not. Asking without context is asking a stranger for advice about your life.
Briefing
Briefing is what you do when you're handing work to someone who needs to know the situation in order to do it well. You brief a new colleague before they walk into a client meeting. You brief a contractor before they start a project. You brief your boss before they take your idea to the board.
A briefing has a shape. It tells the listener:
- Who they need to be for this work.
- What they need to know that isn't obvious.
- What you actually want them to produce.
- What "good" looks like and what to avoid.
That is the entire framework of Phase 2. Four ingredients. Once you start seeing your prompts as briefings, you can't write a Phase 1 prompt anymore — you'll notice yourself doing it and stop.
The slogan that does the work
"If I were handing this task to a sharp new hire, what would I need to tell them first?" Ask yourself that before you type, and most of your prompts will write themselves.
The four ingredients of a brief.
Every strong Phase 2 prompt has these four ingredients. Miss any one and the output suffers in a predictable way. Once you learn the shape, you will spot the missing piece in any weak prompt in seconds.
The mnemonic is RCTC — Role, Context, Task, Constraints. Memorize it. You'll use it the rest of your career.
Role — Who Claude should be.
Tell Claude what role to take for this task. Roles set tone, depth, and judgment in one sentence. "You are a regional sales manager…" gets you different output than "You are a startup founder…" — even with the same question after it.
If you skip Role, you get neutral, vanilla output that doesn't sound like it came from anyone in particular.
You are an experienced HR director at a 200-person logistics company.Context — What Claude needs to know.
Tell Claude what the situation is. Who is involved. What happened. What the stakes are. Anything Claude can't infer on its own. Context replaces guesswork — the more you give, the less Claude invents.
If you skip Context, you get answers based on the most generic version of your scenario.
A long-tenured manager was passed over for promotion last week and has gone quiet in meetings. Two of her reports asked me privately if she's okay.Task — What you want produced.
State the specific output. Not "help me with this" — say what you want in your hands at the end. A 150-word email. A bulleted summary. A list of five options. A draft conversation script.
If you skip Task, you get advice when you wanted a draft, or a draft when you wanted advice.
Draft a 4-bullet talking-points outline for a one-on-one with her this Friday — what I want to listen for, not what I want to say.Constraints — What "good" looks like.
State the rules. Length, tone, things to avoid, things to include. Constraints are the difference between competent and right. They are also the ingredient most professionals skip — which is why so many Phase 1 answers feel "almost there."
If you skip Constraints, you get output that hits the task but misses the brief.
Warm but professional. No HR jargon. Don't assume she's leaving — assume she's hurting. Avoid suggesting a PIP or formal documentation.The 60-second test
Before you hit enter on any prompt, look for all four. Missing one? Add it. That habit alone — applied for one week — will make you better at Claude than 95% of working professionals.
Maria the bank marketer.
You met Maria in Unit 1. She works at a community bank in central Texas and she's about to launch an email blast for a new certificate of deposit promotion. Let's watch her do the same task in Phase 1 and Phase 2.
This is the most important page in the unit. Read both prompts carefully. Pay attention to what the strong version adds — not just how much longer it is.
Give me ten subject line ideas for our spring CD promo.
Output: Ten generic subject lines. "Lock in a great rate today." "Spring into savings." "Special CD promotion inside." Maria can use them. They could also be from any bank in America.
You are a marketing coordinator at a community bank in central Texas with 8 branches. We're promoting an 8-month CD at 4.75% APY (above the local average). Our members skew 55+ and financially conservative — they care about safety more than rate. Per compliance we cannot use "guaranteed" or "risk-free." We've overused "limited time" this year. Give me 10 email subject line options for our blast: friendly tone, each under 50 characters, no exclamation points.
Output: Ten subject lines that sound like a community bank wrote them for older, safety-minded members — avoiding the compliance words and the tired phrases. Half of them are nearly ready to ship as-is.
What changed
Both prompts asked for the same thing. The Phase 2 prompt added all four ingredients:
- Role — "marketing coordinator at a community bank in central Texas."
- Context — the product, the rate, the audience profile, the compliance situation.
- Task — ten subject lines, email blast, specific format.
- Constraints — friendly, under 50 chars, no exclamation, no banned words, no overused phrases.
Total typing time: about 90 seconds. Total time saved on editing the output: probably twenty minutes. The ratio is always like this.
Devon the clinic operations director.
Different industry, different stakes, same framework. Devon runs operations for a 4-clinic primary care group and needs to plan this year's mandatory staff training.
Help me plan staff training for this year.
Output: A generic L&D plan with placeholder topics, generic timelines, and suggestions to "consider your team's needs." Useful as a starting point. Not useful as a plan.
You are an HR consultant who specializes in primary care clinic operations. I run operations for a 4-clinic primary care group with 65 staff (mix of clinical and admin). Annual mandatory training covers HIPAA, OSHA bloodborne pathogens, infection control, and customer service. Our compliance window closes March 31. Constraints: we cannot pull more than 3 staff from any clinic at one time. About half our team is bilingual Spanish/English and we'd like Spanish-language options where compliant providers exist. Give me a 6-week rollout plan: which topic in which week, live vs e-learning recommendation for each topic with a one-sentence rationale, and how to verify completion at the staff level.
Output: A real plan. Week-by-week schedule that respects the 3-staff cap. Format recommendations tied to topic risk. Bilingual options flagged. A verification approach Devon can implement Monday morning.
The pattern is the same
Notice that the strong prompt isn't fancy. It doesn't use clever framings or prompt engineering tricks. It just lays out the four ingredients in plain language.
That's the whole game. You don't need to be a "good prompter." You need to be a good briefer — and you already are one, every time you brief a colleague on something. You're just transferring that skill.
Reflection · 3 minutes
Pick a real task from your work this week. Without writing the full prompt yet, list the four ingredients you'd put in a brief. Role / Context / Task / Constraints.
Three mistakes that keep good briefers in Phase 1.5.
Even professionals who know the framework slip into these patterns. Each one feels productive while it sabotages the output. Here's how to spot and fix each.
Mistake 1 — Over-briefing.
You include every fact you know about the situation, including facts that have nothing to do with the task. The brief is two paragraphs of background and one line of ask. Claude does its best, but the noise crowds out the signal — and small irrelevant details start influencing the output in subtle ways.
Mistake 2 — Vague constraints.
"Make it professional." "Make it good." "Keep it brief." These feel like constraints. They aren't — they are wishes. Claude can't act on them because they describe an emotion, not a rule. "Professional" to one person means buttoned-up; to another it means conversational and warm.
Mistake 3 — Hidden role.
You skip Role because you assume Claude will figure it out from context. Sometimes it does. Often it picks a generic "helpful assistant" tone that's wrong for your task — too formal for an internal note, too breezy for a board memo. Output quality wobbles for no obvious reason.
How to debug a Phase 2 prompt
If your output feels off, don't rewrite from scratch. Walk through RCTC and ask: which ingredient is weak or missing? Nine times out of ten it's Constraints or Role. Add the missing ingredient and re-run.
Your turn.
Two sample projects. You write the brief. Then you reveal a model answer and compare. The goal isn't to match the model — it's to see how a sharp brief takes shape.
Brief Claude on a board update.
You are the head of operations at a 40-person regional staffing agency. Your CEO just asked you to draft the quarterly update she'll send to the four-person board next Friday. The board is mostly retired bank executives who want clean numbers and short prose. You have the Q3 financials (revenue up 8% YoY, margin down 2 points, headcount flat). Two big clients renewed; one churned. Q4 goal is to hold margin and grow revenue 5%.
Write the prompt you'd give Claude. Fill in each of the four ingredients below — or write it as one paragraph at the bottom. Either works.
One way to write this brief
Role: You are a sharp head of operations writing for a four-person board of retired bank executives who value clarity and short prose.
Context: Q3 financials: revenue +8% YoY, margin down 2 points, headcount flat. Two big clients renewed; one churned. Q4 goal is to hold margin and grow revenue 5%. The board is not in the day-to-day — assume they read the prior quarter's memo and remember the broad strokes only.
Task: Draft a one-page quarterly board update from the CEO. Open with a three-sentence executive summary, then sections for Financials, Wins & Losses, and Q4 Plan. End with one paragraph the CEO can use to frame any board questions.
Constraints: Direct, plain English. No marketing language. Numbers presented cleanly with one-line context. Acknowledge the margin dip without spinning it. Maximum 450 words.
The takeaway isn't that your version was "wrong." It's noticing what the model answer's Constraints section did — it turned vague preferences (clarity, plain English, no spin) into rules Claude can act on. That's where most professionals leave value on the table.
Rewrite a Phase 1 prompt.
This time you're not starting from scratch — you're upgrading. Take the weak prompt below and rewrite it as a Phase 2 brief. Use any role, context, and constraints that would make sense for a real customer service team.
The weak prompt.
"Write me a customer service apology email."
Rewrite it as a Phase 2 brief. Invent the details — what was the customer mad about, what's the company, what's at stake, what tone do you want. The goal is to practice the shape of a strong brief, not to nail anyone's real situation.
One way to write this brief
Role: You are a senior customer success manager at a small SaaS company — you write like a real person, not a help center.
Context: A long-tenured customer (3 years, mid-market plan, $24k ARR) was billed twice for their annual renewal due to a payment processor error on our side. Their finance team caught it. The customer's primary contact is frustrated and emailed our support inbox about it this morning. The double charge has already been refunded; the refund will show in 3–5 business days.
Task: Draft a reply email from me to the customer's primary contact. Acknowledge the error, explain what happened in one plain sentence, confirm the refund and the timing, and offer one concrete gesture (a credit toward their next renewal).
Constraints: Warm but not gushing. No "we apologize for any inconvenience" template language. Take real responsibility without over-explaining. Under 150 words. End with a direct line they can reply to me on.
Watch your version vs. the model. Did your Constraints turn vague preferences into specific rules? Did your Task name a concrete output ("a 150-word reply" rather than "an email")? Those two ingredients are where Phase 2 lives or dies.
A note on the projects you just did
You probably noticed something: writing the brief was almost the work itself. By the time you finished filling in the four fields, you'd already thought through the situation, the audience, and what "good" looks like. Claude's draft would just be the artifact. That's the deeper lesson of Phase 2 — briefing makes you a sharper thinker, not just a better Claude user.
Why even great briefs eventually plateau.
You'll get a few weeks of feeling like a Claude wizard. Then you'll start to feel something else — and that feeling is the entire setup for Unit 3.
Once briefing becomes your default, the quality of your work with Claude takes a step up that doesn't reverse. You're not going back to Phase 1. But after a couple of weeks, a quieter problem shows up.
The repetition problem
You realize you've typed the same Role three days in a row. You've pasted the same paragraph of company context into four different chats this week. You're getting Phase 2 results — but you're paying a Phase 2 tax every single time: the cost of re-briefing from scratch.
For a working professional, this tax adds up fast. Five minutes per session, ten sessions a week, fifty weeks a year — that's a full work week of typing the same context. That's the Phase 2 ceiling.
The signal you're ready for Phase 3
When you catch yourself thinking "I just typed this exact context yesterday" — you've outgrown Phase 2. That annoyance is the doorway to Phase 3. Unit 3 is what's on the other side of that door.
What Phase 3 actually fixes
Phase 3 — Train — moves the Role and Context out of every prompt and into your setup. Claude opens already knowing who you are, what your company does, who your customers are, and what your standards look like. You stop briefing. You start picking up mid-conversation, every conversation.
The work you just learned to do well in Phase 2 — defining Role and Context — doesn't get wasted. It gets promoted. Instead of typing it once per session, you write it once and it shows up forever.
That graduation is what Unit 3 will teach you. But you can't graduate if you haven't done the work of Phase 2 first — Phase 3 only works for people who already know how to brief. Which, after this unit, you do.
Reflection · 2 minutes
What's the one chunk of context you'd love to never type again? (That answer becomes your first Project file in Unit 3.)
Are you ready to move to Train?
Three questions that diagnose your readiness for Phase 3. The answers will tell you whether to move into Unit 3 now or spend a week building Phase 2 muscle first.
1. When you sit down to write a prompt, what happens first?
2. Look at your Claude history. How often do you repeat the same chunk of background across different conversations?
3. When you get a weak answer from Claude, what's your move?
Your readiness
Answer all three questions above to see your readiness for Phase 3.
Seven questions.
One per major idea in this unit. Click an answer for instant feedback. Your running score appears below.
0 of 7 answered · 0 correct so far
1. What is the defining mindset shift from Phase 1 to Phase 2?
2. What are the four ingredients of a Phase 2 brief?
3. Which RCTC ingredient is the one most professionals skip — and the one that separates "competent" from "right"?
4. "Make it professional" is an example of what failure pattern?
5. The fix for over-briefing is to…
6. What is the Phase 2 ceiling — the reason briefing alone isn't the endgame?
7. What's the signal that you've personally outgrown Phase 2 and are ready for Phase 3?
Finish the knowledge check to see your score.
All your reflections and briefs are saved — come back to them anytime.
The new thought process.
Stop asking. Start briefing.
Every prompt is a handoff to a colleague. If you wouldn't accept the instruction as a brief, don't send it as a prompt.
RCTC.
Role, Context, Task, Constraints. Four ingredients. Use them every time. Notice which one is missing when a Claude answer feels off.
Constraints carry the most weight.
They are how you tell Claude what "good" looks like. Replace adjectives with rules and the output quality jumps immediately.
Annoyance is the doorway.
When you catch yourself retyping the same context, you're ready for Phase 3. That feeling isn't a problem — it's progress.