1.1 — Creating Effective Prompts for Business and Technical Tasks
CCAO-F Domain 1 · Task 1.1
What You Need to Know
Treat Claude as a brilliant but new employee: highly capable, with no context until you supply it.
The Five Components of a Complete Business Prompt
- Task — verb + deliverable (“Draft a one-page project update for the steering committee”)
- Context — audience, purpose, decisions already made, constraints
- Source material — paste/attach the real inputs; do not describe from memory
- Output specification — format, length, tone, structure
- An example — one sample of a previous document in the house style
Role and Audience Framing
Opening with a role shapes vocabulary, tone and priorities. Naming the audience changes the output more than most instruction tweaks.
Specificity Buys Time
A vague prompt produces generic output that needs heavy rework. A minute on the brief saves a rework cycle.
Key Concept: When an exam item compares prompts, count the components. The keyed answer almost always supplies the missing task, context, source material, output specification or example.
Exam Traps
- Accepting the one-line prompt because Claude will figure it out
- Choosing the option that polishes wording while the real gap goes unfilled
- Writing the deliverable yourself and using Claude only to proofread
Check your understanding
Practice Scenario
A facilities coordinator needs Claude to draft a staff memo introducing a new desk-booking system. She has the supplier's how-to guide and wants a draft she can send without reworking it by hand. Which approach sets the work up best?
Log in to save your progress.
Sources
- Prompt engineering overview, Claude Platform Docs
- Prompting best practices, Claude Platform Docs
- AI Fluency: Framework & Foundations, Anthropic Academy
- Claude 101, Anthropic Academy