High Performance Outcomes

I spend a fair amount of time traveling around the country teaching, presenting, and lecturing on integrated project delivery, collaboration, and acquisition management. I teach the "Owner's Series" course work for DBIA, I just presented a lecture at Drury University (my Alma Mater), I, along with the owner and design-builder, presented a performance-based design-build project at the AIA National Convention. I could go on (lucky for you, I won't)...I just finished a comment in my Linkedin discussion group, and thought I'd share it. During nearly all of these presentations and lectures I ask three (tongue-in-cheek) questions as an 'ice breaker' to get the audience thinking... How do you stump an designer? Answer: Give them a budget. How do you stump a builder? Answer: Give them a blank sheet of paper. How do you stump an owner? Answer: Ask them what they want. The point I want to make is that all three primary players involved in project delivery tr

Consider this question, and you soon realize that Value-Engineering is usually used as a 'reactive tool' to correct a proposed solution for a given problem. Stated differently: VE is used to re-design a set of plans and specs to realign "the design" to fit "inside" the owner's budget. Conversely, the idea of Engineer-Value (EV) is an 'active tool' used to "guide" the solution to a given problem while concurrently maintaining alignment with (fitting in) the ownr's budget.  In defense of true Value Engineers , I recognize that VE is a process (in its purist form) that begins at the inception of a project. But in our industry, today, VE is more commonly used to "hack" the design apart to save money. The real offensive part of this mis-application of Value Engineering is that 'limited' resources have been consumed (fees paid, efforts of design, documentation, bidding the design documents, etc), and the time lost can

Acquisition Evolution With regard to this blog, it concerns the "final outcome" (results) of an owner's Constuction Project. As this is my initial post, and have been wanting to share my views on Construction Project Owners pursuing "High Performance" project outcomes, a definition of "High Performance Outcome" (HPO) is in order. HPO is the absence of deviation between the identified needs of the Constuction Project Owner and the fulfillment of those needs by the Service Provider (designers & builders). Identified needs are those documented, in measurable form, and provided to the designer(s) and/or builder(s)that define what is to be fulfilled. Wow...pretty wordy! How about: "when the owner gets kind of what they expected, and is satisfied." For many of us, in the routines of the day, that would be an improvement. Count how many times you end up disappointed in the 'outcome' of a transaction. I forgot who said it, but &qu