The hottest Program Management Substack posts right now

And their main takeaways
Category
Top Technology Topics

Practical Almanac for Technical Program Managers

Building Rome(s) • 11 implied HN points • 30 Jan 26
💼 Business Program Management
  1. Clarity is the foundation: name goals, constraints, and what “done” means early, use writing to force decisions, and revisit assumptions before they become hidden problems.
  2. Make ownership explicit and real: assign clear accountability and give matching authority so decisions get made and escalations don’t become the default.
  3. Execution is social and continuous: watch handoffs and weak signals at the edges, build structure to avoid heroics, and reinforce decisions and timing so surprises don’t erode trust.

Where Is Technical Program Management Heading in 2026?

Building Rome(s) • 15 implied HN points • 15 Dec 25
🕹 Technology Program Management
  1. AI tools will keep getting much smarter and cheaper, so TPMs should design workflows that age well and leverage compounding improvements instead of chasing a perfect tool.
  2. The novelty phase of AI is ending — leaders will demand real ROI, so TPMs must focus on measurable outcomes like predictive planning, risk simulations, and AI-assisted forecasting rather than surface-level automations.
  3. Companies need to provide access and training for specialized AI tools because lack of access will become an organizational problem, and the TPM role will shift toward a builder, cross-stack, AI-fluent generalist that increasingly overlaps with product management.

A TPM’s Field Guide to Annual Roadmap Planning

Building Rome(s) • 11 implied HN points • 02 Dec 25
🕹 Technology Program Management
  1. Tie every proposal back to company OKRs and use clear metrics and smart questions to influence priorities even if you don’t own the product decision.
  2. Use simple capacity math (engineers × weeks) to make feasibility obvious, label stretch goals as aspirational, and protect teams from overcommitment.
  3. Manage dependencies with simple shared docs, secure soft commits with dates, document decisions clearly, and escalate through defined levels when blockers threaten the roadmap.

How I Keep Up With AI (Without Losing My Mind)

Building Rome(s) • 9 implied HN points • 17 Jul 25
🕹 Technology Program Management
  1. Staying updated on AI is important for progress, but you don't need to know every detail. Just focus on what matters for your work and growth.
  2. A good learning method includes quick updates, deep dives into interesting topics, and casual exploration during downtime. This keeps learning flexible and easy.
  3. Curiosity is key! Experiment with different learning sources and techniques until you find what works best for you.

🔥 48 hours left: Get 40% off Art of TPM

Building Rome(s) • 1 implied HN point • 29 Dec 25
🕹 Technology Program Management
  1. There’s a 48-hour limited-time 40% discount on the annual subscription, lowering the price from $80 to $48.
  2. The offering focuses on helping TPMs build judgment, leverage, and clarity to stay relevant as GenAI and new tools reshape the role.
  3. Paid members get practical, real-world resources—like an interview guide, an AI tools guide, and long-form lessons—plus a quiet community of thoughtful TPMs to learn from.
Get a weekly roundup of the best Substack posts, by hacker news affinity:

Nail Your 1:1 TPM Interviews

Building Rome(s) • 1 implied HN point • 26 Dec 25
🕹 Technology Program Management
  1. Interviews are short—use your 30–45 minutes ruthlessly and keep your introduction to 30–60 seconds so you have time for focused answers.
  2. Center every answer on your role, decisions, and measurable impact; keep background brief and use 'I' so the interviewer can assess what you personally did.
  3. Practice concise, well-paced answers to avoid rambling, and choose high-impact examples (including incidents, outages, or complex bugs) not just large formal programs.

🔐 How TPMs Can AI - Launch Readiness Checklist

Building Rome(s) • 5 implied HN points • 15 Aug 25
🕹 Technology Program Management
  1. AI tools can help Technical Program Managers (TPMs) work more efficiently by providing practical solutions to common challenges. This means TPMs can save time and get better results.
  2. Creating a launch readiness checklist can be daunting, especially for those new to a role. Using AI can simplify this process by generating initial drafts that can be refined with team input.
  3. Writing effective prompts for AI tools is crucial for achieving desired outcomes. A well-structured prompt can lead to a useful template and promote better discussions with engineering teams.

