Purpose
~3 min
Chapter 1 introduces a central shift in prompt cartography: the LLM may help execute ideas, but the human still directs purpose, audience, emphasis, restraint, and responsibility. This lab helps you practice that directorial role by comparing how a model responds as your prompt becomes more intentional.
Core idea Clear language is part of cartographic design. The prompt is where many map decisions begin.
Learning objectives
~2 min
- Explain how prompt cartography shifts execution without surrendering cartographic judgment
- Compare casual, purposeful, and constrained prompts for the same map idea
- Write a short prompt-director brief that states purpose, audience, memory, and guardrails
Tools a web browser and one free LLM such as ChatGPT, Claude, Gemini, Copilot, or Perplexity.
No GIS, coding, paid account, or file upload is required.
Part 1 — Baseline: the casual request
~8 min
Open a free LLM and paste this prompt. Replace the bracketed topic with a real map idea you might care about.
Make a web map about [YOUR TOPIC].
Save or copy the answer into notes. Do not improve the prompt yet.
What to notice
- What purpose did the model assume?
- Who did it seem to design for?
- Which data, colors, or interface choices appeared without you asking for them?
Mini-deliverable Write one sentence beginning: “The model assumed this map was for...”
Part 2 — Purpose and audience first
~12 min
Now give the same map idea a communicative purpose and a specific audience.
I want to create a public-facing web map about [YOUR TOPIC] for [SPECIFIC AUDIENCE].
The purpose of the map is to help them [DECISION, INSIGHT, OR ACTION].
Recommend a map concept, key data layers, and a short explanation of what users should remember after using it.
Do not write code.
What to notice
- Did the answer become more selective?
- Did the model describe what the user should remember?
- Did the response still include unnecessary features or vague audience assumptions?
Chapter connection this is the shift from procedural execution to expressive clarity. You are not asking harder. You are directing more clearly.
Part 3 — Add guardrails
~12 min
Run a third version. Keep your topic, audience, and purpose, then add constraints.
I want to create a public-facing web map about [YOUR TOPIC] for [SPECIFIC AUDIENCE].
The purpose is to help them [DECISION, INSIGHT, OR ACTION].
Guardrails:
- Avoid implying that places or people are simply “good” or “bad.”
- Avoid red/green as the only meaningful color contrast.
- Prefer a small number of layers over a comprehensive but confusing map.
- Include one uncertainty or limitation users should know.
- Keep the recommendation understandable for someone new to maps.
Recommend the map concept, key layers, interaction ideas, and the one thing users should remember.
Do not write code.
What to notice
- Which guardrail changed the answer most?
- Did the model respect all constraints or quietly drift?
- What responsibility still belongs to you, even if the answer improved?
Part 4 — Synthesize as a prompt director
~10 min
Compare the three outputs. Then fill in this short brief in your own words.
Prompt Director Brief
Topic:
Audience:
Purpose:
What users should remember:
What the map should emphasize:
What the map should omit or downplay:
Guardrails:
One risk or uncertainty:
One thing I would check before trusting the output:
Core deliverable your completed prompt-director brief plus a 3–5 sentence reflection on how your wording changed the model's behavior.
- Where did the casual prompt fail to represent your intent?
- What became clearer when you named an audience?
- Which constraint felt most like cartographic judgment rather than “AI prompting”?
Optional stackable labs
~15–30 min each
Option 1 — Cross-LLM director check
Run your final guarded prompt in two free LLMs. Score each one from 1–5 on audience fit, obedience to guardrails, clarity, and overconfidence. Write one sentence naming which model you would keep working with and why.
Option 2 — Audience swap
Keep the same topic and purpose, but change only the audience. For example, switch from “local residents” to “city planners” or “middle school students.” Compare how the recommended layers, language, and interactions change.
Option 3 — Constraint stress test
Add one strong constraint, such as “use no more than three layers,” “avoid ranking places,” or “design for colorblind accessibility.” Ask the model to explain what it had to sacrifice. Decide whether the tradeoff improves the map.
Looking ahead
~2 min
Later labs build from this brief into structured prompt specifications, context documents, critique loops, and reproducible map workflows.
For now the medium changed, not the craft. Your language is part of the mapmaking record.
Submission
checklist
- Main lab artifact or brief
- Comparison/critique notes
- Short reflection
Evaluation Notes Strong submissions show concise prompting, cartographic judgment, human verification where needed, and a defensible keep, revise, reject, or stop decision.
Psst! Before You Turn This In...
~3 minQuick human check before this leaves your desk.
Do the tiny-but-mighty judgment check. If these answers are fuzzy, revise the map idea before polishing the prompt.
- Purpose: Can you say what this map helps someone understand or decide?
- Evidence: Can you point to the data, source, or context behind the claim?
- Omission: Did you leave out, downplay, or defer anything that would distract or mislead?
- Risk: What could be overstated, exposed, or misunderstood?
- Human check: What must be verified outside the LLM?
- Stop rule: What would make you redesign, withhold, or simplify this map?
Ian's recurring refrain Prompt frameworks are scaffolds. The LLM can suggest, critique, and surprise you; you still own the cartographic judgment.
Reference
For use with Prompt Cartography: Interactive Web Map Design with LLMs, CRC Press. www.promptcartography.com
Next lab (recommended)
keep momentum
Go to next lab