Fifteen years ago, a simple question from my boss ignited a flame that still burns bright: “Can you make this idea fly?” That “idea” became my first foray into the exhilarating world of technical program management (TPM), a journey that has since woven its way through over 40 tech projects and a dozen intricate, multi-team programs. From nimble startups to sprawling enterprises, I’ve learned that while contexts may differ, the bedrock of success lies in a meticulous “set-up” phase. This isn’t a rigid checklist, but rather a playbook honed through experience, designed to de-risk delivery and unlock early learning. So, gather around, fellow journeymen, and let’s delve into the secrets that unlock high-flying tech programs.

Step 1: Mapping the Human Landscape - Stakeholders and Their “Why”

First, we lay the foundation with deep stakeholder understanding. Think of it as an intricate map, where each dot represents a person impacted by the program or holding the power to influence its fate. But it’s not enough to simply identify them; we need to understand their “why.” What problems do they hope this program will solve? What opportunities does it unlock? What’s their top priority? Through conversations and active listening, we capture these aspirations, align them with the program’s goals, and translate them into a set of clear, measurable OKRs that become our guiding stars.

Step 2: Forging the Hexad - A Leadership Crucible

No program truly soars alone. That’s why I assemble my Hexad, a carefully chosen team of six critical roles who form the program’s backbone. It’s more than just a program manager - this is a brain trust encompassing the Product Manager, the Sponsor, the Engineering Manager for technical ownership, the Solution and Business Architect for functional alignment, the Quality Engineer to ensure consistency across teams, and the Business Change Manager to orchestrate the human side of the transformation. Together, we co-create the program charter, a living document that maps our vision, approach, risks and dependencies, metrics, resources, and more. It’s our North Star, guiding us through uncharted territory.

Step 3: Igniting the Engines - Sponsorship and Urgency

With the map drawn and the crew assembled, it’s time to ignite the engines. We secure sponsorship, finding champions who lend their clout and voice to the program’s cause. But sponsorship alone isn’t enough. We need to spark urgency, a burning desire to see the program succeed. This is where I weave storytelling magic, painting a vivid picture of the problem we’re solving and the impact we’ll create. The air crackles with anticipation, propelling us forward.

Step 4: Charting the Course - Structure, Prioritization, and Quick Wins

Now, we plot the course. First, embrace agility. We break down the program into iterative cycles, constantly refining our backlog and adapting to changing landscapes. But agility isn’t just about flexibility; it’s about learning. That’s where MVPs come in. We identify those “quick wins,” the minimum viable products that allow us to test our hypotheses and gather real-world feedback. With each iteration, we learn, we adapt, and we build momentum, proving the program’s potential and securing buy-in for the road ahead.

Step 5: Building Bridges - Collaboration and Psychological Safety

No program exists in a silo. Cross-functional collaboration is the lifeblood of success. We create opportunities for engineers, designers, marketers, and business analysts to mingle, share ideas, and break down the walls between disciplines. This is where innovation truly thrives. But collaboration needs a foundation of psychological safety. We encourage open communication, embrace failure as a learning opportunity, and build trust within the team. Only then can diverse minds truly come together and achieve the extraordinary.

Step 6: Anticipating the Headwinds - Identifying Roadblocks and Assumptions

The road ahead is rarely smooth. That’s why we preemptively identify potential roadblocks. Which stakeholders might create obstacles? What dependencies could derail our progress? We actively seek out these hidden pitfalls and develop mitigation plans, ensuring we’re not blindsided by unexpected turbulence. We also challenge our own assumptions, constantly revisiting and refining our hypotheses based on new data and feedback.

Step 7: The Rhythm of Success - Monitoring, Adapting, and Celebrating

Launching a program is akin to conducting an orchestra. Every instrument, every team member, needs to play in perfect harmony. That’s why we establish a regular rhythm of monitoring and adaptation. We track progress against our OKRs, analyze data, and identify areas for improvement. This constant feedback loop ensures we’re always dancing to the music of progress, not clinging to outdated strategies.

But don’t forget the power of celebration. Each milestone achieved, each obstacle overcome, deserves recognition. A quick shout out, a virtual high five, a team lunch – these small gestures fuel morale and remind everyone why we embarked on this journey together. Celebrating success, both big and small, keeps the fire of motivation burning bright.

The Final Frontier: A Legacy of Lessons Learned

As the program reaches its culmination, we don’t simply pack up and move on. We take the time to capture the learnings, the successes and the stumbles, the insights gleaned from the trenches. These become our legacy, a treasure trove of knowledge that future programs can draw upon. By sharing our experiences, we not only elevate our own practice but also pave the way for a future where tech programs soar with even greater precision and grace.

What would you add?