Do you want to build a profitable business or do you want to theorize how to build one?
I was part of a startup with an inexperienced angel who insisted on bringing in a CEO. The CEO made a good pitch to me that we would adopt the lean startup model, so I went along with it.
Anyway the moment he started, the book went out the door. We didn’t have time to discuss things like strategy and market positioning and hypotheses (though he used the word at every opportunity) but we had plenty of time to have risk assessment meetings and road maps and CRM system integrations (zero customers mind you), monthly 3 hour board meetings and weekly 2 hour “senior executive meetings”. The board and executive was larger than our headcount. I had brought an experienced team into the business with me and they were just flown into the ground with this inanity. (It turns out that despite what I’d been told, CEO had only ever been in corporate settings and had basically no experience with starting a business).
Anyway the outcome was as expected. I’ve been in startups my whole professional life and this was easily the worst experience of career.
The moral of this story is that building a business is hard and none of the books are going to tell you how to do it. So I agree with the parent comment. Pick a couple of books, read them, and get going. If things don’t work out, read a couple more.
But for God’s sake, keep your eye on the prize - have a clear vision, execute an early version of it, find some customers, iterate.
The thing is, it seems to me that many of these books are just extremely information-sparse. Very very lengthened ways of making a small set of points. And because of that, I don't particularly remember the lessons learned from the lot.
200 pages to tell you to talk to your customers? 300 pages to explain that you should focus on your core business and not get sidetracked?
Here's a challenge to those who have read books in that list. Pick one you've found useful, and tell me how it changed you. Then look at your comment and decide whether the book could have just made that same point in that many words.
I find the value in continuing to read these books is offering a new perspective (or at least new wording) on a topic I’ve lost touch with over time.
For example, I don’t really get much out of re-reading “the lean startup “. I know the core principles by heart. I do however tend to forget them over time. They get lost in the noise of my day to day. However, simply re-reading the same book doesn’t bring them back sharply. I find, instead, that reading a similar book helps bring back the vividness.
Maybe reading a few on Blinkist initially but all one really needs:
- is repeatedly trying (even on a side project)
- first principles thinking/common sense
Why? Because:
- all those books are repetitive
- we learn faster by doing
- problems a given project faces at a given time are highly situational
I too have most of these books on a shelf. I’ve found most of them can be skimmed and if they have descriptive chapter naming , just skimming the TOC is enough to get the gist. They rarely go into much detail on execution and generally just talk about a couple business cases as examples of the topic in action. But these usually don’t help on your specific business other than making you aware of the topic. If you’re already interested in business and know some of the lingo these are mostly useless. There’s a lot of blogs and content online I’ve read over the years that is significantly more helpful but I could see how given the state of blogs and content how this could be useful for someone young and/or relatively new to business in general.
- Make a plan
- Execute it
- Execute Faster
- Even more Faster
If you get stuck in some parts such as Market Validation, then picking up the recommended book will be useful. It's easier to learn after failing.
I used to take months thinking about idea, market validation, half-decent codebase. Nowadays it's more of build in a day and try the best marketing channels according to the product. Then onto the next one. Improved "Turn Around Time" really helps in increasing number of iterations.
If it's loved(tolerated) in its worst possible self, then it has a chance.
Pricing is a massive question with infinite possibilities. It usually needs to be tested, continuously. Or just locked in and changed on a regular cadence. A lot of it is going to do with you users and the value your product adds, or how that value is perceived. No book is going to answer this for you, just give you ideas of things to think about. Half of which will likely be N/A to your business.
Some of them are excellent, some have better alternatives since they were published, and some are outright obsolete/no longer valid.
I feel like im stuck on step 1.
Cool ideas are the bane of startups. What you need are problems that lack sufficient solutions. Sometimes a solution does exist but not for certain groups or only at certain budget levels - that's a startup! Flow like water to fill gaps in the market.
Selling a 10% improvement it hard, selling a 10x improvement is much easier...
If you actually have few ideas. then that is also fine. Why do you think you need ideas? You can think about or work on other people's ideas.
+don’t hesitate to take shortcuts
I'm guessing if the 20 books are actually written by people in all seriousness and the belief that they understood and cared about the subject, they're probably still going to be better than what we'll have in ten years, which is 200 books all of which are echoing voids of ChatGPT.
It'll be a lot cheaper to produce such books and put them into the marketplace if you don't actually have to write, learn, or know anything: so much cheaper that it'll become untenable to write 'real' books.
Which mostly means 'marketplace' will stop meaning anything. Knowledge will still mean something but we'll have to arrive at it and disseminate it in different ways that don't resemble the commercial marketplace, as that will not stand up against the cheapness of AI labor.
Summarization tools have existed for a while. They don’t take off because they can solve the core problem of deep learning. It takes time to reshape how you think. Reading some summaries won’t do that.
Not super relevant but this was Henry George’s Progress & Poverty, so a pretty well-known book with fairly detailed arguments.
- Can you explain me X in simple terms? - Explain me different between the items 1 and 2 in your response and provide example? - Could you show this in a tabular form? or tree from using markdown
with chatGPT you have access to elaborate knowledge in the most suibitable way for you. You can learn faster. If you prefer an information in a tabular form, you can do it. You can ask differences between concepts and get examples. In a book you can only learn something written by the author.
