How to Use AI at Work
AI is rapidly becoming a core productivity tool in the workplace, but most professionals barely scratch the surface of what it can do. The highest-impact use cases are not the flashy ones — they are the repetitive daily tasks that eat up hours: drafting emails, summarizing meeting notes, preparing reports, and writing first drafts of documents. A well-crafted prompt can turn a 30-minute email chain into a 2-minute task. For example, "draft a follow-up email to a client who missed their deliverable deadline. Tone: firm but professional. Include a proposed new timeline and mention the impact on downstream milestones" produces a polished email you can send with minimal editing.
Meeting prep and follow-up is another area where AI saves significant time. Before a meeting, feed AI the agenda, relevant documents, and your goals, and ask it to prepare talking points, potential questions, and a one-page brief. After the meeting, paste your notes and ask it to generate action items with owners and deadlines, a summary for stakeholders who were not present, and follow-up email drafts. For report generation, provide raw data or bullet points and let AI structure them into a formatted report with an executive summary, key findings, and recommendations.
The professionals who get the most out of AI at work are those who build systems, not one-off prompts. Create prompt templates for your recurring tasks — weekly status updates, performance reviews, project proposals, client communications — and refine them over time. Store these in a shared prompt library so your entire team benefits. The goal is not to replace your judgment but to eliminate the blank-page problem and handle the mechanical parts of knowledge work so you can focus on strategy and decisions.
Work Prompts You Can Copy
Ready-to-use prompts for the most common workplace tasks. Copy, fill in the variables, and send.
Professional Email Drafting
Draft a professional email for the following situation: To: {{recipient_role}} at {{company_or_context}} Purpose: {{email_purpose}} Tone: {{tone}} Key points to include: {{key_points}} Constraints: - Keep it under 200 words - Lead with the most important point - Include a clear call to action in the last paragraph - Use bullet points if there are more than 2 action items - Do not use filler phrases like "I hope this email finds you well" Provide the subject line and email body.
Why it works: The word limit and no-filler constraint produce concise, professional emails. Leading with the key point respects the recipient's time and increases response rates.
Meeting Prep Brief
Prepare a one-page meeting brief. Meeting: {{meeting_topic}} Attendees: {{attendees}} My role: {{my_role}} Agenda: {{agenda}} Background context: {{context}} Generate: 1. **Key talking points** (3-5 bullets I should raise) 2. **Potential questions** others may ask me, with suggested responses 3. **Decision points** — what needs to be decided in this meeting 4. **Risks to flag** — anything that could derail the meeting or the project 5. **Desired outcome** — what success looks like when this meeting ends Keep the entire brief scannable in under 2 minutes.
Why it works: Anticipating questions with suggested responses eliminates being caught off guard. The 'desired outcome' section keeps the meeting focused and productive.
Weekly Status Report
Generate a weekly status report from my notes. Project: {{project_name}} Reporting period: {{date_range}} My notes: {{raw_notes}} Format the report as: ## Status: {{status_color}} (Green / Yellow / Red) ### Completed This Week - (bullet list of completed items, written as accomplishments) ### In Progress - (bullet list with % completion estimates) ### Blocked / Needs Attention - (bullet list with what is blocking and what is needed to unblock) ### Next Week - (bullet list of planned priorities) ### Key Metrics | Metric | This Week | Last Week | Trend | Transform my rough notes into polished, manager-ready language. Be specific and quantify results where possible.
Why it works: The fixed format ensures consistency week over week. Transforming rough notes into 'manager-ready language' bridges the gap between what you tracked and what leadership needs to see.
Decision Framework
I need to make a decision at work. Help me think through it systematically. Decision: {{decision}} Stakeholders: {{stakeholders}} Timeline: {{deadline}} Constraints: {{constraints}} Analyze using this framework: 1. **Options**: List all viable options (including "do nothing") 2. **Criteria**: What factors matter most? (cost, speed, risk, team impact, reversibility) 3. **Scorecard**: Rate each option against each criterion (1-5) in a markdown table 4. **Second-order effects**: For the top 2 options, what happens 3 months and 12 months after this decision? 5. **Reversibility**: How easy is each option to undo if it turns out to be wrong? 6. **Recommendation**: Based on the analysis, which option do you recommend and why? Be honest about trade-offs. Do not present any option as perfect.
Why it works: Including 'do nothing' as an option prevents action bias. The reversibility analysis reduces decision anxiety by showing which choices are low-risk experiments.
Task Prioritization
I have the following tasks on my plate this week. Help me prioritize them. Tasks: {{task_list}} My available hours this week: {{available_hours}} Key deadline: {{key_deadline}} For each task, assess: - **Impact**: How much does completing this move the needle? (High / Medium / Low) - **Urgency**: When does this actually need to be done? (Today / This week / Can wait) - **Effort**: How long will this realistically take? (hours) - **Dependencies**: Does anything else depend on this being done? Then provide: 1. A prioritized daily plan for the week (Mon-Fri) 2. Tasks to delegate or defer with reasoning 3. Tasks to say no to or push back on, with a suggested response to the requester Be ruthless — if the hours do not add up, something has to go.
Why it works: The 'be ruthless' instruction and available-hours constraint force realistic prioritization instead of optimistic planning. Suggested push-back language makes saying no easier.
Knowledge Capture
I just finished {{task_or_project}} and want to capture what I learned before I forget. Here are my raw notes and thoughts: {{raw_notes}} Transform these into a structured knowledge document: ## Summary (What was done and what was the outcome in 2-3 sentences) ## What Worked (Bullet list of approaches, tools, or decisions that went well) ## What Did Not Work (Bullet list of things that failed or were harder than expected, and why) ## Key Learnings (3-5 transferable insights that would help someone doing this task in the future) ## Reusable Assets (Any templates, scripts, checklists, or prompts created during this work that should be saved) ## If I Did This Again (What would I do differently from the start, knowing what I know now?) Write it so a teammate who was not involved could benefit from this in 6 months.
Why it works: Capturing knowledge immediately after a task prevents the forgetting curve from erasing valuable insights. The 'teammate in 6 months' framing ensures sufficient context for future use.
Recommended tools & resources
Professional prompts for reports, strategy, and operations.
Prompt BuilderGenerate structured work prompts for any professional task.
Email Writing PromptsAI prompts for drafting professional emails and responses.
Prompt TipsBest practices for getting reliable output in work contexts.
AI Workflow ToolsTools for building multi-step AI workflows at work.
RolesPre-built role prompts for marketing, sales, HR, and more.