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
Visual Project Management

Visual Project Management

Simplifying Project Execution to Deliver On Time and On Budget
Projects stall in queues, not just bad plans. Learn to expose bottlenecks and get work moving.
by Mark J Woeppel 2015 292 pages
3.79
39 ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Fix project execution, not just the plan, to improve delivery and cost

The gap is execution. Woeppel argues that organizations have invested heavily in planning, training, and controls, yet projects still miss deadlines and budgets because little attention is paid to how work moves once execution begins. An independent survey cited in the book found more than 30 percent of capital projects over budget and more than 35 percent late. The proposed remedy is to focus on three execution failures: teams cannot see the whole situation, they mishandle uncertainty, and they lack a useful picture of resource capacity.

Results follow the work. In one engineering portfolio, applying the approach increased productivity by 25 percent in less than six months. The book’s central claim is practical: better delivery comes from changing how teams coordinate and complete tasks, not simply adding detail to the plan.

Analysis

The emphasis on execution shifts attention from documents to the operating system of a project: information, decisions, handoffs, and incentives. That is a useful systems perspective because outcomes often emerge from interactions among people rather than from any one person’s competence. Still, reported case results do not by themselves establish that the method caused every improvement. A careful adopter should define baseline measures, track comparable projects, and distinguish the effects of the process from changes in scope, staffing, or demand.

Make the work visible so the team can act on the same reality

Give the team a map. A Visual Project Board, or VPB, displays work, status, ownership, and obstacles in a shared format. Its purpose is not decoration or another reporting layer. It lets contributors see how their tasks connect to the project’s goal and helps managers spot stalled work before a deadline makes the problem obvious. Short, frequent meetings around the board focus on what must happen next, who owns it, and what is blocking progress.

Visibility improves response. A GPS software group used a shared board and brief daily discussions to expose bottlenecks and coordinate action. In two months, its weekly issue-resolution rate rose from 7.0 to 11.3, while a separate measure of resolution speed increased from 0.5 to 5.3 per week. The board also made problems visible without turning every discussion into a search for someone to blame.

Analysis

A shared visual can function as a coordination technology: it reduces the time people spend reconciling competing accounts of reality. That connects to distributed cognition, the idea that groups think through people and external tools together, rather than relying on individual memory alone. The board is valuable only if its data is current and its meetings lead to decisions. Otherwise it becomes a theater of transparency, where everyone can see the problem but nobody has authority to remove it.

Align measures and priorities with finishing the project, not staying busy

Local efficiency can hurt. Functional Alignment means organizing the team around the project’s deliverables while recognizing cost and schedule as essential conditions. Departmental targets can pull in another direction: a resource manager may aim to keep staff fully occupied, while a controller protects budget limits. Those aims can be reasonable individually yet slow the whole project. Woeppel recommends tracking task completion speed, rework, and how often progress is blocked, then using the information to correct conflicting behavior.

Choose one priority signal. When several systems, managers, and customers assign different urgencies, people switch tasks or work out of sequence. An airframe manufacturer replaced competing labels such as “hot” and “do it now” with a transparent priority system tied to customer delivery. Past-due tasks fell 40 percent in the first week. The principle is to make the order of work understandable and consistently governed across the portfolio.

Analysis

This is a classic distinction between optimizing a component and optimizing the system. In operations research, local utilization can rise while total throughput falls, especially when work is released faster than the constrained steps can process it. The book usefully treats metrics as behavioral signals, not neutral descriptions. Yet a single project-wide goal should not erase legitimate constraints such as safety, quality, or contractual obligations. The practical task is to make those conditions explicit, then avoid rewarding activity that does not advance a deliverable.

Cap work in progress and start only when the task is ready

More starts can mean fewer finishes. Work in progress, or WIP, is work already released into a process but not yet completed. Too much WIP encourages task switching, queues, and confusion about what matters. Each switch requires people to reconstruct where they left off, and delays to one task can leave dependent work waiting. Little’s law links the amount of work in a system, its completion rate, and the time work spends there: if arrivals exceed completions, waiting time grows.

Use a Clean Start. This is a rule that work should not begin until the necessary inputs, information, and resources are available to finish it. A Malaysian equipment maker used readiness checklists for design and assembly, clarifying customer information and critical parts before work started. Production rose from 25 to 40 machines monthly, with little increase in spending and less inventory. The book also suggests temporarily freezing a portion of active projects to regain control.

