# Why Every TPM Should Learn to Write Prompts Like Code

*By [Gianfranco Mileo](https://gianfranco-mileo.com/) · Published October 18, 2025 · updated September 6, 2026 · 2 min read · Category: Productivity · Tags: Prompt Engineering, TPM, Communication, Productivity, AI Agents · Canonical: https://gianfranco-mileo.com/blog/why-every-tpm-should-learn-to-write-prompts-like-code*

> Prompt engineering isn't just for developers. As TPMs, the way we communicate with AI mirrors how we communicate with teams — and both skills reinforce each other.

## Prompts Are Just Structured Communication

Here's something I noticed after months of using AI tools daily: the skills that make me a better prompt engineer are the exact same skills that make me a better TPM. Clear requirements. Explicit constraints. Concrete examples. Defined success criteria.

When I write a prompt like "Summarize this 50-page design doc into a 1-page executive brief, highlighting the top 3 risks, the proposed timeline, and any dependencies on other teams," I'm doing the same thing I do when I brief a new team member on a project.

## The TPM Prompt Patterns

### The Status Roll-Up Prompt

Instead of: "Summarize these updates"

Try: "You are a TPM preparing a weekly status report for VP-level stakeholders. From the following updates, create a structured summary with: (1) Top 3 wins this week, (2) Blockers requiring escalation, (3) Key metrics vs. targets, (4) Next week's priorities. Use bullet points. Flag anything that's more than 1 week behind schedule."

### The Risk Assessment Prompt

Instead of: "What could go wrong?"

Try: "Given this project plan and timeline, identify the top 5 risks using a likelihood/impact matrix. For each risk, suggest a mitigation strategy and an early warning indicator that would tell me the risk is materializing."

### The Stakeholder Communication Prompt

Instead of: "Write an email about the delay"

Try: "Draft an email to a VP stakeholder explaining a 2-week delay in Feature X. Tone should be direct and solutions-oriented. Include: root cause, what we've already done, revised timeline, and what we need from their team. Keep it under 200 words."

Related: see [From Spreadsheets to AI: The Evolution of Program Management Tools](https://gianfranco-mileo.com/blog/from-spreadsheets-to-ai-the-evolution-of-program-management-tools) and [How TPMs Can Build an MCP Server That Connects to Google Workspace — And Automate Everything](https://gianfranco-mileo.com/blog/tpms-build-mcp-server-gsuite-automation).

## Why This Matters

The TPMs who will thrive in the AI era aren't the ones who use AI the most — they're the ones who communicate with AI the most effectively. And that skill is directly transferable to every meeting, every email, and every escalation you'll ever handle.

> If you can write a prompt that gets the right output from an AI model, you can write a brief that gets the right outcome from a team. The muscle is the same.

---

Original article: https://gianfranco-mileo.com/blog/why-every-tpm-should-learn-to-write-prompts-like-code  
More articles: https://gianfranco-mileo.com/blog · RSS: https://gianfranco-mileo.com/feed.xml · JSON Feed: https://gianfranco-mileo.com/feed.json · Site context for agents: https://gianfranco-mileo.com/llms.txt