Module 3.3: GenAI for Managers — Emails, Meeting Summaries, and Presentations

YOUR PROGRESS — GENERATIVE AI: ZERO TO JOB-READY ← Course home

10 of 20 modules complete

Understanding GenAI ✓ Prompt Engineering ✓ GenAI for Your Job Advanced Techniques Career & India

GenAI for Managers — Emails, Meeting Summaries, and Presentations

⏱ 13 min read 📝 Assignment inside Hands-on examples

Module 3.1 covered developers. Module 3.2 covered analysts. This module is for the third role in every Indian IT team — the project manager, team lead, account manager, or delivery manager whose work is overwhelmingly communication: emails, meeting notes, status reports, client presentations, and stakeholder updates.

If your job involves more writing and communication than coding or data, this module is your highest-value module in the entire course.

The manager’s communication burden

28%

of the workweek spent managing email — approximately 11.2 hours — McKinsey Global Institute

93%

of project managers using GenAI for more than half their tasks report increased productivity — PMI

2.2 hrs

saved per week on average by GenAI users — equivalent to one full workday reclaimed per month (Federal Reserve research)

Knowledge workers spend approximately 28% of the workweek — about 11.2 hours — managing email. Add meeting time, status reporting, and stakeholder updates, and most managers in Indian IT spend over 60% of their time on communication rather than execution. GenAI directly addresses this — not by replacing the judgement in those communications, but by eliminating the time spent drafting and formatting them.

The manager's edge with GenAI: Every prompt in this module produces output you send to someone — a client, your manager, your team, a vendor. The quality standard is therefore higher than in Modules 3.1 and 3.2. The goal is not just faster output but output that reflects your professional voice, your organisation's standards, and your relationship with the recipient. Context and role prompting matter more here than in any other module.

Use case 1 — Professional email writing

✉

Writing professional emails for every situation

Email is where most managers waste the most time — not reading it, but writing it. Drafting a difficult escalation email, a client status update, or a vendor follow-up from scratch takes 15–30 minutes. With AI, the same email takes 2 minutes to prompt and 5 minutes to review and personalise.

EXAMPLE — Project delay escalation to client

You are a professional delivery manager writing on behalf of an Indian IT services team.

Draft an email to my client contact (Sarah Chen, Programme Director at a UK insurance company) about a 5-day delay in the API integration milestone.

Context:

Original deadline: 20 June 2026
New expected date: 25 June 2026
Root cause: Third-party vendor (payment gateway provider) delivered API documentation 8 days late
Impact: Only the payment module is delayed — the rest of the release is on track
What we are doing: Daily standups with the vendor, parallel testing started on mock data

Tone: Professional, factual, accountable without being overly apologetic. Length: Under 150 words. Do not use: “We sincerely apologise”, “please be advised”, “as per our discussion” Subject line: Include one.

The "do not use" constraint is critical for Indian IT emails. Overuse of "we sincerely apologise" and "as per our discussion" are widely recognised patterns in Indian IT client communication that can undermine credibility with international clients. Explicitly excluding them produces a more direct, confident email. The root cause attribution to the vendor (not the team) is factually important and should be stated clearly — the prompt ensures the model includes it.

EXAMPLE — Internal escalation to senior management

You are a project manager at TCS writing to your delivery head.

Write an escalation email about a resourcing issue affecting project delivery.

Situation:

Project: Core banking modernisation for a PSU bank client
Problem: Two senior Java developers were moved to another project 3 weeks ago without replacement
Current impact: Sprint velocity dropped from 42 to 24 story points; 2 features at risk for the August release
What I need: Either return the developers by 15 July or approve hiring 2 contractors
What happens if nothing is done: August release date will slip by 3–4 weeks, risking the ₹2.4 Cr penalty clause

Format: Short paragraphs, not bullet points. Tone: Urgent but professional — not emotional. Include: A clear ask in the last paragraph.

The "clear ask in the last paragraph" instruction is the most important element in any escalation email. Without it, AI produces a narrative without a decision point — and management escalations without a clear ask get filed, not acted on. The ₹ penalty clause context signals commercial urgency without requiring the manager to write that section from scratch.

SCENARIO TEMPLATE

Vendor follow-up (no response)

