2 ms·
E-Myth Revisited: Why Most Small Businesses Don't Work and What to Do About It
- davidw 17y agoI just finished this book, and it's interesting, although somewhat less targeted at startups than at small businesses. Indeed, some of the advice contained seems to actually go against how I have always seen startups. For instance, "operations manuals" are things best left until you are a Big Company - better to spend time working on the product rather than worrying about creating some kind of 'system' to make you replaceable. Indeed, reflecting on this advice is an interesting way of considering the differences between a real 'startup' and someone simply starting a business. Anyone else read it? What'd you think?
- josemaria 17y agoIf you read the history of Paul Graham's Viaweb startup, you will learn that Paul created Viaweb so it can be easely selled. It documented everything.
- davidw 17y agoYahoo wasn't interested in Viaweb in terms of how they did things (the 'system'), though, but in terms of the product. If they were interested in the 'system' that PG and company had, PG would have taught a large number of Yahoo employees Lisp. And... how do you know what they did and did not document? Obviously they documented things enough to get Yahoo people involved... but beyond that?
- dagw 17y ago"Operations manuals" sound like a scary bureaucratic thing that only big companies have, but personally I think everybody needs them. It doesn't have to be big and formal, it could simply be a wiki on the internal web site, but somewhere all important steps and procedures should be documented. Even if no one gets hit by a bus, having a check list on how important things work is always handy to refresh your memory, especially if it's something you only do a couple of times a year. Also if you hire a new person, being able to point them to a place which explains exactly how your company does version control or how your build process works will save everyone a lot of time.
- davidw 17y agoSee above, but the message I got was that if you're a small restaurant or a bike repair shop or something like that, the thing to work on is the 'system', which means making it so you can drop new people in to grow by handing them a manual which describes in detail how things are done. I'm not so sure something like a tech startup is like that. What would have been the point at replacing most founders early on? The whole point is developing a product that scales with the 'hockey stick' curve, which is very different from growing, say, a bike shop into a chain of 3 or 4 bike shops. I agree completely with documenting things, but one is documenting stuff so it doesn't get lost or have to be explained out-loud every time, to help people get up to speed with things. The other is create a system for people to work in that doesn't leave people much room to screw up, so that you can have someone new up and flipping burgers in a day. Edit - the book makes a lot of sense in the context of a 'small business' where the goal, often enough is to extract yourself from being the business and make it run without you. Where I'm a bit more dubious is about startups...
- theBobMcCormick 17y agoCorrect me if I'm wrong, but I thought part of the idea was not so much to replace the founder as it is to allow the founder to drop parts of their responsibilities as you expand. I would think that would be applicable to most startups.
- nhebb 17y agoI thought the entire book could have been written in less than 10 pages. For years I worked as a manufacturing engineer, so documenting your processes is kind of second nature to me. On the other hand, I hated bureaucratic systems like ISO 9000, so my advice is always to do the minimum necessary. For startups, just keep simple documentation of essential processes. For example, I rarely had to process refunds through PayPal, so I would forget how to do it. I kept overlooking the refund link. So I made a screen shot, circled the link, and saved it in my process documentation folder. Basic, but effective. For other processes, I have written documents, flowcharts, and checklists, depending upon how complex the process is. If you have 1-2 people in your company, you're doing it for your own benefit, so there's no need to be formal.
- davidw 17y ago> I thought the entire book could have been written in less than 10 pages. That's true of a lot of business books - even some really good ones. I think the difference, in terms of documentation, is that you're more or less describing "stuff that's useful for us to remember and keep in a specified place", as opposed to "let's document how people work here in detail in order to be able to plug people in". I think it's certainly a valid idea for many fields; I'm just not sure how or where it's applicable to high tech startups at an early stage: most everything is going into the product itself, which is what's going to grow the company, rather than the systems that surround it, although of course you have to increase efficiency where you can...
- hga 17y agoI read the first edition, and it had more than 10 pages worth of useful advice including a fair amount of stuff besides the "document processes" advice (although that was its biggest message). One of the best was "make sure there's a head for every cap." I.e. there are a lot of necessary roles in every small business (at the highest level, things like marketing and sales, at a low level, say, backups); make sure every important role is identified and assigned to someone. It's still on my "top 5" list of books anyone starting up a company should read.