惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

The GitHub Blog
The GitHub Blog
S
SegmentFault 最新的问题
L
LangChain Blog
Simon Willison's Weblog
Simon Willison's Weblog
N
News and Events Feed by Topic
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
WordPress大学
WordPress大学
M
MIT News - Artificial intelligence
A
About on SuperTechFans
Microsoft Security Blog
Microsoft Security Blog
I
Intezer
Know Your Adversary
Know Your Adversary
H
Heimdal Security Blog
博客园 - 叶小钗
B
Blog RSS Feed
F
Fortinet All Blogs
Hacker News: Ask HN
Hacker News: Ask HN
A
Arctic Wolf
小众软件
小众软件
Help Net Security
Help Net Security
MongoDB | Blog
MongoDB | Blog
aimingoo的专栏
aimingoo的专栏
G
Google Developers Blog
Forbes - Security
Forbes - Security
Latest news
Latest news
AI
AI
I
InfoQ
H
Hackread – Cybersecurity News, Data Breaches, AI and More
C
CXSECURITY Database RSS Feed - CXSecurity.com
W
WeLiveSecurity
C
Cybersecurity and Infrastructure Security Agency CISA
人人都是产品经理
人人都是产品经理
Cyberwarzone
Cyberwarzone
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
J
Java Code Geeks
Engineering at Meta
Engineering at Meta
C
Cyber Attacks, Cyber Crime and Cyber Security
O
OpenAI News
博客园 - 【当耐特】
T
Threat Research - Cisco Blogs
GbyAI
GbyAI
U
Unit 42
D
Darknet – Hacking Tools, Hacker News & Cyber Security
G
GRAHAM CLULEY
Apple Machine Learning Research
Apple Machine Learning Research
宝玉的分享
宝玉的分享
Google DeepMind News
Google DeepMind News
T
Threatpost
T
The Blog of Author Tim Ferriss
罗磊的独立博客

ashishb.net

A day in Luxembourg - the richest country in the world I was asked to install malware during a fake interview Book summary: Breakneck - China's quest to engineer the future by Dan Wang Book summary: How to Teach Your Baby to Read Book Summary: The Discontented Little Baby Book by Pamela Douglas Introducing Amazing Sandbox - run third-party tools and AI agents securely on your machine Why software outsourcing gets a bad reputation? Book summary: The Natural Baby Sleep Solution by Polly Moore A day in Antwerp, Belgium Journey of online influencers Two days in Brussels, Belgium Shortcuts - when we love them and when we don't A visit to Rakhigarhi Three days in overhyped Paris Empty Japan, crowded Tokyo The real lock-in in GitHub is not the code, but the stars 11-day Norwegian Breakaway East Caribbean cruise Sanskrit and Sri Lankan Air Force Use REST with Open API The Achilles heel of American capitalism Costa Rica in 4 days At a juice stall in Sri Lanka A short stay at Warsaw, Poland Best practices for using Python & uv inside Docker Two days in Vilnius, Lithuania How IntelliJ IDEs waste disk space Pregnancy Why there aren't many digital nomads from India Two days in Riga, Latvia To keep your machine secure, run third-party tools inside Docker Family Ties in Your DNA: Some relatives are closer than others Doctors per capita Two days in Tallinn, Estonia Ship tools as standalone static binaries Made in America Two days in Helsinki, Finland Maintaining an Android app is a lot of work The land of good deals Two days in Oslo, Norway FastAPI vs Flask performance comparison Google Search is losing to Perplexity Two days in Dublin, Ireland Continuous integration ≠ Continuous delivery World's simplest project success heuristic London in 5 days It is hard to recommend Python in production Inflation, IRS, Credit cards, and Vendors Temu and the Chinese approach Things to do in Miami Florida Revenue vs Cost Axis Language learning as an adult The unanchored babies of the green card limbo Price variance in the United States A day in Louisville, Kentucky A surprisingly positive experience with Air India Unhospitable Airports Android: Don't use stale views USA = Union of Sales and Advertisement A day in Nashville, Tennessee Minimize Javascript in your codebase A day in Birmingham, Alabama In defense of ad-supported products Real vs artificial world The science behind Punjabi singers Hiking Mt. Fuji The Indian startup bubble is insane Repairing database on the fly for millions of users Book Summary: One up on Wall Street by Peter Lynch It is hard to recommend Google Cloud At the Prague airport Kyoto in three days Migrating from WordPress to Hugo Book summary: Sick Societies by Robert B. Edgerton Statistical outcomes require statistical games Illegal immigrants to Europe via Cairo Tokyo in three days Mobs are Status Games Writing Script matters as much as the spoken language Sri Lanka in 5 days LLMs: great for business but bad business Book Summary: Safe Haven by Mark Spitznagel Mac shortcut for typing Avagraha symbol On a bus with an asylum seeker Nicaragua in 5 days When to commit Generated code to version control Why I always buy a local SIM in a foreign country Use Makefile for Android Four days in Guadalajara, Mexico Android Navigation: Up vs Back Hotels vs Airbnb vs Hostels Currency issues in Argentina Abstractions should be deep not wide Some data on podcasting Always support compressed response in an API service A day in El Calafate - Patagonia, Argentina Hermetic docker images with Hugging Face machine learning models American Elections The sound of "ch" API services should always have usage Limits Hiking in El Chaltén - trekking capital of Argentina
Book Summary: The Mom Test by Rob Fitzpatrick
Ashish Bhatia · 2023-05-15 · via ashishb.net