Role: Procurement manager following up with vendor. Situation: 3rd follow-up, no response in 10 days, blocking our go-live. Tone: Firm but not hostile. Ask: Response by EOD Friday or escalate to their account manager. Length: Under 100 words.

SCENARIO TEMPLATE

Positive client update

Role: Delivery manager at Infosys. Situation: Sprint completed ahead of schedule, 2 bonus features delivered. Tone: Confident, brief, client-facing. Include: Next sprint preview, one question for client. Length: Under 120 words.

SCENARIO TEMPLATE

Team appreciation email

Role: Team lead at Wipro. Situation: Team delivered a critical hotfix at 2am on a Sunday, preventing a client outage. Tone: Warm, genuine, specific — not corporate. CC: Senior manager. Length: Under 80 words.

SCENARIO TEMPLATE

Onboarding welcome email

Role: Team lead welcoming a new joinee. Situation: Fresh graduate joining a 12-person scrum team at HCL. Include: First week plan, key contacts, one piece of genuine advice. Tone: Welcoming but professional. Length: Under 150 words.

Claude — most natural email writing, least AI-sounding ChatGPT — strong for structured professional emails Gemini in Gmail — integrated, good for quick drafts

Use case 2 — Meeting summaries and action items

📝

Converting meeting notes into structured summaries

Writing meeting summaries is one of the highest-ROI GenAI tasks for managers. Meeting summarisation, automated task assignment, and querying data from meetings are the top three uses of AI meeting assistants according to Metrigy's research. Even without a dedicated tool, pasting rough notes into a well-structured prompt produces a professional summary in seconds.

EXAMPLE — Sprint review meeting summary

You are a scrum master writing the official meeting summary for a sprint review.

Convert these rough notes into a professional meeting summary:

Sprint 23 Review — 5 June 2026 Attendees: Rajesh (PM), Priya (Tech Lead), Ananya (QA), Vikram (BA), Sarah (Client)

Showed 4 completed features: login with OTP, dashboard redesign, export to PDF, notification preferences
Sarah liked the OTP but said notification preferences UI is confusing — needs redesign
PDF export has a bug with Tamil characters — Priya says will fix in Sprint 24
Velocity this sprint: 38 story points (target was 42)
Sarah asked if we can add WhatsApp notification option — not in scope, Rajesh said will discuss for Sprint 25
Demo of login went well, client very happy
Retrospective separately
Next sprint planning Monday 9am

Format:

Meeting details (date, attendees, purpose)
Completed this sprint (bullet list)
Client feedback (categorised: positive / needs improvement)
Issues and blockers
Decisions made
Action items table: Owner | Action | Due date
Next steps

Keep language concise and professional.

The structured output format is the key. Without it, AI produces a wall of prose. With the numbered sections and action items table, you get a document that is immediately shareable with the client and trackable by the team. The Tamil characters bug detail is an India-specific testing reality — including it in your notes produces a specific, accurate action item, not a generic "fix PDF export" task.

EXAMPLE — Client call follow-up email from notes

Convert these rough call notes into a professional follow-up email to the client.

Call notes (30-min call with Anand Krishnamurthy, VP Technology, Reliance Retail):

Discussed go-live timeline — he wants to pull forward from Aug 15 to Aug 1
We said technically possible if we freeze scope by June 20
He agreed to scope freeze but needs sign-off from his team by June 15
Open issue: data migration strategy not finalised — his team owns the source data extraction
We need their IT team to give us access to the legacy Oracle system by June 10
He wants weekly status calls starting next week — Thursdays 3pm IST
Budget discussion deferred to next call

Write a follow-up email:

Summarise agreements and next steps
Clearly list the 3 items his team needs to deliver and by when
Confirm the weekly call schedule
Professional but warm tone — we have a good relationship
Under 200 words

Relationship context changes the output significantly. "Professional but warm — we have a good relationship" produces a noticeably different email than a standard professional tone. The three deliverable items with dates are explicitly called out — this is the most important part of any follow-up email and the part most likely to be buried or forgotten without this instruction.

Claude — most structured, best at complex meeting notes ChatGPT — fast, strong output for standard meeting formats Otter.ai / Fireflies — dedicated tools if you have recordings

