Strip the waste.
Get usable output the first time.

In Lean manufacturing, waste is defined as anything that doesn't add value. Motion without output. Steps that don't move the product forward. Rework because the specification wasn't clear at the start.

Poor prompting is the same problem. Vague inputs create rework. You get something back from Claude, it's not quite right, you describe what you wanted, Claude tries again, still off — four exchanges later you have something you could have gotten in one if you'd briefed correctly at the start.

The discipline of good prompting is the same discipline as good operations: define the spec before you start the work. That's all this module is. And like most operational disciplines, it feels like extra effort the first few times and then becomes reflexive.

The three failure modes

Most bad outputs trace back to one of three causes:

• Missing role. Claude doesn't know what lens to apply. "Write a summary" versus "Write a summary for a plant manager who needs to present to the board next week" are completely different tasks.
• Missing context. Claude doesn't know your operation, your client, your standards, or your constraints. It fills the gaps with generic assumptions — which is why you get generic output.
• Missing standard. Claude doesn't know what "done" looks like. Without a defined output standard, it'll produce something reasonable by its own measure — which may not match yours.

Every prompt you write from here forward should have four elements. Not all four need to be long — some tasks are simple enough that a sentence handles one of them. But all four should be present in your thinking before you hit send.

Your system prompt is the standing briefing you give Claude in every conversation within a Project. It handles the parts of RCTS that don't change — your role, your operation type, your standards — so you don't have to repeat them every time.

Think of it as the first page of a briefing binder you'd hand any new contractor: here's who we are, here's how we work, here's what we expect. Once it's in the system prompt, Claude reads it before every conversation. You stop repeating yourself.

What belongs in a system prompt

• Who you are and what kind of work you do
• Your operation type, industry, and scale
• The audience for your deliverables (clients, leadership, field teams)
• Your quality standard — what "professional" means in your context
• Any standing constraints: length, format, tone, language
• What Claude should always do (e.g., "flag any assumptions you're making")
• What Claude should never do (e.g., "don't use corporate jargon or filler phrases")

A sample system prompt — adapt this to your practice

WHO I AM:
I'm an operations consultant working with manufacturing, distribution, and service businesses. I build deliverables for clients — Excel trackers, SOPs, leadership briefs, forecasts, and work order reports. My clients are plant managers, GMs, and business owners.

YOUR ROLE:
You are my working partner on client deliverables. You are a skilled operations practitioner — not a generalist AI assistant. Think and write like an experienced operations professional, not like a tech writer or a chatbot.

MY QUALITY STANDARD:
Every output must be production-ready or close to it. That means:
- Clear, direct language. No filler phrases like "certainly," "great question," or "as an AI."
- Correct professional formatting for the document type.
- Specific and operational — not vague or theoretical.
- Appropriate for a client to see without me rewriting it.

STANDING INSTRUCTIONS:
- If you make assumptions to fill in missing context, flag them explicitly so I can correct them.
- If a task is ambiguous, ask one clarifying question before proceeding — don't guess.
- When producing documents, use the format appropriate to the deliverable type. SOPs get numbered steps. Briefs get headers. Trackers get structured tables.
- For bilingual requests, produce English first, then Spanish immediately after.
- Never pad output. If the task is a 200-word brief, write 200 words of substance — not 300 words with filler.

