Start free trial
Trending New Genres Authors
EnglishEnglish
EspañolSpanish
简体中文Chinese
繁體中文Chinese (Traditional)
FrançaisFrench
DeutschGerman
日本語Japanese
PortuguêsPortuguese
ItalianoItalian
한국어Korean
РусскийRussian
NederlandsDutch
العربيةArabic
PolskiPolish
हिन्दीHindi
Tiếng ViệtVietnamese
SvenskaSwedish
ΕλληνικάGreek
TürkçeTurkish
ไทยThai
ČeštinaCzech
RomânăRomanian
MagyarHungarian
УкраїнськаUkrainian
IndonesiaIndonesian
DanskDanish
SuomiFinnish
БългарскиBulgarian
עבריתHebrew
NorskNorwegian
HrvatskiCroatian
CatalàCatalan
SlovenčinaSlovak
LietuviųLithuanian
SlovenščinaSlovenian
СрпскиSerbian
EestiEstonian
LatviešuLatvian
فارسیPersian
മലയാളംMalayalam
தமிழ்Tamil
اردوUrdu
Searching...
SoBrief
Maximizing Project Value

Maximizing Project Value

A Project Manager's Guide
Turn project delivery into measurable business returns, from the investment case through adoption.
by John C. Goodpasture 2013 323 pages
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Judge a project by what the business gains, not what the team ships

Outputs are only potential value. Project value is what a team delivers; business value is what the organization gains when those deliverables are put to use. The two can diverge: a development team may meet its scope, cost, and schedule targets while the product fails to find customers. The book points to New Coke as a project that reached production but failed in the market. By contrast, the delayed Boeing 787 still had strong customer demand, showing that schedule and budget performance do not alone settle a project’s worth.

Balance both scorecards. The project manager is accountable for valuable deliverables, while the sponsor must connect them to organizational results. A public agency might prioritize mission outcomes; a company might emphasize financial returns. The aim is the best value available for the investment and acceptable risk, not simply the cheapest delivery.

Analysis

This distinction resembles the difference between building a tool and changing a system with it. The organization must supply complementary assets, such as trained staff, customer access, and operational processes, or a technically sound product can sit unused. That makes value a joint achievement rather than a project team’s solo product. The challenge is measurement: outcomes such as public trust or employee capability may matter greatly without having a clean monetary proxy. Scorecards should make those priorities visible without pretending every benefit is equally measurable.

Trace every project back to an opportunity and a strategic goal

Strategy gives work its reason. Projects are not valuable simply because they are completed. Their value comes from addressing an opportunity that supports organizational goals. Goodpasture describes a flow from opportunity to goals, strategy, operating concepts, programs, and finally a project charter. The project should also change how the organization operates, so results can feed back into the goals and scorecard.

Strategy is more than efficiency. Improving an existing process can help, but it is not the same as choosing a distinctive direction. The book uses digital photography to show how better execution of film-camera production could not protect manufacturers from a replacement technology. Strategic planning should be revisited as markets, mission, regulation, and competitors change. Project plans, in turn, should be detailed only as far ahead as conditions remain stable.

Analysis

The chain from opportunity to project is a practical defense against activity masquerading as progress. It also reflects systems thinking: a local intervention matters only through its effects on the larger system. Feedback is essential because the original strategy rests on assumptions about a changing world. Yet planning rituals can become theater if scorecards reward the existence of plans rather than the quality of choices. The useful test is whether new evidence can change priorities, including whether a project should stop, not merely whether it remains on its original trajectory.

Make the business case test assumptions, not merely sell the project

A case is a decision instrument. A business case should explain the opportunity, expected scope and investment, risks, operating plan, and the decision being requested. It belongs to the sponsor, but must make sense to executives, specialists, users, and other affected groups. A reference class, meaning a set of comparable past projects, can anchor estimates in experience, provided differences in context are examined rather than ignored.

Compare futures carefully. The with-without principle contrasts likely business conditions with and without the project. In the book’s payroll example, a $500,000 system is associated with lower errors, higher user satisfaction, and $10,000 less monthly cash outflow. Those changes support a case, but do not prove the system caused every improvement. For uncertain or contested problems, a small, bounded project can test one workable piece before larger commitments are made.

Analysis

