10 min · Beginner
Challenge: Your First 10 Minutes
You will run a timed loop: look at the screen, send a vague prompt on purpose, rewrite it with a full brief, and save the better version.
Learning objectives
- Spend two minutes naming the parts of the screen you will actually use.
- Rewrite a vague standup prompt using role, context, task, constraints, and output.
- Ask what was unclear, then save the stronger prompt in a note before the timer ends.
01
Why this matters
Reading about prompts is not the same as feeling a weak one fail. Ten minutes is long enough to compare a vague ask with a brief you can reuse. You stop when the timer ends so the habit stays small enough to repeat tomorrow.
02
Concept
This lesson is a timed practice, not a new theory chapter. Set a 10-minute timer and keep Gemini open. From minute 0 to 2, explore the screen. Name the model label if you see one, the place you would upload, and the control for a fresh chat. Do not hunt for a perfect layout. Say what you see in your own words, because the screen as of late 2026 can change. Check the current screen once, then start.
From minute 2 to 4, send a bad vague prompt on purpose. Something like help with the meeting is enough. Notice how wide and generic the answer is. You are not trying to feel foolish. You are noticing what disappears when you give no role, no context, no real task, no constraints, and no output shape. Keep that vague prompt so you can compare it with the rewrite.
From minute 4 to 7, rewrite the prompt with five pieces. Role is who the helper should be. Context is the facts it needs, with no secrets. Task is the job. Constraints are limits such as time, tone, and what not to invent. Output is the shape you want back, such as a timed agenda plus a note you can paste after the meeting. Send the rewrite in a fresh chat if the first thread is muddy.
From minute 7 to 10, ask what was still unclear in the better prompt. Add one fact it truly needed, such as who speaks first. Then save the better prompt in a note you control. Add one check you will do yourself, such as reading every name and time before you use the plan. Stop when the timer ends. A loop you finish beats a long chat you abandon.
03
Real-world example
Elena times her standup prompt
Elena leads a facilities crew in Rotterdam. She sets a ten-minute timer. For two minutes she names the chat box, the model label, and the new-chat control. She types help me with standup and watches a vague answer wander past her real work. She rewrites with a role, six people, three remote, the Lobby refresh and the Roof leak, a fifteen-minute limit, and an output of a timed agenda plus a note template. She asks what was still unclear. The reply asks whether remote staff should speak first. She adds that line, saves the prompt in a note called Monday standup, and stops when the timer ends. The saved prompt is the result she keeps, not a fantasy of a perfect meeting.
04
Gemini demonstration
A realistic exchange. Open Gemini beside this page and try a version with your own facts.
You
Help me plan the team standup.
Gemini
That prompt is too thin to plan a real standup. I can draft an agenda, but I would be inventing the team size, the time limit, the projects, and who is remote. Those inventions feel specific and can still be wrong. Tell me five things. Role: am I coaching you as the facilitator? Context: how many people, how long, and which projects are actually in play? Task: a plan, not a speech. Constraints: what I must not invent, and whether blame is off limits. Output: a timed agenda, the questions you will ask, and a note template. A stronger prompt looks like this shape: six people, fifteen minutes, Lobby refresh and Roof leak, remote people first, no invented project names. Send that and I will write the plan.
You
You are helping a team lead at a small facilities company. Context: six people, a 15-minute Monday standup, three people on site and three remote. Projects in play are only Lobby refresh and Roof leak. Task: draft the standup plan. Constraints: no more than 15 minutes, plain language, no blame, and do not invent project names. Remote people should speak first. Output: a timed agenda, three questions I will ask, and a four-line note template I can paste in chat after the meeting.
Gemini
Standup plan for six people, fifteen minutes, Lobby refresh and Roof leak only. Remote people speak first. No blame, and no extra projects. Minutes 0 to 2: you state the purpose, priorities and blockers only. Minutes 2 to 9: remote staff first, then on-site staff. Each person gets one minute. Minutes 9 to 12: park anything long. Minutes 12 to 15: read back owners and the next check time. Ask: What will you finish today on Lobby refresh or Roof leak? What is blocked, and who must decide? What should wait until after this standup? Note template: Lobby refresh today. Roof leak today. Blocked, with owner. Parked for later. Read every name and time yourself before you send the note. I did not invent a third project.
05
Prompt breakdown
The prompt
You are helping a team lead at a small facilities company. Context: six people, a 15-minute Monday standup, three on site and three remote. The only projects are Lobby refresh and Roof leak. Task: draft the standup plan. Constraints: stay within 15 minutes, use plain language, no blame, do not invent project names, and let remote people speak first. Output: a timed agenda, three questions I will ask, and a four-line note template I can paste after the meeting. After the plan, list one thing in this prompt that is still ambiguous.
- The role and the real projects stop the model from inventing a different company.
- Context gives headcount, time, place, and who speaks first.
- Constraints forbid blame and extra project names, which vague prompts invite.
- The output names an agenda, questions, and a note, so you can tell when it is done.
06
Common mistakes
Usually
Help me with the meeting.
Better
Draft a 15-minute standup agenda for six people covering only Lobby refresh and Roof leak, plus a four-line note.
Usually
Make the standup inspiring, fun, and also rewrite our whole strategy.
Better
Keep the output to a timed agenda, three questions, and a note. Leave strategy for another brief.
Usually
You know our staff. Use their names and phone numbers from last time.
Better
Do not use personal names or phone numbers. Use roles only, and I will add names offline.
07
Practice exercise
Run the timer once
Done when: Your note holds both the vague prompt and the rewritten prompt, and you stopped when the timer ended.
08
Challenge
Save a prompt you will use Monday
Run the ten-minute loop on a real recurring moment, such as a team standup, a study group, or a family admin check. Keep secrets out. Send the vague version only as a drill, then the full brief in a fresh chat. Ask what was unclear, repair one gap, and save the final prompt where you will find it on Monday. Add a check you will do with your own eyes, such as times, names, or places the model must not invent. If you finish early, do not add a second project. End on time so the loop stays repeatable.
Hint: A prompt you can paste again next week is a better result than a clever answer you forget.
09
Key takeaways
- Minute 0 to 2 is for the screen. Minute 2 to 4 is a vague prompt you send on purpose.
- Minute 4 to 7 adds role, context, task, constraints, and output.
- Minute 7 to 10 asks what was unclear and saves the better prompt in a note.
- A strong standup brief names the people, the time box, the real projects, and the note you will paste.
10