WHAT I'M BUILDING:
[Update this section each time you start a new project or client engagement — describe the specific operation, client context, and what you're producing for them.]

How to install your system prompt

1. Go to claude.ai → Projects and open your Project
2. Click Edit Project or the settings gear
3. Paste your system prompt into the Project Instructions field
4. Save — it now applies to every conversation in that Project

Context is the most underused element in most prompts, and the most important. Claude is only as useful as the information it has to work with. Giving it the right context is the difference between a useful first draft and a generic one you spend an hour fixing.

Four types of context that change everything

Uploading documents as context

One of the highest-leverage moves in Claude is uploading an existing document and asking Claude to work from it. Instead of describing your operation from scratch, hand Claude your current SOP, your tracker template, your client brief — and let it build on what already exists.

• Upload files using the paperclip icon in any conversation
• Tell Claude explicitly what to do with the document: "Use this as the baseline. Revise Section 3 to reflect the new procedure."
• You can upload multiple files — data files, templates, reference documents — in a single session
• In Projects, files uploaded to the Project are available in every conversation automatically

The single most powerful prompting technique most people never use: give Claude an example of the output you want.

Words like "professional," "concise," and "clear" are interpreted differently by everyone. An example is unambiguous. If you have a past SOP that's exactly the format you want, upload it. If you have a brief that hit the right tone, paste a paragraph in. Examples function as guardrails — they constrain Claude's interpretation and pull the output toward your actual standard.

Write a leadership brief on last month's production performance. Keep it professional and concise.

Write a leadership brief on last month's production performance. Match this structure and tone exactly:

"PRODUCTION SUMMARY — MARCH 2026
Overall output: 94% of target. Assembly A over by 4%, Packaging line under by 6%.
Key risk: Packaging line downtime trending up — 3rd consecutive month. Root cause not yet isolated.
Action required: Maintenance RCA due April 18."

One page max. Numbers first, then risk, then action. No narrative padding.

Negative examples work too

You can also tell Claude what you don't want — especially useful when you need to avoid a specific output style:

Write the SOP for our receiving inspection process.

Do NOT produce this kind of output:
"This Standard Operating Procedure is designed to ensure that all receiving inspection activities are conducted in a consistent and systematic manner, leveraging best practices from industry standards to optimize quality outcomes..."

DO produce this kind of output:
"1. Verify shipment count against PO. Log any discrepancy in RecLog before moving product.
2. Inspect outer packaging for damage. Photograph and quarantine any damaged units.
3. Pull 5% sample for dimensional check. Record results on Form RX-7."

Direct. Numbered. Actionable. Written for someone who already knows the job.

When Claude's first output isn't quite right, most people do one of two things: accept it anyway, or start over with a new prompt. Both are wrong. The right move is to refine in the same conversation — and to be specific about what needs to change.

Claude holds the full context of the conversation. It remembers what it produced and can adjust precisely. Think of it like directing a revision: not "do this again but better" — "change this specific thing, keep everything else."

High-leverage refinement instructions

• 1

  Scope corrections

  "Cut Section 2 entirely — the client already knows that background. Move straight from the performance summary to the risk items."

• 2

  Tone corrections

  "The tone is too formal for this audience. Rewrite it the way I'd talk to a plant manager I've worked with for three years — direct, no ceremony."

• 3

  Format corrections

  "Restructure this as a numbered checklist, not paragraphs. Each item should be one sentence — action + responsible party."

• 4

  Fact injections

  "The actual downtime figure was 14.2%, not 12%. Update that number and revise the risk assessment to reflect it."

• 5

  Expansion or compression

  "The risk section is too thin. Expand it to cover the top three risks with a severity rating and owner for each. Everything else stays as-is."

The prompts you write for your most common deliverables are reusable. Once you've written a tight prompt for an SOP, a production report, or a leadership brief — and it produced good output — save it. That's your template for the next time. A prompt library compounds: every good prompt you save means the next version of that deliverable takes less time.

Three starter prompts to build from

ROLE: Operations consultant preparing a status update for a manufacturing client's leadership team.

CONTEXT: [Paste current week's production data or describe the key numbers here]
Client: [Name]. Operation: [Type]. Reporting period: [Week of X].
Audience: Plant GM and ownership group. They want facts, variances, risks, and actions — not narrative.

TASK: Write a one-page production status brief covering:
1. Output vs. target (by line if applicable)
2. Key variances and probable causes
3. Top 1–3 risks requiring attention
4. Recommended actions with owners and due dates

STANDARD: One page. Numbers-first format. Bullet points under each heading. No filler language. Professional enough to send directly to the client.

ROLE: Operations documentation specialist writing for a [manufacturing / service / field] operation.

CONTEXT: [Describe the process: what it is, who performs it, how often, what equipment or materials are involved, any safety requirements, common errors or failure modes]

TASK: Write a Standard Operating Procedure for [process name]. Include:
- Purpose and scope (2–3 sentences)
- Required materials, tools, or PPE
- Step-by-step procedure with responsible party for each step
- Quality checkpoints or inspection criteria
- Common errors and how to prevent them
- Sign-off section

STANDARD: Produce the English version first, then the Spanish version immediately after. Use numbered steps. Language must be plain — written for someone who knows the job but is reading this for the first time. No corporate filler.

ROLE: Senior operations advisor writing a memo to a client's executive leadership.

CONTEXT: [Describe the situation: what happened, what decision needs to be made, what the options are, any relevant data or background]
Audience: [Title(s) of recipients]. Their priorities: [what they care about].

TASK: Write an executive memo covering:
- Situation summary (3–4 sentences)
- Key data or findings
- Recommended course of action with rationale
- Risks of the recommendation
- Requested decision or next step

STANDARD: One page. Direct. Written for a decision-maker who has 5 minutes, not 30. Lead with the recommendation, not the background. Professional letterhead-quality language.

These are starting points. After you use each one, refine it based on what worked and what didn't. Save yours somewhere you'll actually use it — a Project document, a Notes file, a shared drive folder.