Write a winning conference talk proposal

Craft a sharp, outcome-driven conference proposal that selection committees accept. Turns your experience into concrete attendee takeaways.

Prompt

Prompt
Act as a conference selection committee reviewer. Help me write a compelling conference talk proposal that focuses on concrete outcomes instead of a vague topic overview.

First, ask me these 3 questions and wait for my reply:
1. What is the core topic, and what exact technical or operational problem does it solve?
2. Who is the target audience in the room, and what specific challenge are they facing right now?
3. What are 2-3 tangible things attendees will be able to do differently the next morning?

Once I reply, generate:
- 3 Catchy, Action-Oriented Talk Titles
- Short Abstract (under 150 words) structured as Problem, Solution, and Case Study
- Key Takeaways (3 bullet points starting with an action verb)
- Why Me (3 sentences highlighting practical practitioner experience without fluff)

Example output

Example for: a pitch on migrating away from microservices back to a modular monolith

Talk Titles
  1. Trimming the Sprawl: Practical Lessons from Decommissioning 18 Microservices
  2. When Microservices Fail: How We Cut Deployment Latency 40% with a Modular Monolith
  3. The Monolith Strikes Back: A Guide to Consolidating Over-Engineered Architecture
Short Abstract

Every engineering team wants scale, but premature distributed architecture often produces network overhead, debugging nightmares, and broken release cadences. When our team spent 30% of each sprint troubleshooting cross-service dependencies, we stopped adding infrastructure and reversed course. This talk outlines the exact step-by-step framework we used to merge 18 microservices back into a clean, modular monolith over six months without downtime. You will see real latency benchmarks, automated testing patterns that kept data consistent during migration, and the political playbook for convincing leadership to simplify the stack.

Key Takeaways
  • Calculate your true distributed system tax using three production metrics.
  • Execute an in-place code merge using feature flags and branch-by-abstraction patterns.
  • Establish domain boundaries inside a monolith to prevent dependency rot.
Why Me

I spent eight years designing distributed systems before leading the architectural reversal across our 40-engineer product group. I do not promote silver bullets; I share real production rollback data, post-mortem findings, and unvarnished architectural trade-offs.

Written by AI from this prompt. Your results will vary.

Run this prompt in ChatGPT, Claude, or Gemini, then answer the 3 numbered questions. If you have a specific word count limit for a conference form, tell the model in your reply.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Presentations & Public Speaking
Presentations & Public Speaking

Outline a five-minute lightning talk

Turn a single idea into a focused five-minute lightning talk structure that hooks listeners and stays strictly on time.