At the dynamic heart of Ashanti Steel’s sweeping transformation, I sat among voices both familiar and newly introduced—leaders, planners, relentless skeptics, and the engineers of change. The rooms and conference calls often hummed with unresolved tension—interlacing disruption, uncertainty, and the pursuit of better ways. As I reflect on the methodology we lived, it is evident to me—not with pride, but humility—that we forged a path not by imposing order, but by daring to harness chaos as a wellspring for creativity and true organizational ownership.
The Spark: From Discontent to Possibility
It began, as true change must, not with answers but with raw discontent. Inventory was misplaced, forecasts proved unreliable, customer trust was dented, and the language of internal blame became familiar. But amidst this, I recognized something visceral: disruption was already here. Ashanti Steel’s past successes had outgrown their processes; this friction—the messiness we all complained about—was itself the truest evidence of potential.
Our partners at Zambuka Management Consulting Services did not treat this as a sickness to be cured, but as the very precondition for evolution. Diagnostic interviews, data dives, and work sessions surfaced sharp contradictions: one team celebrated a process as mature, another called it broken. There was no agreement on fundamental definitions—what was customer service or sales support—nor, starkly, on who truly “owned” either the inventory or the forecast.
While some might shrink from such volatility, we chose to lean in. In complexity and the unknown, I saw the chance for Ashanti Steel to become not just more efficient, but more imaginative. Our way was not to subdue conflict, but to cultivate and direct it.
Meetings: Inviting Disruption, Not Containment
Our meetings, if you could call them that, rarely followed a script. The structure Zambuka brought was robust but porous—deliberately so, for rigidity would kill the surprises that spark real innovation.
Preparations were not about smoothing the path, but about gathering the raw, undigested truths: errant data points, tales of missed orders, anecdotes of customer frustration, and admissions of internal distrust. We opened with provocations, not platitudes: “What are our blind spots?” “Whose forecast is really driving us?” “Why can’t we sustain trust across the business?”
Rather than quiet the room, these questions often amplified it. Sparks flew between Sales and Supply Chain, between North America and global teams, between those who wanted quick fixes and those who sought frameworks. Each encounter was less a step in a march than a swirl of perspectives, a necessary turbulence. What coherent plans emerged had survived the test of chaos.
I recall how fascinating it was to see action points at the end of each meeting. They were mapped with the explicit understanding that some were points of agreement, others of passionate dispute. Nothing was hidden; even irreconcilable tensions were surfaced — sometimes left suspended for resolution in the next cycle.
Ownership Born of Willing Conflict
A pivotal lesson for Ashanti Steel: ownership is not assigned, it is earned—often in the heat of disagreement. Our approach encouraged—even demanded—ownership by giving every stakeholder a stake in uncertainty. The more individuals wrestled with ambiguity, the more invested they became in untangling it.
This philosophy shaped everything. Forecasting, for instance, was recreated not as a closed technical exercise, but as a continuing negotiation, balancing data-driven projections with the on-the-ground wisdom of sales teams. The process accepted that errors would persist and that only ongoing, collective adjustment would narrow the gap between expectation and fulfillment.
It wasn’t always graceful: teams clashed over KPIs, process ownership, even the proper naming of functions. What made the difference was that these moments of friction were not seen as meetings-gone-wrong, but as sites of true creative labor. Chaos, in these rooms, became not something to be “managed,” but something to be shaped—and, when possible, celebrated.
Massy: The Personification of Creative Disruption
Massy—brilliant, driven, and divisive—became both symbol and crucible for all we were trying to accomplish. Where traditional change programs might have tried to reshape her or move her quietly aside, we recognized that her friction with the organization was not a flaw to excuse but a spark to be ignited.
Massy was, as I came to describe, a Formula One engine stuffed into a Volkswagen chassis. Her technical expertise was rare, her impatience with mediocrity legendary. She clashed with colleagues unafraid, her standards relentless, her appetite for systemic rigor infectious though sometimes bruising.
Initially, some recoiled at her sharp elbows and uncompromising ways. “She’ll never fit,” I heard whispered in corridors more than once. But the truth was simpler: the old model couldn’t hold her. Our task was not to force Massy to conform, but to let her transform the model.
We extracted her from line management and assigned her the lead on high-impact project work. Released from hierarchy but given full accountability for outcomes, Massy’s disruptive energy became fuel for rapid learning and deeper engagement. She was tasked not to “run the machine,” but to help build it anew—guiding ERP implementation, designing ideal-state forecasting, and challenging assumptions at every turn. Under this mandate, she thrived, and many who once distrusted her came to respect—if not always love—her relentless drive for progress.
What we learned is unequivocal: chaos, when embodied thoughtfully by people like Massy and supported by leadership with the courage to channel it, is an engine of ownership. Teams stopped merely following orders and began asking, “How should this work? How can I make it better?”
Creativity, Design, and the Art of Not Knowing
The iterative design phase that followed was intentionally loose-boundaried. Zambuka did not offer us a lockstep plan to march through, but instead gave permission to experiment, adapt, and at times, blow up half-finished solutions. Roles were sometimes left fluid, forcing negotiation and self-organization. Processes were designed in draft, tested in practice, then revised or replaced. Language itself—what we called a given function, or who owned a decision—became something to be debated, changed, or retired.
Forecasting, one of our greatest pain points, saw perhaps the most vivid application of this method. Instead of enforcing a standardized approach, we mapped the conversation across layers: historical data, open orders, model projections, and sales input each became discrete points to be challenged and validated. The only fixed rule was that everyone had to engage in the debate.
Mistakes weren’t buried but analyzed. If a forecast failed, it was not a cause for discipline but a prompt for further innovation. The cycle of “model, test, reflect, adapt” became our lived methodology, applied at the level of system configuration, team design, and even basic terminology.
Embracing Change Fatigue and Learning from Failure
It would be dishonest not to speak to the exhaustion. Ashanti’s leaders—myself among them—were often fatigued by the sheer volume of moving parts: an IBP process overhaul, ERP implementation, sales support realignment, and factory rationalization, all in parallel. Change fatigue was real. Some feared that too much chaos would tip the system into dysfunction.
Yet even here, our philosophy held. Instead of throttling effort or reverting to command-and-control, we confronted overload by sequencing and adapting: extending timelines, adjusting scopes, pacing deliverables. We prioritized not speed for its own sake, but sustained engagement and absorptive capacity. Owning the reality of constraint allowed the team to accept help, ask for extensions, and own the reformulation of their work—again developing a sense of true authorship.
Not every attempt worked. We lost good people along the way—one memorable departure owed as much to managerial culture as to stress. Yet in even these moments of loss, feedback from those leaving was surfaced and discussed honestly, providing lessons to be woven into the next iteration, not swept aside.
Strategic Integration: Naming, Ownership, and the Balance of Chaos
At its core, our methodology held that even the most disruptive elements could be harmonized—not by striving for perfect order, but by embracing productive chaos until a new and better order naturally emerged.
The debate about “customer service,” “sales support,” and “order management” was emblematic. These weren’t just labels but loci of collective identity and, at times, turf wars. Through iterative debate and experiments—sometimes clumsy, sometimes revelatory—we began to see these not as static roles but as dynamic interfaces between teams, customers, and the evolving business context.
Inventory ownership became a crowning challenge. Should flexibility remain the “secret sauce”—allowing sales to override system allocations—or was maturity best served by ceding ultimate control to the supply chain? We confronted this not by theoretical argument alone, but by mapping real consequences, experimenting with changes, and allowing the friction itself to generate new, hybrid approaches. The goal was not to suppress “secret sauce,” but to extract its logic and embed it into systems where possible—or at the very least, to make its tradeoffs explicit and owned.
Conclusion: The Enduring Value of Chaos
Looking back over these many turbulent months, I see now that Ashanti Steel’s transformation succeeded not because we eliminated chaos, but because we embraced it as the crucible of creativity and ownership. Zambuka’s methodology was never a fixed protocol, but a set of guiding precepts: let the teams argue; let mistakes teach; let the structure emerge, be destroyed, then emerge anew.
Real change—lasting, creative, and owned—is not the offspring of control. It is born when a company dares to let disruption in, lets its Massys lead, and welcomes the risk of being wrong as the only path to being truly better.
For those willing to live with uncertainty—and to transform it, together—the rewards are profound: an organization not just efficient, but alive; not merely surviving, but inventing itself, every day, anew.
By MB
Leave a Reply