Project Management

Please login or join to subscribe to this thread

Difference between Outcomes and Deliverables

linkedin twitter facebook  
avatar
Serges-Roberteau Tchoffo Geomatician| Freelance Consultant Yaoundé, Centre, Cameroon
According to your own experience in project management, what is the key difference between the Outcomes and Deliverables of a project (with examples please)?

Thank you in advance for your answer!
Sort By:
< 1 2 3 4 >
avatar
Vishakha Rai Founder| Omsruti India
May 19, 2020 10:01 AM
Replying to Stéphane Parent
...
A deliverable is something expected from your project: a four-lane highway, a new enterprise resource management system, a hospital wing.

The outcome is the benefit realized from the project deliverable: improved traffic circulation, better accounting and tracking of financial and human resources, new health care service.
1 vote from me.
avatar
Abolfazl Yousefi Darestani Manager, Quality and Continuous Improvement| Hörmann-TNR Industrial Doors Newmarket, Ontario, Canada
I agree with Lakeisha. You plan to achieve all the deliverables.
avatar
PETER BEMBIR Freelance PMP Facilitator and Researcher| University of Ghana Accra, Greater Accra, Ghana
Jun 01, 2020 10:31 PM
Replying to Khai Ng.
...
The answer depends on the scope of project and the type of organization you are working for, I mean the requesting organization (buyer) or performing organization (supplier). The requesting organization starts up a project with a business case including a list of positive outcomes then if you are PM, it is your responsibility to realize them. In reality, requesting companies will deliver that responsibility to business units with follow-up plan after project closure because outcomes and benefits realization will take time. The listed outcomes are always positive, no organization will initiate a project that will result in negative outcomes. But if you work for a performing organization then, in most cases, you will responsible for the outputs (Deliverables), not outcomes.
This is a significant addition to the beautiful explanations.
avatar
Denathayalan Ramasamy Chief Technology Officer| Atal Incubation Centre -CIIC Chennai, Tamilnadu, India
According to me

Deliverables are agreed documents, artefacts, attributes with stakeholders which indicates end of respective process

Outcomes are hypothesis, issue logs, updated risk register, lessons learnt documents which developed during monitoring, followed by control action plan of change in planning & execution process
avatar
Omar Haddad Jeddah, Western, Saudi Arabia
The outcomes are emerged from the deliverables. The deliverables are the tangible output while the outcomes are the core value.

I think we can get the deliverables response by asking the "What" question while getting the outcomes by asking the "Whys" questions. Maybe Multiple whys are needed to get the core value of the project.
A project without fulfilling values to customers is considered a non-sense project.
avatar
Justin Fu Senior Systems Engineer| Parsons Bristow, Va, United States
thanks all for info
avatar
Justin Fu Senior Systems Engineer| Parsons Bristow, Va, United States
Agree, thanks for info
avatar
Kevin McCuen IT Project Manager - PMP| Georgia Gwinnet College Lawrenceville, Ga, United States
When I've had to explain deliverable versus outcome I say the following (similar to responses above):

Deliverable: something tangible (working product)
Outcome: something intangible (any affects of the working product)
avatar
Vijay Suryavanshi Project Manager - Engineering| RECARO Aircraft Seating Plantation, Fl, United States
A deliverable is a specific product that is a result of the project. For example sharing a CAD model (step file) that a customer requests.
An outcome is something more amorphous—such as learning, evolving, improving—and is a benefit and direct result of the project deliverables. Outcomes are specific and measurable. It is also meaningful and indicates fulfillment of purpose towards long term achievement. For example, increasing sales by 30 percent in next four quarters or Reducing bad quality buy-ins of parts by 20 percent in next six months.
avatar
Vagner Antonio da Silva São Paulo, São Paulo, Brazil
Dec 06, 2021 10:23 AM
Replying to Thomas Walenta
...
Good discussion, adding a perspective:

- deliverables are the tangible output, or the result / product of the project - e.g. a SW delivered, a bridge built over river, the capability to do haircuts

- outcomes are what recipients / users can accomplish with the output, e.g creating new reports using the SW, cutting travel time by half using the bridge or applying for a barber job using your certified capability

- benefits are outcomes that are seen positively by some stakeholders, dis-benefits are seen negative by other stakeholders

For example the bridge as output creates a benefit for commuters as they save time every day but a dis-benefit for ferry owners.

Talking about benefits means to mention the stakeholders. Talking about outcomes or outputs is neutral.

Thomas
Well elaborated contribution, Mr. Walenta. Depending on the side you are related to the outcome(s) of a project is paramount to understand this process. Many stakeholders can benefit and many others, on the contrary, cannot. Thanks for sharing. All the best in your journey.
< 1 2 3 4 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

"I've had a perfectly wonderful evening. But this wasn't it."

- Groucho Marx

ADVERTISEMENT

Sponsors