The case is strongest when it behaves like a hypothesis that can be challenged, not a prosecution brief for a favored investment. Comparing with and without the intervention is close to counterfactual reasoning in program evaluation: what would probably have happened otherwise? That question can expose benefits that would occur anyway, as well as costs hidden outside the project budget. The comparison is still vulnerable to forecasting error and selection bias. A useful case therefore records assumptions, ranges, and conditions that would trigger revision, rather than presenting a single confident forecast.

Negotiate scope where sponsor ambition meets delivery reality

The project balance sheet is a way to compare the sponsor’s top-down expectations with the project manager’s bottom-up estimate of capacity, cost, and time. The gap between them is risk, not a reason to quietly promise the impossible. Sponsors tend to see a longer horizon and may be more optimistic; project managers see near-term technical and resource constraints and may be more cautious.

Use scope as common ground. Features and outcomes are usually easier for both parties to discuss than abstract estimates of feasibility. The project manager can negotiate which requirements matter most, what can wait, and what resources or milestones must change. After negotiation, any remaining gap is a known residual risk to manage. The sponsor owns the business case; the project manager owns delivery estimates and the risk assigned to the project.

Analysis

The balance-sheet metaphor makes accountability visible: optimism does not disappear when a sponsor transfers a deadline or budget to a team. It becomes somebody’s risk. Negotiation over scope helps convert a vague conflict into choices that can be examined. This resembles boundary-object practices in organizational research, where a shared artifact lets groups with different expertise coordinate without pretending to agree on everything. The metaphor has limits, however. It can imply that all interests can be balanced neatly, while legal duties, power differences, or non-negotiable mission needs may require explicit authority rather than a symmetrical bargain.

Treat requirements as imperfect samples, then release value in useful slices

Requirements translate intent into work. They describe needs such as features, functions, performance, quality, and compliance. A business vision cannot be copied perfectly into technical specifications: analysts sample it through interviews, scenarios, modeling, and prototypes, leaving gaps that must be checked. In the book’s retail example, a broad promise to accept returns in stores must be worked through into distinct cases, such as whether a customer has a receipt and whether the return becomes a refund or store credit.

Plan around learning. Deliverables can be grouped into releases and sequenced by urgency, importance, technical dependencies, and customer need. A roof cannot precede the walls, but among feasible options, business value should guide the order. With agile work, detailed requirements can evolve while investment and key milestones remain bounded. Review each release and adjust the backlog when evidence changes what is useful.

Analysis

The sampling idea is a useful antidote to the fantasy that a long specification has eliminated uncertainty. In complex work, requirements are partly discovered through use, so prototypes and staged releases can produce information as well as functionality. This is also a way to limit the cost of being wrong. Still, flexibility is not automatically wise: frequent releases can burden users, operations, or training teams. The right increment is not the smallest possible one, but a slice that users can absorb and that provides enough evidence to inform the next decision.

Measure completed value, not activity or money spent

Earned value tracks planned work completed. Planned value is the budget assigned to work; earned value is the planned value credited when that work is accomplished; actual cost records what was spent. Comparing them shows whether spending produced the expected progress. In the book’s example, a team spends $20,000 against $25,000 of planned work but earns only $10,000 of value. A report focused on underspending could look favorable, while the earned-value comparison shows poor performance.

Choose a measure that fits the work. Traditional earned value suits defined scope and budgeted work packages. Agile teams can update planned value as scope is elaborated and credit usable work by iteration. Where cost data is unavailable, a time-centric approach tracks planned and completed task starts and finishes. In every case, unfinished work should not be confused with delivered value.

Analysis

The key accounting insight is that cost is an input, not evidence of accomplishment. This is closely related to the distinction between leading indicators, which signal activity, and outcome measures, which show what changed. A well-designed measure can reveal trouble early enough to act, but the numbers remain conditional on rules for what counts as complete. If teams optimize the metric rather than the mission, they can produce impressive-looking reports and weak results. Measurement should therefore support informed judgment, not replace it.

Keep adoption and operations inside the project’s value plan

Delivery is not the finish line. Project outputs have potential business value until users adopt them and the organization applies them in daily operations. The book assigns this post-project work to an attainment manager, usually from the business, who defines measures, prepares the organization, and tracks results. The project manager can help by planning business preparation, such as training, pilots, communications, and rollout rehearsals.

Measure the intended outcome. If a warehouse system aims to improve customer distribution, useful indicators might include fewer incorrect shipments or higher customer satisfaction, not merely system installation. Some benefits, like reduced direct expense, are easier to attribute than softer effects such as morale or productivity. The book’s examples of failed market products show why delivery success cannot guarantee business success. Adoption plans should anticipate users who resist, need support, or leave rather than adopt.

