2 days ago
- The founder started working for himself to avoid being bossed around and does not let customers dictate his work.
- Saying 'yes' too often to feature requests can sink a product; the founder frequently says 'no' to maintain focus.
- User feature requests often lack context and may not benefit the broader user base; understanding the underlying problem is key.
- Examples of 'hard no's' include avoiding automatic machine activation during validation due to technical costs and not becoming a payment provider.
- Feedback is collected over time, and features may be implemented years later when the problem space is fully understood.
- You can build for users without obeying them.