What is a High Performance Outcome?

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 "half the promises broken were never made".

To end, consider this: I believe that every project owner has 7 fundamental expectations (YouTube Vide) relative to the outcome of their project and the people they hire (or "team" with):

Consider 7 Fundamental Expectations
1- Be on budget, don't make me have to go back and ask for more money. You said you could do it for this, so do it for this!

2- Be on schedule, don't wait until halfway through the project to uncover 'surprises' you should have predicted along time back....after all, you have done this before, haven't you?

3- Satisfy my need for Scope, not provide every square inch of the program metric...but accomodate my occupants, users, operators, etc. After all, I started this project to support the physical/environmental needs of the folks I serve.

4- Be Professional. You know, don't try and make decisions and do work you are NOT qualified to do, even though you fooled me in the interview and now I'm stuck with you...calm down.

5- Be Predictable (as referred to in number 2 above) about every single detail...after all, if I can count on number 4 above, then you have the skill to, indeed, be predictable. It is important, because I have a boss to report to...I can't keep changing the story...

6- Be Accountable. Let's use your checkbook for your mistakes...and I'll use mine for my mistakes. By the way, numbers 4&5 should allow me to depend on you, and avoid the use of my checkbook in the first place.

7- Let's Meet-the-Market. I don't want the cheapest or most lavish project...I just want a SQUARE deal...even if I haven't got the foggiest idea of what 'square' is.

And that's it...hope you enjoyed this initial blog.

Thanks
Dave

See more about the Owner's 7 Fundamental Expectations at www.designsense-Inc.com
1980-Builder 1990-Architect 2000-DesignBuilder Today-Experienced and well-worn

Popular posts from this blog

"Proposed Solution" does not equal "Problem Solved" (Problem-Based Contracting)

Image
Prediction: The Key to Planning Let's say 10 people are invited to propose how they would execute the task of taking a trip from New York to LA. The goal is to leave NY and be in LA in 7 days (to deliver a letter for some kooky eccentric who makes-up odd challenges). Each competitor would propose details of their planned trip and would sign a contract to deliver the letter. What would influence the path and pace of their individual routes? Let's say each person had only $1,000 to spend toward the trip. Does the mode of transportation change? Let's say each must visit at least one National Park along the way (more than one park visited earns a 'tip'). Do the routes change? Let's say that each had to spend at least one day photographing a "national landmark" along the way (more than one photographed earns another 'tip'). Does the 'itinerary' change? Of course each 'proposal' would likely be different, there is a thousands
Read more

DBIA's 10 BP's in 10 Post (#2)

Image
NREL's First DB Project If you missed my discussion on DBIA Best Practice #1 and the introduction of this series, now is the time to review . Moving on to BP#2 An owner should implement a procurement plan that enhances collaboration and other benefits of design-build and is in harmony with the reasons that the owner chose the design-build delivery system. Right off the bat, this practice charges the owner with fostering a procurement plan that enhances “collaboration”: a prominent opportunity and result of Design-Build Done Right. However, the beneficial affects of collaboration do not move from opportunity to result without a determined effort on the part of the owner. To pause here, and go deeper into collaboration, consider that this requires the owner, designer and builder to make commitments, and keep them. The owner is, and must be, the guardian of the collaborative effort: because the project owner is uniquely positioned as the default “governor” of th
Read more

Long Long Ago…

Image
C. 2008 Well maybe not “long long ago”. To be real…September 17, 2014 was my last post to this blog. Almost a decade. Back then, bloggin’ was somewhat new, at least to me, having started in 2011. Writing thoughts to anonymous readers was a way to crystallize the research and application of what I’ve developed over my many years in the design and construction industry. Much of this thinkery was applied to projects that achieved great success, beyond my expectations. Many fell flat on their face, providing insult to my ego, a loss of credibility to some, humility, doubt in my mind. What the hell…let’s tweak it and try again! And the outcomes always got better in direct proportion to my learning from both success and failure. On that note, the note of courage to try again, I have a future post coming. The story of a major government project, millions of dollars, a third-party critique of the project approach, an empty office occupied by only me and a government PM (who had about 20 bosses
Read more