Ben Strak

i’ve taught design students for over a decade, but last night was the first time I’ve spent time in the classroom since the wide adoption of claude code, etc. the distance between idea and reality has completely collapsed, which puts the new bottleneck in stark relief: clarity of thought. it used to be that weak thinking could be obscured by impressive execution, while strong thinking could get lost in poor execution. now, the execution is so universally impressive that it recedes into the background to reveal the thinking: what problem are you solving? for who? how do you know it’s a real problem? how do you know that your solution addresses it—not just in theory but in the real world? can you explain your idea clearly? this is *incredibly* hard, but it’s exciting that students can now focus on it without worrying about pixels and syntax. I think it’s a huge opportunity for design education to meet the moment, should it so choose.

on simplicity: simplicity isn’t about stripping everything down to the bare minimum. it’s about finding the simplest system that can do the most things and serve the most people. removing features just to remove them isn’t simple – it’s disruptive. real simplicity comes from unification: building systems that allow for variation and customization to fit different needs and contexts. simplicity is subjective. a pilot wouldn’t be happy if you removed their HUD displays and cockpit controls. but a beginner stepping into that same cockpit for the first time would be overwhelmed, not knowing where to start. the beautiful thing about software is that it’s conceptual and malleable. unlike physical objects, it can adapt and transform for its user. true simplicity in software means: • simplicity at the system level – unified concepts that compose elegantly • transparency – making the system understandable and explorable • progressive disclosure – revealing complexity gradually as people grow • safety – letting people learn without fear of breaking things this is a simple (but hard) way to create systems that feel simple to beginners while staying powerful for experts. not by removing, but by layering thoughtfully. the end is not minimalism. it’s maximum capability with minimum friction.

I’ve been building what I believe is the best AI designer over the past few months - and I’m finally excited to share a first look.

(this is total speculation on my part bc Dia was made after my time at browser but I assume the culture there is still the same) what made Arc’s onboarding great was: we tried signing up for the product every single day, several times a day. every monday morning, the team would get on a call together, one of us would screenshare trying to sign up and the rest of us would write down what was wrong. for a good couple of months, this was excruciating and embarrassing. most of it was broken, a lot of lofty ideas we had for special details or clever animations felt awkward or silly. it felt pointless to do as a group because so little of the prod experience matched what we had in our heads, I think most of us wanted to go back to the drawing board and think of a better flow in our heads. but we filed dozens of tickets for ourselves, and then got back to work. all week eng and design would be running through the entire flow over and over again as they fixed those issues. rinse and repeat, for I don’t remember, maybe twenty weeks. until the real thing was as good as what we had in our heads. that’s it, that’s the secret. you have to actually use your product, more than your users ever will, and then fix everything that feels bad instead of letting it slide.