13 min · Intermediate
Your Personal Productivity Workflow
Assemble one page of prompts and run it on Monday and Friday, checking for outcomes and a human decision.
Learning objectives
- Assemble a context note plus weekly, daily, email, and decision prompts on one page.
- Run that page on Monday and review it on Friday.
- Check that the plan names outcomes and leaves a decision for you.
01
Why this matters
Separate prompts help once. A single page you rerun on Monday and Friday helps every week. The quality checks stop the page from filling your day with tasks and fake decisions.
02
Concept
Keep one page you can open on Monday. Give it five pieces: a context note, a weekly prompt, a daily prompt, an email prompt, and a decision prompt. The note sets boundaries. The weekly prompt picks three outcomes and parks the rest. The daily prompt proposes a top three, suggested blocks, and a shutdown list. The email prompt asks for three tones and bans invented promises. The decision prompt drafts a memo and stops before you commit.
Run the page on Monday and again on Friday. On Monday, paste the note and the weekly prompt, then lock three outcomes before the daily plan. Then run the daily prompt for that day only. On Friday, review what moved, what slipped, what you overrode, and one line to change. Rejecting a suggestion still counts. Keep the page stable while you learn it. A rerun teaches more than a brand-new prompt every morning.
Use two checks. Did the plan name outcomes, meaning finished results, rather than tasks like check email? Did it leave a human decision, with a blank where a fact was missing? If every hour is filled and every mail sounds sent, the draft is overconfident. Ask for each line to be marked proposed or decided by you. You want more proposed than decided. A flow that never lets you choose is a script for accidents.
Keep the promise modest. The page can shorten blank-page time on plans, replies, and memos. It does not know your calendar unless a connected feature is on and you confirm the screen. Check the current screen, since layouts change. As of late 2026, Gmail, Docs, and Meet notes help only on eligible Workspace plans. You can still paste allowed text into the plain Gemini app. You are the person who commits and sends.
03
Real-world example
A page that survived a school pickup
Hassan keeps the one-page workflow in a note titled Monday page. On Monday he pastes the context note and the weekly prompt, dumps twelve tasks, and changes the model's first outcome from clear inbox to send the supplier draft, because clear inbox is a task. He runs the daily prompt and rejects a block that overlaps school pickup, a fact the model could not know. On Wednesday an email prompt gives him three replies. He sends the short one after deleting a date the model invented. On Friday he reviews overrides: the pickup block, the inbox outcome, and the invented date. He changes one line of the weekly prompt so outcomes must be sendable or finishable. The page is not impressive. It is reusable, and it still leaves the supplier decision to him.
04
Gemini demonstration
A realistic exchange. Open Gemini beside this page and try a version with your own facts.
You
Build my one-page productivity workflow. Include five labeled pieces: context note, weekly prompt, daily prompt, email prompt, and decision prompt. Use blanks where you do not know my job, hours, or meetings. Do not invent my calendar. Tell me how to run it on Monday and Friday. Mark every line as a template I must edit.
Gemini
One page, ready to paste again. Context note: role, hours, urgent rule, tools, and a ban on invented meetings or promises. Weekly prompt: dump tasks, mark energy, propose three outcomes that are finished results, park the rest, draft Monday, and hold a Friday review of what moved, slipped, and was overridden. Daily prompt: top three linked to those outcomes, suggested blocks only, shutdown list, and a line that says suggestion not calendar. Email prompt: three replies, direct, diplomatic, and short, with no new dates, money, or blame. Decision prompt: options, criteria, recommendation, risks, review date, and a stop before commitment. I did not invent your job, your hours, or your meetings. Replace the blanks. Check the current screen before trusting any connected calendar. You still commit, send, and sign.
You
Quality-check this plan I might use. Monday items: check email, attend meetings, work on the proposal. It also says I will email the client that the proposal is approved. I have not approved anything. Mark outcomes versus tasks, and proposed versus decided.
Gemini
Quality check, and I am not approving anything. Check email and attend meetings are tasks, not outcomes, because they do not name a finished result. Work on the proposal is also a task unless you name the result, such as send a first draft to yourself by Thursday. The line that emails the client saying the proposal is approved is a decision you have not made in this chat. Mark it proposed, not decided, and delete the approval until you choose it. A safer outcome is: draft ready for your review. Human decisions left open: whether the draft is good enough to share. I do not know your client, your deadline, or your authority to approve. You override any line that pretends you already said yes.
05
Prompt breakdown
The prompt
One-page workflow. Pieces: context note, weekly prompt, daily prompt, email prompt, decision prompt. Weekly prompt must name three finished outcomes and park the rest. Daily blocks are suggestions. Email bans invented promises. Decision memo stops before I commit. Mark each line proposed or decided by me.
- Naming the five pieces stops the page from collapsing into one vague ask for productivity.
- Finished outcomes are required so a task list cannot masquerade as a plan.
- Suggested blocks and a ban on invented promises repeat the boundaries from earlier lessons.
- The proposed-or-decided mark makes the human decision visible on the page.
06
Common mistakes
Usually
Build me an automated life and run it without me.
Better
Build one page I paste on Monday and Friday. Leave blanks where a human decision belongs.
Usually
My outcomes are: email, meetings, and be productive.
Better
Rewrite those as finished results, or park them as tasks. An outcome must be sendable or finishable.
Usually
If I overrode the plan, hide that so the system looks perfect.
Better
On Friday, list what I overrode and change one line of the prompt because of it.
07
Practice exercise
Assemble the one-page workflow
Done when: A stranger could tell which lines are templates, which are outcomes, and which decisions are still yours.
08
Challenge
Mark what you overrode in a messy week
Use a real week, not a demo. Paste your context note and your weekly prompt into a fresh chat. Dump the tasks that are actually on your plate, with sensitive names removed. Let the model propose three outcomes, a Monday sketch, and a parking list. Then do the week as yourself. Each time you ignore a block, change a reply, or refuse a recommendation, write one line: what it said, what you did, and why. On Friday, paste those lines back and ask what to change in the page. Aim for a page that survives contact with your calendar and your judgment.
Hint: An override is useful data. Do not hide it to make the model look right.
09
Key takeaways
- The workflow is one page: context, weekly, daily, email, and decision prompts.
- Monday locks three outcomes before the daily plan. Friday records what you overrode.
- A plan of tasks with no outcome, or a draft with no human decision, fails the quality check.
- The page saves drafting time. It does not know your calendar, and it does not commit for you.
10