🔐 A Practical Guide to Structuring Your Technical Program

This guide will help you structure your next tech program at a tactical level + templates you can steal.

This guide is from my maven cohort course - Become A Great Technical Program Manager.

If you want to learn how Technical Program Management happens at places like Apple, Google, Nike, Blackberry → 🚨 Enrollment is now open for my upcoming cohort.

---

Photo by Xavi Cabrera on Unsplash | Putting Programs together is like building a complex structure out of lego bricks.

The intention of this guide is to share how I approach activating and structuring technical programs I lead.

Everything I do, I start with a solid foundation then build on top of it based on program needs. This is a template developed over time then refined with every program, success, and failure.

This guide includes the following sections:

🤔 What is a Program Structure?

📝 Information Structure

💬 Communication Playbook

🏃‍♂️ Program Momentum

💾 Coda Template You Can Steal

---

What is a Program Structure?

A Program structure is the process of activating a program at the tactical day to day to strategic week to week level. It involves how the teams work together, what information is shared + archived, and the outline of the plan to deliver the desired outcome.

Every Program Structure has three foundational pillars:

• Information - everything from project schedules, milestones, documents, high-level architectural diagrams, meeting minutes.

• Communication - how I manage stakeholders, distribute information, build comms conduits.

• Momentum - all day to day activities like regular meeting minutes, decision making with executive stakeholders.