Module 18 · Lesson 03

Teaching Non-Technical Clients to Prompt Effectively

Reading time: 15 minutes Track: Yungsten Tech Employee Curriculum · Consultant path

The teaching challenge

Most non-technical clients approach Claude the way they approach a search engine: short, keyword-heavy queries that don't give enough context. Or they go the opposite direction and write paragraph-long questions that bury the actual request.

Teaching prompting isn't teaching a technical skill. It's teaching a communication style. The framing matters: "You're learning to communicate with a very capable new colleague" lands better than "You're learning prompt engineering."

The three concepts that unlock 80% of improvement

Concept 1: Context is the input, output is the output

"Claude is a language model — it generates text based on what you give it. If you give it vague input, it makes assumptions. If you give it rich context, it generates specifically for your situation."

Demonstration: Run the same request with minimal context, then with rich context. Show the output difference side by side. This demonstration is worth 20 minutes of explanation.

Concept 2: You're talking to a smart new hire who needs context

"Imagine a brilliant new hire who started yesterday. They don't know your company, your clients, your history, or your preferences. How would you brief them? That's exactly the context Claude needs."

This frame works because everyone knows what it's like to brief someone new. It removes the "talking to a computer" anxiety and replaces it with a communication model they already know how to use.

Concept 3: Iteration is the process

"Getting a good output on the first try is a bonus, not the standard. The normal pattern is: get a decent output, notice specifically what's wrong, and ask for that specific change."

Demonstration: Take a mediocre first output and improve it with one specific refinement instruction. Show that it gets better.

The teaching progression

Session 1 (usually in the first or second seminar):

• Context concept + demonstration
• "New hire" frame
• Participants try one prompt with and without context

Session 2 (usually the second monthly seminar):

• Iteration concept + demonstration
• Introduce format specification: "Teach them to say 'respond as a bulleted list' or 'keep this under 100 words'"
• Participants work on a real task through two iterations

Session 3 (by month 3):

• Introduce the team prompt library
• Workshop: group identifies 3 recurring tasks and documents prompts for each
• The group becomes the teachers for new team members

Coaching individual prompting in the moment

When you're in a session and someone writes a weak prompt, don't take over the keyboard. Ask questions:

• "Who is going to read this output?"
• "What's the one thing you need this to do?"
• "What specifically is wrong with this output?"

These questions guide the person to improve the prompt themselves. The insight sticks better than you fixing it for them.

The confidence building arc

The goal of prompting instruction isn't perfect prompts — it's confidence. A team member who writes imperfect prompts but confidently iterates gets great results. A team member who writes perfect prompts but gives up after one bad output doesn't.

Design your instruction to build confidence first. Celebrate the iteration, not the first-draft perfection.