Productivity Prompts

Prompts for planning your week, running meetings, writing SOPs and clearing decisions. Each one turns a vague task into a concrete plan with owners and next steps.

• Personal Productivity System: Design a custom productivity system for any role.
• Weekly Planning Ritual: Plan a week around a small number of outcomes that matter.
• Inbox Management System: Process email in batches with clear rules for each message.
• Deep Work Schedule: Protect uninterrupted time in a calendar that resists it.
• Decision Making Framework: Make a difficult decision without endless deliberation.
• Delegation Plan: Hand over work so it is done well without being redone.
• Meeting Reduction Audit: Cut the meeting load without losing the coordination it provides.
• Personal Knowledge System: Capture and retrieve notes without building a second job.
• Habit Design Plan: Build a habit around a trigger rather than around motivation.
• Project Kickoff Plan: Start a project with alignment on scope and definition of done.
• Time Audit Analysis: Find where time actually goes before trying to optimise it.
• Saying No Scripts: Decline requests clearly without damaging the relationship.
• Automation Opportunity Audit: Find the repetitive work worth automating and the work that is not.

Best productivity prompts, in full

The top 3 by score on the free Verbito Prompt Scorer.

Inbox Management System (score 97/100)

You are an executive coach who fixes email overload. Design a system for [INSERT ROLE] receiving roughly [INSERT VOLUME] emails daily.

Produce:

1. Processing schedule: how many sessions per day and when, not continuous monitoring
2. The decision rule for each message: delete, delegate, respond now, defer, or file
3. The two-minute rule and where it stops applying
4. Folder or label structure, kept deliberately shallow
5. Filters and rules to apply before a human sees the message
6. Templates for the five most repeated replies
7. Handling the message that needs thought: where it goes so it is not lost
8. Notification settings, with a justification for switching most off
9. A weekly review to catch what slipped
10. How to recover from a backlog of thousands without reading each one

Inbox zero is not the goal; a trustworthy system is. If achieving zero requires two hours daily, the system has replaced the work rather than supporting it.

Tone: practical and forgiving. Systems must survive a bad week.

Audience: the person whose inbox it is. Context: the goal is under 30 minutes a day on email without missing anything urgent.
Keep the system to one page. Example rule: "From the CEO or a client: star and answer the same day; newsletters: auto-file to Read Later."

Habit Design Plan (score 96/100)

You are a behavioural design practitioner. Build a plan to establish [INSERT HABIT] for someone whose context is [INSERT SITUATION].

Produce:

1. The behaviour defined so small it is hard to skip on a bad day
2. The trigger: an existing reliable moment it attaches to
3. The environment change that makes it easier to do than not do
4. Friction removed for the desired behaviour, added for the competing one
5. The immediate reward, since delayed benefits do not reinforce behaviour
6. Tracking that takes under ten seconds
7. The plan for missed days, with a rule against missing twice
8. Scaling up only after consistency is established, with the criterion for scaling
9. The three situations most likely to break it, each with a prepared response
10. What success looks like at two weeks, six weeks and six months

Design for the worst day, not the best. A habit requiring 40 minutes and good mood will not survive a difficult week, and breaking the streak is what ends most attempts.

Tone: practical and non-moralising.

Audience: the person building the habit, not a coach.
Output format: a one-page plan with the cue, the routine, the reward and a 4-week ramp in a table.
Example ramp row: "Week 1 | 2 minutes after morning coffee | tick the calendar".

Personal Knowledge System (score 84/100)

You are a knowledge management practitioner who distrusts elaborate systems. Design one for [INSERT PERSON] who needs to [INSERT USE CASE].

Produce:

1. What is actually being solved: retrieval, thinking, or reference
2. Capture: where things go in the moment, with one inbox rather than several
3. Processing cadence and the decision rule for each captured item
4. Organisation, by usage rather than by taxonomy, since folders built by subject are rarely how things are later sought
5. Note format: what a useful note contains, and the minimum viable version
6. Linking, if it genuinely earns its overhead for this use case
7. Retrieval: how something is found in three months, which is the only test that matters
8. Regular review, kept short
9. What to deliberately not capture
10. Signs the system has become the work, and how to simplify when that happens

Most systems fail because capture is easy and processing is not. Weight the design toward making processing quick.

Tone: pragmatic and anti-fussy.

How to use these prompts

1. Copy the prompt that matches your task.
2. Replace every [INSERT ...] part with your own details: the more specific, the better the answer.
3. Paste it into ChatGPT, Claude or Gemini. To tailor it to your exact situation, describe your goal in the Verbito prompt generator instead.

Build a productivity prompt for your task · The 100 best prompts in one kit

Create a prompt or contact Verbito.