01 — Story

Three lessons

The long version.

Three lessons, not a chronology. What risk taught me, what building at scale taught me, and why I refuse the default.

Read the three lessons

Phillip Kemp, seated in a chair with his hand to his chin, in an olive blazer and white T-shirt.

02 — Risk

What risk taught me

I priced risk before I wrote software. For five years at KEMPRO I priced agricultural and financial exposure: futures, options, hedging.

The work was arithmetic with consequences. A wrong number did not fail a test; it landed on a farmer’s season or a business’s margin.

That taught me to look at the downside first. Before the upside, before the demo, before the slide: what happens if this is wrong, and who pays?

I still start there. It is why I ask what a feature costs when it fails, not only what it earns.

Risk also taught me to write down the assumption. A price is only honest if you can show the inputs. I carry that into software: if a decision cannot be explained, it is not finished.

03 — Building

What building at scale taught me

I joined a Potchefstroom software house as employee number three. I ran delivery and wrote most of the code, much of it e-learning used across Africa.

Small teams teach you the whole system, because there is no one else to hand it to.

Then I spent seven years on frontend architecture at BMW’s IT Hub. There I learned to deliver inside systems that already exist: other teams, other standards.

Scale is not more code. It is more people who have to agree before anything ships.

Today I lead. My job is to make the constraint clear, then get out of the way.

The best delivery I have seen was not heroic. It was a team that knew exactly what it was building, and why.

04 — Refusing

Why I refuse the default

The default is convenient. It listens, decides, nudges and asks for more data than the task needs. Most products drift there because it is easier than choosing.

I started meLink with one rule underneath: the user leads, the technology follows. No ambient listening, no unsolicited action, no dark patterns. The interface can disappear. The decision cannot.

If a feature wins the demo and loses the person, it does not ship.

We Are Still Human is the same argument out loud. The show began with a position, not a product: presence over prediction, identity over automation, people over the systems using them. The systems are getting smarter and we are getting quieter.

Then I wrote the six rules down, because a principle with no implementation is a wish. That is the refusal: not a slogan, a specification.

In short

05 — In short

14 years building 6 rules written 94 episodes

The views on this site are my own. BMW is my employer, not a sponsor of this work.