Strategic Program Management
The strategy-to-benefits chain
Strategic Program Management tests whether you can trace a program's existence back to organizational strategy. Know the hierarchy: the portfolio selects and prioritizes the right programs and projects; the program delivers related benefits through coordinated components; the project produces outputs. A program exists because a set of related benefits cannot be achieved by managing its components separately.
Key concepts to name: program mandate, business case, program charter, strategic objectives, benefits alignment, organizational process assets and enterprise environmental factors, and the program manager's role as an integrator who aligns work to strategy rather than setting strategy.
Traps. Questions often offer a large, complex project and call it a program - size and complexity do not make a program, and neither do unrelated deliverables. Another trap asks the program manager to change the corporate strategic plan or to terminate a program; authority for selection and termination normally sits with portfolio or executive governance, even though the program manager should recommend and escalate. Watch for answers that put the program manager in charge of component project managers' daily task assignments.
Rule of thumb - the three-question test. Ask: (1) Is the justification a single deliverable or a set of related benefits? (2) Would coordinating the components produce benefits unavailable separately? (3) Is there an executive sponsor and a governance body above the program? Three yeses means program.
Worked example. A utility plans five efforts: a new billing system, a call-center redesign, a data warehouse, staff retraining, and a customer portal. Each could stand alone, but together they target a 20% reduction in cost-to-serve over three years. Because the shared justification is a measurable benefit set requiring coordination, this is a program; the billing system alone is a project.