正在加载视频...

视频加载失败

.David Sacks: Anthropic is good at two things—product releases, and scaring people. “They have a proven pattern of using fear as a way to market their new products.” He had Grok create a list of every time they’ve used scare tactics on the public. “At the same time they...

81,234 次观看 • 4 个月前 •via X (Twitter)

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

Steve Jobs explains why it's dangerous for sales and marketing people to run tech companies: Jobs starts with PepsiCo and John Sculley: "At PepsiCo, they at most would change their product once every 10 years. To them, a new product was like a new-size bottle." In that world, sales and marketing people drove success and ran the company. For PepsiCo, that worked. But Jobs warns about what happens in tech: "The same thing can happen in technology companies that get monopolies like IBM and Xerox. When you have a monopoly market share, sales and marketing people end up running the companies." The danger? "The product people get driven out of the decision-making forums and the companies forget what it means to make great products. The product genius that brought them to that monopolistic position gets rotted out by people who have no conception of a good product versus a bad product, no conception of the craftsmanship required to turn a good idea into a good product, and no feeling in their hearts about wanting to really help the customers." Jobs uses Xerox as his cautionary tale, where marketing executives had "no clue" about the revolutionary technology they owned: "They grabbed defeat from the greatest victory in the computer industry. Xerox could have been the IBM of the '90s. Could have been the Microsoft of the '90s." The bottom line: Jobs argues that sales and marketing people can run companies where products don't change. But in technology, they'll hurt what made the company great.

Data Desk

234,989 次观看 • 7 个月前

Stripe CEO Patrick Collison shares the tactics he used for finding product/market fit “We tried very hard to understand in granular detail what exactly it was that people were doing, where they were tripping up and so on.” Patrick gives some examples of specific tactics: - A public chat room to provide support to people integrating Stripe - For the first 10 users of Stripe, every API request sent an email to the founders so they could better understand how users were using their product and see if users were doing anything weird - All errors generated a high-priority email to the founders. This created a pleasant user experience where 15 minutes after hitting an error, Patrick could reach out to them and let them know the issue was fixed “These are all kind of examples of a general pattern of trying to be hyper-attentive to all the micro details of what people were doing in the product and iterating rapidly in response to it. Generally speaking, I think pre-product/market fit metrics are actually relatively unhelpful because probably not that many people are using your product. If it’s 20 users, you can in some sense afford to just look at everything they’re doing to understand what’s working and what isn’t.” Another example of this Patrick gives is embedding a text input on each of their web pages with placeholder text prompting users to give them useful feedback(e.g. “The worst thing about Stripe is…”, “The worst thing about this page is…”, or “I really hate the way Stripe does…”). As Patrick explains: “At that stage, you have to be kind of masochistic. We’d always be waking up to all these emails telling us all the terrible things about Stripe. But that was a helpful to-do list for the day ahead." Source: Y Combinator (Oct 2018)

Startup Archive

32,192 次观看 • 23 天前

Stripe CEO Patrick Collison shares the tactics he used for finding product/market fit “We tried very hard to understand in granular detail what exactly it was that people were doing, where they were tripping up and so on.” Patrick gives some examples of specific tactics: • A public chat room to provide support to people integrating Stripe • For the first 10 users of Stripe, every API request sent an email to the founders so they could better understand how users were using their product and see if users were doing anything weird • All errors generated a high-priority email to the founders. This created a pleasant user experience where 15 minutes after hitting an error, Patrick could reach out to them and let them know the issue was fixed “These are all kind of examples of a general pattern of trying to be hyper-attentive to all the micro details of what people were doing in the product and iterating rapidly in response to it. Generally speaking, I think pre-product/market fit metrics are actually relatively unhelpful because probably not that many people are using your product. If it’s 20 users, you can in some sense afford to just look at everything they’re doing to understand what’s working and what isn’t.” Another example of this Patrick gives is embedding a text input on each of their web pages with placeholder text prompting users to give them useful feedback(e.g. “The worst thing about Stripe is…”, “The worst thing about this page is…”, or “I really hate the way Stripe does…”). As Patrick explains: “At that stage, you have to be kind of masochistic. We’d always be waking up to all these emails telling us all the terrible things about Stripe. But that was a helpful to-do list for the day ahead. Video source: Y Combinator (2018)

Startup Archive

45,833 次观看 • 7 个月前