Working With Donaldson And Dunfee's Framework In Practice
The integrative social contracts theory (ISCT) approach to business ethics can feel abstract until you actually try to apply it inside an organization. I spent a lot of time dealing with exactly this problem while advising a mid-size logistics company that was expanding into Southeast Asia and kept running into situations where local customs directly contradicted their corporate code of conduct. The tension between what the handbook said and what actually kept operations running was exhausting to manage. This is the textbook by Thomas Donaldson and Thomas W. Dunfee that lays out ISCT and gives it a structured way to resolve those exact tensions. The second edition updated some of the earlier material and clarified the hypernorm concept, which is central to how the framework actually works. It is not a quick read, but it is the most practical attempt at a middle ground between absolute ethical rules and cultural relativism that I have found. The book organizes its argument around three core moves: establishing hypernorms (fundamental principles that all legitimate communities accept), identifying thick norms (the culturally specific practices that are acceptable within a given community), and using the call process to resolve conflicts when they arise. That third element is where most people stumble, and it is also where the real utility of the book sits.
How To Use It Without Getting Stuck In Theory
Start by mapping your organization's existing code of conduct against the hypernorm list the book provides. You do not need to accept every single one, but you should be able to justify why you have accepted or rejected any particular principle. The authors include a fairly comprehensive list covering human dignity, basic rights, proportionality, and mutual benefit. Any policy you cannot map onto at least one of these needs reworking before it will survive scrutiny from either side of a cross-cultural dispute. The call process is the mechanism they propose for resolving conflicts between thick norms and hypernorms. When a local practice conflicts with your corporate standards, you do not just default to headquarters. You run it through the call process: identify the competing norms, assess whether either violates a hypernorm, check whether there is sufficient community consensus around the thicker norm, and then make a decision with documented reasoning. This takes about an hour per case if you are organized, or three days if you are winging it. I had a situation where a supplier in Vietnam was offering expedited shipping at a cost that required paying a local customs facilitator what the United States would call a grease payment. Our code prohibited it. Vietnamese norms around the practice were ambiguous enough that calling it a bribe versus a standard facilitation fee depended entirely on who you asked. Running it through the call process, we determined that the payment did not violate a clear hypernorm because it was transparent, routinely expected, and did not undermine fair competition. We documented that reasoning, created a written policy exception for that corridor, and moved on. Without the framework, we would have just banned it outright and lost a competitor advantage, or approved it silently and exposed ourselves to compliance risk.
Common Mistakes People Make
The most frequent error is treating hypernorms as fixed endpoints rather than as a starting point for reasoning. They are not exhaustive. No list covers every scenario. If you treat the book as a decision tree that spits out answers, you will hit dead ends quickly. The framework is designed to be used as a reasoning tool, not a substitute for judgment. A second mistake is ignoring the community legitimacy requirement. Thick norms only count if they come from a genuinely authentic community practice, not from whatever local management team happens to want permission to cut corners. Assessing authenticity takes real investigation. I have seen companies use ISCT language to justify practices that were clearly invented by a regional office after the fact. The framework catches this if you apply it honestly, but it requires more effort than a quick legal review. A third issue is underestimating the time cost. Documenting each call process decision properly means writing down the norms in conflict, the hypernorms involved, the community evidence, and the final reasoning. This usually adds about twenty minutes per case on top of the decision itself. Over a year, for a company dealing with multiple regions, that is not trivial. Some organizations skip the documentation and then fail the exercise entirely when it matters during an audit or lawsuit.
Get the Full Details
Where The Framework Falls Short
It does not handle power imbalances well. A subsidiary in a developing market facing existential pressure to conform may not have the same community legitimacy as a long-established practice, but ISCT gives you no real tool to measure that difference. The framework assumes relatively communities negotiating norms, which is not always the reality in multinational operations. It also struggles with entirely novel ethical situations that predate any existing norm. AI governance, data privacy in new markets, and platform economy labor questions all fall into this category. There is no existing thick norm to anchor to, and hypernorms alone are too abstract to guide specific operational decisions. You can use the framework to reason through them, but you will be doing more original philosophical work than the book itself leads you to expect. If your primary need is a practical compliance checklist, you might be better served by ISO 37001 for anti-bribery management systems or the OECD guidelines for multinational enterprises. Those give you concrete procedural requirements. Donaldson and Dunfee's approach is better suited for the cases those systems leave unresolved, which is often exactly where the hardest decisions happen.
What To Read First And What To Skip
The introductory chapters cover the basic architecture and are worth reading straight through. Chapters four through six on hypernorms, thick norms, and the call process are the operational core. The later chapters on applications tend to repeat the same logic in different contexts, so you can skim those unless a particular industry case is relevant to you. The bibliography is useful if you want to go deeper, but most people will not need it unless they are building an internal training program. I keep a copy at my desk not because it answers questions for me, but because it forces me to ask the right questions before I answer them. That is probably the most accurate way to describe what this book actually does in practice.
