
Cofounder & Product https://nitter.gq/t.co/1osdzuRV2B ex @AlibabaGroup head of product and design in AIGUI
Joined April 2011
- Tweets934
- Following605
- Followers4.4K
- Likes4.9K
Cursor is hiring design engineers.
looking for people with taste, systems thinking, and deep care for fast, polished experiences – especially folks excited to build the tools that help designers, engineers, and agents ship quality code.
know someone? tag them or DM me 📧
Long Wang retweeted
We're hosting an event on June 16th in San Francisco.
Compile is a one-day event that brings together engineers, researchers, designers, and builders of all kinds to discuss the future of software.
cursor.com/compile
Long Wang retweeted
最近做设计数据集,不断在看公开的「网站和应用集合站点」除了 Mobbin.com 这种偏平台和工具应用以外。特别推荐一个 designnokoto.com 日本网站集合,里面都是以内容优先的营销网页。每隔一段时间打开,都会有非常多制作精良的网站,十分养眼了。
Long Wang retweeted
CUI 或者 LUI 可能当下阶段大家对 AI 设计最危险的「共识」。AI 时代的设计将打破传统固定尺寸框定的「界面」,不会局限在一张张界面里了。设计的对象是「广义的界面」,你的元素、商品、服务等内容将是夸页面的、跨应用的甚至是跨系统的,这些会动态组成「广义的界面」。
Long Wang retweeted
AIGC 项目结束后,这周开始研究 AutoGPT 在业务场景的可行性。我的工作内容从 GC 转向了人-机,机-机。虽然目前 AutoGPT 还处在相对实验性的阶段,但依然惊艳。#AutoGPT 将会进一步构建更加庞大复杂的协同网络,这背后的每一个人可能变成盯着大屏幕的「交易员」,那么谁又会成为算力领域的华尔街呢。
Long Wang retweeted
sharing my story and a secret with @sequoia
Long Wang retweeted
The invention of modern writing instruments like the typewriter made writing easier, but they also led to the rise of writer’s block, where deciding what to write became the bottleneck. Similarly, the invention of agentic coding assistants has led to a new builder’s block, where the holdup is deciding what to build. I call this the Product Management Bottleneck.
Product management is the art and science of deciding what to build. Because highly agentic coding accelerates the writing of software to a given product specification, deciding what to build is the new bottleneck, especially in early-stage projects. As the teams I work with take advantage of agentic coders, I increasingly value product managers (PMs) who have very high user empathy and can make product decisions quickly, so the speed of product decision-making matches the speed of coding.
PMs with high user empathy can make decisions by gut and get them right a lot of the time. As new information comes in, they can keep refining their mental models of what users like or do not like — and thereby refine their gut — and keep making fast decisions of increasing quality.
Many tactics are available to get user feedback and other forms of data that shape our beliefs about users. They include conversations with a handful of users, focus groups, surveys, and A/B tests on scaled products. But to drive progress at GenAI speed, I find that synthesizing all these sources of data in a PM's gut helps us move faster.
Let me illustrate with an example. Recently, my team debated which of 4 features users would prefer. I had my instincts, but none of us were sure, so we surveyed about 1,000 users. The results contradicted my initial beliefs — I was wrong! So what was the right thing to do at this point?
- Option 1: Go by the survey and build what users told us clearly they prefer.
- Option 2: Examine the survey data in detail to see how it changes my beliefs about what users want. That is, refine my mental model of users. Then use my revised mental model to decide what to do.
Even though some would consider Option 1 the “data-driven” way to make decisions, I consider this an inferior approach for most projects. Surveys may be flawed. Further, taking time to run a survey before making a decision results in slow decision-making.
In contrast, using Option 2, the survey results give much more generalizable information that can help me shape not just this decision, but many others as well. And it lets me process this one piece of data alongside all the user conversations, surveys, market reports, and observations of user behavior when they’re engaging with our product to form a much fuller view on how to serve users. Ultimately, that mental model drives my product decisions.
Of course, this technique does not always scale. For example, with programmatic online advertising in which AI might try to optimize the number of clicks on ads shown, an automated system conducts far more experiments in parallel and gathers data on what users do and do not click on, to filter through a PM's mental model of users. When a system needs to make a huge number of decisions, such as what ads to show (or products to recommend) on a huge number of pages, PM review and human intuition do not scale.
But in products where a team is making a small number of critical decisions such as what key features to prioritize, I find that data — used to help build a good mental model of the user, which is then applied to make decisions very quickly — is still the best way to drive rapid progress and relieve the Product Management Bottleneck.
[Original text: deeplearning.ai/the-batch/is… ]


















