Work and notes from building digital products in complex worlds.
Making got easy. Understanding never did.
Anyone can produce a design now. A working app, a convincing document, a hundred variations of either. Good news, mostly. It also removes some of the things this profession leaned on for as long as I have been in it.
What it does not remove is the understanding. What a business is really trying to move. What the technology can carry. What the person at the other end is dealing with, and how each of those pulls on the others. That still gets done the slow way: a chair next to a physicist, a neurosurgeon coming in to disagree, the same software used case after case until you feel where it fights the people using it. It takes months. It cannot be produced.
Selected work
Problems like these rarely come with easy answers. A brief is a snapshot of what everyone already believes. What is actually going on sits a layer down, connected to things nobody wrote down, and it does not show itself to people in a hurry. The best outcomes I have seen came from distrusting that first answer long enough to find the real one.
Simple is earned. The work I admire most has the simplest possible concept at its core and refinement in every detail, and you cannot start there. Simplicity you did not earn is a facade, and a facade gives the first time reality pushes back.
You can feel it in certain products. Someone stayed with the problem longer, asked better questions, left out the right things. And on the complicated day, when the edge case shows up and the person is tired, it holds.
About
I'm Johannes Lamers. I've been designing and building digital products for nearly twenty years: first on my own, end to end, then commerce at global scale, now complex systems at Reaktor in Amsterdam.
I want to know how things work, all the way down. I'm in the technical conversation, the business one, and the odd constraints that only show up once you get close. The work moves between the system and the smallest detail, because they explain each other.
Being that close makes me direct. The people who decide get my honest read, not my agreeable one, and the questions that are easier to skip. When the evidence changes, so does my view. When someone else has the better idea, I want it to win.
I usually get brought in while the problem is still vague and the stakes are already real, and I stay through the whole arc: strategy, research, prototypes, the interface, and the months after launch when it becomes what it was meant to be. A product is finished when it sits in someone's hands and the problem is gone.
If you're working on something ambitious or unusually thoughtful, I'd like to hear about it.