Ben Strak

Product designer @monzo • Writing at 🦞 • Discover your subconscious beliefs about money at

[Ben Strak @ben_strak]

@christiancalgie I’ve found it quite effective to keep the earbuds they hand out on flights and then hand them out to people playing videos on trains. The offer of a gift disarms people and gets the message across without raising their hackles.

[Ben Strak @ben_strak]

Sad but true

[mehedi @mehedih_]

renaissance branding in 2026 is the new corporate memphis

[Ben Strak @ben_strak]

Come join!

[Simon | Morse @SimonRAmor]

Join us for AIxDESIGN Vol. 02.

Monday, 2nd March at the @SlingMoney office.

@rich_cahill, Design engineer from @Lovable and Benjamin Strak, Senior Lead Product Designer @monzo , will break down how they’re actually using AI in their workflows, using design-skills and more. We're starting the morning with hands-on build time to give you a chance to create, explore, get advice and collaborate.

As always, we're keeping the event small, so slots are limited. We will keep registrations open until Friday. https://t.co/zKSqDukGyl

[Ben Strak @ben_strak]

Thinking clearly and imaginatively has always been the hardest part of design.

[kasey @kaseyklimes]

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.

[Ben Strak @ben_strak]

Latest side project 👀

[Ben Strak @ben_strak]

@cursor_ai And do buy your full report if you fancy subsidising my Gemini API costs 😜

[Ben Strak @ben_strak]

Have a little side project to share…👀

https://t.co/oVeQ5z4okA

Discover your subconscious beliefs about money.

Excited to see your tarot card if you’re willing to share it here!

[Ben Strak @ben_strak]

All built with @cursor_ai - let me know if you spot any bugs or have thoughts on how relevant the insights were for you 🙏

[Ben Strak @ben_strak]

"Design, in this sense, is not about artifacts or tools. It is about forming and shaping clarity of the intent through ideas, exploration, research, and discussion. It is about deciding what matters, what constraints apply, and what tradeoffs are acceptable." 👏

[Karri Saarinen @karrisaarinen]

https://t.co/RU33K24RsJ

[Ben Strak @ben_strak]

@kasrak this is so cool

[Kasra @kasrak]

In 2025, I wrote 800k words in my notes (War & Peace is 500k words), so manually reviewing wasn't going to happen. But luckily computers understand language now!

I spent the past week building this Lookback feature: it reads through all the notes & chats to pull out highlights & insights

People use Lightpage in very different ways: as a journal, as a work scratchpad, as a learning notebook, etc. So instead of being prescriptive about the output, I gave the LLM general principles to follow and it turned out pretty well

A few screenshots from my lookback:

[Ryo Lu @ryolu_]

the old way of scaling teams is dead:

we used to hire specialists – designers, engineers, PMs – each in their lane, scaling by adding more people. but when Cursor can take you from idea to code in minutes, execution isn't the bottleneck anymore. taste and judgment are.

what matters now: people who can see the full stack, move between layers, but specialize deeply in something AI can't replicate yet. T-shaped but way wider – conversant across domains, expert in one thing.

AI doesn't just make you faster. it ties teams together differently. no more waterfall – designer codes the prototype, engineer extends it, both work in the same medium. the gap between disciplines disappears.

this raises individual ceilings. i'm a designer who built ryOS entirely in Cursor – couldn't have done that before. but i'm not replacing engineers, i'm just removing execution barriers while keeping my design taste and systems thinking.

you're not hiring for roles anymore. you're hiring for breadth + depth, taste, systems thinking, learning velocity. 5 people who can work across code/design/product beat 20 specialists coordinating handoffs.

the new bottlenecks are deeply human: taste, vision, judgment, context. AI explores options, but can't tell you which is right. that's where specialization matters now – in judgment, not execution.

small teams, fluid boundaries, everyone working in the same tools. roles still matter but as overlapping concerns with different depths, not separate silos. tools handle execution, you handle vision.

this is what we're building at Cursor – closing the gap between idea and reality. so your taste becomes the main thing, and teams have more freedom to explore crazy ideas.

[Ben Strak @ben_strak]

@LightpageApp is well worth checking out. Some great human-centered design choices for how the AI features work that others should copy.

[Kasra @kasrak]

A lot of the time it feels like I'm discovering Lightpage rather than designing it

But the exploration is grounded in how I'd like it to feel

So it was very nice to read @ben_strak's post and see that some of the underlying feelings I'm hoping to capture are coming through

[Ben Strak @ben_strak]

Have been having one of the most profound experiences with a computer that I can remember over the past few days exploring 17 years of Apple Notes with the help of @claudeai code 😮

[Ben Strak @ben_strak]

My hot take is nearly every major app would benefit from removing 5-10 features.

We are drowning in features.

[Ryo Lu @ryolu_]

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.

[Ben Strak @ben_strak]

I feel like I am falling for engagement bait here, but when has any worthwhile design problem been expressed in anything like the phrase "Please create the WhatsApp in-chat UI"?
Can we throw this AI-designer a more ambiguous problem?

[Michael Goldstein @mlg27_]

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.

[Ben Strak @ben_strak]

Do I have any super strong freelance product designers in my network here? Need to be NYC or SF-based and able to dive into some Monzo US projects asap 👀

[Ben Strak @ben_strak]

@ArisXK Yes indeed. It's not a substitute for putting it in front of other people. The important thing is to know what you're shipping in uncomfortable detail and committing to fix everything that doesn't meet your bar.

[Ben Strak @ben_strak]

Use your product more than your users.

[kristina v. saint @kristinatastic]

(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.