46 lines
4.2 KiB
Markdown
46 lines
4.2 KiB
Markdown
|
---
|
|||
|
|
title: ”The Hardest Lessons for Startups to Learn”で気になった部分
|
|||
|
|
author: kazu634
|
|||
|
|
date: 2006-05-06
|
|||
|
|
url: /2006/05/06/_252/
|
|||
|
|
wordtwit_post_info:
|
|||
|
|
- 'O:8:"stdClass":13:{s:6:"manual";b:0;s:11:"tweet_times";i:1;s:5:"delay";i:0;s:7:"enabled";i:1;s:10:"separation";s:2:"60";s:7:"version";s:3:"3.7";s:14:"tweet_template";b:0;s:6:"status";i:2;s:6:"result";a:0:{}s:13:"tweet_counter";i:2;s:13:"tweet_log_ids";a:1:{i:0;i:2343;}s:9:"hash_tags";a:0:{}s:8:"accounts";a:1:{i:0;s:7:"kazu634";}}'
|
|||
|
|
categories:
|
|||
|
|
- つれづれ
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
<div class="section">
|
|||
|
|
<p>
|
|||
|
|
<a href="http://www.paulgraham.com/startuplessons.html" onclick="__gaTracker('send', 'event', 'outbound-article', 'http://www.paulgraham.com/startuplessons.html', '');" target="_blank"><img alt="The Hardest Lessons for Startups to Learn" align="left" src="http://img.simpleapi.net/small/http://www.paulgraham.com/startuplessons.html" border="0" /></a>
|
|||
|
|
</p></p>
|
|||
|
|
|
|||
|
|
<p>
|
|||
|
|
Paul Grahamのサイトで”The hardest Lessons for Startups to Learn”が公開されました。気になった部分について載せておきます。
|
|||
|
|
</p>
|
|||
|
|
|
|||
|
|
<hr />
|
|||
|
|
|
|||
|
|
<ul>
|
|||
|
|
<li>
|
|||
|
|
Users hate bugs, but they don’t seem to mind a minimal version 1, if there’s more coming soon.<br /> （bugsがあるのは論外だけれども、最小のversion 1であれば受け入れる。論文にたとえれば、根本的な事実誤認はあり得ないけれど、発展が見込めるものであればとりあえずはOK…ということか？）
|
|||
|
|
</li>
|
|||
|
|
<li>
|
|||
|
|
Perhaps the most important reason to release early, though, is that it makes you work harder. When you’re working on something that isn’t released, problems are intriguing. In something that’s out there, problems are alarming. There is a lot more urgency once you release. And I think that’s precisely why people put it off. They know they’ll have to work a lot harder once they do.<br /> （困難な問題に取り組むのを嫌がっている可能性を常に疑っておくべき）
|
|||
|
|
</li>
|
|||
|
|
<li>
|
|||
|
|
As with exercise, improvements beget improvements. If you run every day, you’ll probably feel like running tomorrow. But if you skip running for a couple weeks, it will be an effort to drag yourself out. So it is with hacking: the more ideas you implement, the more ideas you’ll have. You should make your system better at least in some small way every day or two.<br /> （常に改善することを考えよ）
|
|||
|
|
</li>
|
|||
|
|
<li>
|
|||
|
|
They’ll like you even better when you improve in response to their comments, because customers are used to companies ignoring them. If you’re the rare exception– a company that actually listens– you’ll generate fanatical loyalty. You won’t need to advertise, because your users will do it for you.<br /> （何らかの反応をしてくれた人の話は謙虚に耳を傾けるべき。）
|
|||
|
|
</li>
|
|||
|
|
<li>
|
|||
|
|
If your product seems finished, there are two possible explanations: (a) it is finished, or (b) you lack imagination. Experience suggests (b) is a thousand times more likely.<br /> （もうこれ以上考えられないというときは、想像力が欠けていると思った方がよい）
|
|||
|
|
</li>
|
|||
|
|
<li>
|
|||
|
|
The other thing I repeat is to give people everything you’ve got, right away. If you have something impressive, try to put it on the front page, because that’s the only one most visitors will see. Though indeed there’s a paradox here: the more you push the good stuff toward the front, the more likely visitors are to explore further.<br /> （自分の印象に強く残ったものをいつも語るようにすべき）
|
|||
|
|
</li>
|
|||
|
|
<li>
|
|||
|
|
As Richard Feynman said, the imagination of nature is greater than the imagination of man. You’ll find more interesting things by looking at the world than you could ever produce just by thinking. This principle is very powerful. It’s why the best abstract painting still falls short of Leonardo, for example. And it applies to startups too. No idea for a product could ever be so clever as the ones you can discover by smashing a beam of prototypes into a beam of users.<br /> （つねにusersが求めるものを作り続けること）
|
|||
|
|
</li>
|
|||
|
|
</ul>
|
|||
|
|
</div>
|