Chronic Unease for Project Leaders Staying Alert When Projects Look Healthy
The most dangerous project is not always the one reporting red. It is often the one reporting green while underlying conditions start to move against it.
Experienced project leaders know the pattern. The dashboard looks acceptable. The contractor is confident. The schedule narrative says the critical path is protected. Safety performance looks strong. Quality issues are “being managed.” The client is reassured. Then, weeks or months later, the project discovers that progress was thinner than reported, productivity had been deteriorating, key interfaces were unresolved, a late design change had infected procurement, commissioning logic was fragile, and recovery actions had quietly become part of the baseline.
This is where chronic unease matters.
Chronic unease is the disciplined habit of staying alert to what may be wrong, even when the project looks healthy. It is not anxiety, cynicism, or leadership by doubt. It is a practical project leadership capability: constructive skepticism, applied consistently, without undermining the confidence needed to deliver.
The idea has strong roots in high-reliability organization research, safety science, and major hazard industry practice. The Energy Institute, IOGP, regulators, and safety researchers have long emphasized vigilance, weak-signal recognition, and sensitivity to operations in high-risk environments. The same habit applies to capital projects. PMI, APM, ISO, AACE International, CII, ICE, RICS, and other professional bodies all point, in different language, toward disciplined risk management, assurance, contingency, governance, decision quality, and control.
The point is simple. Good leaders back the plan, but they do not fall in love with it.
Chronic Unease Is A Leadership Discipline, Not A Mood
Chronic unease is sometimes misunderstood because the phrase sounds negative. In practice, it is closer to disciplined attention.
A project director with chronic unease does not walk around expecting failure. They look for conditions that could make failure more likely. They understand that major projects are complex systems, not simple task lists. They know that performance data is always incomplete, reports are filtered, and teams under pressure tend to simplify the story.
That mindset is especially valuable in complex capital projects because weak signals often appear long before visible failure. A fabrication yard starts missing small milestones. Engineering deliverables are issued “for information” rather than truly complete. Field crews begin creating workarounds to compensate for missing material. A brownfield tie-in depends on an isolation plan that has not been fully tested with operations. The commissioning team accepts a temporary bypass “just to get through the sequence.” Each item looks manageable. Together, they may show that the project’s apparent health is fragile.
High-reliability organization research often describes a preoccupation with failure, reluctance to simplify, and sensitivity to operations. Those ideas translate directly into project leadership. They encourage leaders to ask:
What could make this report misleading?
Where are we relying on good luck rather than good control?
Which assumptions have aged since approval?
What would we expect to see if the project were starting to drift?
This is not the same as micromanagement. Chronic unease does not require leaders to second-guess every technical decision. It requires leaders to create a climate where reality can interrupt optimism.
That matters because project systems can reward confidence more than accuracy. Steering committees often want concise assurance. Sponsors want certainty. Contractors want to protect entitlement and reputation. Project teams want recognition for progress. None of that is malicious. It is human and commercial. Yet these pressures can delay difficult facts.
The best leaders make it safe and normal to surface unwelcome evidence early. They do not punish bad news. They punish avoidable surprise.
Healthy Indicators Can Mask Hidden Exposure
A green dashboard is useful, but it is not proof of control. It shows how the project has chosen to measure itself. It may not show what is changing in the field, the supply chain, the design office, or the commissioning sequence.
Professional standards and guidance from PMI, APM, ISO 31000, ISO 21502, AACE International, and others stress the need for risk-based governance, progressive assurance, and evidence-based controls. The practical challenge is that many project controls systems are better at reporting known problems than detecting emerging ones.
Here are the exposures that often sit behind a healthy-looking project.
Weak Signals Are Dismissed As Noise
Weak signals rarely arrive as dramatic warnings. They arrive as small anomalies.
A marine contractor requests more weather standby than expected. A utilities interface meeting is postponed again. The vendor data schedule slips by a few days every month. A construction manager says, “We are managing it,” but cannot show crew-level productivity trends. A commissioning lead raises concerns about systemization, then withdraws the comment after being told the schedule cannot move.
Each signal can be explained away. Chronic unease asks whether the explanations are adding up too neatly.
In EPC and infrastructure settings, weak signals often appear in the gaps between disciplines. Engineering says procurement has enough information. Procurement says vendor data is late. Construction says the design is not field-ready. Commissioning says the turnover sequence does not match how the asset will start up. When everyone is partly right, the risk usually hides in the interface.
Productivity Deteriorates Before Progress Fails
Reported progress can keep rising while productivity declines. That's why experienced construction and shutdown leaders look beyond percent complete.
In a brownfield turnaround, the daily progress curve may look acceptable because crews are completing accessible work packs. At the same time, constraint removal may weaken, permits may take longer, and scaffolding or isolation availability may drive inefficient sequencing. The project still looks productive until the remaining work becomes more complex.
AACE and CII guidance on cost, schedule, and construction performance has long emphasized the importance of sound baselines, objective progress measurement, and trend analysis. Chronic unease turns that guidance into leadership behavior. It asks whether the rate of earned progress is believable, repeatable, and supported by actual field conditions; permits may take longer, and scaffolding or isolation availability may drive.
Useful questions include:
Are crews earning progress on planned work, or only on available work?
Is the remaining work harder than the completed work?
Are supervisors spending more time expediting, resequencing, and removing blockers?
Are productivity rates supported by field observation, not just quantity reports?
Are recovery actions becoming normal operating practice?
The last question is critical. A project that depends on continuous recovery is not healthy. It is consuming resilience.
Forecasts Become Optimistic Through Habit
Forecasts often fail gradually. The team does not decide to mislead. It updates the forecast using assumptions that no longer hold.
A procurement package assumes vendor documentation will recover next month. Engineering assumes late comments will not affect procurement. Construction assumes it can add additional crews without losing efficiency. Commissioning assumes punch items will close at the historical rate, even though the remaining items are more complex.
This is assumption drift. The original logic remains in the plan after the conditions supporting it have changed.
A strong project leader treats forecasts as arguments, not outputs. The question is not “What does the software say?” The question is “What must be true for this forecast to happen?”
That reframing helps separate confidence from wishful thinking. It also helps sponsors and boards distinguish between a possible outcome and a probable one.
Chronic Unease Must Follow The Project Life Cycle
Chronic unease is not only a construction behavior. It applies from concept through handover. The questions change as the project matures, but the discipline stays the same.
Concept And Select Require Skepticism About Value And Framing
Early project stages set the risk profile. By the time execution starts, many choices have already narrowed. Scope definition, site selection, contracting strategy, battery limits, brownfield constraints, technology choices, and stakeholder commitments all create future conditions.
At concept stage, chronic unease challenges strategic optimism. The team should test whether the project is being framed to pass approval rather than to expose the real delivery challenge.
Leaders should ask:
Have we defined the business need clearly enough to avoid scope churn later?
Are we comparing options using realistic execution constraints?
Have we tested the downside case, not only the preferred case?
Which assumptions are politically convenient but technically weak?
Are early cost and schedule ranges being treated as commitments too soon?
This aligns with the principle behind stage-gate governance: decisions should mature as evidence matures. A project that locks into a preferred solution too early may carry hidden risk into every later phase.
FEED and Engineering Require Challenge To Maturity Claims
Front-end engineering design is where many future overruns are either prevented or baked in. Chronic unease during FEED focuses on definition quality, interfaces, constructability, contracting readiness, and the realism of execution plans.
A FEED package can look complete while containing unresolved decisions. For example, plot plan constraints may still be open, vendor data may be provisional, tie-in strategies may not be validated with operations, or hazardous area classification assumptions may affect layout and procurement later.
Experienced leaders look for evidence of maturity, not just document count. They ask whether drawings are stable enough for procurement, whether constructability reviews have changed the design, and whether operations, maintenance, commissioning, and safety input has meaningfully shaped the solution.
ISO 31000’s risk principles and APM’s emphasis on governance and decision-making both support this approach. Risk work should inform decisions, not sit as a separate register exercise.
Procurement Requires Attention To Dependency Risk
Procurement problems often look minor until they hit the critical path. A late valve, transformer, subsea component, control system cabinet, or specialist package can distort the whole execution sequence.
Chronic procurement unease means testing the full chain of dependencies. Knowing that a purchase order has been placed is not enough. Leaders need to understand engineering inputs, vendor capacity, inspection requirements, logistics constraints, customs, expediting quality, preservation, and site readiness.
In mining, utilities, offshore, and large infrastructure projects, long-lead equipment creates a particular risk. The purchase order date may be green while vendor drawings, manufacturing slots, test plans, shipping routes, and installation access contain exposure.
Good questions include:
Which purchase orders are green only because the next milestone has not arrived yet?
Where are we depending on vendor recovery without evidence?
Do inspection and test plans match the project schedule?
Have logistics risks been tested against actual route, port, lifting, and site constraints?
What equipment could arrive on time but still be unusable because data, preservation, or installation readiness is weak?
Construction And Shutdowns Require Field Verification
Construction is where reporting can become detached from physical reality. Chronic unease brings leaders back to the workface.
That does not mean senior leaders should bypass the management chain or solve every site issue. It means they should regularly verify that the reported story matches observable conditions. Field verification can include walks with frontline supervisors, independent quantity checks, permit-to-work reviews, constraint reviews, quality surveillance, and direct discussion with commissioning and completions teams.
In shutdowns and turnarounds, the need is even sharper. Time windows are short, sequence logic is tight, and unexpected findings can rapidly consume float. A shutdown can report good early progress while deferring difficult work into the final days. Leaders need to know whether the plan is retiring risk or pushing it forward.
A practical behavior is to ask supervisors what they would stop if they had the authority. Their answers often reveal constraints that formal reporting hides.
Commissioning, Start-up, And Handover Require Skepticism About Readiness
Commissioning is a common point of truth. It exposes earlier decisions, late design changes, incomplete construction, poor preservation, weak systemization, and gaps between project delivery and operational readiness.
A project can be mechanically complete in a contractual sense while still not ready to start up safely and reliably. Punch items, temporary modifications, incomplete procedures, limited spares, untrained operators, poor alarm rationalization, and weak maintenance readiness can all sit behind a positive completion metric.
Energy Institute and IOGP guidance on process safety and human factors reinforces the need to treat start-up as a high-risk phase. Chronic unease during commissioning asks whether evidence, drills, walkdowns, test records, and operational involvement have proven readiness.
The handover question is not “Can we transfer the asset?” It is “Can the receiving organization operate, maintain, and control the asset safely from day one?”
Confidence And Skepticism Can Work Together
Some leaders worry that too much challenge will damage morale. That is a real risk if challenge is careless, performative, or used to assign blame. But confidence and skepticism are not opposites.
Project teams need confidence in the mission, the plan, and the leadership. They also need confidence that leaders will face reality early. False reassurance creates a deeper morale problem later because it forces teams into crisis recovery.
The tone matters. Chronic unease works best when leaders challenge the evidence, not the person.
A poor challenge sounds like this:
“I don’t believe your forecast.”
“This looks like optimism.”
“You need to fix your numbers.”
A better challenge sounds like this:
“Show me what must be true for this forecast to hold.”
“What evidence would tell us this recovery plan is not working?”
“Which assumptions have changed since the last confidence review?”
“Where would you look first if this plan started to fail?”
“What are we not seeing because our dashboard is too high-level?”
The second style is firm but professional. It invites better thinking. It also reduces defensiveness by focusing on the decision, the evidence, and the risk.
The Traps That Chronic Unease Helps Counter
Major projects are vulnerable to predictable cognitive and organizational traps.
Overconfidence
Experienced teams can become too sure of their ability to recover. Past success may lead them to underestimate new complexity, market constraints, regulatory scrutiny, or stakeholder risk.
Normalization of deviance
Sociologist Diane Vaughan’s work on normalization of deviance is often discussed in safety and organizational failure. In projects, the same pattern appears when late decisions, incomplete work packs, temporary fixes, and repeated exceptions become accepted as normal because nothing has failed yet.
Groupthink
Under commercial or schedule pressure, teams may see dissent as disloyal. Leaders may get agreement instead of insight. Independent assurance, peer reviews, and pre-mortems help break this pattern.
Confirmation bias
Teams tend to notice evidence that supports the preferred view. If the project believes recovery is working, it will naturally highlight progress that confirms recovery. Chronic unease deliberately searches for contradictory evidence.
Management pressure
Pressure does not need to be explicit. A sponsor’s repeated focus on a target date can shape how teams report. Teams may stop raising concerns because they believe the answer is already known.
Green dashboard dependence
Dashboards simplify reality. They are necessary, but they can hide variation, local deterioration, and emerging exposure. When the underlying risk is high, a green indicator should trigger curiosity, not automatic comfort.
Practices That Make Chronic Unease Useful
Chronic unease only helps if it changes behavior. Otherwise, it becomes a slogan. The following practices are practical, repeatable, and suited to complex projects.
Test Assumptions As Live Risks
Every major forecast rests on assumptions. Treat the important ones as live risks with owners, evidence, review dates, and triggers.
Examples include:
Regulatory approvals will be received before construction mobilization.
Vendor data will support IFC design release by a target date.
Modular units will arrive before the heavy-lift window.
Brownfield isolations can be completed within the planned outage period.
Commissioning systems will be handed over in the required sequence.
Operator training can be completed before start-up.
The leadership question is whether the assumption is still valid, not whether it was reasonable when the plan was approved.
A simple assumption review should ask:
What evidence supports this assumption today?
What has changed since approval?
What would invalidate it?
Who is closest to the evidence?
What is the fallback if it fails?
Run Scenario Challenges Before The Project Forces Them
Scenario challenge is a structured way to test the plan against plausible disruption. It should not focus only on extreme events. The most useful scenarios are often ordinary and uncomfortable.
For example:
A critical vendor slips by six weeks but reports confidence until late.
Offshore weather reduces access during a short campaign window.
A brownfield discovery adds unplanned repair work during a shutdown.
A tunnel boring machine support system has quality issues before launch.
Commissioning reveals control logic defects across multiple packages.
A key subcontractor becomes commercially stressed and loses supervisors.
The purpose is not to predict the future. It is to see whether the plan has enough resilience, decision rights, float, contingency, and commercial clarity to cope with foreseeable stress.
Verify In The Field, Not Only In The Report
Field verification is one of the most powerful antidotes to false confidence.
Project directors and sponsors do not need to inspect every weld or cable pull. They do need contact with the physical truth of the job. That includes field walks, completions reviews, quality observations, logistics checks, permit reviews, and conversations with supervisors who understand the constraints.
Good field questions are direct:
What is stopping tomorrow’s work?
Which work packs are not ready?
What are crews doing that the plan did not expect?
Which materials are being borrowed, substituted, or chased?
Where are we accepting rework risk?
What would make this area unsafe or inefficient next week?
If the answers differ from the dashboard, believe the field long enough to investigate.
Use Independent Assurance Without Making It Ceremonial
Independent assurance should protect decision quality. It should not become a ritual that confirms what the project already believes.
Assurance is most useful when it has a clear scope, access to evidence, independence from delivery pressure, and the authority to raise uncomfortable findings. It can focus on cost and schedule confidence, technical readiness, process safety, quality, contract strategy, claims exposure, operational readiness, or commissioning.
PMI, APM, ISO, RICS, ICE, and related institutions all recognize the role of governance, assurance, and competent review in project delivery. In practice, leaders should be wary of assurance that arrives too late, reviews only documents, or avoids commercial tension.
Strong assurance asks whether the project can still meet its objectives under current conditions, not whether the team has produced the required paperwork.
Hold Confidence Reviews, Not Just Progress Reviews
Progress reviews ask what has been achieved. Confidence reviews ask whether future delivery remains believable.
A confidence review should combine schedule, cost, risk, technical, commercial, quality, safety, and operational readiness evidence. It should focus on trends rather than static status.
Useful review prompts include:
What has to go right for the current forecast to hold?
Where has float reduced without a matching change in risk rating?
Which recovery actions are now part of the assumed plan?
What is the confidence range around the forecast, and why?
Are contingency and management reserve still adequate for the remaining risk?
Which risks have become issues but are still shown as risks?
What evidence challenges the current delivery narrative?
This is where AACE-style cost and schedule discipline, risk analysis, and transparent basis of estimate thinking become commercially valuable. Confidence is stronger when it has been tested.
Run Pre-mortems When The Story Sounds Too Clean
A pre-mortem asks the team to imagine that the project failed, then explain why. Organizational psychologist Gary Klein is widely associated with this technique. It helps teams voice concerns that might otherwise remain private.
A pre-mortem works well before sanction, before major contract award, before site mobilization, before shutdown execution, before first energization, before hydrocarbons introduction, and before handover.
Ask the team:
Imagine we are six months from now,to engage with the job's physical reality and the project has missed a key commitment. What happened?
Which early warning signs did we ignore?
Which assumption proved false?
Which interface failed?
Which decision did we make too late?
Which stakeholder did we underestimate?
The answers often reveal practical actions: strengthen an interface, accelerate a decision, add assurance, improve data quality, protect contingency, or change the sequence.
Questions Senior Leaders Can Use When Everything Looks Green
When a project reports healthy status, senior leaders need better questions than “Are you on track?” That question often receives the answer the room expects.
The table below offers a practical set of questions for sponsors, project directors, steering committees, and senior functional leaders.
Area to test | Questions that reveal whether health is genuine |
Forecast integrity | What must be true for the current forecast to hold? Which assumptions have changed since the last review? |
Schedule confidence | Where is float being consumed? Which near-critical paths could become critical next month? |
Cost confidence | Are trends consistent with the forecast at completion? Which risks are not fully reflected in contingency? |
Productivity | Are earned quantities matching planned productivity? Is the remaining work more difficult than completed work? |
Interfaces | Which interfaces depend on informal coordination rather than clear ownership? Where are decisions stuck between parties? |
Contractor health | Are commercial tensions affecting behavior, staffing, supervision, or reporting quality? |
Engineering maturity | Which deliverables are technically issued but still unstable? What vendor data is driving rework risk? |
Procurement | Which items are on time by milestone but still exposed through documentation, inspection, logistics, or preservation? |
Construction readiness | Are work packs constraint-free? What work is being resequenced because prerequisites are missing? |
Quality | Where are defects repeating? Are nonconformances being closed or carried forward? |
Safety and process safety | Are teams accepting temporary arrangements that would not have been accepted earlier? |
Commissioning readiness | Does mechanical completion follow the required system sequence? Are procedures, spares, training, and permits ready? |
Operational readiness | Can operations safely receive the asset, or is the project transferring unresolved risk? |
Governance | What bad news has reached leadership recently? If none, why are we confident the reporting system is working? |
These questions work because they shift the conversation from status to evidence. They also reduce the chance that senior leaders unknowingly reward good news over accurate news.
Making Chronic Unease Part Of The Project Culture
Chronic unease cannot depend on one exceptional project director. Build it into routines, governance, and leadership behavior.
Start with language. If every review celebrates green status and treats challenge as resistance, the culture will drift toward optimism. If leaders ask for disconfirming evidence as part of normal governance, teams learn that challenge is expected.
Create regular weak-signal discussions. These should be short, practical, and cross-functional. Ask engineering, procurement, construction, HSE, quality, contracts, commissioning, and operations what feels different, harder, slower, or more fragile than it did last month.
Protect independent voices. The planner, risk lead, cost engineer, completions manager, quality manager, or operations representative may see the issue before the leadership team does. Don't reduce their role to maintaining tools or producing slides. They are part of the project’s early warning system.
Watch for workaround growth. Workarounds are useful in moderation. Projects need practical people who can solve problems. Yet growing workarounds can show that the formal system is failing. If teams constantly bypass material processes, revise work packs in the field, depend on expediters, or use temporary fixes to maintain progress, leaders should ask what the project system is no longer providing.
Separate challenge from blame. People disclose risk when they believe the organization will respond fairly. Safety science and human factors literature have long shown the value of learning cultures that distinguish error, drift, and reckless behavior. Project leadership needs the same maturity.
Keep the commercial lens clear. Chronic unease is not only about safety or technical risk. It protects margin, cash flow, claims position, working capital, contractual relationships, and reputation. Late discovery is expensive. Early discomfort is usually cheaper.
Most of all, leaders must model the behavior. A sponsor who asks hard questions but reacts badly to bad news will get polished narratives. A project director who says “bring me the facts early” and then supports problem-solving will get more truth.
The most effective project leaders hold two thoughts at once. They show confidence in the plan so teams can execute with focus. They also remain alert to what the plan may be missing. That balance is the essence of chronic unease: steady belief in delivery, paired with the discipline to keep searching for the evidence that could prove the project is less healthy than it appears.
