Build the case for joining an InfoQ Certification cohort.
Use the guided prompt to build the request around the work you already own, or start from a ready-to-edit email.
Practitioners leading the current cohorts
Choose the one that fits how you want to work.
Guided AI prompt
Best when you want the request tailored to the work you already own.
The prompt asks about your role, current work, why the cohort is relevant now, and what your manager is likely to care about.
It produces:
- A ready-to-send manager email
- A version under 150 words for Slack or Teams
- Five short talking points
- One note on a missing detail that could strengthen the request
Ready-to-edit email
Best when you want a quick starting point you can copy and edit yourself.
The template gives you a clear structure with placeholders for the exact program name, dates, schedule, the work you already own, and the capstone.
Build the request around your actual work.
You are helping me write an honest business case to my manager for approval to join an InfoQ Online Certification cohort. Write in my voice. Make a credible case, not a sales pitch. Use only: 1. the information I give you; 2. any cohort facts already supplied below. Do not invent projects, company details, outcomes, ROI, technical challenges, cohort facts, or claims about what the program will achieve. ## Program naming rule The program name and certification name are the same. Use the exact public program name exactly as I provide it or exactly as it appears in the supplied cohort facts. Do not abbreviate it, rewrite it, or add words such as "InfoQ Certified", "Certification Program", or "Course". When referring to what I am joining, write "[PROGRAM NAME] cohort". When referring to what I earn after successful completion, write "[PROGRAM NAME] certification". ## How to run this Ask me the questions below in small batches of three or four. Wait for my answers before moving on. Skip anything already answered by the supplied cohort facts. If the exact program name has not been supplied, ask this first: "Which InfoQ Certification program are you considering? Please use the exact program name shown on the cohort page." If I have the cohort page open, ask me to share the link or give you the start date and schedule instead of guessing them. Then ask: "What are you working on right now that makes this cohort relevant?" ## Questions to ask About my work: - My role and main responsibilities - What my team currently owns - A project, system, proposal, or decision I am working on - What is difficult or uncertain about it - Why outside perspectives would be useful now About the cohort: - Which parts of the syllabus are most relevant to that work - What I hope to test, clarify, or apply during the five weeks - How I expect to use the capstone or work produced - Whether I plan to share anything back with my team About the approval: - My manager's name - What my manager normally cares about when approving professional development - The most likely objection, such as budget, time commitment, or workload - The tone I want: plain and formal, or more casual ## Cohort facts, when supplied Program name: Facilitator: Facilitator credential: Start date: Source schedule: Device-local schedule: Device time zone: Format: Price: Focus areas: Audience: Capstone: If one of these fields is empty, ask me for it only if it is needed. Do not guess it. ## Write the manager request Produce: 1. A ready-to-send email. 2. A version under 150 words for Slack or Teams. 3. Five short talking points for an in-person conversation. 4. One short note telling me if a missing detail would materially strengthen the case. The email should: - open with the request to join the [PROGRAM NAME] cohort; - connect the cohort to work I already own; - include verified dates, schedule, time commitment, price, and capstone; - mention that successful completion earns the [PROGRAM NAME] certification only if useful; - address the likely objection if I gave you one; - close with a straightforward request for approval. ## Style Plain, specific, first person. No hype or marketing language. Do not promise ROI. Do not claim the cohort will solve my company's problem. Do not invent business impact. Use short paragraphs. Do not use em dashes. The strongest argument should be the connection between the cohort and work I already own.
Start from a simple email and fill in the details that matter.
Subject: Approval request to join the [EXACT PROGRAM NAME] cohort Hi [Manager's Name], I'd like approval to join the upcoming [EXACT PROGRAM NAME] cohort. It's a five-week live online InfoQ Certification cohort with four live hours per week and a registration cost of USD 1,470. I'm interested in it because [CONNECT THIS TO WORK YOU ALREADY OWN]. In particular, [SYLLABUS AREA / DECISION] is relevant to [PROJECT / SYSTEM / RESPONSIBILITY]. I'd use the cohort to work through [SPECIFIC DECISION / QUESTION / CHALLENGE] while that work is active. The capstone is [CAPSTONE / CONCRETE OUTPUT]. I'd expect to use or share that work by [HOW IT CONNECTS BACK TO THE TEAM]. The cohort starts [START DATE] and runs [SOURCE SCHEDULE]. [OPTIONAL: In my device time zone, that is LOCAL SCHEDULE · DEVICE TIME ZONE.] Successful completion earns the [EXACT PROGRAM NAME] certification. Could I get approval for the USD 1,470 registration cost and the live session time? For reference: [COHORT PAGE] Thanks, [Your Name]
The strongest case is the connection to work you already own.
A manager should be able to see:
-
01
What you already own.
A system, initiative, workflow, strategy, or decision.
-
02
Why the cohort is relevant now.
Which part of the syllabus connects to that work.
-
03
What comes back to the team.
A capstone, recommendation, operating model, assessment, or share-back.
-
04
What it requires.
The current schedule, weekly time commitment, and USD 1,470 registration cost.
Avoid invented ROI or generic claims about career growth.