A first message is a briefing, not a greeting. If Grok has to guess the job, you will spend the thread undoing the guess.
Why this matters
Most weak Grok output is a weak brief. “Write a professional email.” “Help me plan my week.” “Explain drones.” The model will fill every blank you left. It will pick a reader you do not have, a length you cannot use, and a tone that sounds like a press release.
You already know how to brief a person. Site, time, who is standing there, what “done” looks like, what not to touch. Grok needs the same. The difference is that a person will interrupt you. Grok will cheerfully invent the rest.
This lesson is one useful message about a real job from your next seven days — a parent email, a vendor note, a listing description, a kitchen prep list, a county form. If you do not have a job you would show a colleague, you are not ready to call the model useful. It does not have to be geospatial or software.
Teach
A useful first message has five parts. You do not need headings. You do need the information.
- Job. What should exist when this is done? A 150-word email. A six-line checklist. Three questions to ask a vendor. Not “help with my inbox.”
- Reader. Who gets this, and what do they already know? A superintendent is not a student. A parent is not a contracting officer.
- Context. What is true right now? Dates, place, constraints you did not choose, the last thing that happened. Two to six lines. Not your life story.
- Constraints. Length, format, tone, must-include, must-not. If you need plain text, say so. If names must stay out, say so.
- Stop. How will you know it is finished? “I can send this after one edit.” “I can read it aloud in two minutes.” If you cannot name a stop, you asked for a conversation, not a product.
What you leave out on purpose:
- Do not open with “hi” or “act as.” Grok already knows it is Grok. Role-play is a spice, not a brief.
- Do not ask what Grok can do. That produces a brochure. You came here to do a job.
- Do not stack five jobs. One message, one output. A second job is a second message or a second thread.
- Do not outsource the decision you still own. “Should I fire this vendor” is not a first-message job. “List three risks in this renewal paragraph” is.
A first message is allowed to be ugly. Bullet points are better than a speech. If you only have a messy paragraph, send it and add one line: “Turn this into [format] for [reader], [length].”
You will edit. The first reply is a draft, not a verdict. Your job after send is to read it like you would read a junior’s work. Would you put your name under it? If not, the next lesson is how to iterate. This lesson is only: did you brief the job well enough that a draft is possible?
A note on honesty. If the real job involves a client name, a student’s grade, a medical detail, or a password, strip it. Use a stand-in. Useful does not mean careless.
Worked example
Bad first message:
Write a professional email about the meeting.
Grok will invent a meeting, a tone, and a call to action. You will spend four turns saying “no, not that.”
Useful first message:
Job: 120–150 word email I can send today.
Reader: Maya Chen, county GIS lead. She already knows the flight happened. She does not know why the deliverable is late.
Context: Thursday corridor scan, Hughes County. Memory card fault on the second battery swap. We have the north half processed. South half reflies Monday 10:00 if weather holds. She asked Friday for the mosaic by end of day Monday.
Constraints: Calm, specific, no apology paragraph. Offer two options: partial mosaic Monday 16:00, or full mosaic Wednesday 10:00. I need her to pick one. No jargon she would have to look up. No mention of the intern.
Stop: I can hit send after changing only the greeting.
That brief is not clever. It is complete. The reply you want is an email you could send, not an essay on communication.
If you work outside field ops, the shape is the same. A teacher: quiz for period 3, twenty minutes, no names. A shop owner: voicemail script, forty seconds, hours and the Saturday exception. A student: outline for a two-page lab, methods only.
Your turn
Open grok.com. Start a new thread named after the job, not after this course. Use a real task from the next seven days. If you truly have nothing, use a real email, note, or message you owe a person who exists.
Do not reuse the tailboard example from the last lesson. Grok should have to work on your facts.
Exercise a1-l02-e1
| Field | Value |
|---|
| whereToDo | grok.com |
| time | 14 min |
Copy-ready prompt
Fill the brackets. Delete the bracket hints. Then send it as your first message in the new thread.
Job: [what should exist when this is done — name the artifact and a length]
Reader: [who gets it, and what they already know]
Context: [4–8 lines of what is true right now. Dates, place, the last thing that happened.]
Constraints:
- Format: [email / checklist / outline / script / other]
- Length: [words, lines, or minutes]
- Tone: [one line]
- Must include: [facts that have to appear]
- Must not: [names, topics, or tone to keep out]
Stop: I can use this after at most one edit.
Write only the artifact. After the artifact, add:
- a short "Assumptions" list of anything you had to invent (mark invented facts)
- Session stamp: today's date and the sentence "First useful draft written by Grok in this thread."
Artifact to paste
Paste all three:
- The exact first message you sent (the filled brief).
- Grok’s artifact plus the session stamp (keep assumptions if they are short).
- Two lines from you:
Send? yes / no — plus one reason.Missing from my brief: plus the one fact you wish you had included.
Rubric
- Pass: The brief names a job, a reader, and a stop. Context has concrete facts (a date, a name-or-role, or a place). Grok returned an artifact you could show someone, not a lecture about how to write. The session stamp is present. You answered Send? with a reason. The job is yours, not the course’s tailboard example.
- Fail: “Write a professional email” with no reader. A paste of Grok’s capabilities page. No stamp. A yes you could have written without opening Grok. Five jobs in one message. You claim pass without Grok’s artifact.
Common failure
The common failure is asking Grok to be a search box or a therapist. “What’s going on in the news.” “I’m overwhelmed, tell me what to do with my life.” You will get words. You will not get a product you can stand behind.
If you need news, you will use Search later. If you need a plan for a messy week, shrink it: “Thirty-minute plan for Thursday morning, three tasks, I have a 9:00 call and a truck at 11:00.” That is a job.
The other failure is a brief so long Grok cannot see the request. If you paste two pages of notes, add one line at the top: “Read this. Then write [artifact] for [reader], [length]. Ignore greetings and small talk in the notes.”
What’s next
You can brief a first draft. Module A2 is how conversations actually work: intent, context, constraints as a habit — then how to iterate in the same thread instead of starting over every time the reply is off.
