A lesson is a job with a clock. Grok can fill a template. It cannot know your students, your shop, or what your program already promised.
Why this matters
Teachers open Grok and type “make a lesson on GIS” or “make this more engaging.” They get a cheerful pack: a hook, a video, a worksheet, a reflection. None of it fits the 50 minutes they have, the outcome the syllabus named, or the machine that is actually in the room. Students then perform the pack. Nobody can say what was learned.
This track is for people who already teach or take a real course — school, technical college, workplace training, a shop apprenticeship. If you do not have a course, pick one you will sit in this term. Hypothetical “Intro to Everything” fails the rubric.
Grok is useful here. It is also eager to invent standards, rosters, and equipment. Keep the outcomes yours.
Teach
Design backward, in shop language. Four blocks, in this order:
- Job. What can a student do when the period ends that they could not do when it started? One verb, one object, one context. “Name three drainage questions from this orthomosaic and say what they would measure next” is a job. “Understand remote sensing” is not.
- Proof. What will you see? A labeled screenshot. A six-line card. A 90-second oral. A calculation with the number they measured, not a number Grok offered. If you cannot name the proof, you do not have a lesson. You have a vibe.
- Practice. The smallest sequence that produces that proof. Minutes, not units. What they open. What they write. When they talk. When they use Grok — and for what.
- Rails. Time. Materials. Reading level. What they must not upload. What Grok is allowed to draft. What the student must still do with their own hands.
That is the whole method. Engagement is a side effect of a job that fits the room. Do not start there.
Outcomes are not Grok’s to write. Paste the one your program already named, or write it yourself before you open the thread. Then: “Do not add outcomes. Do not rephrase these into jargon. Design only the period that serves this job.” A model that “improves” your outcome into five Bloom verbs has already left the work.
Time is a constraint, not a mood. “A class period” is not a number. 45, 50, 75, 120. Subtract the first five minutes (login, attendance, the card on the board) and the last five (collect, say what is due). Design the middle. If the practice does not fit, cut the job. Do not speed-talk.
Grok’s honest jobs in design
- Interview you about the room, the clock, and the last thing students actually did.
- Expand one practice into timed steps.
- Find the hole: missing material, two jobs in one period, a proof Grok could finish alone.
- Draft the student-facing card once the design is yours.
Grok’s dishonest jobs
- Inventing a standard (“aligns to NGSS MS-ESS3-2”) you did not give.
- Inventing a roster, a reading level, or a lab with 24 iPads.
- Writing the student artifact for you and calling it a lesson plan.
A lesson that uses Grok needs a lab card even in this first draft: surface (grok.com), the prompt shape, the artifact, the stop. Next lesson is the integrity SOP. Today, name whether students open Grok at all. A period that never opens it is allowed. This track still requires you to open Grok to design.
One period, one job. “Cover chapter 4” is three weeks. Local beats generic: your county excerpt, last week’s shop photo. Grok is bad at your county unless you attach the page.
Honesty starts now. If Grok writes the worksheet and the key and you never do the job, you will ship a lab the model can finish in four minutes. Before you keep a practice, ask: could a student paste this prompt, submit the reply, and score full marks without looking at the world? If yes, change the proof.
Worked example
A 50-minute technical college lab. Course already exists: introductory geospatial. Last week they opened an orthomosaic in the lab software and only panned. The instructor wants them to read a site.
Job (instructor-written, before Grok): From a provided orthomosaic clip of a rural development at a prairie edge, write three drainage or access questions a field crew would actually measure, and name the tool or layer they would use next. No invented acreage.
Proof: A 10-line card: three questions, three next measurements, one line they are unsure about. Plus a 60-second oral if sampled.
What the instructor sent Grok (not “make a fun remote-sensing lesson”):
Intent: A 50-minute lab sequence I can run Thursday. I already have the job and the proof below. Do not change them. Do not add standards.
Context: 16 students, shared lab PCs, grok.com available. They have panned an ortho once. They have not done hydrology. Clip is a PNG I will attach — a new subdivision, prairie to the west, a slough on the south line, one county road. Clock: 5 min start, 35 min work, 10 min close. I will project the PNG. They may open Grok to critique their three questions, not to invent the site.
Constraints: No video. No group poster. No invented acres, elevations, or addresses. If you need a fact I did not give, write NEED instead of filling it.
Draft only: timed steps, what they open, the student card headings, and one hole in this design.
Grok tried to add a photogrammetry lecture and a “calculate area” step. The instructor deleted both — they did not have time to measure area honestly, and Grok would have invented it. The hole Grok did catch was real: no scale bar. The instructor added: “Do not report a length you did not measure in the GIS.”
Notice what never entered the thread: a request to write the students’ three questions. That would have been the key.
Your turn
Open grok.com. Start a new thread named lesson design — [course]. Use a course you teach or take this term. If you only train people at work, that course counts. You cannot pass with a made-up elective.
Exercise d-edu-l01-e1
| Field | Value |
|---|
| whereToDo | grok.com |
| time | 22 min |
Copy-ready prompt
Send this first. Answer Grok’s questions. Do not let it skip ahead.
I am in Grok Mastery (Russell Tech), Pathway D, Education, lesson 1 — lesson design.
Interview me with exactly six short questions, one at a time:
1) Course name and who the students actually are (age or program, not a persona)
2) Exact minutes I have for this one period
3) The job I want them to be able to do when they leave (I will draft it; do not invent it)
4) What proof I will look at
5) What materials I already have (file, photo, tool, room)
6) Whether students will open Grok this period, and if so, for what one task
Rules:
- Do not invent outcomes, standards, equipment, or student counts I did not give.
- Do not write the student artifact (the thing they will submit).
- After I have answered all six, write a Lesson Skeleton with exactly these headings:
- Course and clock:
- Job (verbatim from me, or "not given"):
- Proof:
- Practice, timed (you may draft steps):
- Grok’s role this period (none / named task):
- Materials I already have:
- NEED (facts you still lack):
- One way a student could let Grok finish the proof without looking at the world:
- Session stamp: today's date and "Lesson skeleton written by Grok in this thread."
If Grok dumps all six questions, answer in one block and tell it to proceed. If it adds a standard or a 24-iPad cart, tell it to delete the invention and reprint the skeleton.
Artifact to paste
- Grok’s Lesson Skeleton (all headings, including NEED, the cheat-path line, and the session stamp).
- The six answers you gave (short).
- Two lines from you:
Job is mine: yes/no — if no, what Grok invented.I will change the proof so Grok cannot finish it alone: plus the change, or already true because: plus the reason.
Rubric
- Pass: The skeleton is Grok-authored and stamped. Job and proof match what you said, not a new outcome. Clock is a number. The cheat-path line is specific to this job. Your extra line either patches the proof or defends it. The course exists.
- Fail: “Make a lesson on X” with no interview. A skeleton you typed without Grok. Invented standards left in. A job of “understand the unit.” A hypothetical course you do not teach or take. No session stamp.
Common failure
The common failure is starting with activities. Stations, a Kahoot, a “hook,” then an outcome taped on at the end. Grok is extremely good at that shape. It is how you get a busy period and an empty proof.
The other failure is letting Grok write both the lab and the exemplar. You now have an answer key that is also the student pathway. Change the proof until a human has to look at this site, this paragraph, or this weld.
What’s next
You have a skeleton. Next: rubrics and academic integrity — the line between a student using Grok and a student submitting Grok’s work. That line is the rest of this track.
