Rules for revolutionaries

此记录保留了作者、时间和来源链接，请打开 HN 阅读完整上下文。

此记录保留了作者、时间和来源链接，请打开 HN 阅读完整上下文。

此记录保留了作者、时间和来源链接，请打开 HN 阅读完整上下文。

此记录保留了作者、时间和来源链接，请打开 HN 阅读完整上下文。

此记录保留了作者、时间和来源链接，请打开 HN 阅读完整上下文。

此记录保留了作者、时间和来源链接，请打开 HN 阅读完整上下文。

此记录保留了作者、时间和来源链接，请打开 HN 阅读完整上下文。

此记录保留了作者、时间和来源链接，请打开 HN 阅读完整上下文。

The excellent book by Guy Kawasaki, "Rules for Revolutionaries", has examples from lots of industries over various periods of time. I'm confused by what you mean about "business models", here. I doubt that you could say that Henry Ford had a "business model" when he went into business; what he had was a mechanical knack, and the idea that cars should be manufactured the way that guns were at the time. That turned out to be a great idea -- and one that pretty much all automotive manufacturers today have completely forgotten -- but I would hesitate to call it a "business model". Business strategies , however, are pretty damn useful, and Guy Kawasaki's book is about nothing but. It was the first book I read, years ago, that turned me on to the idea of having a business.

Not on the list: Guy Kawasaki's "Rules for Revolutionaries". It's been one of my guides for a long time, and it's responsible for changing the way I think about business enough to make me want to run my own.

…es how to really understand user perspectives as opposed to 'inside-out' development. The book's based on many principles taught in the Pragmatic Marketing prodm course. Inspired (Marty Cagan) - good cross section of PM, covers People, Process and Product separately. Startups to large companies. The Art of Product Management - a series of articles, describes software PM in startups to larger companies. More about the role of PM rather than product itself. Rules for Revolutionaries - Guy Kawasaki's book, half entrepreneur morale book and half how to create a product quickly. --- Blogs --- Cranky Product Manager - crankypm.com Silicon Valley Product Group - svpg.com (Marty Cagan's blog) --- I would avoid: --- Value Prop (Jose Palomino) Will It Fly? (Thomas McKnight)

…ery vague terms, they can't usually be specific enough to actually help someone that's trying to implement an idea. I _think_ it was Guy Kawasaki that described this in "Rules for Revolutionaries", but it might've been Gladwell in "Blink" -- I don't remember now. Anyway, you're usually better off making observations about behavior and then attempting to solve the problems that you see there. In this case, you could frequent web designer forums and the like, as well as the forums for competing software, and see what the most common complaints and requests are.

…mpetitors do a particular thing. By that metric, Amazon doesn't need to provide awesome customer service because their competitors don't either. (See also Guy Kawasaki's Rules for Revolutionaries.)

I kind of agree, but with the caveat that nobody's right all the time. (See also the "Don't let bozosity get you down" section of Guy Kawasaki's "Rules for Revolutionaries".)

…m as a distraction that is sometimes an opportunity. To really love criticism is to dwell on what will ultimately be a distraction. I really wish I could find my copy of Rules for Revolutionaries. (I really dig that book, and it was signed! Sometimes I loan it out ... rats.) It cited some specific examples of this, sometimes where businesses had too closely followed criticism and been hurt by that, and others where they hadn't followed it, and benefited from that. So, it's not just scheduling criticism. In the book writing example, sometimes you have to know when to ignore your editor altogether.

…ruth of the matter ...unless I assert that morality is subjective. :-) As for the rest of it ... well, I do disagree. I think Guy Kawasaki outlined it best in his book, "Rules for Revolutionaries". It has a section titled, if I remember correctly, "Don't let bozosity get you down". A certain amount of criticism that a person will encounter will be, well, wrong. It can even be wrong when it's coming from an expert. You see this all the time in the business world. I can't tell here if you're suggesting that a person take all criticism to heart -- I think so, because of the way you talk about changing to adapt to criticism -- but, if you are, then you're suggesting that a person allow themselves to be buffeted by the winds of the popular and the trendy. There's no way to always to always be correct, to always do the right thing. You might li…

…n issue. My impression is that GK'S intention is not to mock other people, but to motivate them to do something great. Also, to chill out in a way, I guess. At least in "Rules for Revolutionaries" he is also mocking himself, when he lists famous blunders and also mentions him dismissing the offer to work for Yahoo in it's early days, for how could it possibly successful. I like his books, and even if not everything is new (how could it be), some things need to be repeated over and over again to finally sink in. Also, I just looked at trueomors again: it seems the quality of submissions has improved greatly compared to the early days.

I actually don't read any of the above unless linked from another source - too much noise, not enough signal. I read Programming Reddit, News.YC, and occasionally Startupping and LambdaTheUltimate. I try to keep up with some blogs of startup-type people - Dharmesh Shah, Joe Kraus, Raganwald, Paul Buchheit, Mark Fletcher, and Marc Andreesen and Wil Schroter look interesting based on their recently-linked news.YC articles. Also, don't underestimate the importance of good old fashioned dead-tree books. I know it's fashionable to spend all day online now, but I still find I get lots more information out of published works than the Internet (the net is great for pointers to books, though). I read a lot of history, economics, corporate histories, some biographies, theoretical computer science, etc. Some selected titles off my reading history (m…