Senior Product Designer at @Careem - previously worked at @WeAreInsightful @TheVeryGroup @Laterooms @Parcel2Go
Dubai, United Arab Emirates
Joined August 2010
- Tweets4.5K
- Following5.6K
- Followers2.1K
- Likes16.5K
Adam Morgan retweeted
.@clairevo: "We can now ship all our bad ideas. Congratulations!"
Adam Morgan retweeted
🟧 39 Design Principles for Human–AI Interaction
A practical framework for designing AI products, with real examples from leading products.
→ syntaxstream.substack.com/p/…
By Taras Bakusevych
Adam Morgan retweeted
Paper × Conductor: super complimentary tools
In this video, @charlieholtz and @harcourttt show working with @conductor_build in paper.
It's a new workflow that we see more people using.
Full video link in the thread! What do you think?
Adam Morgan retweeted
The founder in their 40s with taste and discernment is the new gentleman unicorn founder
Because there can be 100x to 1000x of them working at their beck and call via agents and software factories all the time
The age of the 40-year-old founder is back.
Bryant Chou spent 12 years as CTO of Webflow, which now powers something like 1.5% of the entire internet. He's back in the current YC batch with Ploy, an AI marketing platform, and he describes himself as "a bit of a boomer, double the age of the YC founders." But over 13% of his batch is already using his product, within months of launch.
There is a side of the argument which destroyed one of the main edges young founders have, which was being faster and cheaper at building.... speed is everyones game.
If what's left is knowing what to build this is more likely to come from spending 15 years watching an industry up close, collecting the thousand small frustrations that tell you where the real problem is. Bryant can build an anti-slop website tool because he spent over a decade learning exactly why websites are slop.
So I'm updating. I don't think it's young vs. old. I think AI rewards whoever has the most domain knowledge to point it at, and only sometimes is this younger founders who are thinking outside of the box...
Adam Morgan retweeted
been watching how y'all have been using @mobbin mcp for a month. if you think the no. 1 use is "generate ui", you'd be very surprised.
save this thread 🧵
(img credit @zygisSS22)
Adam Morgan retweeted
Introducing Claude Opus 4.8: it builds on Opus 4.7 with sharper judgment, more honesty about its own progress, and the ability to work independently for longer than its predecessors.
Available today at the same price.
ALT Benchmark table showing how Claude Opus 4.8 compares to its predecessor and to other models on tests of coding, agentic skills, reasoning, and practical knowledge work tasks.
Adam Morgan retweeted
Automation is a lie. CLIs are over. The SaaSpocalypse is dumb.
A year ago @danshipper came on the podcast to predict where AI was heading. He was remarkably right—including the call that everyone was sleeping on Claude Code.
Dan has a unique lens into where things are going because his team at @every is possibly the most AI-pilled group of people in tech. I always learn a ton talking to Dan.
So I brought him back for round two. We'll score these in exactly a year:
🔸 Every company will have one “super-agent” in Slack.
🔸 Codex and Claude Code will become the new operating system for knowledge work.
🔸 The AI job apocalypse is not happening.
🔸 PMs and designers will thrive.
🔸 We will read way more AI-generated writing and we will like it.
🔸 "I would buy SaaS stocks right now."
Listen now 👇
youtube.com/watch?v=4D3hDmGh…
Adam Morgan retweeted
what's happening inside Anthropic right now is genuinely fascinating:
DESIGNERS are now shipping production code
with no engineer in the loop at all
these are non-technical people with zero coding background.
engineers on the team said designers are making "large state management changes you typically wouldn't see a designer making"
think about what that means for a second.
at every tech company in the world, designers and engineers are two separate roles.
designers make mockups, engineers write code. that's been the deal for decades.
at anthropic, that line is completely disappearing now.
here's what their designers actually do now:
it starts with a screenshot.
1) a designer takes their figma mockup and pastes the image directly into claude code.
2) claude looks at the image and generates a fully functional prototype from it.
working code that engineers can immediately build on.
this alone replaced the entire traditional cycle of:
make static design → write spec → hand to engineer → wait → review → give feedback → wait again → repeat.
but that's just prototyping.
from there, designers implement front-end changes themselves.
typefaces, colors, spacing, layout, etc directly in the codebase.
no ticket filed, no engineer pulled in.
and it goes further than visual polish.
designers are now making state management changes
(the code that controls how data moves through the app, even junior engineers find this tricky)
and for their ongoing backlog of polish and bug fixes, they don't even open claude code.
they just file a github issue (basically task description) describing what they want changed…
and claude automatically proposes a code solution.
then the designer reviews it and ships it.
so there's a persistent stream of improvements flowing into production without pulling a single engineer off their work.
they also use claude code to map out edge cases during the design phase.
the stuff that used to only get discovered later when engineers actually built the thing.
so now the designs are better
AND they ship faster because the edge cases are already handled before engineering starts.
one detail i love:
they set up a custom memory file that tells claude:
"you're working with a designer who has little coding experience. give detailed explanations. make smaller, incremental changes."
claude adapted its entire approach based on that one file.
here are some cool numbers, straight from the product design team:
• claude code is now open alongside figma 80% of the time
• 2-3x faster execution across the board.
the designers' reaction when it all clicked:
"holy crap, I'm a developer workflow"
the boundaries between roles are dissolving. quietly.
i think what's happening internally at anthropic is 2-3 years ahead of what will happen to the rest of the world
Adam Morgan retweeted
Design lead for Claude: The classic design process is dead.
Here's what's replacing it.
Jenny Wen (@jennywen) leads design for Claude at @AnthropicAI, was previously director of design at @Figma, and a designer at @Dropbox, @Square, and @Shopify.
In our in-depth conversation, we discuss:
🔸 Why the classic discovery → mock → iterate design process is becoming obsolete
🔸 What a day in the life of a designer at Anthropic looks like, including her AI tool stack
🔸 Whether AI will eventually surpass humans in taste and judgment
🔸 Why Jenny left a director role at Figma to return to IC work
🔸 The three archetypes Jenny is hiring for now
This conversation changed how I think about the future of design.
Listen now 👇
youtu.be/eh8bcBIAAFo
Adam Morgan retweeted
Announcing a new Claude Code feature: Remote Control. It's rolling out now to Max users in research preview. Try it with /remote-control
Start local sessions from the terminal, then continue them from your phone. Take a walk, see the sun, walk your dog without losing your flow.
Adam Morgan retweeted
Introducing Claude Opus 4.6. Our smartest model got an upgrade.
Opus 4.6 plans more carefully, sustains agentic tasks for longer, operates reliably in massive codebases, and catches its own mistakes.
It’s also our first Opus-class model with 1M token context in beta.
Adam Morgan retweeted
I'm back with a new pocket guide - 10 principles for better design critique.
I've sat in hundreds of design crits over 30+ years as a designer. These are tried and true.
Hemeon’s Pocket Guide to Design Critique
01 / Same Team, Same Goal
Critique is not a courtroom. It’s a shared effort to make the work better. The enemy is unclear thinking, weak craft, and lazy solutions. If it feels like combat, the culture is broken.
02 / Safety Is the Container
People don’t risk honesty when they feel exposed. They perform. They defend. They shrink. Strong critique only happens inside trust. Tend the room before you touch the work.
03 / Honesty Without Harm
Truth matters. So does delivery. Say the real thing, cleanly. You can be direct without being destructive. If people leave wounded instead of clearer, the moment failed.
04 / Critique the Artifact, Not the Human
The work is not the person. The draft is not the designer. Speak to flows, clarity, and decisions. The moment feedback touches identity, growth stops.
05 / Don’t Break the Good, While Fixing the Bad.
You can’t improve what you don’t yet understand. Naming strengths is not politeness. It’s precision. It tells the designer what to protect while they evolve.
06 / Taste Without Reason Is Noise
“I don’t like it” is not critique. It’s mood. Real feedback anchors to users, goals, systems, constraints, or craft. If you can’t explain why, it’s preference.
07 / Turn Reactions Into Direction
“Confusing” is a feeling, not feedback. Do the extra work. Translate reactions into requests. Direction moves the work forward. Vibes do not.
08 / Context Comes Before Solutions
If you don’t understand the intent, you’re solving the wrong problem. Ask first. What’s the goal? What’s fixed? What’s fragile? Critique without context is theater.
09 / All Notes Are not Equal.
A bug demands attention. A preference does not. When you label feedback clearly, the team can prioritize without emotional confusion.
10 / Many Voices, One Owner
Choose a clear owner.
Without ownership, critique becomes endless discussion.
Thank you for reading. Drop a comment on the best tips you have for running a design crit. Would love to hear your ideas!
Adam Morgan retweeted
Claude: "I've defined phase one of your project to be completed during weeks 1-4 and updated the spec."
Me: "Implement phase one now."
*5 minutes pass*
Claude: "Phase 1 is complete."
Adam Morgan retweeted
Good Products are Opinionated.
“Every great founder I’ve seen up close, or even from afar, is highly opinionated and they’re almost dictatorial in how they run things.
Also, early-stage teams are opinionated. And the products they build are opinionated. Opinionated means they have a strong vision for what it should and should not do.
If you don’t have a strong vision of what it should and should not do, then you end up with a giant mess of competing features.
@Jack Dorsey has a great phrase: “Limit the number of details and make every detail perfect.” And that’s especially important in consumer products. You have to be extremely opinionated. All the best products in consumer-land get there through simplicity.
You could argue the recent success of ChatGPT and similar AI chatbots is because they’re even simpler than Google.
Google looked like the simplest product you could possibly build. It was just a box. But even that box had limitations in what you could do.
You were trained not to talk to it conversationally. You would enter keywords and you had to be careful with those keywords. You couldn’t just ask a question outright and get a sensible answer. It wouldn’t do proper synonym matching, and then it would spit you back a whole bunch of results. That was complicated. You’d have to sift through and figure out which ones were ads, which ones were real, were they sorted correctly, and then you’d have to click through and read it.
ChatGPT and the chatbot simplified that even further. You just talk to it like a human—use your voice or you type and it gives you back a straight answer.
It might not always be right, but it’s good enough, and it gives you back a straight answer in text or voice or images or whatever you prefer.
So it simplifies what we looked at as the simplest product on the Internet, which was formerly Google, and makes it even simpler. And you just cannot make a product that’s simple enough.
To be simple, you have to be extremely opinionated. You have to remove everything that doesn’t match your opinion of what the product should be doing. You have to meticulously remove every single click, every single extra button, every single setting.
In fact, things in the settings menu are an indication that you’ve abdicated your responsibility to the user. Choices for the user are an abdication of your responsibility. Maybe for legal or important reasons, you can have a few of these, but you should struggle and resist against every single choice the user has to make.
In the age of TikTok and ChatGPT, that’s more obvious than ever. People don’t want to make choices. They don’t want the cognitive load. They want you to figure out what the right defaults are and what they should be doing and looking at, and they want you to present it to them.”
Adam Morgan retweeted
I don’t get it. Otherwise smart people proclaim the end of SaaS because AI takes over the software part.
Software-as-a-Service was never about the software and always about the service.
AI changes nothing about the business reasons to buy instead of build.
And yes, you can built much faster with AI assistance. But professional software never had an implementation problem. People figure these things out every day. The hard part is the spec, the requirements, understanding what this will cost to run and maintain, not just to build.
That’s what the -as-a-service part does. It outsources the headache of everything but the cost to build.
Adam Morgan retweeted
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.
Adam Morgan retweeted
We’re looking for 4 world class creatives to join the @elevenlabs Design Team.
Product Design (Creative Platform, designing interfaces for our AI audio research)
Product Design (Agents Platform, it’s a technical product, so ideally technical background)
Website Design (Designing pages for a rebranded marketing website)
Brand Design (Levelling up the brand, and supporting asset creation)
If this is you, or someone you know, DMs are open.
