From Project Completion to Asset Outcomes
Interviewer: Nicholas Johnson, Chief Evangelist, Kahua
Interviewee: Jack Dempsey, Founder, Asset Management Partnership
A Q&A with Jack Dempsey on Asset-Centric Project Management
Most owners implement a PMIS to improve project delivery: better cost control, better schedules, better workflows, better reporting.
But for asset owners, the more important question is not simply, “Did we deliver the project?”
It is, “Did we deliver an asset that is ready to operate, perform, and create value over its full lifecycle?”
That question sits at the heart of Asset-Centric Project Management. To explore why this matters, I spoke with Jack Dempsey, founder of the Asset Management Partnership, about the difference between managing projects and delivering long-term asset outcomes.
Nicholas: Jack, you often say that “better asset management leads to better outcomes.” What does that mean?
Jack: It means organizations need to focus on the outcomes their assets are supposed to enable.
Those outcomes usually fall into a few key categories: mission performance, financial performance, risk management, and sustainability. Infrastructure is not valuable simply because it was built. It is valuable because it supports the work of the organization over time.
That may mean supporting military readiness, healthcare delivery, education, transportation, energy, public service, or commercial operations. The asset has a purpose. Asset management is about making sure the organization gets the best possible value from that asset across its lifecycle.
Nicholas: Why is traditional project-centric delivery not enough?
Jack: Because a project is temporary, but an asset can last for decades.
Capital programs are often optimized around project completion. They track scope, schedule, cost, change orders, documents, and closeout. Those things matter, but they do not tell the whole story.
If the project is delivered on time and on budget, but the owner does not receive the information needed to operate and maintain the asset, then the project has created a downstream problem.
The owner may have a completed building, facility, or infrastructure asset, but not an operations-ready asset.
Nicholas: Where does that problem usually become visible?
Jack: At handover.
That is when the operations team needs structured asset data: equipment lists, locations, warranties, manuals, maintenance requirements, commissioning records, and other information needed for the CMMS, EAM, GIS, ERP, or facilities systems.
Too often, that information was not captured in a structured, usable way during design and construction.
So the organization ends up recreating the asset inventory after the fact. Teams audit equipment, validate data, reconcile drawings with field conditions, and manually populate operational systems.
That can take months. And in some cases, the asset may be physically complete before it is truly ready to operate.
Nicholas: You make a distinction between “managing assets” and “asset management.” Why is that important?
Jack: Managing assets is what you do to assets. It includes maintenance, inspections, repairs, replacements, and work orders.
Asset management is what you do with assets to achieve organizational objectives.
That distinction matters because organizations can be very busy maintaining assets while still lacking a strategic view of asset performance, risk, cost, and value.
Capital planning, lifecycle costing, maintenance strategy, deferred renewal, risk exposure, and mission readiness are all connected. If those areas are managed in silos, owners may optimize individual decisions while missing the bigger lifecycle outcome.
Nicholas: How does Asset-Centric Project Management change the starting point?
Jack: It changes the first question.
Instead of asking only, “How do we deliver this project?” owners also ask, “How will this asset perform across its lifecycle, and what information will we need to manage it?”
That means asset information requirements need to be defined early. Owners should know what assets must be tracked, what data attributes are required, what documents need to be linked, what naming conventions will be used, and what operational systems need at handover.
Those requirements should not be discovered during closeout. They should shape the project from the beginning.
Nicholas: From Kahua’s perspective, this is where the PMIS has to evolve. It cannot just manage project activity. It has to help create the asset record.
Jack: Exactly. A PMIS should support the delivery of an operations-ready asset.
That means capturing structured asset data during design and construction, linking project records to the asset, validating data quality before handover, and connecting that information to the systems used by operations.
The owner should be able to see whether the asset information is becoming complete as the project progresses.
That is a very different measure of readiness than simply asking whether the project documents have been uploaded at the end.
Nicholas: What should capital program leaders do differently?
Jack: They should expand the definition of project success.
Success is not just budget, schedule, scope, safety, and quality. It is also operational readiness, asset data quality, lifecycle value, and the ability to manage the asset from day one.
That requires governance. Owners need to involve operations earlier, define asset data requirements, assign accountability, and make asset information a deliverable throughout the project.
If the team is responsible only for delivering a project, they will behave one way. If they are responsible for delivering an operations-ready asset, they will behave differently.
Nicholas: What is the core message for asset owners?
Jack: Do not wait until handover to think about the asset.
The asset lifecycle begins before design, not after construction. Every capital project is an opportunity to improve the owner’s asset data foundation, but only if asset information is treated as part of delivery.
A project-centric PMIS may help manage the work.
An asset-centric PMIS helps manage the outcome.
For owners responsible for large, complex, long-lived portfolios, that difference matters.
Closing Thought
Construction is not the finish line for an asset owner. It is the beginning of a much longer operational story.
That is why Asset-Centric Project Management matters. It connects capital delivery to lifecycle performance. It treats asset data as a strategic deliverable, not a closeout artifact. And it helps owners build not only projects, but assets that are ready to perform.