Erik Berg

How on earth did "shake to provide feedback" become a standard UX pattern? Struggling to think of any other pattern that is so unintuitive and clunky.

I've never been good at not knowing what comes next. At Bible study one idea stuck: wherever you are, chase the Lord, and you'll be in the right place. I can't see where my building efforts lead, but I can always see the next step. I'm getting better at letting that be enough.

AI makes shipping almost free. Friction used to force us to ask whether something should be built at all. Without it, the risk is that we ship the wrong products faster.

Lyft auto-renewed a $200 membership without telling me. Then it let me cancel and get refunded in two clicks. I'll check Lyft first next time I need a ride, because of the second part.

In the world of AI the new "that meeting could've been an email" is "that dashboard could've been a spreadsheet". Overbuilding is the failure pattern of the day.

Every design choice is a normative choice. Someone decided the unsubscribe link should be hard to see. A better frame: build as if for a friend. If you made an appliance for a friend, you wouldn't design it to fail early. You'd want it to work well for as long as possible.

"It is the diner not the cook that pronounces upon the merits of a dinner." Aristotle No builder can judge their work through the eyes of the person they built it for. That's why discovery matters and why skipping it so often separates good products from bad ones.

A wedding gift that isn't a toaster: a premarital course the couple does together. Five modules, on their own schedule, $129. I built the first version for my brother. modernmarital.com/gift?utm_s…

In 2024 my brother asked me to officiate his wedding. I said yes on one condition: he and his fiancée had to take a premarital course I'd build for them. That course is now live for anyone. It's called Modern Marital. modernmarital.com/?utm_sourc…

Ready for church 😊 #COYG