Chronic Unease for Project Leaders Staying Alert When Projects Look Healthy
A project can look healthy right up to the week it starts to fail.
The dashboard is green. The critical path is under control. The forecast at completion is holding. The contractor reports good progress. Safety numbers are clean. Quality issues are being closed. Senior stakeholders hear a confident story.
Then the hidden exposure becomes visible. An interface that was “being managed” has no owner. Engineering deliverables are technically complete but not construction-ready. Procurement is on time, yet vendor data is late. Productivity has softened for six reporting periods, but overtime is masking it. Commissioning logic depends on systems that are not fully segregated. The handover plan assumes operations, maintenance, spares, permits, and training will all converge at the same time.
This is where chronic unease matters.
In high-hazard industries, people often discuss chronic unease in a safety context. It describes a disciplined state of alertness, a refusal to be comforted too quickly by good news. High-reliability organization research uses related ideas, such as preoccupation with failure, sensitivity to operations, and reluctance to simplify. Safety science, including work influenced by James Reason and later organizational researchers, also warns that serious failures often emerge from weak signals, normalized shortcuts, and assumptions that drift over time.
Project leaders need the same capability. Chronic unease is not anxiety, negativity, or distrust. It is a leadership habit: support the plan while actively searching for evidence that it may be wrong.
Chronic Unease Is A Leadership Capability, Not A Mood
Experienced project directors know that belief matters. Projects do not get delivered by teams that expect to fail. Confidence helps people make decisions, hold commitments, recover from setbacks, and keep moving when conditions are messy.
But confidence becomes dangerous when it turns into comfort.
Chronic unease creates a productive tension. It lets leaders say, “We believe in the plan,” while still asking:
What evidence would prove us wrong?
Which assumptions have aged since approval?
Where are we relying on heroic recovery rather than genuine control?
What are people not saying in the formal reports?
What weak signals are being explained away because the dashboard is still green?
This is not the same as second-guessing every decision. In complex capital projects, hesitation can be expensive. A leader who turns every meeting into a forensic challenge slows the work, damages trust, and teaches people to defend rather than disclose.
Good chronic unease is more precise. It focuses on the places where project health can be misread.
PMI, APM, ISO, AACE International, the Construction Industry Institute, and professional institutions such as ICE and RICS all stress, in different ways, that project control depends on active risk management, reliable information, governance, assurance, and disciplined change control. None of those practices work well if leaders only look for confirming evidence.
The same holds for oil and gas, mining, utilities, marine, infrastructure, and energy projects. The formal process may be strong, but the project still depends on human judgment. That judgment is exposed to familiar pressures:
Overconfidence after early progress
Confirmation bias when leaders prefer information that supports the baseline
Groupthink in teams that want to maintain alignment
Management pressure to protect sanction promises
Normalization of deviance when workarounds become routine
Excessive trust in green dashboards with weak underlying data
The leader’s job is not to eliminate optimism. It is to keep optimism evidence-based.
Why Green Status Can Be Misleading
A green report is only as reliable as the system that produced it.
A planned progress curve may hide out-of-sequence work. Earned progress may reflect installed quantities but not testable completion. A procurement milestone may show purchase orders placed while expediting risk grows in vendor engineering. A safety performance report may show low incident frequency while permit quality, simultaneous operations control, or dropped-object observations deteriorate. A quality report may show nonconformances closing, while repeat defects indicate the same root cause is unresolved.
In most cases, the problem isn't dishonesty. It is simplification. Complex projects compress messy reality into reporting categories. Executives need concise information, but the compression strips out texture.
That texture is often where the risk lives.
A chronic unease mindset asks whether the reporting system is still connected to physical reality. It also asks whether the project is becoming dependent on conditions that may not hold.
For example:
A brownfield turnaround remains on schedule because craft labor is working extended hours, but fatigue, access congestion, and permit delays are increasing.
An offshore module is reported as mechanically complete, but punch items affect commissioning sequence and preservation status is uncertain.
A rail infrastructure package is within budget, but unresolved utility interfaces are accumulating behind the next possession window.
A mining process plant shows good concrete and steel quantities, but vendor package integration has fallen behind the construction need date.
An EPC contractor reports engineering progress above plan, yet interdisciplinary checks are late, and field queries are rising.
The point is simple. Progress is not always readiness. Activity is not always control.
Where Chronic Unease Applies Across The Project Life Cycle
Chronic unease is often most needed when a project appears under control. This can happen at any stage. The form of unease changes as the project moves from concept to handover.
Concept And Business Case
At concept stage, the main exposure sits inside assumptions. Leaders often make strategic decisions with incomplete information, as they must. The danger comes when early assumptions harden into facts.
Common hidden risks include:
Optimistic demand, production, throughput, or availability assumptions
Underdeveloped site, geotechnical, metocean, environmental, or permitting information
Understated stakeholder, land, access, logistics, or security constraints
Technology readiness that is described too confidently
Benchmark estimates used outside their valid range
AACE guidance on cost estimating and recommended practices emphasizes that estimate quality depends on scope definition, basis, assumptions, and maturity. ISO 31000 also frames risk as the effect of uncertainty on objectives, which is useful at this stage because uncertainty is not a side issue. It is central.
Chronic unease at concept stage sounds like:
Which assumptions most influence value?
Which assumptions have not been tested independently?
What would make this concept unattractive?
What lessons from similar projects are being ignored because this project feels different?
Where have we converted uncertainty into a single-point number too early?
FEED And Definition
Front-end engineering and design can create the conditions for delivery success. It can also create an illusion of certainty.
CII research has long emphasized the value of front-end planning, scope definition, and alignment. Most experienced project teams accept that in principle. The risk is that FEED becomes a stage-gate exercise rather than a genuine test of deliverability.
A FEED package can look complete on a document register while still carrying unresolved interfaces. Battery limits may be unclear. Long-lead equipment may be specified before operating philosophy is settled. Constructability reviews may occur too late or without input from field-experienced teams. Permitting constraints may sit outside the schedule logic.
Chronic unease during FEED focuses on decision quality:
Are we freezing scope, or only freezing drawings?
Which decisions are being deferred into execution?
Are assumptions traceable, owned, and reviewed?
Do contractors, operations, commissioning, and maintenance agree on the same outcome?
Have we tested modularization, logistics, access, labor, and shutdown constraints against real site conditions?
Engineering And Procurement
Engineering and procurement often report progress through milestones. That is necessary, but it can hide readiness gaps.
Engineering progress may be measured by deliverable issue status. Procurement progress may be measured by requisitions, purchase orders, inspections, or delivery dates. The project looks green when those milestones are achieved. Yet construction readiness depends on something more integrated.
Watch for:
Rising technical queries and field design changes
Vendor data delays affecting downstream design
Late model reviews or unresolved clash issues
Substitution requests that affect certification, maintainability, or commissioning
Expediting reports that rely on supplier promises without evidence
Procurement savings that create later cost through quality, logistics, or schedule risk
A chronic unease leader does not merely ask whether engineering is “percent complete.” They ask whether engineering is fit for the next user.
That user may be fabrication, construction, completions, commissioning, operations, or the regulator. Each has different evidence needs.
Construction And Installation
Construction is where weak assumptions meet physical constraints.
A green construction report can mask deteriorating productivity if the team focuses on total quantities rather than planned sequence, workface readiness, rework, access, and constraints. Lost productivity rarely announces itself with one dramatic event. It appears through small signals:
Crews waiting for permits, materials, scaffolding, lifting support, or isolations
Work packs issued without full prerequisites
Rework hidden inside punch lists or “minor” modifications
Supervisors spending more time expediting than controlling the work
Increasing overtime to protect milestone dates
Higher levels of out-of-sequence installation
More reliance on informal agreements between contractor teams
Construction Industry Institute and AACE publications both treat productivity, change, and project controls as major drivers of outcome. Field leaders know this from experience. The challenge is to make the weak signals visible before they become claims, delays, or quality failures.
Chronic unease in construction means going to the field, not just reviewing the field report. Leaders should test whether planned work can actually be performed as planned.
Ask crew-level questions:
What stopped you today?
Which constraint keeps coming back?
What work is being done out of sequence?
Where are we installing something that may need to be removed later?
Which drawings, materials, permits, or access points are not ready?
What are we calling complete that still needs hidden effort?
The answers often reveal more than the dashboard.
Commissioning, Start-up, And Handover
Commissioning harshly tests earlier optimism. It exposes missing interfaces, incomplete documentation, late punch items, gaps in operating procedures, preservation failures, software issues, vendor availability problems, and unclear ownership.
A project may be mechanically complete in a contractual sense but not ready to start safely and efficiently. Operational readiness requires trained people, spares, maintenance systems, emergency arrangements, permits, procedures, acceptance criteria, and clear handover boundaries.
IOGP, the Energy Institute, and regulators in high-hazard sectors consistently stress barrier management, process safety, competence, and operational control. These are not late-stage administrative tasks. They are delivery conditions.
Chronic unease near start-up should be intense but calm. The leader must resist two bad choices. One is reckless acceleration because the end is near. The other is paralysis after discovering late issues. The better path is evidence-based readiness.
Useful questions include:
Are systems complete in the sequence needed for energization, flushing, testing, and start-up?
Are safety-critical elements verified, not just listed?
Has operations accepted the asset condition, or only the handover documents?
Are temporary overrides, bypasses, or concessions visible and time-bound?
Do start-up scenarios include credible failure modes?
Is the organization ready for the asset, including people, spares, procedures, permits, and emergency response?
The commissioning phase rewards leaders who have stayed uneasy earlier.
The Hidden Exposures That Healthy Projects Often Carry
The same patterns appear across EPC, construction, shutdowns, offshore campaigns, infrastructure programs, and brownfield modifications. The details differ, but the signals are familiar.
Weak Signals Get Rationalized
Weak signals rarely arrive as clean warnings. They look like irritations, exceptions, or local problems.
A supplier misses a data date but promises recovery. A contractor relationship becomes more formal. The project controls team adds a caveat to the forecast. Commissioning asks for earlier involvement but gets told the sequence is not ready. Site teams start building their own trackers because the central system does not reflect field reality.
Each signal is explainable. Together, they may be telling a coherent story.
High-reliability research encourages leaders to treat small failures as system information. That idea fits project delivery well. A weak signal is not proof of failure, but it is a reason to look harder.
Assumptions Drift Without Formal Change
Most projects control formal change. Fewer control assumption drift.
An assumption may change quietly because of a late permit, a supplier constraint, a design clarification, weather impacts, labor market conditions, revised access rules, or stakeholder requirements. The baseline remains intact on paper, but the underlying conditions have shifted.
For example, a shutdown plan may assume 24-hour access for work. Later, noise restrictions, fatigue rules, or simultaneous operations reduce effective working time. If the plan still reports against the original productivity basis, the schedule may look healthier than it is.
A chronic unease leader asks whether the plan's basis can be achieved only through a growing stack of recovery actions, each depending on the last.
Recovery Actions Become The Plan
Recovery plans are normal. Complex projects need them. The warning sign appears when the baseline can be achieved only through a growing stack of recovery actions, each depending on the last.
Common examples include:
Engineering recovery depends on late vendor data arriving clean
Procurement recovery depends on air freight and expedited inspection slots
Construction recovery depends on overtime, additional crews, and perfect access
Commissioning recovery depends on parallel activities that increase permit and isolation demand
Handover recovery depends on operations accepting documentation after start-up
Recovery can work when it is targeted, funded, resourced, and risk-assessed. It becomes dangerous when leaders treat it as a confidence statement rather than a fragile scenario.
Contractor Tension Becomes A Project Control Issue
Commercial tension is not automatically a problem. Contractors and owners have different interests, and good contracts manage that reality. But deteriorating trust can distort information flow.
Watch for changes in behavior:
More correspondence and fewer problem-solving discussions
Claims language appearing earlier in routine communications
Reluctance to share bad news until formally required
Field supervisors escalating minor issues through commercial channels
Joint planning sessions becoming defensive
Acceleration instructions issued without agreement on constraints
RICS and other professional bodies often stress commercial administration, records, valuation, and change management. Chronic unease adds a leadership lens. The question is not only whether the contract position is protected. It is whether the commercial climate is reducing the quality of delivery information.
How Leaders Practice Chronic Unease Without Spreading Pessimism
Chronic unease can be misused. If leaders ask only suspicious questions, people may hide issues. If leaders meet every positive report with disbelief, teams learn that evidence doesn't matter. If assurance becomes a blame exercise, it will find less each time.
The practice has to be disciplined and fair.
Test Assumptions In Public
Assumptions should not sit in old sanction papers, risk registers, or estimate bases that no one reads. Leaders should bring key assumptions into live governance.
That means asking:
Which assumptions are still true?
Which ones need evidence?
Which ones have changed without a formal change event?
Which assumptions are now owned by someone different from the person who made them?
Which assumptions are embedded in multiple parts of the plan?
Public assumption testing reduces personal defensiveness. The target is the assumption, not the person.
Search Deliberately For Contradictory Evidence
Most reporting systems collect evidence that the plan is on track. Chronic unease adds the opposite search.
Ask each function to bring one item that challenges the current narrative. Engineering may identify a design maturity concern. Procurement may identify a fragile supplier commitment. Construction may identify access constraints. Commissioning may identify a system boundary issue. Operations may identify a maintainability or competency gap.
This practice fights confirmation bias. It also gives permission to raise uncomfortable facts before they become urgent.
Use Confidence Reviews, Not Only Progress Reviews
Progress answers, “How much have we done?”
Confidence answers, “How sure are we that the remaining work can be done as planned?”
A confidence review should look at data quality, assumptions, constraints, interfaces, productivity trends, contingency drawdown, change exposure, quality trends, and decision latency. It should also test whether the team’s forecast has become a negotiated position rather than a realistic prediction.
AACE practices around estimating, cost control, and forecasting support this way of thinking. A forecast without confidence logic is just a number with authority.
Go To The Workface
Field verification is one of the strongest antidotes to false confidence.
For a construction project, that may mean walking a system from battery limit to battery limit. For a shutdown, it may mean observing permit issuance, isolation points, crane access, scaffold readiness, and material kitting. For a marine campaign, it may mean checking weather windows, vessel readiness, lift plans, spares, and interface responsibilities. For commissioning, it may mean walking down the energization path and asking who accepts each boundary.
Leaders should avoid ceremonial site visits. The purpose is to learn how the work really gets done.
Run Pre-mortems And Scenario Challenges
A pre-mortem assumes the project has failed and asks why. This technique, rooted in organizational psychology and decision research, helps people surface concerns that might otherwise stay private.