Analysis

The queueing logic explains why visible busyness can coexist with slow delivery. Reducing WIP limits the number of competing claims on attention and makes delays easier to diagnose. Clean Start also moves coordination upstream, where missing requirements are cheaper to address than after partial work has accumulated. A freeze is not a universal cure: stopping work can carry contractual, safety, or morale costs. It should be selective, based on portfolio priorities, and paired with clear criteria for restarting.

Separate task work from contingency, then manage risk at project level

Variation is normal; surprises differ. Common-cause variation is the everyday fluctuation built into a process, while special-cause variation comes from a distinct event, such as a road closure or a supplier failure. Treating every delay as exceptional encourages frantic replanning; treating a serious event as routine can leave the project exposed. Because estimates often include personal safety allowances, the actual work time is obscured and contingency becomes scattered across tasks.

Let the project own safety. In Schedule Risk Management, task estimates focus on likely work duration, while contingency is gathered into a project buffer that protects delivery. Team members report time remaining to finish a task rather than a vague completion percentage. A Schedule Risk Ratio compares remaining buffer with remaining critical-path work, helping teams see when a project needs attention. The buffer is expected to be consumed as work proceeds; its trend guides early action rather than blame.

Analysis

Pooling contingency makes risk legible and reduces the incentive to protect each individual estimate at the expense of the shared deadline. This resembles portfolio approaches to insurance: shared reserves can absorb idiosyncratic setbacks more efficiently than many isolated cushions. The method depends, however, on credible progress updates and a realistic understanding of dependencies. A ratio is an indicator, not a forecast with magical precision. Teams should use it to prompt investigation and recovery planning, not as a substitute for technical judgment.

Protect the bottleneck and promise dates against real capacity

The constraint sets the pace. A bottleneck is the resource whose workload is high relative to its available capacity, creating a queue and threatening the schedule. It need not be the slowest resource. Bottleneck Management identifies current and future overloads, then responds by changing sequence, removing unnecessary steps, shifting work, adding support, or finding an alternate source. The book favors moving people to the work that needs attention instead of releasing more work simply to keep everyone occupied.

Check capacity before promising. Delivery Promising evaluates how proposed work fits with existing projects and critical resources before a date is committed. One producer of engineered structures found its critical component supply would fall short despite short-term productivity improvements. It identified alternate suppliers, shifted production, and managed the constrained operation closely, preventing the component from delaying fabrication. A credible promise may require staging a project’s start rather than launching it immediately.

Analysis

The constraint lens helps leaders focus scarce attention where an intervention can change total throughput. It also makes the cost of a new commitment visible across a portfolio rather than hiding it inside one project. The choice of constraint is strategic: a scarce specialist may be more important than a machine that is easy to replace. Because constraints can move, the analysis must be repeated. A bottleneck that is relieved today may simply expose the next limiting resource tomorrow.

Give remote teams and critical suppliers one shared view of progress

Distance magnifies coordination gaps. Remote teams face delayed messages, limited meeting time, and fewer informal conversations. ViewPoint extends shared boards, common priorities, and structured collaboration across locations, with meeting frequency matched to task duration and risk. A technology manufacturer coordinated parts suppliers and subcontractors across several countries using an electronic board and virtual meetings. The team reported a fivefold increase in capacity, fourfold output, and a 23 percent reduction in lead time.

Integrate suppliers selectively. Subcontractor Integration focuses on external partners whose delays threaten the critical chain. It distinguishes suppliers providing specific items from subcontractors performing multiple, custom deliverables. Teams assess delivery capability, share relevant workflow information, and align contract payments with meaningful schedule progress. Earned value can show that spending or activity has advanced without proving that a critical deliverable is closer to completion. For high-risk partners, execution support and early risk checks can reveal trouble before it reaches the project deadline.

Analysis

The approach treats organizational boundaries as part of the workflow rather than as an excuse for poor visibility. Shared artifacts can reduce the coordination burden of geography, but trust and incentives remain decisive: a supplier may have little reason to expose problems if disclosure threatens payment or reputation. Contract design can help, though outcome-based incentives must not encourage corner-cutting. Schedule performance should be balanced with quality and safety, and information sharing should be reciprocal enough to feel like joint problem-solving rather than surveillance.

