UPI Study › Courses › Project Management › Free lessons › Lesson 1.4 Free with a free account
Business Value and Strategic Benefits of Project Management
Project Management · Chapter 1: Foundations and Framework of Project ManagementSection 1.4 · lesson 4 of 7311 min · free with a free account
Free preview
Create a free account to keep watching
It takes a minute and costs nothing. Your free account unlocks all of Chapter 1 and 3 more lessons of Project Management.
Lesson complete
Earn the 3 college credits for Project Management
Enrolling adds a quiz after each lesson, the graded work and the official transcript. Recommended for credit by NCCRS.
Next lesson: Identifying and Managing Project Stakeholders →← Structure and Functions of a Project Management OfficeNext lesson: Identifying and Managing Project Stakeholders →
In this lesson
How projects create business value through alignment and realized benefits.
- Trace a project to a strategic objective using the so that what test
- Distinguish outputs, outcomes and benefits and explain benefits realization
- Evidence tangible and intangible benefits with baselines, proxies and benefit owners
- Describe how disciplined practice and maturity stages affect predictability and risk
Free study notes
Get this lesson's notes by email
The key points and 4 practice questions with answers, in your inbox. One email, free.
One email. Unsubscribe in one click.
Transcript
Everything said in the video, section by section (1,505 words). Read along, or search it.
Opening Question
Proving a Claim Form Project Is Worth It
Dana is an operations manager at Fernhill Mutual, an insurance cooperative owned by its members. Members complain that the claim forms are long and confusing, and Dana wants a project to simplify them. But the executive committee funds only projects that link to its objectives, and come with a way to tell whether they worked. So how do you prove a project is worth it, when most of the payoff arrives after the team has gone?
Definition
Vision, Strategy and Strategic Objectives
The worthwhile return an organization gets from an activity, measured against what it gave up, is its business value. Value starts with alignment. A vision is a short statement of the future position an organization wants to reach. Fernhill's vision: be the most trusted insurer in its region. Its strategy, the chosen approach: win trust through service that's easy to use. A strategy breaks into strategic objectives: specific results within a set period. One of Fernhill's: shorten the wait for a decision on a simple claim. Strategic alignment means a project is chosen because it delivers, or directly serves, an objective like that.
Alignment Test
Asking So That What
To test alignment, keep asking: so that what? A new one-page claim form exists so that members can complete claims without help. That exists so that decisions come sooner. That serves the objective of shorter waits, and that serves the strategy of easy service. If the chain breaks, the project isn't aligned. A refresh of the internal newsletter, however well run, traces to no stated objective. Alignment is necessary for value, but not sufficient. A perfectly aligned project can still deliver nothing.
Case Study
Outputs, Outcomes and Benefits at Brightwater
Here's how that happens. Brightwater Haulage, a small freight company, spends a quarter building an online booking portal. The portal is finished on time and to specification. That's the output: a thing the project produces and hands over. The intended outcome, a change in behavior when the output is used, was that customers would book online, and stop phoning the dispatch desk. The intended benefit, the advantage the outcome brings, was freeing a dispatcher's time for route planning. Six months later, the phones ring just as often. The portal asks for an account number most small customers don't know. The output was delivered. The outcome never happened, so the benefit never arrived. A project team controls the output almost completely, influences the outcome partly, and controls the benefit hardly at all.
Process
The Benefits Realization Loop
Benefits realization is the discipline of making sure the improvements a project was approved for are identified, planned, delivered, and then checked. Identifying means stating, before approval, what will be better, for whom, and by how much. Planning means deciding how and when each benefit will be measured, who is responsible, and what behavior must change. Delivering means handing over the outputs, and supporting the changes that put them to use. Checking means measuring, once they're in use, whether things improved. The four repeat as a loop, and checking falls almost entirely after the project has closed. Projects are temporary, but benefits aren't. So someone must stay responsible after the team is gone: a benefit owner.
Quick Check
A Scheduling System Nobody Uses
Quick check. A clinic's new scheduling system passes its acceptance test and goes live. Months later, the night shift still keeps paper lists, because nobody showed them the system. What failed: the output, the outcome, or alignment? Pause, and decide. The outcome. The system exists, so the output was delivered, but the change in how people work never happened. Alignment is fine: faster scheduling surely serves the clinic. The missing step was training, the bridge between output and use.
Tangible Benefits
Measuring Against a Baseline
Some benefits are tangible: expressed directly in money, hours or counts, and checkable against records. Cost reduction is spending less for the same result. Revenue is new income. Time saved is less effort or less elapsed time. Every tangible benefit is evidenced the same way: against a baseline, a measurement taken before the change. Say an office spent 30 hours a week on manual entry before a project, and 18 after. Thirty minus eighteen: 12 hours a week saved. But saved hours become a cost reduction only if something happens to them: removed from a budget, or moved to other valuable work. Two habits make the evidence credible. Define the measure before the project starts, and name a benefit owner. A benefit with no owner is nobody's job.
Worked Example
A Nine-Day Claims Baseline
Dana applies this to her claim form. The claims log already records when each claim arrived, and when it was decided. Over the last three months, simple claims took an average of nine working days. That's her baseline. She proposes a target of six days, three days faster, and names the head of claims as the benefit owner.
Intangible Benefits
Proxy Measures and False Precision
Other benefits are intangible: real and valued, but not countable directly. Reputation, learning, morale and safety culture are examples. Their trap is false precision: a figure presented as more exact than its evidence. Morale up fourteen percent sounds impressive. Unless morale was measured the same way before and after, and the change is tied to the project, the number hasn't earned its authority. Honest evidence uses proxy measures: observable quantities expected to move with the thing you can't see, like a survey score or near-miss reports. Whether to convert intangibles into money is contested. Supporters say unpriced benefits get ignored. Critics say one money figure invites false confidence. Both sides accept one rule: state the type of evidence plainly, and never dress it up as a better type.
Predictability
Narrowing the Schedule Gap
A second kind of value is about how an organization works. Predictability is how closely what a project delivers matches what it promised. Other departments plan around those promises. The schedule gap is the delivered duration minus the promised one. Two projects each promise 20 weeks. Project A takes 26, a gap of 6 weeks. Project B takes 22, a gap of 2. Disciplined practice tends to produce gaps like B's, in two ways. Planning breaks work into pieces small enough to estimate. And tracking spots a small slip while it's still small, when there's still time to respond. The limits matter. Discipline narrows the gap, but never removes it. A project can be perfectly on time and still worthless, like the portal. And padding every estimate makes promises predictable in an unhelpful way, by wasting time.
Risk and Waste
Finding Problems Earlier
Risk exposure is the overall possible harm being carried, weighing how likely problems are and how damaging they'd be. The argument for discipline here is about timing. A problem found in week two offers several remedies. Found in the last week, it offers one, and an expensive one. Waste has familiar forms: work redone after a misunderstood requirement, people waiting on an overrun task, and good staff stuck on a project that should never have started. Clear scope reduces the first, a visible schedule the second, and alignment the third. Each is a plausible mechanism, not a guarantee.
Maturity Model
Four Stages of Project Maturity
Project management maturity is how consistent, documented, measured and improved an organization's project practices are. It's usually pictured in four stages. At the ad hoc stage, every manager runs projects their own way, and success is hard to repeat. At the defined stage, written methods exist, so two managers given similar work do it in recognizably similar ways. At the measured stage, the organization collects data on how projects actually perform, such as schedule gaps. And at the continually improving stage, that data feeds deliberate changes to the methods, so lessons reach the next project. A caution: more process is not automatically more value. A small, low-risk project loaded with heavy process is wasting effort, and how much maturity pays off is disputed.
Quick Check
A Shared Playbook Without Data
Quick check. At a city agency, every project uses one shared playbook for its plans and reports. But nobody tracks how the projects actually turn out. Which maturity stage is that: ad hoc, defined, or measured? Pause, and decide. Defined. The shared playbook makes the work consistent, so it's past ad hoc. But without performance data, it hasn't reached measured, and it can't improve its methods from evidence yet.
Case Resolution
A Modest Claim She Can Evidence
Back to Dana, in front of the committee. It wants a quick decision, and the budget is small. She asks to delay the start by three weeks, to finish the baseline. It postpones the benefit, but without a baseline, nobody could ever show the project worked. For member satisfaction she offers no percentage. She'll use the survey question that asks how easy the claim process was, as a proxy, and read it as a direction. She commits firmly to six days, but only to a direction for satisfaction. A rival proposal promising a precise percentage sounds more impressive. Her reasoning answers the opening question. A modest claim she can evidence beats an ambitious one she can't.
Key Takeaways
Alignment, Benefits and Discipline
To recap. Trace every project back to an objective, by asking so that what. Outputs enable outcomes, and outcomes yield benefits, but the team controls only the output. A baseline and a named owner turn a promised benefit into one you can check. And discipline makes delivery more predictable and finds problems earlier. It narrows the gap, but never removes it.
About Project Management at UPI Study
Project Management (Business 230) is a self-paced online course of 73 video lessons in 12 chapters, from starting and defining a project to planning, budgets, scheduling tools, proposals, contracts, execution, monitoring, closure, teams and certification. It carries a NCCRS credit recommendation for 3 semester credits.
Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Enroll now → Course details Download the syllabus All Business courses Every course with PRO →
Why take it here
Why students take Project Management with UPI Study
Where the credit goes
Universities that work with NCCRS
Project Management carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Thomas Edison State UniversitySigned partner
University of the PeopleSigned partner
Charter Oak State CollegeSigned partner
Strayer UniversitySigned partner
Columbia Southern UniversitySigned partner
Indiana TechSigned partner
Penn StateWorks with NCCRS
Southern New Hampshire UniversityWorks with NCCRS
SUNYWorks with NCCRS
+many more cooperating universitiesFind my college →Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.
FAQ
Questions students ask us
About Business Value and Strategic Benefits of Project Management
What is the difference between outputs, outcomes and benefits in a project?
What is benefits realization in project management?
How do you measure a tangible project benefit?
What are the stages of project management maturity?
About the Project Management course
How many college credits is Project Management?
How much does Project Management cost and what is included?
Which universities accept UPI Study credits?
How long does Project Management take?
How are the exams done?
How do my credits reach my college?
Ready for the full course? Earn 3 credits in Project Management.
73 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.
3 credits · NCCRSEnroll →