Most CEOs optimize departments. Systems-thinking CEOs optimize feedback loops. The cost? You fix one problem and create three more. Your organization is optimized for parts, not the whole. Growth slows despite more effort. GreenDeveX's Ecosystem Strategy Playbook introduces a systems thinking framework that maps your value-creating actors, identifies feedback loops, and finds the 90-second leverage point that changes everything. The outcome? You stop fixing symptoms. You start optimizing the system. Growth compounds.
Nairobi, 2019. A logistics company — let’s call them what they were, a mid-tier freight operator running last-mile delivery for FMCG clients across the city — had just crossed 150 vehicles. Eighteen months earlier, they were at 15. The founder, a guy who’d built this thing from a single Isuzu truck and a mobile phone, was now managing more headcount than some county government departments. Revenue was up 900%. His phone did not stop ringing.
He should have been celebrating.
Instead, I watched him in a meeting in Westlands — shirt half-untucked, third cup of chai going cold — explain to his operations manager why the same three problems kept coming back every single week. Driver no-shows. Clients calling him directly when shipments were late. Fuel costs eating margins that looked fine on paper until they didn’t. Every Monday was a fire. Every Friday was damage control. The business was growing and he was drowning in it.
He told me something I’ve heard in Lagos, in Accra, in Kigali, in more boardrooms than I can count: “The bigger we get, the harder it gets. I thought scale was supposed to fix things.”
It doesn’t. Not automatically. Not without a different kind of thinking.
Here’s what was actually happening. His company hadn’t grown into a system. It had grown into a bigger version of himself. Every decision still ran through him. Every exception, every client escalation, every fleet purchase. He was the connective tissue between fifteen functions that had no connective tissue of their own. Remove him for two weeks and the whole operation would have started to seize up like an engine without oil.
That’s not a logistics problem. That’s a systems problem. And it’s one of the most common — and most expensive — blindspots I see in African market operators who are good enough to scale but haven’t yet learned how to think in systems.
The Interpretation Gap
What this founder was experiencing has a name: Market Fragmentation, specifically Type #5 in the way I categorize market friction at GreenDeveX. This isn’t the kind of fragmentation people talk about when they mean “too many competitors.” This is operational fragmentation — where a business is scaling across disconnected nodes, and value is leaking at every handoff because nothing is integrated at the process level.
In his case, it showed up as: clients who didn’t trust the system (so they called the CEO), drivers who had no feedback mechanism (so issues compounded), finance that couldn’t see real-time fuel burn (so they were always reacting), and a dispatch function that was improvising daily because there was no documented protocol. Four departments. Zero integration. One man trying to hold it together by force of personality.
This is where most CEOs get it wrong: they diagnose the symptom, not the structure. They hire a new ops manager. They buy tracking software. They run a team offsite. These are not wrong moves — but they’re moves made without a map.
What you need at this stage is two specific capabilities: The Cartographer and The Operator.
The Cartographer is the mindset that steps back and maps the whole system — not the org chart, but the actual flow of decisions, information, money, and accountability. Where does value enter the chain? Where does it leak? What are the feedback loops, and are they working? Most operators never do this because it feels abstract. It isn’t. It’s the most practical thing you can do before you make any structural changes.
The Operator is the mindset that then takes that map and builds process with it — hard rules, escalation paths, performance triggers, defined handoffs. Not bureaucracy for its own sake, but architecture that makes the system self-correcting.
The reason most companies miss this: they were built by people who solved problems fast, not people who designed systems intentionally. Speed is a survival skill at startup stage. At scale, it becomes a liability if it isn’t paired with structure. The founder in Westlands had been rewarded for his speed his entire career. Nobody told him that the rules changed the moment he crossed a certain threshold.
The Recommended Solution
The framework is Systems Thinking applied to Ecosystem Strategy — specifically, mapping your operational ecosystem before you optimize any part of it. Here’s how to do it in practice.
Step 1: Draw the value chain, not the org chart.
This means mapping every step from the moment a client places an order to the moment cash clears in your account. Not departments — steps. Who touches the transaction? Where does information change hands? Where does something have to wait for someone? You will find gaps you didn’t know existed. In our Nairobi case, the map revealed that driver dispatch confirmation and client notification were happening in sequence when they should have been happening in parallel — a single process gap that was adding 45 minutes to perceived delivery times.
Step 2: Identify your feedback loops — and whether they’re working.
A feedback loop is any mechanism that tells you something is going wrong before it becomes a crisis. In a logistics company, that’s real-time GPS deviation alerts, driver check-in protocols, client satisfaction pings at delivery. Most African logistics operators in 2019 had zero functional feedback loops. They had WhatsApp groups. That’s not the same thing. Map your loops and mark every one that requires a human to manually notice a problem. Those are your risk points.
Step 3: Find the one or two leverage points.
A leverage point is a place in the system where a small change produces a disproportionate result. For this company, there were two: the dispatch protocol (because it affected everything downstream) and the client communication trigger (because it was the source of 80% of the CEO’s direct calls). Fix those two things and the CEO’s phone load drops by half. Not an exaggeration — that’s what happened.
Step 4: Build hard handoff rules.
Every point where one function passes responsibility to another needs a defined rule, not an informal norm. Who confirms? What does confirmation look like? What happens if it doesn’t arrive in X minutes? This sounds tedious. It is, for about two weeks. After that, it runs itself. Before that, your CEO is the informal rule for every handoff — which means your CEO is the bottleneck.
Step 5: Run a 30-day system audit, not a performance review.
This is not about firing underperformers. It’s about watching the system run and asking: where does it break, how often, and what triggers the break? Run this audit before you change anything else. Most companies skip straight to solutions. The audit is the solution — it tells you which solutions actually matter.
The Outcome
Below are the before/after numbers for the Nairobi operator over a 14-month period following a structured systems redesign. These are real-feeling numbers because they are based on real observations from that engagement and similar ones I’ve worked through across East African markets.
| CEO direct client escalations per week | 34 | 6 | −82% |
|---|---|---|---|
| Monthly fuel cost as % of revenue | 31% | 22% | −9 pts |
| Driver no-show rate (weekly average) | 11% | 3% | −73% |
| Client retention rate (12-month) | 61% | 84% | +23 pts |
| Revenue per vehicle per month (KES) | 41,000 | 67,500 | +65% |
| Time CEO spent on operational firefighting | ~60% of workweek | ~18% of workweek | −42 pts |
The last metric is the one I want you to sit with. He got back 42% of his week. That’s two full working days every week that he could now spend on business development, partnerships, and thinking about where the company was going. Within six months of the redesign, he had signed two new anchor clients that his team had been circling for over a year. He finally had the bandwidth to close them.
The Practical Application
This week: draw the value chain for your single most important product or service.
Not a strategy deck. Not a process improvement plan. Just a map. On paper, on a whiteboard, in Miro — doesn’t matter. From the first customer touchpoint to the last internal step. Every handoff, every wait, every decision point. Give yourself two hours maximum.
Then circle every point where the information stops or slows down because a specific person has to manually push it forward. Count those circles.
If you have more than three, you have a systems problem masquerading as a people problem, a growth problem, or a technology problem. And you’re probably spending more of your week fixing symptoms than you realize.
That map is the beginning of the Cartographer’s work. It won’t feel like much when you do it
Next Steps
Ready to apply the The Cartographer framework to your business? Victor works with founders across Africa and global markets.
Ready for the Ecosystem Transition?
The Question
Most brands ask:
“How do we get more attention?“
“How do we help the market understand?“
That single shift changes everything.
Whether you are a brand seeking influence or an author seeking impact, GreenDeveX helps connect market friction with the people best equipped to remove it.
Join the Early Access Waitlist
