Building
experiences
through design
I’ve built products from zero, failed, iterated, and figured out what actually matters in the early stages of a business. Now I help others skip the expensive mistakes.
Already know what you need? Send a brief.
I take vague problems
to shipped first versions.
Usually with two or three other people, usually with less time than the plan needed. 7+ years of it, mostly SaaS and mobile apps.
Making things is
no longer the hard part.
Anyone can produce a screen. Almost nobody can say why that one and not another. That’s the part I work on, and the only part worth writing down.
Three things
I’m fairly sure of.
Each one cost me something specific, which is the only reason I trust them.
-
Most of the work is avoiding work
What you do not build shapes the product more than what you do. Products rarely die of one bad feature. They die of forty reasonable ones.
-
Enthusiasm is not demand
The only signal that means anything is somebody using the thing a second time, on their own, without you in the room. Everything else is manners.
-
The cost is the lesson
If it cost me nothing, then I read it somewhere and I’m repeating it. That’s the filter for everything I publish here.
Some of my projects
are buried, in public.
A portfolio of things that worked teaches nobody anything, because what worked depended on a team, a market and a moment you will never have.
Every other week,
one thing I got wrong.
And what it cost. No roundups, no five tips, no news.