About the Reinvention Architect
I’ve been on both sides.
From frontline operations to executive strategy, I spent nearly twenty years learning how organizations work from the inside out. I have been close enough to the work to see what breaks, and close enough to the decisions to understand why.
The story started with curiosity. It still does.
How it started
How I learned that organizations work from the inside out
I was sixteen, working behind a fast-food counter in Casablanca, when I began paying attention to what happened behind the visible rush. What looked like chaos was rarely random. Speed depended on timing, roles, handoffs, information, and people knowing what came next. When one part stopped working, the effect reached the customer quickly.
I did not have language such as governance, operating model, or transformation. I was simply intrigued by the system behind the result.
At eighteen, I joined Dell. My first role involved reading incoming emails and routing them to the right team. It was a small place to start, but it gave me a view across the organization. Every request had a customer. Every delay had a cause. Every handoff had an owner, even when that owner was not clear. And every apparently simple problem revealed another part of the system.
That pattern never stopped. I was amazed by how numbers could reveal what customers were experiencing, so I moved into reporting, analysis, and governance. I was fascinated by work that crossed functions and never stayed still, so I moved into programs and transformation. I was frustrated by how decisions made at headquarters could land in regions without enough room for the people executing them, so I joined a global rotation program to understand both sides. I was surprised by how much strategic value sat inside frontline signals, so I moved into customer advocacy and global process engineering.
Every time I saw something I did not understand, I did not step back. I stepped in.
The titles changed. The pattern did not.
That curiosity eventually took me through customer care, executive escalations, supply chain, transformation, organizational redesign, process engineering, automation, AI and ML, risk, finance, and executive governance. It eventually took me to Frankfurt, where I became Chief of Staff and Regional Transformation Leader, working across Finance, Customer Experience, and Supply Chain in a USD 14 billion global organization.
The scale had changed. The underlying pattern had not. Strategy was often clear at the top and difficult to carry through the work. Ownership blurred. Handoffs broke. Dashboards disagreed. Technology arrived before the process was understood. Change was added to operations that were already full.
Strong people compensated. They built private trackers. They remembered the exceptions. They protected customers. They resolved the handoff. They kept the deadline moving when the formal system could not. Because they compensated, weak systems often looked functional.
That changed the question I learned to ask.
Not: Why are people not executing?
But: What is the system asking good people to carry that it should have designed itself?
I built governance, workflows, operating rhythms, automation, and continuity mechanisms that produced measurable results. The numbers are documented in the Proof section. The lesson that stayed with me is simpler.
The people closest to the work often see the problem first. They see the exception, the workaround, the hidden dependency, and the improvement that might actually hold. They should not be invited into transformation after the important decisions have already been made. They should help shape the system. That is the work I decided to carry forward: putting better systems, clearer authority, and more useful operating language closer to the people already holding the organization together.
The next chapter
The next question
By 2024, I had spent almost twenty years learning how organizations work from the inside. Leaving Dell was not about starting over. It was about asking what those years had prepared me to build next.
For most of my career, curiosity had led me into another role, another function, another part of the system. This time, the next chapter was not waiting inside the organization. I had to build it.
Could the patterns I had learned inside a global business become useful to people leading change elsewhere?
I began putting into words what had previously lived in the work: how I read friction, connect strategy to execution, create ownership, and build change that can hold after the person driving it steps away. That became S|B Engine.
The work is still evolving, because I am still learning from it. I am testing the language, challenging the assumptions, and refining the method as new questions emerge. The setting has changed. The instinct has not. When I find something worth understanding, I still move closer.
What guides the work
What I believe
Systems over heroics
Good people will compensate for broken work.
Their commitment should not become the excuse for leaving the system broken.
The people closest to the work belong in the design
Operational knowledge is not feedback to collect after the decision.
It is part of the decision.
Clarity creates capacity
Every hour spent guessing about ownership, priorities, measures, or definitions is an hour not spent moving the work.
Clarity is not bureaucracy. It is operating capacity.
Technology follows understanding
Automation and AI create value when the work, judgment, exceptions, risks, and intended result are understood first.
A tool should strengthen the work, not disguise what has not been designed.
Change should leave capability behind
The work is not finished because something launched.
It is finished when the people who remain can run it, question it, improve it, and carry it forward.
I’m a proud Moroccan who speaks Arabic, French, English and is learning German. I split time between Germany and wherever the work takes me. When I’m not building systems, you’ll find me exploring new places with my family, listening to podcasts or walking with my yorkie, Teddy. Life outside of work fuels the empathy and perspective that feed back into my practice.
The journey moved. The instinct did not.
The journey has moved from a counter in Casablanca to executive operating rhythm in Frankfurt. The scale changed. The instinct did not. When I find a part of the system I do not understand, I move closer to it.