4 ms·
See 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
by davidw 17y ago
See 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.