12 min · Intermediate
Daily Planner and Weekly System
Run a weekly planning session and a short daily pass that suggest blocks without inventing your calendar.
Learning objectives
- Turn a task dump into three weekly outcomes and a parking list.
- Draft a Monday plan and a Friday review you can paste again.
- Treat time blocks as suggestions and reject any meeting you did not supply.
01
Why this matters
A week without a system becomes a list of reactions. A Monday plan and a Friday review give Gemini the same job every time, so you can see what to change. You stay faster at drafting the week, and you still own every commitment on the real calendar.
02
Concept
A weekly planning session is one sitting, not a mood. Dump every open task first, without ranking. Mark energy as high focus, medium, or low. Pick three outcomes: a finished result, not a motion such as check email. Park the rest so they stay visible without pretending to fit. The model can cluster and challenge those three outcomes. It cannot know which promise you already made to another person.
The daily pass stays short. Ask for a top three, suggested time blocks, and a shutdown list. A time block, meaning a proposed slice of the day, is not a booking. A shutdown list covers send, file, or an explicit postpone. Keep blocks as suggestions until you compare them with the day you have. Gemini does not know your calendar unless a connected feature is on and you confirm it. Check the current screen first.
State four meetings and a proposal due Thursday, and paste titles and times yourself. Label each meeting as given by you, not discovered. Ask for deep work only in the gaps you listed. A fifth meeting is an error. Demand a conflict check against the meetings you already named. Fiction dressed up as your calendar is a failed plan, even when it looks tidy.
End the week by reviewing the same three outcomes. Ask what moved, what slipped, and what you overrode. Overrode means you rejected a suggestion, and that can be a success. Capture one prompt edit, such as a tighter rule against invented attendees. Save the weekly prompt and the daily prompt for Monday. The system is the rerun, not one clever answer. If the week was messy, the review should say so.
03
Real-world example
A Sunday prompt that survives Thursday
Nia manages a four-person finance team. On Sunday she pastes nine tasks and three outcomes: finish the Thursday proposal, close two vendor questions, and publish the staffing note. She marks the proposal as high focus and the staffing note as low. The prompt lists four Thursday meetings with times and forbids any new meeting. It asks for work blocks only in the open gaps she named. Gemini suggests writing before the design review and a vendor block after lunch. Nia deletes a 16:15 slot because it hits her one-to-one. She keeps a shutdown list: send the draft to herself, file the notes, and postpone the rest. That saved prompt is her weekly productivity system.
04
Gemini demonstration
A realistic exchange. Open Gemini beside this page and try a version with your own facts.
You
I manage a finance team. Thursday I already have four meetings, which I am listing so you do not invent any: 09:00 to 09:30 standup, 11:00 to 12:00 design review, 14:00 to 14:45 stakeholder update, 16:00 to 16:30 one-to-one. A proposal is due Thursday. Outcomes this week: send the proposal, close two vendor questions, publish a staffing note. Energy: proposal is high focus. Propose a Thursday plan using only the gaps between these meetings. Do not add meetings. Say unknown if you lack a fact. Label the plan as a suggestion, not my calendar.
Gemini
This is a suggestion, not a calendar I can see, and I am not adding meetings. From 09:30 to 11:00, draft the proposal, because it is due Thursday and you marked it high focus. From 12:00 to 14:00, handle one vendor question and leave room to eat. From 14:45 to 16:00, handle the second vendor question rather than new writing. After 16:30, shutdown only: save the draft, file the vendor notes, and postpone the staffing note if it did not fit. I do not know your commute or whether these meetings still stand. Confirm the gaps before you commit. If a meeting moved, say so and we rebuild from your list.
You
The 12:00 block is wrong: I eat with the team most Thursdays and that gap is not free. Rebuild the day without booking 12:00 to 13:00. Then write a five-line Friday review I can paste next week. It should ask what moved, what I overrode, and which outcome is still open. Do not invent how the proposal went.
Gemini
Rebuilt suggestion, still not a calendar. 09:30 to 11:00 remains proposal drafting. 12:00 to 13:00 stays blank because you said it is not free. 13:00 to 14:00 can hold one vendor question if you are back, otherwise mark it unknown. 14:00 to 14:45 is your stakeholder update, unchanged. 14:45 to 16:00 holds the second vendor question. 16:00 to 16:30 is the one-to-one. Shutdown after that: save the draft and file notes. Friday review to paste: What moved on the three outcomes? What did I override in the plan, and why? Which outcome is still open? What fact was missing? What one line should change in next week's prompt? I do not know whether the proposal was sent. Leave that answer for you.
05
Prompt breakdown
The prompt
Weekly productivity system. Dump follows. Mark energy high, medium, or low. Propose only three outcomes that are finished results, park the rest, and draft Monday as suggested blocks. Here are meetings I already have, with times. Do not add meetings. Flag conflicts with this list. End with a Friday review: moved, slipped, overridden, still open.
- The dump comes before ranking so a loud task does not hide a real outcome.
- Three outcomes force a choice. A parking list keeps the rest visible without pretending they fit.
- Meetings are supplied by you, and the conflict check may only use that list.
- The Friday lines make the next paste better instead of starting from zero.
06
Common mistakes
Usually
Plan my perfect week and fill every hour.
Better
Here is the task dump and the meetings I already have. Propose three outcomes and suggested blocks only in the gaps. Leave buffers.
Usually
You know my calendar. Schedule deep work wherever I am free.
Better
You do not know my calendar unless I paste it and confirm it. Use only the times below, and label the plan as a suggestion.
Usually
My Friday review: tell me the week was a success.
Better
Ask what moved, what slipped, what I overrode, and which outcome is still open. Do not invent the result.
07
Practice exercise
Build your weekly productivity system
Done when: You can rerun the weekly productivity system from saved prompts, and the plan contains no meeting you did not supply.
08
Challenge
One real Monday, then a Friday edit
Run the weekly productivity system on your next real Monday, not on a fictional team. Paste your context note, dump your actual tasks with private names removed, and mark energy. Ask for three outcomes, a parking list, and a Monday plan whose blocks are suggestions. Compare every block with your real day before you accept it. Cross out anything that double-books a commitment you already have. On Friday, paste a short note of what you overrode and ask for one prompt change. Save both prompts. The point is a rerun you trust, not a perfect week.
Hint: Compare each block with a commitment you already have before you praise the wording.
09
Key takeaways
- Outcomes are finished results. Tasks such as check email do not count as the week's point.
- Time blocks are suggestions until you compare them with the day you actually have.
- Gemini does not know your calendar unless a connected feature is on and you confirm the screen.
- A Friday review of what you overrode is how the prompt improves.
10