Lexicon · II · Access
Prompt
Also: instruction
The brief you give the model: the request, the context, the constraints and the expected format. The quality of the answer is largely decided by the quality of that brief.
The analogy
The brief you give a talented freelancer who knows nothing about your company. "Make me a brochure" will produce something generic and clean. "Here is our positioning, the audience, three examples we love, the required format and what must absolutely be avoided" will produce usable work. Same freelancer, same rate: everything is in the brief.
A concrete example
"Summarize this report" versus "Summarize this report in ten lines for a rushed executive committee: keep the financial impact figures, flag what remains uncertain, end with the decision to be made". Same model, same document, two answers worlds apart. The second required no technical skill, only knowing what you want.
What it is NOT
It is not a magic spell: the "perfect prompt" compensates neither for a bad question nor for missing context. It is not an engineering specialty: it is a management skill, that of knowing how to brief. And it is less and less a purely human act: in AI products, most prompts are assembled backstage by the harness.
Often confused with
The distinction that changes the conversation.
- Search query
- On a search engine, you throw keywords and sort the results yourself. A prompt is a brief to a doer: goal, context, constraints, format. Prompting the way you google is briefing a collaborator in three keywords, and being surprised by the result.