Build capacity plans around the portfolio’s scarce skills and future demand

Look beyond today’s workload. Capacity Management reconciles expected resource demand across current and prospective projects with the people, skills, equipment, and supplier capacity available. It uses a rolling planning horizon to identify conflicts early enough to hire, train, outsource, or change project timing. The process depends on shared resource definitions and consistent estimates, but future forecasts need only be precise enough to support the decision at hand.

Choose where capacity is tight. The book recommends selecting a strategic constraint and maintaining enough protective capacity elsewhere to keep it supplied and absorb variation. A semiconductor company, for example, centered its business on specialized design work and used external manufacturers for production. A different organization created a three-year component-demand forecast, matched it against supplier profiles, and reviewed supply and demand monthly. This shifted management from last-minute procurement scrambles to planned capacity decisions.

Analysis

Capacity planning connects project delivery to strategy: decisions about scarce skills determine which opportunities an organization can pursue and when. The deliberate reserve capacity described here can appear inefficient under utilization-focused accounting, even though it may improve resilience and reduce costly recovery work. The tradeoff should be evaluated across total system cost, not only idle hours. Long-range forecasts are also fragile, so a rolling plan should preserve options and be revised as bids, demand, and project probabilities change.

Start with control of work. The Project Execution Maturity Model, or PEMM, describes three stages: Basic Collaboration, Improved Coordination, and Integrated Planning and Execution. The first makes current work visible, aligned, prioritized, and limited. The second extends coordination to remote teams, capacity bottlenecks, realistic commitments, and schedule risk. The third connects probabilistic plans, resource strategy, and supplier performance to ongoing execution. Each stage gives the organization a wider time horizon and more integrated decisions.

Adapt the sequence to need. Woeppel describes a typical Basic Collaboration implementation taking about 12 weeks for an organization of roughly 50 people, followed by another roughly 12 weeks for Improved Coordination. Troubled, complex projects may need collaboration and probabilistic planning to begin in parallel, rather than waiting for a perfect maturity sequence. The goal is not to install a rigid method. It is to make planning responsive to what execution reveals, while measuring behaviors and results so changes can be refined.

Analysis

The staged model is compelling because it avoids asking teams to adopt sophisticated forecasting before they can reliably see the work already underway. In change management, visible early wins can create credibility for more demanding reforms. Yet maturity models risk becoming scorekeeping exercises, where organizations optimize their rating rather than their delivery system. The strongest use is diagnostic: identify the behavior causing friction, test a targeted change, and measure whether the bottleneck or delay actually improves. A sequence should guide learning, not replace it.

Analysis

The book’s central contribution is a shift in the unit of analysis. Instead of treating project failure primarily as inaccurate estimation or weak managerial control, it treats delivery as a flow problem shaped by visibility, priorities, variation, capacity, and handoffs. That diagnosis makes familiar symptoms, late tasks, overloaded specialists, firefighting, and strained meetings, legible as connected consequences rather than isolated personnel failures.

Its strongest practical insight is the insistence that starting work is not the same as making progress. Limiting WIP, clarifying priorities, and requiring ready inputs address the mechanics of queues and task switching. Visual boards and short collaboration routines then give teams a common basis for action. The later practices extend that logic from a local team to a portfolio and its suppliers. Together, they form a coherent progression from seeing work to controlling flow, anticipating risk, and planning capacity.

The model also has limits worth keeping in view. The book reports striking improvements from consulting engagements, but the cases are not controlled comparisons, and several claims rely on studies cited by the author or his firm. Outcomes may depend on leadership support, project type, baseline conditions, and how faithfully the practices are implemented. The results are persuasive as evidence of possibility, not proof that one method will reproduce the same gains everywhere.

The deeper organizational tension is between local incentives and shared delivery. A board cannot resolve that tension alone. Leaders must change what gets measured, who can set priorities, and how teams are protected from incompatible demands. Nor should speed displace safety, quality, or legitimate customer obligations. The method is most valuable as a disciplined operating system: expose work, make tradeoffs explicit, learn from variation, and revise the plan when reality changes. Its promise is not certainty. It is earlier recognition and more coordinated response.