Analysis

This is a strong reminder that implementation is a social process, not just a technical event. Diffusion research likewise emphasizes that people adopt innovations at different speeds, shaped by experience, communication, and trusted peers. Pilots and internal ambassadors can make those dynamics observable before a full rollout. The harder question is who owns outcomes when they depend on operational managers as well as the project team. Clear accountability helps, but incentives should avoid pressuring managers to report favorable indicators while ignoring inconvenient effects on users or customers.

Build a real team, not just a roster of assigned specialists

A team requires mutual commitment. A group may have roles and a shared purpose, but a team depends on members collaborating toward a goal that requires their collective contribution. The book highlights trust, accountability, clarity, and shared responsibility as important conditions. Members should understand their authority and duties, and unresolved competition for dominance can undermine the work even when everyone is technically capable.

Location changes the work. Co-located colleagues can exchange information through brief conversation and observation. Virtual teams gain access to people across distance and time zones, but face slower trust-building, asynchronous work, and more communication boundaries. They need deliberate protocols for sharing files, decisions, and culture. Strong individual talent still matters, but innovation often depends on whether execution specialists and idea generators can work together rather than compete for credit.

Analysis

The distinction between a team and a staffing list is valuable because collaboration is an emergent property of relationships, not a label on an organization chart. Research on distributed work adds an important nuance: proximity can support informal coordination, but it does not guarantee psychological safety or good decisions. Remote teams can compensate through explicit documentation and predictable interaction, although that work has a cost. Managers should diagnose the task before prescribing location. Creative, interdependent work may benefit from richer contact; independent tasks may not justify the overhead of co-location.

Challenge anchors and familiar precedents before trusting project forecasts

Judgment bends estimates. An anchor is an initial number or assumption that influences later estimates, even when evidence should move the result. If a sponsor suggests a project should cost $1 million, that figure can shape planning before the team has assessed the work. Representative bias carries patterns from one project or domain into another without checking whether the conditions match. Availability bias favors the example easiest to recall, which may not be the most relevant.

Check how risks combine. If four independent project conditions each have an 85 percent chance of success and all must succeed, the combined chance is about 52 percent, not 85 percent. This conjunctive risk is easy to underestimate. Historical benchmarks help only when their context is comparable. Estimates should be adjusted for the present project, and decisionmakers should distinguish calibrated probability from an ungrounded guess.

Analysis

These biases are not merely personal flaws; they are predictable features of human judgment under uncertainty. Forecasting research has found that base rates and comparisons with similar cases can improve estimates, especially when intuitive stories feel more compelling than data. But reference classes can mislead when projects are selected or described to make them look comparable. The discipline is to ask what differs, not just what resembles the case at hand. Explicitly recording an estimate before discussion can also reveal how strongly a powerful person’s anchor has shifted the group.

Compare long-term cash flows only after time and risk are priced

Money changes value over time. Net present value converts future inflows and outflows into present terms using a discount rate. In the book’s example, a $500 investment followed by two annual benefits of $1,000 has a positive NPV at a 10 percent discount rate, but those future benefits are worth less than their face amounts today. Economic value add asks whether earnings exceed the opportunity cost of the capital invested. Expected monetary value combines possible outcomes according to their probabilities.

Keep the adjustments straight. NPV addresses timing and discounting; expected monetary value addresses uncertain outcomes. Applying the same risk in both calculations can count it twice. Probability estimates should be calibrated through comparable results, expert consensus, or simulation where possible. If probabilities are simply guesses, a precise-looking expected value can create false confidence rather than better investment decisions.

Analysis

These measures answer different questions that are often blurred together: when money arrives, whether capital could earn more elsewhere, and what uncertain outcomes average to. Separating them improves debate because a project can be attractive on one dimension and poor on another. Yet an average payoff can hide a catastrophic downside or a range of outcomes that investors cannot tolerate. Decisionmakers should pair summary metrics with scenario analysis and explicit affordability limits. Financial precision is useful when assumptions are transparent, not when decimals disguise uncertainty.

Optimize the portfolio as a system, and model rivals’ incentives

Portfolio value exceeds isolated project scores. A portfolio manager distributes scope and resources across projects, managing dependencies, timing, and shared risks. Coherence aligns project outcomes with strategy; cohesion helps components hold together; coupling describes how strongly one project affects another; diversification spreads risk across projects. Redundancy can protect the whole portfolio from a single failure, though it adds cost and coordination.

