Think in Systems, Not Silos

A workstream can hit every milestone and still damage the project it belongs to. Most experienced project managers have seen some version of this. A supplier is chased hard to recover a date, a test phase is compressed to protect a launch, or a team is pulled across to fix one crisis while another quietly builds behind it. Each decision made sense where it was taken. The trouble appeared somewhere else, often weeks later, and usually in someone else's report.

Adopting a holistic view means judging project decisions by their effect on the whole system the project sits within, including the parts outside your immediate problem. The project manager treats scope, schedule, finance, resources, risk, stakeholders and governance as connected. The project itself is seen as one part of an organisation that has its own strategy, operations and constraints. In practice, this means tracing where a fix will land before you make it.

Why local fixes travel

The Eighth Edition sets out this principle in Section 3.3 of The Standard for Project Management, as one of six principles for project practice. Like the others, it is written as a guide for judgement. It does not tell you which document to produce. It asks you to build a habit of attention that holds up when a deadline is pressing.

That habit matters because project variables are coupled. Pulling a milestone forward usually draws on resources, and those resources were already committed somewhere else. Adding a reviewer to reduce quality risk lengthens the approval path, which puts pressure on a date the sponsor has already given to operations. A cheaper supplier may move cost out of the project budget and into running costs that the business carries for years after closure. None of these trade-offs is wrong in itself. The error is making one while watching a single variable.

The same coupling extends beyond the project boundary. Organisational structure creates silos almost by design. Functional teams own their targets, workstreams own their plans, and suppliers own their contracts. Each boundary is a place where a problem can be pushed across and made to look solved. Those boundaries usually exist for sound reasons, and a holistic view leaves them in place. It makes the project manager responsible for noticing what crosses them.

A cutover that reported green

Consider a fictional shared services transition. A retail group is moving accounts payable processing from four regional finance offices into a central service centre. Governance is predictive, with a stage gate tied to each region's cutover. The benefits case assumes the regional teams will be reduced once all four regions have moved.

The second region's cutover date is at risk. The receiving team has been trained on standard invoices but not yet on supplier exceptions, which make up a stubborn share of the volume. The workstream lead is under pressure to protect the stage gate. She moves the full workload on the planned date and marks the milestone complete. The migration dashboard shows the cutover as done. The post crates stacked in the aisle of the service centre tell a different story.

Within a fortnight, exception invoices are ageing. Several suppliers are paid late, and two put the retailer's account on stop, so stores start seeing missing deliveries. The procurement workstream had been renegotiating terms with those same suppliers, and it loses leverage. The regional team that was due to be released is asked to stay on and clear the backlog, so the saving in the benefits case slips by a quarter. By the workstream's own measures, everything went to plan.

A project manager applying a holistic view would have treated the cutover date as one input to a wider decision. Several practical questions were worth asking before the move:

• Where does exception work go if the receiving team cannot handle it yet?
• Who outside the project feels the effect first if payments slow?
• Which other workstream depends on supplier goodwill over the coming month?
• What does the benefits case assume about the timing of this cutover?

The answers might still have supported moving on the date, perhaps with the regional office keeping exceptions for a few more weeks. They might equally have supported a short, deliberate delay, taken through the stage gate with the sponsor's knowledge. Either choice would have been a decision about the whole. Neither would have hidden the cost in another team's queue.

Widening the frame without freezing the project

Systems thinking is sometimes misread as an instruction to analyse everything before acting. That would be its own failure, and a slow one. The skill is widening the frame in proportion to the decision. A small, reversible change inside one team needs little more than a moment's thought about its neighbours. A change that touches a baseline, a contract, an operational handover or a funded benefit deserves a deliberate look across the system.

A few habits make this manageable on a busy project. One is following the output of a decision to its next recipient, because most unintended effects show up one handoff downstream. Another is watching the measure nobody is reporting. A local target that improves often has a partner metric that quietly gets worse: speed against rework, purchase price against lifetime running cost, milestone dates against operational readiness. A third is asking what the operation will have to live with after the project team has gone, since that is where many project savings turn into organisational costs.

When a trade-off crosses someone else's authority, the holistic view becomes a governance question. A workstream lead cannot decide alone to spend the procurement team's supplier goodwill, or to defer a benefit the sponsor has committed to the board. Recognising that point, and taking the decision to the people who own the wider consequences, is part of applying the principle.

The development approach shapes where the principle does its work. In predictive delivery, integrated planning and change control are natural points to test a proposed change against its knock-on effects before a baseline moves. In adaptive delivery, the typical risk is a team optimising its own velocity while work piles up at an integration point, a testing queue or a release gate it does not own. Looking at end-to-end flow, and at the users who receive each increment, keeps the view wide. Hybrid environments carry the sharpest version of the problem. The interface between a fixed-milestone workstream and an iterative one is exactly where each side can assume the other is absorbing the uncertainty.

Reading the whole scenario

For a PMP® candidate, the relevant skill is recognising when a situation is wider than the symptom presented. The current exam uses scenario-based questions to test whether candidates can apply practice to realistic project situations. Many scenarios include details that point beyond the immediate problem, such as a dependent team, a regulatory milestone, an operational handover or a stakeholder who has not yet been told. The tempting answer often fixes the visible issue fastest. A stronger answer usually shows that the candidate has considered what else the action would affect, gathered the missing information and involved the people whose work or authority is touched.

This connects to a wider shift in how success is framed. The current Examination Content Outline aligns with thinking that measures project success by whether the work delivers worthwhile value and outcomes, not only by schedule, budget and scope. Holistic thinking is how that idea becomes practical, because value is usually created or lost at the joins between parts of the work. Omega's PMP® Exam Preparation works through situations of this kind, where the better response depends on noticing what sits just outside the immediate problem.

On real projects, the principle matters most when pressure narrows attention: a slipping date, a budget challenge, a difficult supplier, a sponsor asking for good news. Those are the moments to step back far enough to see who the next decision will reach. A project manager who does this consistently will still make trade-offs, and some will still disappoint someone. The costs, though, will be chosen, visible and owned, and they will not surface later in someone else's backlog.

Andre Malowney

Interested in going further?

Scenarios that test holistic judgement tend to bury the wider consequences in details that are easy to skim past. Structured preparation gives you repeated practice at spotting those details before you commit to a response.

The holistic view principle is set out in full in The Standard for Project Management, which is published within the PMBOK® Guide Eighth Edition.

Ad · Amazon affiliate link.

References

A007: The Standard for Project Management vs the PMBOK Guide
A035: Focus on Value: How Project Managers Make Better Trade-offs
A032: The PMI Mindset Explained: How PMP Expects You to Think
A037: Quality Is Designed In, Not Inspected In
A043: When Should a Project Manager Escalate?

PMP and PMBOK are registered marks of the Project Management Institute, Inc.