Summary in 30 Seconds
Project delivery depends on how work flows during execution, not just on the quality of the initial plan. Shared visual boards reveal ownership, status, and obstacles; limiting active work and starting tasks only when inputs are ready reduces queues and switching. Track task completion, rework, and blocked work instead of busyness. Set realistic commitments around constrained capacity, pool schedule contingency at the project level, and coordinate suppliers through shared priorities.
Contains spoilers

Last updated:

Report Issue

Review Summary

3.79 out of 5
Average of 39 ratings from Goodreads and Amazon.

Visual Project Management receives mixed reviews. Many praise its robust project management system and focus on execution, highlighting techniques for on-time, on-budget delivery. Readers appreciate insights on team productivity, process enhancement, and cost reduction. Some find the title misleading, expecting more visual content. Critics note the book's text-heavy nature and limited visual elements. Overall, reviewers value the practical strategies for effective project management, though opinions vary on readability and visual content. The book is recommended for project managers seeking to improve delivery processes and overcome common project pitfalls.

Your rating:
4.34
71 ratings
Want to read the full book?

Glossary

ViewPoint

Visual execution method

ViewPoint is Mark Woeppel’s project execution methodology for improving delivery by controlling work, coordinating action, and releasing capacity. It uses shared visibility, consistent priorities, work-in-progress limits, risk management, and resource planning. The method is intended to complement existing project management practices and software rather than replace all planning or control systems.

Project Execution Maturity Model

Three-stage execution framework

The Project Execution Maturity Model, or PEMM, organizes execution capability into Basic Collaboration, Improved Coordination, and Integrated Planning and Execution. Each stage adds a wider scope and planning horizon, from managing visible current work to coordinating dates, resources, uncertainty, and suppliers across a portfolio. It is used to assess practices and guide improvement.

Visual Project Board

Shared work-status map

A Visual Project Board, also called a Visual Portfolio Board, displays a project’s work, status, ownership, and obstacles in a format the team can inspect together. It can be physical or software-based. Its purpose is to support shared situational awareness, expose bottlenecks, clarify accountability, and help teams decide what action will move work forward.

Clean Start

Readiness check before work

Clean Start is a process that prevents a task from entering active work until the information, inputs, materials, and other essential conditions needed to complete it are available. Checklists and handoff criteria make readiness explicit. The method aims to reduce stalled work, rework, premature task switching, and delays caused by incomplete requirements.

Schedule Risk Ratio

Buffer-based risk indicator

The Schedule Risk Ratio compares the remaining project buffer with the remaining work on the critical path to indicate schedule risk and help prioritize action. In Woeppel’s method, the ratio supports a shared early-warning system across projects. It should prompt investigation and recovery planning, rather than be treated as an exact prediction of the final delivery date.

Probabilistic Planning

Planning with outcome ranges

Probabilistic Planning estimates a range of possible project outcomes and their likelihoods instead of assuming one certain completion date. It considers task-duration variation, identified risks, and resource availability, then incorporates buffers into an execution schedule. The resulting analysis supports commitments suited to an organization’s tolerance for risk and guides action as new information emerges.

Bottleneck Management

Manage the pacing resource

Bottleneck Management identifies resources whose workload is high relative to their available capacity, creating queues and schedule risk. It aims to detect both current and future overloads, then improve flow through changes such as reallocating people, changing work sequence, removing steps, or adding capacity. The bottleneck is the resource limiting overall project progress, not necessarily the slowest resource.

Little’s law

Work, throughput, and waiting

Little’s law is a relationship from queuing theory among the amount of work in a system, its average completion rate, and the average time work spends in that system. In project execution, it helps explain why releasing work faster than teams can complete it increases queues and lead time. It provides a reason to manage work in progress.

About the Author

Mark J. Woeppel is an experienced author and expert in project management. He has written three books on the subject, with Visual Project Management being his third publication. Woeppel's work is based on extensive research and his considerable experience in the field. He focuses on practical, real-world insights to help project managers improve their skills and deliver projects successfully. Woeppel's approach emphasizes the importance of team productivity, efficient delivery processes, and cost management. His writing style is described as informative and helpful, providing readers with simplified techniques for managing projects throughout their lifecycle. Woeppel's expertise is particularly valued in addressing common project management challenges and offering strategies for timely and budget-conscious project delivery.

Download PDF

To save this Visual Project Management summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.33 MB     Pages: 16

Download EPUB

To read this Visual Project Management 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.40 MB     Pages: 20
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...