Translation and notes
A readable adaptation of the article's core ideas, with the original source clearly credited.
At the beginning of a company, it is tempting to make everything scalable from day one: acquisition, sales, onboarding, support, even culture. But the beginning is usually less like building a growth machine and more like earning trust by hand. The founder has to stay close to users, hear the pain directly, and help create the first version of the experience personally.
Unscalable work is not waste when it is chosen well. It is a learning instrument. When founders onboard users themselves, answer support, or protect quality manually, they learn things that early dashboards cannot reveal. These habits should not last forever, but they often shape the product and the organization.
The operating test is whether the manual work creates learning or loyalty. If it only exhausts the founder, it is a trap. If it helps users feel that a serious team is listening, or helps the team see where value is really created, a small manual act can become the root of large growth.
The useful way to read Do Things that Don't Scale is to connect it to a live decision rather than consume it as general advice. A product choice, a customer conversation, a hiring question, or an operating tension can turn the essay from inspiration into a thinking tool.
Operating takeaways
- In the earliest stage, talk to users directly and complete the experience manually.
- Before automating, learn which part of the experience creates real value.
- Unscalable work should be temporary, intentional, and insight-generating.
- Write one concrete operating question after reading.
Quick feedback
What did this article make clearer for you?
Choose a reaction or share a question or experience. Useful responses can shape future notes.
This is a free adaptation, not a word-for-word republication of the original article.