Use case 3 — Status reports and project updates

📋

Weekly status reports and project health updates

Weekly status reports are the most repetitive writing task in Indian IT project management. AI can generate a consistent, professional report from bullet-point inputs in under 2 minutes — with the same structure every week, which clients and management actually prefer over creative prose variation.

EXAMPLE — Weekly project status report for an IT services engagement

You are a project manager at Wipro writing a weekly status report for a client engagement.

Project: Digital transformation for a leading Indian private bank Week ending: 6 June 2026 Report audience: Client steering committee (non-technical)

Input data:

Overall status: Amber (was Green last week)
Milestone 2 (API integration): 80% complete, 3 days behind schedule
Milestone 3 (UAT): On track, starts July 1 as planned
Issues: SSL certificate renewal took 2 extra days — root cause of delay
Risk: Upcoming bank holidays (June 19–20) may affect vendor response times
Team: Full team available, no attrition
Budget: On track, 47% utilised at Week 8 of 18

Generate a status report with these sections:

Executive Summary (3 sentences max — status, main issue, outlook)
Milestone Status table: Milestone | Status | % Complete | Planned Date | Forecast Date
Issues and Risks (RAG status per item — Red/Amber/Green)
Highlights this week
Focus areas next week

Use RAG status colours (Red/Amber/Green) as text labels since this will be pasted into email. Keep total length under 400 words.

"Use RAG as text labels since pasted into email" is a practical India IT context constraint — most Indian IT status reports are sent as email body text, not formatted documents. Specifying this prevents the model from generating HTML colour codes or markdown that will look broken in Outlook. The Amber change from Green is the most important signal — the executive summary prompt forces the model to address it directly.

Claude — best for consistent structured reports ChatGPT — good, especially with a saved system prompt template

Use case 4 — Presentations and slide content

📊

Creating presentation outlines and slide content

AI does not make slides for you — it generates the content that goes into slides. The highest-value use is converting data, meeting notes, or strategic thinking into structured slide outlines that you then build in PowerPoint or Google Slides.

EXAMPLE — Quarterly business review presentation outline

You are a senior delivery manager preparing a Quarterly Business Review presentation for a client.

Audience: C-suite executives at a mid-size Indian manufacturing company Duration: 20 minutes (approximately 15 slides) Quarter: Q4 FY2026 (Jan–Mar 2026)

Key facts to include:

94% on-time delivery (target was 90%)
3 features delivered ahead of schedule
1 critical bug resolved within SLA (4-hour resolution vs 8-hour SLA)
Team expanded from 8 to 12 members — all onboarded within 2 weeks
2 innovation proposals submitted, 1 approved for Q1 FY2027
NPS score: 8.4 (up from 7.9 last quarter)
Budget utilisation: 96% (within 5% variance — compliant)
1 risk open: Legacy database migration complexity — mitigation plan in place

Create a 12-slide presentation outline. For each slide:

Slide number and title (max 7 words)
3 bullet points with the key message
One “so what” statement — the business value for the client

Slides should tell a story arc: Performance → Highlights → Challenges → Value delivered → What’s next

The story arc instruction is what separates a good QBR from a data dump. The model structures the 12 slides into a narrative: opens with performance validation, moves to specific wins, addresses challenges honestly, quantifies value, and closes with forward momentum. Without the arc, AI generates slides in data-delivery order — which is not how executives want to receive information.

EXAMPLE — Internal team retrospective presentation

Create a retrospective presentation outline for a 45-minute team session.

Team: 10-member agile delivery team at HCL, end of a 3-month project phase Facilitation style: Collaborative and honest — psychological safety is important

Retrospective framework: Start / Stop / Continue Key themes I want to address:

Communication gaps between frontend and backend teams
Client scope changes mid-sprint disrupting planning
Strong performance on code quality and test coverage
New CI/CD pipeline working well
Two team members leaving at end of phase

For each slide provide:

Title and activity type (discussion / voting / reflection)
Facilitator instructions (what to say or ask)
Expected time (total must add to 45 minutes)
One “watch out” — something that could go wrong in this part

End with a slide on celebrating wins before the transition.

