Thomas Gaultier
Menu

From Mitigation to Enhancement: Designing for Shared Benefit

Thomas Gaultier 9 min read

Most projects stop at not making things worse. The environmental and social plan lists the harms, proposes a mitigation for each, and calls the job done when the damage is contained. Containment is necessary. It is also the floor, not the ceiling. A project that only avoids harm gives a community no reason to want it there, and gives the investment no durable base of local support. The gap between mitigating harm and building benefit is where a project earns its place, or fails to.

That gap is the subject here. Mitigation reduces what a project takes. Enhancement adds what it can give, on purpose, designed in rather than donated later. Done well, enhancement is not charity and it is not a public-relations budget. It is the deliberate design of a project so that its presence leaves the surrounding livelihoods stronger and, in the same move, makes the investment safer and more stable. Both sides gain, or the design is wrong. This article is about how to make that shift real, how to prioritise it, and how to keep it honest.

First, exhaust the mitigation hierarchy

Enhancement does not replace mitigation. It sits on top of it, and it only works if the mitigation underneath is done in the right order. That order is the mitigation hierarchy, and it is embedded in standard practice and in IFC Performance Standard 1: avoid the impact, then minimise what you cannot avoid, then restore or rehabilitate, then offset or compensate for the residue.

The sequence matters because the steps are not interchangeable. Avoidance is the cheapest and most complete form of protection, and it is the one most often skipped in the rush to a compensation figure. Move a road corridor to spare a burial ground and you have avoided a conflict that no amount of money would have settled. Compensation is the last resort, not the first tool, because paying for a loss is always worse for the community than not inflicting it, and usually worse for the project than designing around it.

Get the hierarchy backwards and enhancement becomes a cover story. A project that skips avoidance, damages something it did not have to, and then funds a clinic to make up for it has not designed for shared benefit. It has bought forgiveness, and communities know the difference. Enhancement earns trust only when the harm beneath it was genuinely minimised first. Otherwise it reads as what it is: a payment to look past an avoidable loss.

Enhancement means keeping value in the region on purpose

The clearest definition of enhancement I use is simple. The purpose is to retain part of a project’s socio-economic benefits in the region where the project sits, rather than letting all of them flow out to shareholders, distant suppliers, and a capital city. A mine or a plant generates wages, procurement, taxes, and skills. Enhancement is the deliberate decision to route a meaningful share of those into the local economy in ways that outlast the project.

The mechanisms fall into two families, and a serious plan uses both. Monetary mechanisms move money directly: a foundation, trust, or fund; equity or shareholding for the community; royalties tied to output or profit; taxes channelled to local government. Non-monetary mechanisms build local capacity: hiring and training local people, procuring from local suppliers, developing enterprises, and investing in education and health infrastructure that serves the wider population, not only the workforce.

The non-monetary side is often where the durable value lives, because it survives closure. A cash transfer ends when the payment stops. A local supplier base, a trained workforce, and a functioning technical school keep generating income after the last truck leaves. That is the test of real enhancement: what remains standing when the project is gone. This is also where enhancement connects to the harder commitments in a community benefit agreement, which is where these mechanisms get written down and made enforceable rather than left as goodwill.

Prioritise with a method, not a wish list

The failure mode of enhancement is a scattered list of good intentions that pleases no one and changes nothing. A borehole here, a football pitch there, a scholarship or two, none of it aligned with what the community most needs or what the project can sustain. Prioritisation is what turns a wish list into a strategy, and it should be done with a method, not a meeting-room instinct.

Ana Maria Esteves built exactly such a method in 2008, the Social Investment Decision Analysis Tool. The logic is worth borrowing whether or not you use the full technique. First, senior managers agree the three or four business objectives that community investment must actually serve over the next few years: reduced risk of disruption, access to land, a local labour pool, a supplier base, reputation with a regulator. Not fifteen objectives. Three or four, chosen honestly. Then every candidate enhancement is scored on how much it contributes to each objective, on a simple scale from major contribution down to insignificant.

What the scoring surfaces is the overlap: the enhancements that rank high for the community’s priorities and high for the business at the same time. In a worked example of the tool, technical and vocational training that fed graduates into the operation and its supply chain scored at the top across every business objective. Scattered items like leisure facilities and one-off grants sat near the bottom. That result is not a coincidence. Skills that the operation will actually hire serve the community’s need for jobs and the project’s need for a local labour pool in a single investment, which is exactly what a shared-value enhancement looks like on paper.

The method does not remove judgement. It forces the conversation to be explicit about why one investment beats another, and it exposes the difference between an enhancement that builds a working relationship and one that just spends a budget. Prioritise this way and you can defend every choice to both a board and a village, which is the only kind of choice that holds.

Design for shared value, not a trade-off

The habit this article argues against is treating community benefit and business interest as opposites, where every gain for one is a cost to the other. That framing produces the worst of both: grudging community investment that the business resents, and thin benefits the community sees through. Designing for shared value means finding the enhancements that serve both at once, and building the project around them.

