Department Use Cases
How different teams can apply AI more effectively
This document provides practical use case ideas organized by department or role type. For each use case, the focus is on what the prompt should include and what common mistakes to avoid.
Product Management
Use cases
Feature briefs and specs
AI is useful for drafting the structure of a feature brief, but only when you provide the problem, the user, the constraints, and the decision context. Without those, you will get a generic template that could apply to any feature.
Key inclusions: who the user is, what problem they have, what the acceptance criteria are, what is out of scope, and who the audience for the brief is.
Prioritization framing
AI can help frame a decision between two options — presenting tradeoffs, criteria, and questions to resolve. Give it the two options, the relevant criteria the team cares about, and the decision-maker's known priorities.
Sprint planning summaries
Give AI a raw list of issues, context about the sprint goal, and instructions to group by theme, flag dependencies, and highlight carry-overs. Specify the audience (engineering team) and format.
Stakeholder update emails
Useful for communicating status, delays, or decisions. Provide: what happened, what the impact is, what the plan is, who the recipient is, and what tone is appropriate for the relationship.
Marketing
Use cases
Campaign and email copy
AI produces workable copy quickly when you give it: the audience segment, the offer or message, the channel (email, social, landing page), the tone, and explicit exclusions for language to avoid.
Avoid: vague audience definitions ("our customers"), missing exclusions (AI defaults to promotional language), and no length guidance.
Messaging frameworks
AI can help structure a messaging hierarchy — headline, subheads, supporting points — when you give it the product's differentiation, target persona, and the key emotional and functional needs to address.
Blog outlines and first drafts
Useful for generating structure and starting points. Provide audience, goal, angle, and tone. Always treat the first draft as a starting point — especially for blog posts, where the voice needs to be human.
Ad copy variations
Ask for multiple variations (e.g., five subject lines, three headline options) so you can test. Include the target audience, the core message, the desired action, and the channel.
Support and Documentation
Use cases
Help articles
AI is well-suited for step-by-step documentation. Provide: the task the user is trying to complete, the user's likely expertise level, the tone (calm and reassuring for frustrated users, efficient for power users), and the format (numbered steps, no jargon).
FAQ drafts
Give AI a list of common customer questions and ask it to draft answers. Specify the tone, the assumed knowledge level, and the length per answer. Then refine for accuracy.
Escalation email templates
For support leads who need a template for handling difficult customer situations. Provide: the situation type (complaint, bug, delay, billing issue), the tone (empathetic but professional), and the outcome to work toward (resolution, retention, clarification).
Knowledge base cleanup
AI can help rewrite outdated or unclear documentation. Provide the original article, the problem with it (too technical, outdated process, wrong tone), and instructions for the rewrite.
Operations and Project Coordination
Use cases
Process documentation
AI can draft SOPs when you provide: the steps in rough form, who performs each step, what tools or systems are involved, and who the reader is. For non-technical readers, add explicit plain-language instructions.
Post-mortem summaries
Give AI the facts of what happened, why it matters, and what changed. Request a structured format: timeline, root cause, impact, corrective actions. Specify the audience (leadership vs. team vs. external).
Status reports and weekly updates
Useful when you have a list of items to communicate and want them organized into a readable format. Specify what to prioritize, what the audience already knows, and what action each item requires from the reader.
Vendor or partner communications
When communication needs to be professional and clear but not drafted from scratch. Give AI the situation, the key message, the tone (firm vs. diplomatic vs. collaborative), and any specific information to include.
Developers
Use cases
Technical explainers for non-technical audiences
Give AI a technical concept and ask it to explain it to a specific non-technical audience (project manager, executive, customer). Explicitly instruct it to avoid technical jargon and focus on practical impact.
Documentation for implementation decisions
Give AI the decision you made (e.g., chose PostgreSQL over MongoDB), the reasons, and the audience (non-technical stakeholders or new team members). Ask for a brief explainer that serves as a record.
Sprint planning support
See product management section. Developers can use the same approach for technical planning documents.
Code explanation for cross-functional review
When you need to explain what a piece of code does to a non-technical reviewer. Give AI the code, the audience, and the goal of the explanation (general understanding vs. approval for deployment vs. security review).
Architecture decision records (ADRs)
AI can draft an ADR structure when you provide the decision, the options considered, the reasons for the choice, and the known tradeoffs. Specify audience and completeness level.
Leadership and Internal Communication
Use cases
Decision memos
One of the highest-value use cases. Provide: the decision, the recommendation, the supporting reasons, the known objections, and the specific approval or action needed. AI produces strong memos when the decision context is complete.
Board or executive summaries
Give AI the full content and ask it to compress it to the audience's level of detail. Specify: outcome-first structure, no jargon, no background they already know. Length matters especially here.
All-hands or team communications
Tone is critical for this use case. Describe the audience relationship (direct reports vs. whole company), the message, the emotional register (celebratory, serious, transitional), and what you want people to feel or do after reading.
Difficult communications (delays, layoffs, changes)
AI can help with structure and language when the content is difficult. Give it the facts, the framing you want, and the tone (honest, direct, not evasive). Review carefully — this is content that matters too much to accept at first draft.
Hardware and Systems-Adjacent Roles
Use cases
Technical summary for procurement
When explaining a systems decision to procurement or finance. Give AI technical context, translate it to business impact, and ask it to write for a non-technical buyer.
Cross-functional requirements documentation
AI can help structure requirements that cross between hardware and software teams. Give it the need, the constraints, and the two audiences it needs to serve (engineering and operations, for example).
Vendor evaluation summaries
Provide AI with evaluation criteria and raw notes about each vendor. Ask it to produce a structured comparison. Specify whether the output is for internal use or stakeholder review.