Professional development
Moving from projects to programs changes the questions.
Omer Khan · 4 min read
The shift is towards dependencies, benefits and choices across a connected set of initiatives.
Delivering a project well is a strong foundation for program leadership. The next step is to understand how several initiatives combine to produce an outcome, and where their individual priorities may conflict.
Look beyond individual milestones
A project can meet its own deadline while another initiative remains unable to use its output. Understand the dependencies between teams, systems, suppliers and operational change. Discuss readiness rather than treating completion as sufficient.
Connect delivery with benefits
A delivered capability is not automatically a realised benefit. Identify who will change their way of working, how adoption will be supported and which measures will show progress. Work with operational owners to establish that connection early.
Make choices across the program
Resources and funding are limited. Program leadership involves recommending where effort will produce the greatest value and where a change should be delayed or stopped. Explain the reasoning so that affected stakeholders can assess the trade-off.
Build a shared picture
Give stakeholders a concise view of outcomes, dependencies, risks and decisions. Details still matter, but they should support a common understanding rather than create a separate version of the program for every audience.
Develop through real decisions
Take responsibility for a cross-project dependency, benefits discussion or prioritisation recommendation. Ask for feedback on your judgement and communication. Qualifications can support the transition, while practical responsibility develops the capability.