The Accountable Executive's Dinner Test: Can You Explain Your Tailings Strategy to Your Family?
The Accountable Executive’s Dinner Test: Can You Explain Your Tailings Strategy to Your Family?
Picture this: You’re at a family dinner. Your teenage daughter asks, “So what exactly do you do at work?” You start explaining your role overseeinAnd it starts with taking the test.
Does your GISTM compliance system help you understand or just help you comply?ailings facilities. She looks confused. Your spouse jumps in: “You know, the waste from mining.” Your mother-in-law, who’s been half-listening, suddenly perks up: “Isn’t that what caused that disaster in Brazil?” The table goes quiet. Everyone’s looking at you. Can you explain - in plain language, without jargon, in under three minutes - exactly how you ensure the facilities you’re responsible for won’t be the next headline? If you can’t pass the dinner test, you have a problem. And it’s not a communication problem - it’s an understanding problem. Why This Matters More Than You Think GISTM designates someone in your organization as the “Accountable Executive” (Requirement 8.4). This isn’t just a box on an org chart. It’s the person who must answer - to the CEO, to the Board, to regulators, and yes, to their own conscience - for the safety and integrity of tailings facilities. But here’s what we’ve discovered working with mining operations worldwide: Many Accountable Executives can navigate complex technical documentation but struggle to articulate the core safety case in simple terms. This isn’t about dumbing things down. It’s about clarity of thought. As Einstein supposedly said: “If you can’t explain it simply, you don’t understand it well enough.” The dinner test reveals what you really understand versus what you think you understand. The Jargon Trap: When Complexity Hides Confusion Open any Design Basis Report. You’ll find:
“The facility employs centerline construction methodology with upstream raises” “Piezometric response within acceptable parameters relative to design assumptions” “Factor of safety exceeds 1.5 under static loading conditions” “Consequence classification determined per ICOLD methodology”
Now imagine explaining what any of that means to your 12-year-old nephew. The problem isn’t that technical language exists - it’s essential for precision among specialists. The problem is when we use it as a substitute for understanding. Consider this real conversation from a site visit: Auditor: “What’s your tailings management strategy?” Site Manager: “We follow our TMS which integrates with our ESMS, maintain our OMS manual, conduct TARPs according to the DBR, and have regular EOR reviews coordinated by the RTFE reporting to the Accountable Executive.” Auditor: “Okay, but why do you do those things?” Site Manager: (pause) “Because GISTM requires it.” Auditor: “What problem are they solving?” Site Manager: (longer pause) ”…To reduce risk?” This is the jargon trap. The site manager can recite the alphabet soup of acronyms, but can’t articulate the fundamental purpose: We’re managing a facility that, if it failed, could harm people and the environment. These systems help us understand risks, monitor performance, respond to changes, and maintain safety throughout the facility’s life. The Five Questions Your Family Would Ask (And Why You Need Answers) Let’s run through the dinner test. Here are the questions a reasonably intelligent non-expert would ask - and what your struggle to answer them reveals about your actual understanding. Question 1: “What Could Go Wrong?” The jargon answer: “We’ve identified credible failure modes including slope instability, liquefaction under seismic loading, overtopping events, and foundation issues, all assessed per consequence classification methodology.” Your teenager’s face: Blank stare The dinner test answer: “Imagine a massive pile of wet sand and rock that we’ve engineered to stay stable. The main risks are: the slope could slide, an earthquake could shake it apart, too much water could overflow the top, or the ground underneath could be weaker than we thought. We’ve identified which scenarios are realistic for our site and designed against each one.” What this reveals: Do you actually understand your site-specific failure modes, or are you reciting generic possibilities? Can you explain why liquefaction is a concern at your facility but not at the one 50km away? Can you articulate what makes a failure mode “credible” versus merely theoretical? The deeper test: If you can’t explain what could go wrong in plain language, how confident are you that your risk assessment is comprehensive? Risk identification isn’t about checking boxes on a standard list - it’s about understanding your unique facility in its unique context. Question 2: “How Do You Know It’s Safe?” The jargon answer: “We maintain a comprehensive monitoring system with piezometers, inclinometers, and settlement monuments, with data analyzed per the Observational Method and TARPs triggered at predetermined thresholds reviewed by the EOR.” Your spouse’s response: “That sounds like a lot of equipment. But are you actually safe?” The dinner test answer: “We know it’s safe three ways: First, we designed it with huge safety margins - like building a bridge to hold ten trucks when only two will ever cross. Second, we constantly monitor it like a patient in intensive care - measuring water pressure, movement, and settlement. If anything starts trending wrong, we have action plans that kick in automatically. Third, we have independent experts review everything regularly to catch what we might miss.” What this reveals: Do you understand the defense-in-depth philosophy, or do you think safety comes from a single source? Can you articulate the relationship between design conservatism, operational controls, and monitoring? Do you truly grasp how these layers work together? The deeper test: Many Accountable Executives can describe their monitoring systems in detail but struggle to explain what decisions change based on the data. If you collect data but don’t use it to drive actions, you’re not monitoring - you’re just measuring. Question 3: “What Happens If You’re Wrong?” The jargon answer: “We’ve conducted breach analysis modeling inundation zones, developed an EPRP in coordination with project-affected people and public sector agencies, and established protocols for emergency response and long-term recovery per GISTM Requirements 13 and 14.” Your mother-in-law: “So you do think it could fail?” The dinner test answer: “We design assuming nothing will go wrong, but we plan assuming it might. We’ve modeled what would happen if the facility failed - where water would go, how fast, who would be affected. We’ve worked with downstream communities on evacuation plans. We’ve coordinated with emergency services. We’ve set aside funds for recovery. It’s like wearing a seatbelt - you don’t expect to crash, but you prepare anyway.” What this reveals: Can you distinguish between planning for failure and expecting failure? Many executives struggle with this - they worry that acknowledging failure scenarios undermines confidence in the design. But the opposite is true. The deeper test: If discussing emergency response makes you uncomfortable, ask yourself why. Is it because you don’t want to alarm people? Or is it because you haven’t actually worked through the scenarios yourself and don’t want to confront what they reveal? Question 4: “Who’s Actually in Charge?” The jargon answer: “We have clearly defined accountabilities with the Accountable Executive responsible for strategic oversight, the RTFE managing day-to-day operations, the EOR providing design authority, and the ITRB conducting independent review, all operating within our governance framework per Requirements 8 and 9.” Your daughter: “So… is that you? Are you the one in charge?” The dinner test answer: “Yes, I’m accountable. That means if something goes wrong, I answer for it. But I don’t do everything myself - I have a site engineer who manages daily operations, a specialized engineering firm that designed the facility, and independent experts who check our work. Think of it like a hospital: I’m like the chief of surgery - ultimately responsible, but working with specialists who bring different expertise.” What this reveals: Do you actually understand your role versus simply accepting a title? Many Accountable Executives can describe the org chart but struggle to articulate what accountability means in practice. The deeper test: Here’s the real question: If your RTFE makes a decision you disagree with about the facility, whose decision wins? If you say “theirs, they’re the technical expert,” you don’t understand your role. If you say “mine, I’m accountable,” but can’t explain why you’d override technical judgment, you also don’t understand your role. The answer requires understanding the difference between accountability (which you hold) and technical authority (which you delegate but must understand well enough to challenge). Question 5: “How Do You Know This Will Still Be Safe in 50 Years?” The jargon answer: “We’ve developed closure designs demonstrating feasibility of safe closure, established financial provisions for perpetual care, incorporated climate change projections into the knowledge base, and implemented Adaptive Management protocols per Requirements 3.1 and 5.7.” Your spouse: “Wait, you mean this thing has to be safe forever?” The dinner test answer: “Essentially, yes. Unlike most infrastructure that has a design life of 50-100 years, tailings facilities need to be stable indefinitely. So we design for closure from day one - what it will look like when mining stops, how water will be managed, how we ensure stability for centuries. We also set aside money now for future maintenance. And we update our plans as we learn more, because what we understand about climate or geology will change over time.” What this reveals: Do you grasp the perpetual nature of tailings facility responsibility? Many executives think in terms of mine life (20-30 years) rather than geologic time (centuries to millennia). The deeper test: Can you articulate specifically how your facility will transition from operation to closure? Not generic platitudes about “safe closure design,” but actual understanding of post-closure water management, long-term stability mechanisms, and who will be responsible for monitoring and maintenance after your company exits. The Signal That You Don’t Understand: Common Red Flags Red Flag #1: You Can’t Explain It Without a Slide Deck If your answer to “tell me about your tailings strategy” starts with “let me pull up a presentation,” you don’t understand it well enough. Why this matters: In a crisis, you won’t have slides. When the Board asks tough questions, you won’t have time to prepare. When communities demand answers, they won’t sit through a technical presentation. The test: Can you draw your tailings facility on a napkin and explain its key features, risks, and controls? If not, you don’t have a mental model - you have memorized materials. Red Flag #2: You Answer Different Questions Differently Board meeting: “Our facilities have robust design criteria with multiple layers of review and conservative factors of safety.” Community meeting: “We follow international best practices and exceed regulatory requirements.” Internal meeting: “We need to upgrade monitoring at Facility B because performance is outside expected parameters.” Wait - which is true? All of them might be technically accurate, but the different framings reveal something concerning: you’re tailoring your message to your audience rather than consistently articulating the same truth in accessible ways. The dinner test reveals this immediately: You can’t tell your family one thing, your Board another, and communities a third version. The truth is the truth. If you can explain it clearly to your family, you can explain it clearly to anyone. Red Flag #3: You Rely on “Trust Me, I’m the Expert” Your nephew: “But how do you know the earthquake design is strong enough?” Poor answer: “We use industry-standard probabilistic seismic hazard analysis methodology.” Better answer: “We study all the earthquakes that have happened in this region historically, and we design for earthquakes bigger than anything that’s occurred. Then independent experts review our work to make sure we didn’t miss anything.” What this reveals: If your explanation boils down to “it’s complicated and you wouldn’t understand,” you’re relying on authority rather than understanding. That’s fine for brain surgery, but you’re the Accountable Executive - you’re supposed to understand and be able to explain. Red Flag #4: You Can’t Connect Requirements to Outcomes Someone asks: “Why do you need to update your knowledge base every five years?” Poor answer: “GISTM Requirement 2.1 mandates it.” Better answer: “Because conditions change. Climate patterns shift, downstream development happens, our understanding of material properties improves, and seismic hazard models get updated. If we’re making decisions based on 10-year-old information, we might be missing critical changes.” What this reveals: Do you understand the purpose behind requirements, or just the requirements themselves? Compliance isn’t the goal - safety is. The requirements are means to that end. The test: For any GISTM requirement, can you explain what problem it solves and what would happen if you didn’t do it? If not, you’re following a checklist without understanding the underlying risk management logic. Red Flag #5: You Can’t Explain Trade-offs Your spouse: “Why don’t you just use the safest possible design for everything?” Poor answer: “That would be economically prohibitive.” Better answer: “We actually do use very conservative designs - far more than for most infrastructure. But ‘safest possible’ could mean building a dam three times larger than needed, which creates its own risks during construction and requires disturbing much more land. Engineering is about finding the right balance: conservative enough to manage risks appropriately, but not so over-engineered that you create new problems. That’s why we use consequence classification - higher potential consequences get more conservative design.” What this reveals: Real understanding means grasping trade-offs and being able to explain the reasoning behind design choices. If you can’t articulate why you didn’t just “make everything maximum safety,” you don’t understand your risk-based approach. The Exercise: Actually Take the Test Here’s your homework: This weekend, sit down with someone who loves you but knows nothing about mining. Tell them: “I need your help with something. I’m going to explain what I do at work and why it matters. I need you to stop me every time I use a word you don’t understand or say something that doesn’t make sense. Okay?” Then try to cover:
What a tailings facility is and why they exist What the main risks are at your facility specifically How you manage those risks Who’s responsible for what What would happen if something went wrong How you prepare for that possibility
Rules:
No acronyms unless you immediately define them in plain language No slides, no reports, no props - just you talking They must interrupt you every time they’re confused You must answer their questions without saying “it’s complicated”
Set a timer for 10 minutes. If you can’t cover the basics in 10 minutes of plain language, your understanding isn’t clear enough. What This Reveals About Your Organization If you, as the Accountable Executive, struggle with the dinner test, what does that say about others in your organization? Consider this cascade: If you can’t explain your tailings strategy simply — You probably can’t effectively challenge your RTFE when something doesn’t make sense If you can’t articulate risks clearly — Your Board probably doesn’t understand them well enough to provide meaningful oversight If you can’t describe your monitoring program’s purpose — Your operations team probably sees it as compliance theater rather than critical risk management If you can’t explain consequence classification — Your community engagement team probably can’t build trust with stakeholders If you can’t connect requirements to outcomes — Your organization is probably checking boxes rather than managing risks The dinner test isn’t just about you - it’s a diagnostic for your entire organization’s understanding. The Path to Clarity: Five Practices Practice #1: The “Why” Chain For any aspect of your tailings management, ask “why” five times: Example:
We conduct Dam Safety Reviews — Why? To get independent assessment of facility safety — Why do you need independent assessment? Because internal teams might miss issues or be reluctant to raise concerns — Why might they miss issues? Because familiarity can create blind spots and organizational culture can discourage bad news — Why does that matter? Because undetected problems grow into crises, and we need systems that catch issues early — Now you’re getting to the real purpose
Try this with:
Your monitoring program Your EOR relationship Your knowledge base updates Your ITRB structure Your consequence classification
If you can’t complete the “why” chain without circling back to “because GISTM requires it,” you don’t understand the underlying risk logic. Practice #2: The Analogy Bank Develop plain-language analogies for technical concepts: Factor of safety = “Like designing a bridge for ten trucks when only two will cross” Observational Method = “Like a patient in ICU - constantly monitored with action plans if vitals change” Consequence classification = “Like stadium safety - larger venues need more stringent requirements because more people could be affected” Brittle vs. non-brittle failure = “Like glass vs. metal - glass shatters suddenly, metal bends and gives warning” ALARP = “Like crossing a street - you can’t eliminate all risk, but you can reduce it until further efforts are unreasonably difficult compared to the tiny additional benefit” Build your own analogy bank. Test them on non-technical people. Refine them until they work. Practice #3: The Board Brief You’d Actually Want to Read Write a two-page memo to your Board about your tailings facilities. Requirements:
No acronyms in the main text (definitions in footnotes if needed) No sentences over 25 words At least one visual (map, diagram, chart) Must address: current status, key risks, mitigation measures, next steps
If you can’t write it simply, you don’t understand it clearly. Then - and this is the key part - ask someone from finance or legal (someone smart but not technical) to read it and tell you what they learned. If they can’t accurately summarize your key points, your writing isn’t clear enough. Practice #4: The Crisis Communication Simulation Imagine this scenario: There’s been a minor incident at your facility. Nothing catastrophic, but concerning enough that local media is asking questions. You have 60 seconds on camera. What do you say? Write it out. Read it aloud. Time it. Your statement must:
Acknowledge what happened Explain why it’s not a catastrophe (if it’s not) Describe what you’re doing about it Demonstrate you understand the situation Build confidence without dismissing concerns
If you can’t articulate this clearly, you’re not ready for crisis communications. And if you think “I’ll just let the PR team handle it,” remember: you’re the Accountable Executive. When things go wrong, it’s your face on camera, your name in the story. Practice #5: The Socratic Method With Your Team In your next RTFE meeting, try this approach: Instead of asking “What’s the status of the monitoring program?” ask:
“What are we trying to learn from our monitoring?” “What would it tell us if piezometer readings started trending up?” “How quickly would we know if something was wrong?” “What decisions would change based on different monitoring results?”
Listen to how they answer. Are they reciting procedures, or demonstrating understanding? Are they connecting data to decisions, or just reporting numbers? The quality of your team’s understanding reflects the quality of your leadership. If they can’t articulate the “why” behind what they do, you need to work on building that understanding - starting with your own. The Real Reason This Matters: Crisis Decision-Making Here’s the uncomfortable truth: The dinner test predicts how you’ll perform in a crisis. When something goes wrong - monitoring shows unexpected trends, unusual seepage appears, performance deviates from predictions - you need to make decisions quickly with incomplete information. In that moment:
You can’t call a consultant to interpret data You can’t spend three days reviewing technical reports You can’t hide behind jargon and hope someone else decides You need to understand what’s happening, what it means, what options you have, and what decision to make
If you can’t explain your tailings management simply when everything is fine, you won’t be able to think clearly when everything is on fire. Consider the Accountable Executive who can articulate: “Our main concern is slope stability. We monitor it with inclinometers measuring movement and piezometers measuring water pressure. If readings exceed thresholds, we have three levels of response: increased monitoring, operational restrictions, or emergency drawdown. Right now we’re at level one, which means…” That executive can make informed decisions under pressure. Compare to the executive who says: “We have comprehensive monitoring per the OMS manual with TARPs established by the EOR consistent with the DBR and…” That executive is going to freeze or defer to others because they don’t have a clear mental model. The Accountability Question That Haunts Here’s what keeps thoughtful Accountable Executives awake at night: If something goes wrong at my facility - really wrong - and I have to explain to victims’ families, to investigators, to the public why I thought it was safe… will I have an answer? Not a legal defense. Not a technical explanation. A human answer to the question: “How could you let this happen?” The dinner test is practice for that moment you hope never comes. If you can explain to your family - right now, over dinner - why your facilities are safe, what you’re doing to keep them that way, and how you’re prepared if something goes wrong, then you can answer that question. If you can’t, you’re not really accountable. You’re just the person with the title. The Transformation: From Checklist to Understanding Many Accountable Executives start with GISTM as a compliance checklist:
— Appoint RTFE — Engage EOR — Establish ITRB — Conduct risk assessment — Update knowledge base — Develop EPRP
But compliance isn’t understanding. The transformation happens when you can explain the system those requirements create: “We have people with clear responsibilities, supported by specialized expertise, with independent oversight, making risk-informed decisions based on current knowledge, prepared for emergencies, and communicating transparently with stakeholders. Each piece reinforces the others. The RTFE manages daily operations but the EOR provides design authority. The ITRB challenges both. I ensure they have resources and take action on what they find. The Board holds me accountable. Communities know what we’re doing and why. It’s a system of overlapping responsibilities and checks that makes failure less likely and ensures we’re prepared if it happens anyway.” That’s understanding. And you can explain it to anyone. Your Compliance Tool Should Enable This Understanding A sophisticated GISTM compliance platform shouldn’t just track whether you’ve completed requirements. It should help you understand the system those requirements create. Questions your tool should help you answer:
“Show me all the ways we monitor slope stability and what actions trigger at different thresholds” “If consequence classification changes, what else changes automatically?” “Connect my EPRP to my breach analysis to my community engagement” “When was the last time each oversight layer identified an issue, and what happened?” “What decisions have we made based on knowledge base updates?”
If your compliance tool is just a checklist tracker, it’s enabling box-checking, not understanding. The dinner test works because it forces you to mentally integrate disparate pieces into a coherent whole. Your compliance system should do the same - help you see the forest, not just catalog trees. The Invitation: Take the Test This week, don’t just read this article and nod along. Actually do the dinner test. Find someone who:
Cares about you Knows nothing about mining Will be honest when you’re not making sense
Set aside 15 minutes and explain:
What you’re accountable for What could go wrong How you prevent it How you’d respond if it happened anyway
Record yourself (audio is fine). Then listen back. Count how many times you:
Used an acronym Said “it’s complicated” Couldn’t answer a simple question Circled back to “because regulations require it” Relied on “trust me” instead of explanation
Then ask yourself: If I can’t explain this to my family, do I really understand it? The uncomfortable answer might be no. And that’s okay - recognizing the gap is the first step to closing it. Because here’s the thing: You’re the Accountable Executive. When something goes wrong, “I was following the technical experts’ advice” isn’t an answer. “I was compliant with the standard” isn’t an answer. “It’s complicated” definitely isn’t an answer. The only answer is: “I understood the risks, I managed them appropriately, and here’s why I believed the facility was safe.” Can you give that answer right now? Over dinner? In plain language? To people you love? If not, you have work to do. And it starts with taking the test.
Does your GISTM compliance system help you understand or just help you comply? [Discover tools that build insight, not just track checkboxes]