18 Useful ChatGPT Prompts for Everyday Work

These prompts are frameworks, not magic commands. Replace the bracketed details, provide relevant non-sensitive context, and review the response before using it. ChatGPT features can vary by plan and change over time.

1. Turn a Vague Goal Into an Action Plan

Act as a practical project planner. My goal is [goal]. My deadline is [date], available time is [hours per week], and constraints are [constraints]. Ask up to five essential questions first. Then create a prioritized plan with milestones, first actions, likely obstacles, and a weekly review checklist. Clearly label assumptions.

Best for: business owners, students, creators, and personal projects.

2. Prepare a Decision Brief

Help me compare [option A] and [option B] for [decision]. Use these criteria: [criteria]. Create a table showing benefits, risks, costs, reversibility, and missing information. Do not choose for me. End with five questions I should answer before deciding.

Quality check: Add your own criteria and verify any factual comparison.

3. Improve a Professional Email

Edit the email below for clarity, respect, and brevity while preserving my meaning and voice. Audience: [recipient]. Desired outcome: [outcome]. Tone: [tone]. Flag any sentence that could be misunderstood, then provide a revised version under [word limit] words. Email: [paste email]

4. Build a Content Brief

Create a people-first content brief about [topic] for [audience]. Their main problem is [problem]. Include search intent, a distinct angle, questions to answer, evidence needed, examples to gather, a logical outline, and a checklist that prevents generic or unsupported claims. Do not write the article yet.

5. Learn Through Questions

Teach me [topic] at a [beginner/intermediate/advanced] level using questions. Start with a short diagnostic quiz. Ask one question at a time, respond to my answer with targeted feedback, and adapt the next question. Do not reveal the complete answer until I attempt it.

6. Review Code Without Rewriting Everything

Review this [language] code for correctness, security, readability, and edge cases. Explain the three highest-risk issues first with specific references. Suggest the smallest safe fixes and focused tests. Do not rewrite unrelated code. Context: [context]. Code: [paste code with secrets removed]

7. Create a Customer Interview Guide

Create a 30-minute interview guide for people who [audience description]. We want to learn about [problem], not sell a solution. Write neutral questions about current behavior, pain points, workarounds, costs, and decision factors. Identify leading questions to avoid and suggest follow-ups.

8. Analyze Feedback Themes

Analyze the anonymized feedback below. Group it into recurring themes, needs, positive signals, frustrations, and contradictory views. For every theme, cite supporting excerpts and note how confident you are. Do not invent percentages. Feedback: [paste anonymized feedback]

9. Run a Pre-Mortem

Imagine that [project] failed six months from now. Generate realistic reasons across strategy, execution, customers, technology, people, budget, and external factors. Rank them by likelihood and impact, then suggest one early warning sign and one prevention action for each.

10. Design a Weekly Review

Create a 20-minute weekly review for my role as [role]. My priorities are [priorities]. Include questions for progress, unfinished work, decisions, energy, learning, risks, and next-week commitments. Keep it practical and format it as a reusable checklist.

11. Convert a Process Into a Standard Operating Procedure

Turn the process below into a practical standard operating procedure for [team/role]. Separate purpose, prerequisites, numbered steps, decision points, quality checks, escalation conditions, and evidence of completion. Identify missing details instead of inventing them. Process notes: [notes]

Best for: documenting repeatable work without hiding unclear ownership.

12. Create Test Cases From Requirements

Review these requirements for [feature/process]. Create test cases covering normal use, boundaries, invalid inputs, permissions, failure recovery, accessibility, and security-sensitive behavior. For each test, state setup, action, expected result, and the requirement it verifies. Flag ambiguous or untestable requirements. Requirements: [text]

13. Prepare a Difficult Conversation

Help me prepare for a respectful conversation with [person/role] about [issue]. My goal is [outcome], and the facts I can verify are [facts]. Separate observations from assumptions, suggest neutral opening language, likely responses, useful questions, boundaries, and a follow-up plan. Do not diagnose motives.

14. Audit a Proposal for Hidden Assumptions

Audit this proposal before approval. List its explicit claims, hidden assumptions, dependencies, missing evidence, affected groups, failure modes, and decisions that would be difficult to reverse. Then create a short validation plan for the three riskiest assumptions. Proposal: [text]

15. Design an Accessible Content Checklist

Create an accessibility review checklist for [content/page/document] intended for [audience]. Cover structure, headings, link text, image alternatives, color dependence, reading clarity, keyboard use, captions, and error messages. Explain how each check helps users and identify items requiring human testing.

16. Diagnose a Recurring Operational Problem

Help me investigate this recurring operational problem without jumping to a solution: [problem]. Known examples: [examples]. First separate symptoms, possible causes, and missing evidence. Then create a cause-and-effect map, questions for the people doing the work, data to collect, and a small test that could disprove the leading explanation. Do not treat correlation as causation.

Quality check: Confirm the diagnosis with observations from the real workflow before changing it.

17. Create a Handover Plan for Important Work

Create a handover plan for [responsibility/project] moving from [current owner] to [new owner]. Include purpose, current status, recurring tasks, deadlines, access requirements, key contacts, decision history, known risks, unresolved questions, first-week priorities, and a checklist for confirming the new owner can operate independently. Flag any secrets or personal data that should be transferred through an approved secure channel instead of pasted here.

18. Review a Form for Completion and Error Risk

Review this form or intake questionnaire for [purpose] and [audience]. Identify unclear questions, unnecessary data collection, duplicate fields, missing instructions, likely user errors, accessibility concerns, and sensitive information that needs justification. Propose clearer wording and a short validation plan. Do not assume collecting more data is better. Form fields: [paste fields without real personal data]

How to Get Better Results

  • Provide a real audience, goal, and constraint.
  • Ask ChatGPT to label assumptions and uncertainties.
  • Request a critique or verification checklist after the first response.
  • Do not paste confidential information, passwords, or private customer data.

Advertisement