4 steps to product-centric IT program management
Learn how to bring product thinking to IT Program Management and deliver measurable ROI from every project
Executive summary
IT Program Managers are stretched thin. Leadership wants ROI, stakeholders want shiny new features, and teams want clarity on what actually matters. Meanwhile, dependencies pile up, capacity creeps, and the loudest project wins instead of the most valuable one.
In this guide, we sat down with Richard Sworder, Head of Product Ownership at Atlassian Williams F1, to map out a 4-part journey from chaos to clarity. His team measures every idea in milliseconds shaved off lap time, and that same outcome-first lens applies to any IT program. You'll see the exact frameworks they use to align goals, prioritize across a portfolio, track progress, and stay ahead of bottlenecks.
This guide will give you a shared language to talk about value with stakeholders, frameworks you can put to work this quarter, and tactics to take back to your teams on Monday.
What's inside
- Why outcomes beat outputs for IT Program Managers, and how to define "value" so priorities become self-evident
- 4 proven frameworks from Atlassian and Williams F1, including OKRs, Impact vs Effort, the RUF pyramid, and the Rolling 4 planning cadence
- The anti-patterns to avoid, from shiny object syndrome to capacity creep to manual status collection
- Practical tactics for dependency mapping, custom stakeholder roadmaps, and Red-Yellow-Green status scoring across teams