Board meetings were conversations. Minutes weren’t kept. Financial records lived on my laptop. It worked until it didn’t. |
I want to tell you about the mistakes. Not the polished version, but the real ones.
In Develop Africa’s first five years, I ran a nonprofit the way most founders do: on passion, improvisation, and personal relationships.
Board meetings were conversations. Minutes weren’t consistently kept. Financial records lived in a spreadsheet on my laptop. The “governance structure” was mostly me making decisions and informing people afterward.
We were legally compliant and institutionally fragile.
It worked until the moment it didn’t.
That moment came when a key team member departed and took institutional knowledge with her that existed nowhere else. We had no documented processes. No financial procedures anyone else could follow. No succession plan for any role. The organization was dependent on a small number of people in ways we hadn’t examined because things had been going well enough not to.
That’s the gap most founders don’t see until they’re inside it.
The legal filing says you’re an institution. The behavior says you’re still a movement.
Crossing from one to the other requires intentional work that no state registration can substitute for.
I spent the next fifteen years building the systems I should have built in year one. The financial controls. The board accountability structures. The documented SOPs. The governance policies that turned good intentions into repeatable practice.
Mission to Systems™ is the distillation of what I learned from that.
It is offered not as a critique — because I made every mistake in this book — but as protection. You don’t have to learn these lessons the hard way. I did it so you don’t have to.
Build the systems before you need them. You will need them.