AI prompts by IT role:
the copy-paste library
The same AI tool delivers very different value depending on how you brief it. Here are ready-to-use prompts, organized by IT role — filter yours, copy, replace the [brackets]. They work with ChatGPT, Copilot, Claude or Gemini: it's the structure that counts, not the tool.
CIO & IT leadership
You are an experienced CIO. Context: [stake, sector, constraint]. Write a one-page framing note to launch an AI initiative: problem, measurable objectives, scope, risks (data, compliance, adoption), and 3 milestones. Board tone, factual.
Compare build, buy and adapt for this need: [need]. Three-column table: total cost (incl. run), lead time, vendor dependency, compliance/sovereignty, internal effort. End with your reasoned recommendation.
Project manager
You are an IT project manager. From this project context: [context], write a communication plan: stakeholders, key message per audience, channel, frequency. Table format. Flag adoption risks.
From this project description: [description], generate a risk register: risk, probability, impact, criticality, mitigation action, owner. Prioritize by criticality.
Product Owner
You are a senior PO. Business need: [need]. Write 3 INVEST user stories with acceptance criteria in Gherkin (Given / When / Then) and list the assumptions to validate.
Business Analyst
You are a Business Analyst. From this need expressed by the business: [need], extract the numbered business rules, the edge cases, and the questions to clarify. Mark ambiguous areas "⚠ to validate".
Describe the current process (AS-IS) and the target process (TO-BE) for: [process]. List steps, actors, removed friction points and expected gains. Comparative format.
Data
You are a data analyst. For this business question: [question], propose the analysis: required data, indicators, method, possible biases, and the most readable visualization for a non-technical decision-maker.
IT architect
Write an Architecture Decision Record for this choice: [decision]. Sections: context, options considered, decision, consequences (positive and negative), and security/cost impacts.
Dev & DevOps
Review this code and flag: potential bugs, security issues, readability, and missing tests. For each point: severity, the snippet involved, proposed fix. Code: [paste].
From these logs and this timeline: [inputs], write a blameless post-mortem: summary, impact, root cause, what went well/badly, and 3 corrective actions with owners.
The full prompt kit by role as a PDF
Every prompt from this article, one role per page, with the reminder of the "role · context · task · format" structure. Ready to share with your team. Leave your email to receive it, or download directly.
or download directly, no email →The structure that makes any prompt work
- Role — "You are a CIO / PO / architect…": sets the tone and the bar.
- Context — your situation, constraints, audience. The brick 90% forget.
- Task — a precise verb, a bounded scope.
- Format — table, word count, tone. Otherwise you'll get a wall of text.
Frequently asked questions
How do you write a good AI prompt?
Do these prompts work with ChatGPT and Copilot?
Can you use these prompts with company data?
In IAPLC, you no longer copy prompts: you learn to build them on YOUR cases, role by role, through 30 levels generated for your job.
Explore the course →