Turning Projects into Products

Making Delivery Stick in

Complex Organizations

Why project and program leaders should treat go-live as the start of adoption,

not the end of delivery  

COMMENTARY

By Sudhakar Shivaraju                                                                     

Atlanta, Georgia, USA

In large organizations, many initiatives begin with strong sponsorship, a credible business case, and a committed project team. Yet a year after go-live, the reality can look very different. The new process is only partly adopted, reports still need manual reconciliation, and teams quietly keep pieces of the old way of working because it feels safer or faster. This is where many projects fall short, not because the project team failed to execute, but because the organization treated the change as something to launch rather than something to operate, measure, and improve.

A product mindset can help close that gap. This does not mean turning every internal initiative into a software product or borrowing start-up language that does not fit the environment. It means applying disciplines that matter in any serious delivery setting: clarity of outcome, visible ownership, user feedback, adoption measures, and continued improvement after the formal milestone has passed. In project and program environments, those disciplines can be the difference between a completed initiative and a durable capability.

A useful starting point is to define the outcome in operational terms. Many project charters still describe success as a deliverable: implement a system, roll out a process, migrate data, or complete training. Those deliverables matter, but they are not the same as business change. The more useful question is simple: what should be different in the day-to-day work six or twelve months after go-live? If the answer is fewer manual reconciliations, faster onboarding of new projects, or more reliable portfolio reporting, then those outcomes need to be named early and revisited often. Once the outcome is explicit, decisions about scope, sequencing, and trade-offs become easier to defend.

For example, if a new PMIS is intended to improve portfolio reporting, success should not be measured only by whether the system went live on time. It should also be measured by whether project teams enter data consistently, whether leaders trust the reports enough to use them in decision reviews, and whether manual spreadsheet reconciliation begins to decline. Those signals say more about the value of the change than the launch milestone alone.

Ownership is the next practical issue. In complex organizations, accountability can become diluted across steering committees, PMOs, technology teams, operations leaders, and control functions. Each group may be doing its part, but no one is clearly responsible for whether the new way of working takes hold. A product-style model does not remove governance. It makes accountability more visible. One person should be responsible for the end-to-end outcome, supported by a cross-functional team that can make practical decisions, resolve competing priorities, and keep the focus on value after implementation.

More…

To read entire article, click here

How to cite this article: Shivaraju, S. (2026).  Turning Projects into Products: Making Delivery Stick in Complex Organizations, commentary, PM World Journal, Vol. XV, Issue VIII, August.  Available online at https://pmworldjournal.com/wp-content/uploads/2026/08/pmwj167-Aug2026-Shivaraju-Turning-Projects-Into-Products.pdf

About the Author

Sudhakar Shivaraju

Atlanta, GA, USA

Sudhakar Shivaraju leads governance and systems strategy for a global real estate technology platform supporting thousands of active capital projects across more than 60 countries at a major global financial institution. His career spans capital project management and enterprise systems governance across manufacturing and financial services, including project management information system implementation experience at a multinational aluminum products manufacturer prior to his current role governing PMIS access, data ownership, and multi-party delivery models at scale. His work focuses on data governance, access control architecture, and project governance in complex, multi-party, and regulated environments. He holds a PMP certification and a Master of Science in Mechanical Engineering from the University of North Carolina at Charlotte in the United States. His writing has previously appeared in CoreNet Global & CIO Dive.

The views expressed in this article are those of the author alone and do not represent the views of the author’s employer.