The "watch out" per slide instruction is a facilitation technique prompt — it prepares the team lead for difficult moments in the session. This is a management use case where AI genuinely adds skill, not just speed: a less experienced facilitator gets guidance on where retrospectives can derail, embedded directly into the presentation structure.

Claude — best narrative structure and business writing ChatGPT — strong for structured slides and QBR formats Canva AI — generates actual slides if you need the file

The manager’s AI workflow

RECOMMENDED WORKFLOW — AI-ASSISTED MANAGEMENT COMMUNICATION

Save your context once, reuse it always. Write a "manager persona" prompt describing your role, your company, your client relationship, and your communication style. Paste this at the start of every communication prompt — it takes 30 seconds and eliminates 80% of the editing you do on AI drafts.

Dump bullet points, not prose. AI converts bullet-point inputs into polished prose far better than it converts vague descriptions. Keep rough notes as you go — meeting bullets, key numbers, decisions made — and prompt from those rather than trying to remember everything when writing.

Always add your personal voice in one pass. AI drafts are structurally correct but impersonal. Read every output and add one specific, personalised detail — a reference to a shared context with the client, a specific team member's name, or a phrase that sounds like you. This takes 2 minutes and makes the difference between an email that gets a reply and one that gets filed.

Use the two-pass approach for sensitive communications. For escalations, difficult feedback, and client-facing issue communications — generate first, then use a second prompt: "Review this email. Does it sound defensive? Is the ask clear? Would a senior manager be comfortable sending this?" Fix what the model finds.

Never send AI output without reading it fully. AI gets names, dates, and numbers wrong in ways that are easy to miss. A client email with the wrong milestone date or a misspelled stakeholder name damages credibility instantly. Read every line before sending.

The three things to remember

KEY TAKEAWAYS — MODULE 3.3

Context and relationship define quality for manager communications — unlike code or SQL, every output in this module goes to a person who knows you. Include your role, your company, your relationship with the recipient, and the specific situation. Generic prompts produce generic emails that sound AI-written. Specific prompts produce communications that sound like you.
Structure the output you want, not just the content — for status reports, meeting summaries, and presentations, specify the exact sections, tables, and format. AI produces consistent, immediately usable output when given a precise structure. Without structure, you spend as much time reformatting as you saved drafting.
Add one personal touch to every AI draft before sending — one specific detail, reference, or phrase that is genuinely yours. This single habit transforms AI-assisted communication from obviously AI-written to professionally effective. It takes 2 minutes and is non-negotiable for client-facing work.

✎

Assignment 3.3 — Draft Three Professional Communications Using AI

Three real communication tasks. Use your actual work context or realistic scenarios from your target role.

Professional email: Write a prompt for a real email you need to send — or a realistic scenario you will face in your first job. Use the context-heavy structure: role, recipient, situation, tone, constraints. Note what you had to edit after the first AI draft and why.
Meeting summary: Take notes from any real meeting — a college group project meeting, a webinar, or a team discussion — and paste them into the meeting summary prompt structure. Compare the AI output to notes you would have sent manually. What did the model add? What did it miss?
Status update: Write a weekly status update for a project you are currently involved in — academic project, internship, or personal project. Use the RAG status structure. Note whether the Amber/Red items are framed accurately — this is where your judgement matters most.
Save all three prompts in your AI Learning Journal under "Module 3.3 — Manager Prompts." These feed into your complete prompt library in Module 3.4.

After completing this assignment, you will have a working set of manager communication prompts that cover 80% of the recurring writing tasks in an Indian IT management role.

Claim	Source
28% of workweek spent managing email — approximately 11.2 hours	McKinsey Global Institute, The Social Economy, July 2012 — still current benchmark per readless.app 2026
93% of project managers using GenAI for more than half their tasks report increased productivity	PMI, cited in sembly.ai GenAI in Project Management, February 2026
2.2 hours saved per week on average by GenAI users	Federal Reserve research, cited in autofaceless.ai AI Productivity Statistics 2026
Meeting summarisation, automated task assignment, and querying data from meetings are top AI meeting assistant uses	Metrigy research, cited in TechTarget AI meeting assistants February 2026
27% of AI users save over 9 hours per week	autofaceless.ai AI Productivity Statistics 2026, April 2026