A few years ago, I had a problem I couldn't quite name.
We were delivering websites. Clients were validating every step. And yet, at final delivery, it almost always fell apart. "It's not quite what I had in mind." "I thought it would look different." Revisions, tension, projects spinning out of control even though we thought everything was well-scoped.
For a while, I looked for the problem on the technical side. Then on the communication side. And then one day I understood what was really happening.
The problem was projection. Or rather, the absence of it.
Validating without seeing
The process back then was straightforward: select templates online, present them to the client, the client picks a model, and we move straight to content integration. Logical, fast, budget-friendly for small businesses.
Except validating a template means validating a skeleton. An empty structure. And a skeleton says very little about what the final result will actually look like with the client's real colors, real images, real copy.
The client says "yes" because they have no other reference point. Not because they actually see what they're going to receive.
That's exactly where dissatisfaction is born, not at delivery, but much earlier, in that moment when we asked them to validate something they couldn't truly picture.
One simple decision, immediate impact
I decided to add a prototyping step to the process. Not a rough wireframe. A real prototype built on the chosen skeleton, dressed in the client's colors, with their navigation structure, their sections, their visual identity. Something that already looks like the final result, before development even begins.
To fund this extra step without losing margin, we adjusted our pricing slightly. Honestly, it didn't create any pushback, because the perceived value was immediately obvious. For the first time, the client could see their website before receiving it. They could react, adjust, and co-build with a clear picture in mind.
Satisfaction rates went up. Back-and-forth exchanges dropped. Projects started finishing on time, with clients who referred others.
Why this speaks directly to datocracy's mission
What I experienced with this prototyping problem is exactly what datocracy is trying to solve, but on the data side.
How many decision-makers, NGO managers, and entrepreneurs across Africa and the Global South make decisions without truly "seeing" their data? The numbers exist somewhere. They know data is available. But no one has taught them how to read it, question it, or build on it.
As a result, they validate strategies the same way my clients used to validate templates: based on a vague impression, without being able to project what the implications actually are.
datocracy's mission is to change that. Not just teaching Python or SQL to technical profiles. Making data literacy accessible to those who need it most to make decisions: development actors, MSMEs, governments, communities that don't have access to big consulting firms.
Think of it as competency prototyping. Giving non-expert people the tools to see what their data is saying, so they can finally project themselves, react, and decide with clarity.
What working on the ground taught me about co-creation
Co-creation isn't just "involving the client in the process." It's creating the conditions for them to genuinely participate, not just nod along.
As long as a client can't see the output, they can't truly co-create. They can validate, but validating is not the same as deciding with a clear vision.
This is true for a website. It's true for a data-driven strategy. It's true for any process where you ask someone to commit to something they don't yet fully grasp.
The prototype, whether it's a UI mockup or a simplified data dashboard, is what bridges that gap. It translates abstraction into something tangible, readable, and appropriable.
That's exactly where real co-creation begins.
One takeaway
If you're a project lead, entrepreneur, or development actor: the next time someone presents you with an analysis or recommendation based on data, ask to see the data. Not just the conclusion. The data itself, formatted, contextualized, explained.
That's your right. And it's what will allow you to make an informed decision rather than approving something you can't quite picture.
That's exactly why datocracy exists.
