Written by Melvin Bosso
A Story About Mines, Money, and the People Who Keep It All Together
The sun hadn’t fully committed to rising yet when Maimouna Diallo set her coffee on the conference table at Tombouctou Mines headquarters. She liked the early quiet, no ringing phones, no hallway chatter, just the soft hum of the building coming to life. Today was the first of three sessions she’d been asked to lead with Nasr Ben Mohamed, and she wanted to be ready.
Nasr walked in two minutes early, notepad already open. He was known around TM as the guy who got things done, not flashy, not political, just relentlessly practical. He’d spent years running operations and now he was stepping into the most ambitious role of his career: leading cost transformation across every business unit and site in the company. He sat down, uncapped his pen, and looked at Maimouna like a man who’d already decided he wasn’t leaving until he had something real to work with.
“I don’t want to run another initiative that dies after six months,” he said, skipping pleasantries. “I want something that actually changes how we work.”
Maimouna smiled. She’d heard that before from leaders who meant it and from leaders who didn’t. She could already tell Nasr was the former. “Good,” she said. “Because that’s exactly what we’re going to build.”
She walked to the whiteboard and wrote four words, each on its own line, each underlined.
Engagement. Visibility. Risk. Sustainability.
“These aren’t buzzwords,” she said, turning around. “They’re the four things every cost transformation lives or dies by. Skip one, and the whole thing unravels. Nail all four, and you’ve built something TM will still feel in ten years.”
Nasr studied the board. “Walk me through them.”
Engagement, Maimouna explained, wasn’t about town halls or memos. It was about pulling the people closest to the work into the room where decisions get made. She told him about what happened at the Bourem business unit a couple of years back. The maintenance team had been sitting on ideas for months, frustrations, workarounds, small process hacks they’d figured out on their own. When a transformation team finally stopped lecturing them and started listening, something shifted. The technicians helped redesign the preventive maintenance schedule themselves, and within six months, downtime dropped by fifteen percent. Not because of a consultant’s slide deck. Because the people who lived the process every day finally got a voice in it.
“How do you get them to actually open up?” Nasr asked. “In my experience, frontline teams are skeptical of transformation programs. And honestly, they’ve earned that skepticism.”
“You start with listening sessions,” she said. “No PowerPoint. Just open questions and a closed mouth. You recognize their expertise publicly. And the most important thing, when you actually implement one of their ideas, you celebrate it loudly and you make sure everyone knows where it came from. Trust is built in those moments.”
Visibility was the second pillar, and Maimouna had a clear point of view on it. People don’t resist change because they’re lazy or stubborn. They resist it because they can’t see where they’re going or how far they’ve come. At Goundam, someone had the simple idea of putting digital dashboards on the screens in the break rooms, real-time production KPIs, updated daily. Workers started noticing patterns. Teams started talking about numbers that had previously lived only in management reports. It created a kind of healthy energy around performance that no motivational speech could’ve produced.
Nasr raised an eyebrow. “What if a site doesn’t have the budget for that kind of tech?”
“A whiteboard works,” she said, without hesitation. “A printed sheet pinned to the wall works. The tool matters a lot less than the habit. If people can see the plan and see the progress, they stay connected to it. That’s the whole point.”
The third pillar was risk mitigation, and here Maimouna was blunt. Every transformation program hits walls. Suppliers fall through, key people leave, budgets get cut, external shocks hit from directions nobody anticipated. The question isn’t whether things will go wrong, it’s whether you’ve thought hard enough about *what* could go wrong and built a plan for it. She described how TM’s procurement team, during a major overhaul of their supply chain, had spent serious time mapping out which suppliers were single points of failure. When a global supply crunch hit, they weren’t scrambling. They had backup options already vetted and ready.
“How do you keep risk management from becoming a checkbox exercise?” Nasr asked. He’d seen it before, thirty-page risk registers that nobody looked at after the kickoff meeting.
“You make it a living conversation, not a document. Risks get reviewed in every project meeting. They’re part of the rhythm, not a separate process.” She paused. “If it feels like bureaucracy, you’ve already lost.”
The fourth pillar was sustainability, and Maimouna said this one out loud slowly, like she wanted it to land. “The real test of any transformation program is what it looks like two years after you’ve left the room. Are the new ways of working embedded? Are they improving? Or has everything quietly drifted back to how it was before?”
TM had learned this the hard way on a production standardization effort years ago. The results were impressive during the program. Then the program ended, the external team wrapped up, and six months later it was as if nothing had changed. They went back, assigned process owners, set up quarterly audits, and ran refresher training. Three years on, those improvements were still delivering value. The difference wasn’t the original intervention. It was the infrastructure they built around sustaining it.
In their second session, Maimouna took Nasr deeper into the actual work, the seven streams of activity that make up a real transformation program.
Performance management, she told him, had to start local before it went company-wide. You couldn’t design a system at headquarters and push it down. You had to go into each business unit, map what meetings were already happening, what reports were already being produced, what KPIs people were already tracking, and find out where the overlaps and gaps were. At Bourem, that exercise alone revealed that the weekly production meeting and the maintenance review were covering 70% of the same ground. Consolidating them freed up hours every week and made the remaining conversations sharper. From there, you design what the ideal routine looks like, you pilot it in one place, you adjust based on what you learn, and then, only then, you roll it out company-wide. TM’s central office eventually built a performance portal that pulled live dashboards from every business unit. But it only worked because the foundation was solid at each site first.
Culture, Maimouna said firmly, isn’t a poster on the wall. It’s what leaders do when nobody’s watching, and what the organization rewards and punishes over time. TM had run a program called “Leaders as Coaches” that trained supervisors to give real-time feedback instead of saving everything for annual reviews. Employee engagement scores went up twelve percent in a year, not because of a policy change, but because people started feeling heard on a daily basis. When Nasr asked about resistant leaders, Maimouna didn’t sugarcoat it. “Start with the willing ones and let their results do the talking. Peer influence moves faster than top-down mandates. But don’t avoid the hard conversations with people who are actively working against the change. You can’t afford to.”
Communication, she continued, was the thing that most programs underinvested in. People’s imaginations fill any vacuum of information, and they almost always fill it with something worse than the truth. At Kidal, a simple WhatsApp group for shift updates completely transformed information flow between teams. Not sophisticated, not expensive, just consistent. The medium didn’t matter. The regularity did. Even at remote sites with limited connectivity, a daily huddle at shift change or a physical noticeboard updated every morning could do the job.
On the operations side, Maimouna pushed hard on standardization. Gao’s adoption of a standardized maintenance playbook had lifted equipment uptime by ten percent, not through magic, but through consistency. When everyone follows the same baseline, you can actually measure what works and what doesn’t. When every site does it differently, you’re just managing noise. But she was careful to add that standardization wasn’t the ceiling. It was the floor. “Set the baseline, then encourage sites to improve on it. If someone in Hombori figures out a better way, we want to know about it and share it everywhere.”
Benefits review was where transformation programs often got embarrassed. You announce savings. Someone challenges the numbers. Nobody can quite explain what’s been measured against what. Maimouna had seen it kill the momentum of otherwise good programs. The fix was simple but required discipline: set baselines early, track results against those baselines consistently, and report to leadership regularly with honest numbers. TM’s benefits review committee used monthly scorecards, and when discrepancies showed up, they caught them early instead of letting them compound into credibility problems. To Nasr’s question about gaming the numbers, she had a straightforward answer: independent audits and a focus on leading indicators, not just the headline savings figure.
Procurement, in Maimouna’s framing, was about much more than squeezing suppliers. It was about value, risk, and building relationships that held up under pressure. By renegotiating its haulage contracts strategically, TM’s procurement team had saved eight percent on logistics costs, not by being adversarial, but by coming to the table with data and a long-term perspective. Getting business units to accept centralized sourcing was always a political challenge, but the answer was to show them the concrete benefits and then involve them in the process. Nobody fights a decision they helped make.
Organization design was often the most anxiety-inducing workstream, and Maimouna didn’t pretend otherwise. The restructuring at Timbuktu had removed management layers that had accumulated over years, and the decision-making speed improvement was immediate and measurable. But getting there required being transparent early about what was changing and why, involving people in the design where possible, and being honest that the purpose was to make the organization work better, not to eliminate people for the sake of a smaller headcount.
***
By their third session, Nasr had filled most of his notepad. Maimouna could see he was ready to move, he just had one more big question.
“How do I know where to start? Every site has different problems, different cultures, different levels of maturity. How do I prioritize?”
Maimouna leaned back in her chair. “You assess two things: impact and readiness. Where is there already some momentum? Where is there a burning platform, a problem so obvious and urgent that people are already motivated to change? That’s your entry point. Quick wins build credibility, and credibility is what lets you take on the harder stuff.”
The PMO, the program management office, was, in her words, the nerve center that held everything together. Not a bureaucratic layer that slowed things down, but a coordination function that kept workstream leads aligned, flagged risks before they became crises, and made sure the executive team had an accurate picture of progress. The instinct to micromanage through the PMO was always there and always counterproductive. The job of the PMO was to remove obstacles, not to create new ones.
And then, winding down, Maimouna came back to sustainability one last time. She called it the ultimate deliverable. Not the savings announced on a program launch slide, not the number of SOPs documented, not even the employee engagement scores, but whether, when the dust settled and the program team had moved on, the new ways of working were still alive and improving. TM had started recognizing employees who sustained improvements over time through what they called the “Sustainability Champions” program. The recognition wasn’t elaborate. But it sent a signal that the finish line wasn’t the launch. The finish line was what happened after.
***
The final session ended in the same conference room where it had started, the same light coming through the same windows. Maimouna looked at Nasr directly.
“Leading a cost transformation is as much about people as it is about processes. Engage your teams. Make the plan visible to everyone who has to live it. Think hard about what can go wrong and get ahead of it. And build everything with one question in mind: will this still be working in three years? Adapt everything to the specific context of each site and business unit, but never compromise on those four pillars. That’s how you deliver something real for Tombouctou Mines.”
Nasr closed his notepad and sat with it for a moment. For the first time since stepping into this role, he didn’t feel like he was staring down an impossible task. He felt like he had a map.
“Thank you, Maimouna,” he said. “Now I know where to start.”
Tò
– Nasr, an operations leader at Tombouctou Mines, is coached by Maimouna to lead a company-wide cost transformation built on four core pillars: engagement, visibility, risk management, and sustainability.
– They focus on involving frontline teams so improvements are co-created, with past examples showing big gains when technicians and supervisors help redesign processes instead of having solutions imposed on them.
– Visibility is emphasized through simple but consistent performance routines and dashboards or whiteboards so everyone can see plans, progress, and their role in hitting targets.
– Maimouna pushes Nasr to treat risk management as a live habit in every meeting, using supplier mapping and contingency plans so disruptions or global shocks don’t derail operations.
– Multiple workstreams, performance management, culture and leadership, communication, operations, benefits tracking, procurement, and organization design, are built up locally first, then integrated across TM once they actually work on the ground.
– A lean PMO acts as the “nerve center,” coordinating these streams, unblocking issues, and tracking a few critical KPIs like cost savings, process compliance, employee engagement, and supplier performance.
– By the end, Nasr understands that success depends less on fancy tools and more on engaging people, adapting the approach to each site, and building ways of working that are still alive and improving years later.
Leave a Reply