Game theory tests interdependence. It examines how one party’s payoff changes with another party’s choices. In a buyer-seller negotiation, the buyer may prefer speed while the seller prefers price. A payoff matrix can reveal whether a stable compromise exists, where neither side benefits by changing its choice alone. Such analysis can expose options that adversarial communication might otherwise hide, but its conclusions depend on the accuracy of assumed preferences and payoffs.

Analysis

The portfolio perspective counters a common organizational trap: rewarding every project for local efficiency while the combined system misses its purpose. Network thinking helps identify where dependencies create leverage or fragility. Game theory adds a structured way to consider the other party’s incentives, rather than assuming cooperation or treating disagreement as irrational. Its value is diagnostic, not prophetic. Real actors may have incomplete information, shifting goals, or relationships that alter their preferences. A payoff matrix is best used to surface assumptions and explore alternatives, not to claim certainty about human behavior.

Analysis

The book’s central achievement is to treat project management as a value conversion problem rather than a delivery-control problem. It follows the investment from opportunity and strategy, through requirements and execution, into adoption and business results. That lifecycle view corrects a familiar bias: organizations often evaluate the team on a completed product while leaving the business consequences to emerge without an owner. The distinction between project value and business value is therefore more than vocabulary. It allocates responsibility across people with different horizons and incentives.

The project balance sheet is the most useful organizing metaphor because it makes the conflict between sponsor expectations and delivery capacity discussable. It also clarifies that unspoken gaps are risks. But its apparent symmetry can mask power asymmetries: a project manager may be asked to accept risk without authority to change resources, scope, or policy. Governance must ensure that responsibility follows control, and that sponsors retain accountability for the business assumptions they set.

The book’s strongest operational advice is to learn through the work. Reference classes challenge optimistic estimates; staged releases reduce exposure to changing requirements; earned value distinguishes accomplishment from spending; adoption measures connect outputs to actual use. These methods form a feedback system. Their quality depends on honest baselines and an ability to act on bad news. A dashboard that cannot alter priorities is decoration.

The approach is less complete where value is contested or difficult to quantify. Mission, equity, trust, and user burden may not translate cleanly into cash or a single KPI. Quantification can discipline debate, but it can also privilege what is easiest to count. The answer is not to abandon measurement, but to pair financial metrics with explicit nonfinancial outcomes and disclose uncertainty. Overall, the book offers a coherent managerial ethic: optimize for organizational benefit, while making trade-offs, risk ownership, and post-project obligations visible.

Summary in 30 Seconds
A completed deliverable creates only potential value; benefits depend on adoption and use in operations. Link projects to strategic opportunities, test business-case assumptions against comparable work, and adjust scope as evidence changes. Track completed work rather than money spent: a team spending $20,000 on $25,000 of planned work may have earned only $10,000. Forecasts need context, and four independent 85% success chances combine to about 52% when all must succeed.
Contains spoilers

Last updated:

Report Issue
Want to read the full book?

Glossary

Project value

Worth of project deliverables

The worth created by a project’s outputs during project performance, considered in relation to the resources invested and the needs the outputs are meant to serve. It is distinct from business value: deliverables can be completed successfully yet produce little benefit if the organization does not put them to effective use.

Business value

Worth gained by the organization

The improvement an organization receives when project deliverables are applied to its operations, mission, customers, or other goals. It may be measured financially or through other scorecard outcomes. Business value is usually realized over a longer period than the project itself, and depends on adoption and operational use.

Best value

Most worthwhile affordable outcome

The most valuable combination of outcomes achievable for the investment, constraints, and level of risk acceptable to the organization. Best value does not automatically mean the lowest cost or the largest financial return. It depends on the organization’s mission and scorecard priorities, and may require trade-offs among scope, performance, time, and resources.

Project balance sheet

Map of expectations, capacity, and risk

A management tool comparing the sponsor’s expectations, investment, constraints, and desired outcomes with the project manager’s estimates of delivery capacity and capability. The imbalance between the two sides represents risk. The parties use scope and priorities to negotiate the gap, then assign ownership to remaining risks.

With-without principle

Compare futures with and without

A method for assessing a project’s likely effects by comparing the expected business situation after doing the project with the expected situation if it is not done. The comparison identifies relevant differences, including benefits that may be difficult to monetize. It does not, by itself, prove that the project directly caused those differences.

Wicked problem

Problem without agreed definition