🔐 TPM Microguide: Lessons On Running Effective AI Projects + Project Plan Template

Building Rome(s) • 5 implied HN points • 03 Aug 25
🕹 Technology Program Management
  1. Beta and pilot testing are crucial for AI projects. They help find issues that regular testing might miss and provide early feedback from users.
  2. It's better to launch AI features gradually rather than all at once. Starting small and monitoring the results can help avoid bigger problems later on.
  3. Involve privacy and legal teams from the beginning. Early discussions about data practices can prevent delays and help build trustworthy AI products.

🔐 TPM Microguide On Interview Preparation - v1.0

Building Rome(s) • 9 implied HN points • 11 Feb 25
💼 Business Program Management
  1. Preparation is key for Technical Program Management (TPM) interviews. You should practice personalizing your answers based on your experiences rather than just memorizing them.
  2. Understanding the types of questions you'll face can help a lot. Interviews often include hypothetical scenarios and technical questions, so being ready for these can make you feel more confident.
  3. Having a strong elevator pitch is important. This is your chance to introduce yourself and explain what you bring to the table in a quick and engaging way.

Why I Stopped Writing In 2024 + I Am Back

Building Rome(s) • 7 implied HN points • 04 Jan 25
💼 Business Program Management
  1. The author stopped writing in 2024 due to personal and professional changes but is returning in 2025 with fresh energy and focus.
  2. The newsletter has been rebranded to better reflect its content, now called 'The Art of Doing Technical Program Management', and will provide practical insights for TPMs.
  3. New subscription options and courses will be introduced, offering deeper content and personal coaching to help both new and experienced Technical Program Managers.

TPM Guide To Ticket Intake Management

Building Rome(s) • 5 implied HN points • 03 Feb 25
🕹 Technology Program Management
  1. Teams can improve how they handle incoming requests by using different models like dedicated triage teams, intake funnels, or individual component owners. Each model has its own benefits and can suit different team sizes and needs.
  2. It's important for teams to balance structure with flexibility when managing requests. A rigid system may cause more issues, so finding a process that works best for the team is key.
  3. As technology, like AI, advances, ticket management may become more automated. For now, focusing on effective intake processes will help teams stay productive and reduce chaos.

Feeling overwhelmed by information / TPMs are World Builders / The Right Amount of Slack

Building Rome(s) • 11 implied HN points • 18 Jul 23
🕹 Technology Program Management
  1. Feeling overwhelmed by information is common for Technical Program Managers, so it's important to focus on what truly matters and develop a system for rapid recall.
  2. TPMs are not just program runners; they are world builders who can shape engineering organizations by influencing decision-making processes, strategy, and more.
  3. Adding the right amount of slack in project plans is crucial for TPMs to build flexibility and account for uncertainties, especially in testing phases.

🔐 A Practical Guide to Structuring Your Technical Program

Building Rome(s) • 11 implied HN points • 09 Jul 23
🕹 Technology Program Management
  1. A Program Structure involves activating a program at tactical and strategic levels by focusing on information, communication, and momentum.
  2. The foundational pillars of Program Structure are Information, Communication, and Momentum.
  3. Having a solid foundation and refining it based on program needs is essential for successful program activation and structuring.

A Dispatch On All Things Tools

Building Rome(s) • 7 implied HN points • 11 Sep 23
🕹 Technology Program Management
  1. Building timelines can be frustrating due to lack of ideal tools like Gantt charts or whiteboarding tools.
  2. C4 Diagrams are a great visual language to discuss software architecture for TPMs and PMs.
  3. There is a desire for an all-in-one tool to manage product development, simplifying the use of multiple tools like Slack, Linear, Coda, Figma.

Ask Aadil - Wrong way to use the TPM function

Building Rome(s) • 7 implied HN points • 12 May 23
💼 Business Program Management
  1. Technical Program Managers operate on two planes: strategic and tactical.
  2. The real value of TPMs comes from operating on both strategic and tactical planes.
  3. To fix the situation of using TPMs in the wrong way, help evangelize the TPM role, ensure the culture is right for a TPM, and ease in the TPM role while establishing a Program Charter.