The Mom Test is an intriguing book by Rob Fitzpatrick about how to do user research and validation of one’s product idea.

  1. Until you get specific with an idea, all products seem good.
  2. Don’t ask future hypothetical questions. Ask about specifics in the past.
  3. Talk less; listen more. If you are doing more talking then you are not learning; you are pitching.
  4. A user who doesn’t have time to try the good-enough products that exist today won’t have time to try your perfect product tomorrow either. This user won’t value your product regardless of what they say.
  5. You should charge based on what value you create not what it costs you. See how much the user is paying currently to solve the problem.
  6. User research is about the user and not your product. If they start complimenting you, then you are doing something wrong. If they complimented you then immediately bring the meeting back to the learning conversation.
  7. Users’ ideas and feature requests should be understood but not obeyed.
  8. For unpleasant tasks, ask yourself if you delegated this task to someone else, what would they do? And then do that yourself.
  9. In case of product risk, for example, games, it is better to build the core game-play mechanics and test it early on.
  10. The early user meetings should be quick. It is better to do them spontaneously in person, at say conferences. Video calls and phone calls are expected to be more formal.
  11. During a customer research avoid giving too much information about what you are working on to avoid biasing them. However, it still, nudges the discussion in a useful direction.
  12. Every meeting succeeds or fails. You lost a meeting if it ends with a compliment or a stalling tactic.
  13. To identify real early adopters, look for currencies of commitment. A compliment costs nothing and it is worth nothing. A real commitment is cash, time (e.g. committing to a trial), or reputation.
  14. At the initial stage, the goal is not to get users but to get learning about users. So, adding temporary friction can help identify serious ones.
  15. The rejection rate, of say cold calls, is completely irrelevant at the initial stage. The goal is to find some potential users to learn from and not to build a reproducible sales pipeline.
  16. The ultimate excuse to ask random people is to claim that you are doing Ph.D. research or claiming to write a book.
  17. How to send cold emails (VFWPA - Very Few Wizards Properly Ask!)
    1. Vision - e.g. helping busy teachers in classroom activities
    2. Framing - tell them if you have a product to sell
    3. Weakness - tell them about the product, this shows one has done the basic research
    4. Pedestal - Show how the user is uniquely positioned to help
    5. Ask - ask for the help
  18. When the customer feedback is all over the map, you cannot extract value. You need to narrow down to one specific segment of customers to actually start learning.
  19. The best early adopters are reachable, profitable, and personally rewarding. The last part is really important. Choose customers you like, admire, and enjoy being around. Customer research is draining and if you don’t like the market you are in, you are going to drain yourself out.
  20. You can make three mistakes in early segmentation - picking the wrong segment, overlooking the right segment, or not talking to all the stakeholders in the case of a business.
  21. If you don’t know what you are trying to learn, don’t bother having customer conversations. You need to have some hypothesis of what you are trying to learn first.
  22. Best to have two people doing user research together. One takes notes. One interview. More than two, and it starts to feel like a focus group. And the customer becomes intimidated. If you don’t have a co-founder, find a friend who you can count on.
  23. Customers are surprisingly happy to be recorded. However, almost no one goes through recordings later, so, there isn’t a point in collecting one. Best to transfer notes to a spreadsheet afterward along with an emoji symbolizing emotions.
  24. Do not take notes on the laptop. It makes the conversation more formal. The only way to make it work is to put the laptop on the side and do touch typing while talking to the customer! And of course, tell the customer that you are a super-slow writer!