Humans are sense-making animals
Start here, because everything else follows from it.
Humans don't receive information passively. We construct meaning from signals -- constantly, compulsively, and mostly without knowing we're doing it. Every interaction broadcasts something. The words chosen and the ones deliberately avoided. The pace of a response. The physical arrangement of a room. The way an organisation talks about the people it serves. We are signalling before we open our mouths, with our systems before anyone uses them, with our silences as much as our statements.
Most people are entirely unaware that they're doing this. And most systems are designed as if the people using them aren't doing it either.
This is where most things go wrong. Not through malice or incompetence -- through a fundamental misunderstanding of what communication actually is.
Communication isn't the transmission of information from one place to another. It's a biological act. We evolved to signal to each other because we need things from each other -- connection, safety, belonging, recognition, understanding. These aren't soft extras layered on top of the real business of communication. They are the real business.
Data is not information. Information is not knowledge.
There's a pipeline that most system designers ignore and most communicators have never been taught.
Data is a raw representation. Information is data with context. Knowledge is information applied. Wisdom is knowledge internalised. And then there is activation: the moment understanding becomes personally real enough to move someone.
Most systems are designed at the data end. Most humans live at the wisdom and activation end. The gap between them is where things fail.
The gap is where human needs go unmet
When a system fails to communicate, it isn't only an efficiency failure. It's a human needs failure.
The person on the other side of that gap isn't just confused. They're unseen. Unserved. Sometimes excluded from services that legally belong to them. Sometimes unable to access healthcare because the system meant to serve them has no way to verify they exist.
Different rooms. The same gap. The same underlying question: who is on the other side of this, what do they need, and what is standing between them and it?
Constraints are where the thinking gets honest
My work is fundamentally about puzzles with hard constraints, incomplete information, and real stakes.
Most people treat constraints as unfortunate. I treat them as the design brief. Remove them and you don't have an easier problem. You have a less interesting one.
Offline only. Basic Android phones. Frontline health workers with no margin for error. Brutal constraints, clarifying constraints.
A grant process for people in crisis, designed by people who are not in crisis. The constraint reveals who the system was built for.
A first-of-its-kind independent electoral campaign with no precedent. You build the playbook while running the campaign.
The constraint is the brief. Once you see it that way, difficulty becomes direction.
What the translation engine actually is
I move between signal systems.
Every context has its own language and assumptions. Most failures at those intersections are translation failures: the signal was sent, but it wasn't received in the form needed by the person who needed it.
The translation engine is the capacity to notice this, read the full signal environment, and redesign transmission so it lands.
A festival accreditation system at 2am. A biometric identity system in low-resource settings. A civic accountability platform. A first-ever independent campaign. Surface differences, same underlying problem.
The two questions
I've never been able to answer "where do you see yourself in five years?" I don't navigate like that.
What I have instead are two questions: Am I learning? Am I having fun?
Learning asks whether this expands understanding. Fun asks whether there is enough aliveness to sustain serious attention. Both must be yes.
Together, they've produced something that looks non-linear from outside and coherent from inside.
Not random. Not planned. Accumulative.
genetic drift is change through accumulated events rather than strategic design. jeneticdrift is an honest name for how I got here.
I didn't plan the sequence of civic tech, biometrics, elections, and live events. Each context answered yes to the two questions. Each added to the understanding.
The pattern is visible in hindsight. That is not a flaw in the system. It is evidence the system works.