SYSTEMS THINKING
Before I touch anything,
I walk the whole system first.
You treat the world as given. I treat it as designed. A person made every rule, every product, every system. Which means another person can make a different one.
A way of seeing. Here's how to learn it.
- Tyson Harding, solo Māori founder
THE FIRST LESSON
My first idea was rotational saving. Four people saving $250 each, that's $1,000 a week. Four times faster than saving alone. Makes sense, right?
I found out it already existed. Dropped it.
Here's what I learned: when something already exists, don't improve it. Ask what it assumes. Then ask what nobody has asked yet.
What doesn't exist? That's the first move. Everything after it will EKKO.
Strip to first principles, then ask 'What else?'
Strip every convention (this is how it's done) back to its reason. Keep asking why until you can't go further.
Every "this is how it's done" is a question, not an answer. Why do they do it this way? Is there a better way? The gap between what everyone assumes and what's actually true is where the new thing lives.
I never stop at the first answer. The first answer is the obvious one, that's why everyone arrives at it. The third is where it gets interesting. Every convention is a question. Never an answer.
In EKKO
When the AI built my budget builder it put the category on the left and the amount on the right. Standard. Then I asked: "wouldn't that feel like housing is taking $500 from me? What if I swapped them?" Same numbers. Different direction. Completely different feeling.
Arena game → users save weekly. What else? Users build a track record. What else? That track record proves discipline. What else? Discipline history is better lending eligibility than a credit score. What else? A solo Māori lender can offer the lowest rates in Aotearoa to people banks won't touch — because I can verify they actually save. The game is the start of a financial system, not just a savings tool.
What others built tells me what's been tried — not what's right. Most founders add to what's there. I'm not interested in increments. I'm interested in what's true.
That's the first move. Now here's how to hold the whole field.
Think at system level. Act at specific level.
Never touch a part without first holding the whole.
Before I touch anything I walk the whole system first. What does this affect? What breaks upstream? What gets created downstream? The specific change is the LAST thing I think about, not the first. Skip the system level (bigger picture) and you solve one problem while creating three you can't see yet.
In EKKO
The prize pool math required holding three things at once: give back enough to create real incentive, stay sustainable with zero overhead, make the numbers feel fair. I held all three before touching a single figure. When I found the number where all three conditions were true at the same time, I stopped. Anyone who moves one variable without holding the others breaks the machine.
Hold the whole web at once
Several threads run at once. The connections between them are the insight.
I don't finish one thought before the next begins. Three or four threads run at once. The good stuff is always where they touch.
In EKKO
Non-custodial is a legal decision, a trust one, a cost one, and a UX one, all simultaneously. I didn't solve them in sequence. I held them all until they became the same decision.
Once I find the structural solution, I translate it into something simple for the user.
Cut the noise
Every extra thing on a screen costs the user energy they didn't agree to spend.
Too much to think about is what kills products. Every button, every duplicate input, every clever feature "someone might use" - it's all weight the user carries through your interface. So before I add anything I ask: does it earn its place? What breaks if I cut it? Usually nothing. So it goes. The test is simple - remove it. If nothing breaks, it shouldn't have been there.
In EKKO
The budget builder had a slider on every row, identical to the text input right next to it. Two ways to do the same thing. That's not flexibility. It's noise. The slider had to go. Five minutes after I removed it, the product was better.
Curiosity that pays out
Every screen should have one question the user desperately wants answered.
Curiosity is the strongest pull there is. But it only works if the answer's worth finding. Slot machines use curiosity to pull you down. I use it to pull you forward. Question → honest answer → user's life is better. Not better for the business. Better for them. That's the only pull worth building.
In EKKO
"What's left each week?" is the question EKKO is built around. Answer it honestly and the next step is a budget. Then a plan. Then a game. Then a habit. Every step makes the user's life materially better.
Build for the people who haven't been served
Three quarters of the world thinks collectively. Finance tools serve the other quarter.
Most finance tools assume money is just for you. But most of the world — Māori, Pasifika, collective cultures globally — decides money as a family. That's billions of people no tool actually fits. So I build for them, not the saturated market.
In EKKO
Kotahitanga isn't a feature. It's the structural premise. Solo tools exist to feed the group decision. Five people reach a house deposit in 18 months instead of 8 years alone. That's the whole point.
These aren't just principles. Here's how they look in motion.
The decisions
Theory is easy. Here's how this thinking actually built EKKO.
Why the budget builder has the amount on the LEFT and the category on the RIGHT.
Every budget app I'd seen put the category on the left and a number on the right. The user types in what they spend. Each row feels like the system taking money away from them.
Why does the typical layout feel bad? → Because the way it looks goes from "your money" to "what gets taken." You're losing.
What if I flipped it? → Amount on the LEFT, category on the RIGHT. The movement goes from you, toward the thing it serves.
Why does direction matter that much? → Western reading flow is left-to-right. The left side is the actor, the right is who it's for. Whoever is on the left is doing something.
So if the amount is on the left and the category is on the right... → You're the one giving. Housing isn't taking my money. I am giving money to my living.
Same numbers, same math. Different direction. Completely different feeling.
The conclusion
The budget builder is built around this idea: I am giving money to my living. Not: my living is taking my money. Same data, one way it's framed makes you feel like the author of your life and the other makes you feel like its victim. The way it's framed is the product.
Why the game is legally not gambling, and how predictability became the architecture.
The AI told me this was gambling. Instead of lawyering around it, I asked: how do I make it actually not gambling? That question unlocked predictability, percentage-based fairness, and the entire architecture.
Read By Design →How I went from “I want $1 net per person” to the actual business model.
I started with one conviction: give back more than I take. I iterated until the revenue model, prize pool, and player's win all interlocked. These aren't targets I set. They're numbers I discovered by holding the whole system.
Read By Design →The interlock is the moat.
The map
Why it can't just be copied.
Each decision above is smart alone. Together, they're a machine that can't be copied. The moat isn't any one feature. It's the interlock.
Non-custodial
Deterministic outcome
Percentage-based fairness
Solo founder, zero overhead
Interlocking math
Refuses pressure
To see what this thinking actually built, read By Design →
The invitation
The tools are free. Use them.
Every tool in EKKO is built from the thinking on this page. Start anywhere. Each one will show you something true about your situation that you didn't know before.
Building free tier live. No teaser, no trial. Just the tools.
Built by Tyson Harding · Immiscible Tech Limited · Whangarei, Aotearoa