Zero-shot prompting asks an AI to solve a problem with no prior examples—just the task itself—testing whether it can apply general knowledge to new situations. This matters because it reveals both the limits and surprising capabilities of AI reasoning, and teaches you to write clearer instructions by forcing you to be explicit about what you want rather than relying on pattern-matching.
You need to create a decision matrix for choosing between three competing priorities. You've never asked an AI to do this before, and you don't have an example of what you want. You just describe what you need: "Create a table comparing these three projects on criteria: timeline, impact, resource needs, and risk." The AI does it, unprompted. That's zero-shot prompting.
The opposite approach—showing the AI an example first, then asking it to do the same thing—is called few-shot prompting. Both have their place. Zero-shot is faster; few-shot is more reliable when you have specific requirements.
A "shot" is an example. Zero-shot means zero examples. You're asking the AI to infer what you want from your description alone. One-shot means you've shown one example. Few-shot means you've shown a few. This vocabulary matters because it describes your strategy—how much guidance you need to give the AI before it understands your task.
Zero-shot works well for tasks that are straightforward or common enough that the AI already understands the pattern. Summarization, brainstorming, task breakdown, categorization—these are tasks AI has seen thousands of times in training data. The AI can infer what you want from natural description alone.
Ask for common productivity outputs with clear descriptions, and zero-shot prompting almost always succeeds. "Break this project into weekly milestones." "Summarize these three meeting notes." "List potential risks for this plan." These are standard enough that AI doesn't need to see an example.
Zero-shot also works when your needs are unique, but your description is very specific. "Create a daily checklist for onboarding a new remote contractor, customized for someone with no experience in our industry." The AI can extrapolate from the specificity of your request.
Use few-shot prompting when:
Few-shot doesn't require perfect examples, just clarifying ones. Even a rough example of "this is the style/format/depth I want" helps the AI calibrate.
Start zero-shot. Describe what you want clearly, and most productivity tasks will work. If the output is close but needs refinement, you can iterate: "More detailed" or "More concise" or "Follow this format instead." Only move to few-shot if iteration isn't getting you there, or if you need to be faster next time on a similar task.
Try this: Pick a productivity task you need to do—maybe a decision matrix, a brainstorm list, or a project breakdown. Ask your AI with zero examples: just a clear description of what you want. Note what works well and what doesn't. Next time you need something similar, if the zero-shot attempt didn't nail it, save a good example and use few-shot prompting for faster results.
Peri can explain this concept, give practical examples, help you decide whether it applies to your situation, or recommend a journey if appropriate.
Explore related journeys or tell Peri what you're working through.