Insights

Six months into construction, the monthly steering committee meeting for a major mineral processing and downstream manufacturing expansion in Eastern Indonesia began, as it always did, with a review of the dashboard.

Engineering, on schedule. Safety incident rate, below target. Budget variance, within tolerance (a little tight, but explainable). Procurement, on track. Environmental permits, secured. The project director moved through the slides in eleven minutes. Nobody had a question. The meeting adjourned early.

Everyone in that room was doing their job well. That is the part of this story worth sitting with, because it is the part that makes what happened next so difficult to see coming, and so easy, in hindsight, to explain away as bad luck.

Three things had been happening quietly, in parallel, for weeks.

• In the Directly Affected Villages, the term operators use for the communities in the immediate zone of impact, informal conversations about uang ganti rugi (land compensation) had stalled. The community consultation process that had opened the project two years earlier was well documented. But follow-up conversations with the tokoh adat (customary community leaders) whose blessing carried real weight on the ground had gone quiet after the company’s community relations officer was reassigned mid-project. Not broken down, just stalled, the way things stall when a relationship’s continuity depends on one person and the handover is incomplete. Nobody escalated it, because it wasn’t yet a dispute.
• At the same time, a subcontractor responsible for a mid-critical-path civil works package was quietly absorbing cost pressure by trimming its local labor complement (the workforce hired under the project’s local labor commitments) and replacing experienced local hires with cheaper crews brought in from outside the district. This showed up nowhere on a dashboard, because subcontractor labor composition isn’t a line item anyone tracks, until it becomes one.
• And separately, the regional contact at the dinas lingkungan hidup (provincial environmental office) who had been the project’s main point of continuity through two years of permitting had been rotated to a different post, as happens routinely in Indonesian civil service assignments. His successor was, by all accounts, capable. He was also new, unfamiliar with the project’s history, and understandably cautious about approving anything his predecessor had cleared verbally but never formally documented in the permit file.

None of these three things was, on its own, a crisis. Each had an owner, technically. Community relations had the land issue, project controls had the subcontractor relationship, government relations had the dinas contact. Each owner considered their piece manageable. None of them was in a position to see what happened when the three threads met.

They met in week nine. By then, the subcontractor crew was already working under pressure, with too few people, limited familiarity with the area, and instructions to keep the schedule moving. During clearing work near the disputed parcel, a crew member damaged a tree that the local community regarded as sacred. On its own, the incident might have been manageable. But the community had already been frustrated by weeks of unresolved discussions over land compensation. The damaged tree became a symbol of something larger: to them, the project was moving forward while their concerns were being pushed aside. Within days, residents organized a road blockade, preventing project vehicles from reaching the site. At the same time, the newly assigned contact at the dinas lingkungan hidup, faced with a growing community dispute and still getting up to speed on the project’s environmental commitments, held off on a pending approval until the situation was clarified.

Three functions. Three green dashboards. One shutdown, lasting five weeks, that no single report had flagged as a risk — because no single report was built to see the space between them.

Naming the Pattern: The Orphan Risk

We call this pattern the orphan risk, a risk that exists in the gap between organizational functions rather than inside any one of them, and therefore has no natural owner, no line on any register, and no one whose job it is to ask how it is trending.

Technical risks tend to have clear parents. A schedule risk belongs to project controls. A safety risk belongs to HSE. A credit risk belongs to finance. Each has an established methodology, a register, a reporting cadence, and, critically, a person whose performance is measured on managing it well.

Non-Technical Risk (NTR), the term used across the industry for exactly this category, rarely works that way. Land and community relations, labor sentiment, stakeholder continuity, relationships with local government and lembaga adat (customary institutions), contractor behavior beneath the visible layer of the contract — these risks are real, and experienced operators know they’re real. But they frequently sit across multiple functions at once, which in practice means they belong fully to none of them.

Community relations owns the community relationship, but not the subcontractor’s hiring practices. Government relations owns the dinas contact, but not the land negotiation. Everyone owns their slice. Nobody owns the intersection.

This is different from simply having low awareness of NTR as a category. Most experienced leadership teams understand, at least in theory, that “soft” issues matter, even if some Indonesian operators still shorthand them as urusan sosial (social affairs) and treat them as separate from the primary risk register. The orphan risk pattern is subtler than that: it persists even in organizations that take NTR seriously, because the organizational structure itself, built around clean functional ownership, is not designed to see risks that live in the seams.

For Those Who Already Track This

If you already run a structured NTR program, the useful question the story above raises isn’t “do we track community, labor, and regulatory risk.” You likely do, each on its own register, each reviewed on its own cadence. The sharper question is: who is accountable for the correlation between them, not just the components?

A genuinely mature NTR posture treats interaction effects as a first-class risk category in their own right, not an emergent risk you discover after the fact. In practice, that means:

• A named owner for cross-functional risk correlation, distinct from the owners of each individual risk stream, with the authority to escalate a combination even when no single component has crossed its own threshold.
• Review cadences that force different functional leads into the same room on a recurring basis to compare trend lines, not just cite green statuses.
• A composite indikator, even a simple one, that tracks the number of adjacent amber signals across functions, since a cluster of near-threshold issues is itself a leading indicator, even when every individual metric looks fine.
• Institutional memory that survives personnel rotation, on both sides, since staff rotation is as routine inside government offices as it is inside operators, so a relationship’s history doesn’t reset to zero every time the person managing it changes, as happened with the dinas contact in the story above.

If any of that isn’t yet formalized, the gap usually isn’t a lack of awareness. It’s that the organization’s structure, for entirely sensible reasons built around clear accountability,  makes the correlation invisible by design.

A Short Self-Check

Whether NTR is a new concept for your organization or a well-established discipline, three questions tend to surface where the orphan risks are hiding:

1. The Correlation Test: If two of your “green” risk categories started trending amber in the same month, would anyone notice the correlation, or just the two green boxes turning amber separately, on two different reports, reviewed by two different people?
2. The Departure Test: Is there a risk currently being managed informally, through a personal relationship, a verbal understanding, or “someone keeping an eye on it,” that would have no owner at all if that person left tomorrow?
3. The Interaction Test: When was the last time your project or transition risk review deliberately asked “what happens if X and Y occur at the same time,” rather than reviewing X and Y as separate agenda items?

If any of these produces hesitation rather than a confident answer, that hesitation is the signal worth acting on.

The Point of Naming It

We don’t tell this story to suggest the project teams in it were negligent. They weren’t. Every function did what it was measured on doing, and did it well.

That is precisely why the orphan risk pattern is worth understanding on its own terms: it isn’t a failure of diligence, and it isn’t solved by simply asking people to work harder within their existing lanes, or by adding one more line item to the sosialisasi checklist.

It is a structural blind spot, and structural blind spots require a structural answer: someone whose explicit mandate is to sit across the seams and ask what the individual dashboards can’t, before the ganti rugi conversation, the subcontractor’s crew list, and the dinas handover find each other in week nine.

Let’s Start a Conversation

Navigating complex, interconnected non-technical risks does not have to mean waiting for hidden seams to open. Reach out to us for a confidential baseline consultation.

There is zero obligation, just a peer-to-peer dialogue where we bring decades of frontline operational judgment directly to your leadership team.

MRG brings decades of hard-won, real-world experience managing these exact challenges across Indonesia, translating lessons from past successes and failures into practical guidance that helps your organization build lasting resilience before friction turns into loss.

Mandala Resilience Group

mandalaresilience.com

Your Anchor in a Volatile Landscape