The Smallest Test
Who this book is for
Người đang xây một business ở Việt Nam trong giai đoạn đầu, từ lúc còn là một ý tưởng tới lúc có vài chục khách trả tiền. Người đọc TỰ LÀM gần như mọi việc, tiền của chính mình, và câu hỏi lớn nhất của họ là thứ này có ai cần không. Đây KHÔNG phải người điều hành một công ty đã chạy: chiến lược, tổ chức và mở rộng thuộc cộng đồng CEO.
Sound familiar?
- Builds for six months before learning nobody needs it.
- Adds features for fear of missing one, and each pushes the launch further out.
- Unclear which question this build is answering.
- Finishes the test with no conclusion, because no threshold was set beforehand.
After reading, you can
Help a founder design the smallest test that answers the most important question.
Each chapter answers one question
Chapter 1: Is my prototype testing the riskiest question?
Which question is this prototype answering?
A prototype is not meant to make a product; it is meant to answer a question dangerous enough to matter.
Chapter 2: How can I learn anything before writing code?
Is there a way to find this out without building anything?
Most questions can be answered without writing a single line of code.
Chapter 3: Should my test be good, or small enough to repeat?
How many days and how much money does this prototype take?
The smaller the prototype, the faster you learn, and you still have money left to try a second time.
Chapter 4: What's the harm in testers being nice to me?
Who will test this, and do they have any reason to be kind to me?
A prototype only tells the truth when users do not know you and do not want to please you.
Chapter 5: If nothing changes after a test, what did I learn?
What will this result make me do differently next week?
An experiment without a conclusion is time spent that bought no information.