The examples are concrete. Local procurement lowers a project’s logistics costs while building an enterprise base that outlasts it. A trained local workforce reduces the expense and instability of flying in labour while creating skills that stay in the region. Investment in water or health infrastructure that the project needs anyway can be sized and sited to serve the wider population, turning a project cost into a community asset. In each case the benefit to the community and the benefit to the investment are the same act, not a transfer from one to the other.

This is where the mediation mindset earns its place inside the design, well before any dispute. Shared-value enhancement can only be identified by understanding what each side actually needs, and those needs are usually not on the surface. It takes structured dialogue to find them: sessions where the community’s real priorities and the project’s real business drivers are put on the same table and matched. Skip that and you get enhancement designed in a head office, aimed at impacts the community does not rank and missing the ones it does. The true cost of the conflict that follows a project’s misreading of local priorities is almost always larger than the cost of the engagement that would have prevented it.

Guard against elite capture and dependency

Enhancement done carelessly creates its own harms, and a design that ignores them is not shared benefit. It is a new problem wearing a friendly label. Two failure patterns show up again and again, and both have to be designed against from the start.

The first is elite capture. Benefits routed through a single leader, a committee, or a well-connected group get absorbed before they reach the people they were meant for. The result is not development. It is a widening of the very inequalities that fuel conflict in the first place. Guarding against it means transparency about who decides, who distributes, and who benefits, and it means structures that put those decisions in the open rather than in the hands of a few. An enhancement whose distribution cannot be seen is an enhancement that will be captured.

The second is dependency. A project that becomes the sole source of income, services, and infrastructure for a community creates a fragility that closure will one day expose brutally. The aim of good enhancement is the opposite: a resilient local economy that can stand without the operation, so that the region is stronger for the project having come and not hollowed out for its having left. That means favouring enhancements that build independent capacity, local enterprises, diversified livelihoods, functioning public services, over those that simply substitute the company for the functions of a state or a market. Design for the day the project leaves, from the day it arrives.

A framework for turning impacts into benefit

The Impact-to-Benefit Design Framework is a framework matrix that walks a project from containing harm to building shared value across five stages: exhaust the mitigation hierarchy, define the region’s real priorities, match those to genuine business drivers, choose the mechanism, and safeguard the design. Each stage names what to decide, the question that drives it, and the trap to avoid, so you can work down the left column stage by stage and read across to what each one demands in practice. Use it to structure the conversation between a project team and a community rather than to score anything: it is a sequence and a common language, not a checklist. The payoff is a defensible line from every enhancement back to both a community need and a business objective, the test that separates real shared value from a public-relations budget. Download it and put it on the table at your next design session.

Download the Impact-to-Benefit Design Framework

When benefit is contested, mediation makes it durable

Enhancement generates its own disputes, even when it is well designed. Communities disagree internally about priorities. Expectations outrun what a project can deliver. A benefit that helps one group is felt as neglect by another. These tensions are not a reason to retreat to bare mitigation. They are a reason to build the process that keeps enhancement fair and agreed as it plays out over years.

The adversarial default handles this badly. It lets grievances about distribution fester until they become the reason a project is blockaded, and then treats the blockade as a security problem rather than a design failure. The better path is structured, independent facilitation: a way to surface competing priorities, test them against what the project can sustain, and reach commitments that both the company and the community can live with and hold each other to. Mediation is what turns a contested benefit into a durable one, because it produces agreements that both sides own rather than terms one side imposed. That is the work the Social Accord Architecture is built for. It is the field-tested methodology I use to move a company and a community from an argument over who benefits to a shared, monitored plan for how value is created and distributed, designed for dual accountability so it holds when the pressure comes. If you are designing an enhancement strategy and want it built to survive contact with real community politics, reach me at thomas@thomasgaultier.com.

Start with one honest audit this week. Take your current community investment list and, for each item, write the specific community priority it serves and the specific business objective it serves. Anything that cannot name both is not shared value yet. It is a cost or a gift, and it will not hold. Redesign those items until each one earns its place on both sides of the table, because that is the only enhancement that protects livelihoods and investment together.

I am Thomas Gaultier. I mediate company-community disputes in mining, oil and gas, and energy projects, and I have resolved more than 2,000 claims across Sub-Saharan Africa and Europe. More about the work, or tell me what you are dealing with.

If the relationship around a project is under pressure, or heading there, let us talk.

A 30-minute call is enough for me to understand the situation and tell you honestly whether I can help. Active opposition, a social license problem, an FPIC process that needs an independent facilitator, a negotiation a community has to prepare for, or a conflict that is not public yet but will be. It makes no difference which side of the table you are on. No obligation, no generalist pitch.

Every first conversation is confidential.

Cover of Legacy Grievances and Historical Claims by Thomas Gaultier

New release, and the last one

Legacy Grievances and Historical Claims

The tenth and final volume completes the library. It is the field guide to harm that outlived the operation: transitional justice adapted to corporate disputes, successor liability when the asset changes hands, and the pathway behind more than two thousand resolved claims.