The hottest Program Management Substack posts right now

And their main takeaways
Category
Top Technology Topics
Building Rome(s) 9 implied HN points 11 Feb 25
  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.
Building Rome(s) 5 implied HN points 03 Feb 25
  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.
Building Rome(s) 7 implied HN points 04 Jan 25
  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.
Building Rome(s) 11 implied HN points 18 Jul 23
  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.
Building Rome(s) 11 implied HN points 09 Jul 23
  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.
Get a weekly roundup of the best Substack posts, by hacker news affinity:
Building Rome(s) 7 implied HN points 11 Sep 23
  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.
Building Rome(s) 7 implied HN points 12 May 23
  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.