Most Grok work is not a research paper. It is a message you have to answer and a week you have to run. This lesson is that desk.
Why this matters
People either never let Grok near the inbox, or they paste the whole account and accept the first draft. Both are sloppy. The first leaves the worst part of the job untouched. The second invents a date, a promise, or a tone you did not authorize, and then you click send.
A useful operator brings one thread, names the outcome, and forbids invention. Grok lists what the message actually contains. You decide. Grok drafts. You send.
The same pattern runs a week. Grok cannot see your life unless you show it. A five-day plan built from invented meetings is fiction. A five-day plan built from the commitments you paste is a tool.
Teach
Do this on grok.com, in a thread named after the job (Vendor delay — Aug, Board packet week). Not on X. Not in a public place.
Do not start by connecting your whole mailbox unless you already understand connectors and your shop allows it. Grok can attach Gmail, Google Calendar, Outlook, and others from grok.com/connectors. That is optional. For this lesson, paste is the default. Paste is visible. Paste is enough. If you do use a connector later, you are still the one who sends.
What you paste:
- one email, chat, or voicemail transcript you must deal with this week
- redacted names if the other party did not agree to land in a model
- no passwords, account numbers, medical details, student records, SSNs, badge numbers, or anything you would not put on a shared shop computer
If the real message is too hot to paste even redacted, pick a different message. Do not invent a fake crisis for sport. The exercise needs a real ask.
Give Grok a job in this order:
- Extract. Decisions already made. Asks of you. Asks you made. Dates. Numbers. Risks. A line that says
NOT IN MESSAGE for anything it wants to assume.
- Outcome. What “done” looks like (a reply, a hold, a meeting, a no).
- Constraints. Tone, facts you will not state, promises you will not make, length.
- Draft. A reply you could send. Short. No new commitments unless you listed them.
- Plan. Five working days. Only items that came from the message plus a short list of commitments you add. If a day is empty, write empty. Do not fill Thursday with “deep work on synergy.”
A few rules that keep you employed:
- Grok does not send. You do. Read the draft as if opposing counsel will.
- Numbers in the reply must appear in the source or in a note you typed (“I confirmed $1,200 with Dana”). Otherwise cut them.
- Apologies and blame. If you did not tell Grok to apologize, it should not. If you did not assign fault, it should not.
- Calendar math. “Next Friday” is a date. Make Grok write the date. Then check a calendar you trust.
- Fast vs Think. Fast is fine for extract-and-draft on a single message. Think if the thread is long or the plan has dependencies.
You already know how to challenge a claim. Use it here. If the draft says “as we agreed on the 12th” and the email never said that, the line is WRONG. Delete it.
After the draft is good, ask for a send checklist of five lines you will look at before you hit send. Then look at them. Do not outsource the last look.
Worked example
A vendor writes: the insulator shipment slips from Thursday to the following Tuesday. The crew is scheduled Friday. The email asks whether to hold the crew or split the job.
Wrong use: “write a nice reply.” Grok invents a 10% discount, thanks them for “continued partnership,” and offers Saturday overtime nobody authorized.
Better use. She pastes the email (vendor company kept, personal cell cut). She writes:
Extract only. Then draft a reply: we hold Friday’s crew; we do not split; we need a firm Tuesday AM window by 10:00 tomorrow. Do not offer money. Do not apologize for their slip. Tone: plain.
Extract comes back with the slip, the Friday crew, and NOT IN MESSAGE: any new price. Draft is eight lines. She changes one sentence. Five-day plan:
| Day | Work |
|---|
| Mon | Wait for Tuesday window in writing. |
| Tue | If window is firm, confirm gate time. If not, call. |
| Wed | Empty on this job. |
| Thu | Pre-stage what we already have. |
| Fri | Crew held. Do not show up to install what is not there. |
She sends the reply herself. The thread stays named. That is the operating system.
Your turn
Open grok.com. New thread. Use one real message from this week (email, text, LMS note, vendor portal, voicemail you transcribe). Redact what you must. If your week is quiet, use a real message you have been avoiding — not a hypothetical from a blog.
Exercise a7-l01-e1
| Field | Value |
|---|
| whereToDo | grok.com |
| time | 18 min |
Copy-ready prompt
I am in Grok Mastery (Russell Tech), Pathway A, lesson A7 — email and planning.
I will paste one real message (redacted). Then I will state the outcome I want.
First pass — Extract only, using these labels:
- Decisions already in the message:
- Asks of me:
- Dates and numbers (quote them):
- Risks:
- NOT IN MESSAGE (list assumptions you are tempted to make, and do not use them):
Do not draft yet. Do not invent facts. End with a Session stamp: today's date and "This extract was written by Grok in this thread."
After the extract, send:
Outcome I want: [one or two sentences]
Constraints: [tone, promises I will not make, length]
Facts I am adding in my own name: [or "none"]
Now write:
1) a Reply I could send (no new facts except the ones I just added)
2) a five-day plan (Mon–Fri or the next five working days) using only the message + my added facts + this one extra commitment list I type here: [list or "none"]
3) a five-line Send checklist
If a day has no work from those inputs, write "empty."
End with a Session stamp: today's date and "This draft and plan were written by Grok in this thread."
Artifact to paste
Paste, in this order:
- The Extract (not the raw email if it is sensitive) and first stamp.
- The Reply, five-day plan, Send checklist, and second stamp.
- One sentence you wrote: whether you will send the reply as-is, and one line you changed or would change.
Redact remaining names if needed. Keep dates and the NOT IN MESSAGE list.
Rubric
- Pass: Extract has a
NOT IN MESSAGE list. Reply does not introduce facts that are absent from the extract and from your added-facts line. Plan has five days; empty days are allowed. Both stamps present. Your sentence names a send decision. The source was a real message, not a movie plot.
- Fail: You let Grok invent a discount, a date, an apology, or a meeting that was not in the inputs. No extract, only a “professional email.” You pasted secrets (passwords, medical, student records, SSNs). You used Grok on X for a client message. No session stamp. You claim you sent Grok’s first draft unread.
Common failure
The common failure is the helpful extra. Grok adds a meeting, a percentage, or “let’s hop on a call.” You leave it in because it sounds like management. You have now promised a call you will resent and a number you cannot defend.
The fix is the NOT IN MESSAGE list. If a line is on that list, it does not appear in the reply unless you add it in your own name. The other fix: empty Thursdays. A plan that cannot tolerate an empty day is a wish list.
What’s next
The inbox is one loop. Next lesson: learning a topic you actually need — questions first, then study, then a closed-book check so Grok cannot take the exam for you.