A situation in which stakeholders disagree about what the problem is, what counts as a solution, or which values should take priority. Constraints and consequences may change as the situation is examined, and no answer satisfies everyone. A project can address a limited, agreed part of the situation without resolving the whole problem.

Reference class

Set of comparable prior projects

A group of completed, canceled, or deferred projects used to inform estimates for a new proposal. Comparisons can consider scope, method, environment, customers, staff, and technology. Because context differs, historical results should be adjusted carefully and should not be treated as automatically predictive.

Earned value

Budgeted value of completed work

A measure of planned work that has actually been accomplished. Planned value is the budget assigned to work, while earned value is the planned value credited for completed work; actual cost records spending. Comparing these measures helps distinguish progress from expenditure and supports forecasts of project performance.

Value attainment

Business benefits realized from outputs

The realization of business outcomes after project deliverables are adopted and used. It may include revenue, cost reductions, mission results, customer satisfaction, or other scorecard measures. Attainment often requires preparation, training, change management, operational ownership, and tracking beyond the project’s final delivery milestone.

Expected monetary value

Probability-weighted monetary average

A single monetary estimate calculated by multiplying each possible outcome by its probability and summing the results. It represents the probability-weighted average of uncertain outcomes and can support comparisons. It does not show the full range of outcomes, and its usefulness depends on credible probability estimates.

Nash equilibrium

Stable set of mutual choices

An outcome in a strategic situation where no participant can improve their payoff by changing their choice alone, given the other participants’ choices. Such an outcome can be stable even if it is not the best possible joint outcome. It depends on assumptions about preferences, available options, and payoffs.

Coherence, cohesion, coupling, diversification

Portfolio design and risk properties

Four system properties used to reason about portfolios. Coherence aligns project outcomes and timing; cohesion helps components remain connected under stress; coupling describes how strongly changes in one component affect another; diversification distributes scope and risk. Each can improve portfolio performance, but choices involve trade-offs in cost, coordination, and resilience.

Download PDF

To save this Maximizing Project Value summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.37 MB     Pages: 17

Download EPUB

To read this Maximizing Project Value summary on your e-reader device or app, download the free EPUB. The .epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.
Download EPUB
File size: 1.43 MB     Pages: 23
Want to read the full book?
Follow
Listen
Home
Swipe
Library
Get App
Try Full Access for 3 Days
Listen, bookmark, and more
Compare Features Free Pro
📖 Read Summaries
Read unlimited summaries. Free users get 3 per month
🎧 Listen to Summaries
Listen to unlimited summaries in 40 languages
—
❤️ Unlimited Bookmarks
Free users are limited to 4
—
📜 Unlimited History
Free users are limited to 4
—
📥 Unlimited Downloads
Free users are limited to 1
—
Risk-Free Timeline
Today: Get Instant Access
Listen to full summaries of 26,000+ books. That's 12,000+ hours of audio!
Day 2: Trial Reminder
We'll send you a notification that your trial is ending soon.
Day 3: Your subscription begins
You'll be charged on Nov 24,
cancel anytime before.
Consume 2.8× More Books
2.8× more books Listening Reading
Our users love us
600,000+ readers
Trustpilot Rating
TrustPilot
4.6 Excellent
This site is a total game-changer. I've been flying through book summaries like never before. Highly, highly recommend.
— Dave G
Worth my money and time, and really well made. I've never seen this quality of summaries on other websites. Very helpful!
— Em
Highly recommended!! Fantastic service. Perfect for those that want a little more than a teaser but not all the intricate details of a full audio book.
— Greg M
Save 62%
Yearly
$119.88 $44.99/year/yr
$3.75/mo
Monthly
$9.99/mo
Start a 3-Day Free Trial
3 days free, then $44.99/year. Cancel anytime.
Unlock a world of fiction & nonfiction books
26,000+ books for the price of 2 books
Read any book in 10 minutes
Discover new books like Tinder
Request any book if it's not summarized
Read more books than anyone you know
#1 app for book lovers
Lifelike & immersive summaries
30-day money-back guarantee
Download summaries in EPUBs or PDFs
Cancel anytime in a few clicks

Why one summary?

Scanner
Find a barcode to scan

⭐
⭐
⭐
We have a special gift for you
Open
38% off
DISCOUNT FOR YOU
⭐
⭐
⭐
$79.99
$49.99/year
Only $4.16 per month
Continue
2 taps to start, super easy to cancel
Settings
General
Widget
Loading...