29 lines
1.5 KiB
Markdown
29 lines
1.5 KiB
Markdown
---
|
||
title: Because ”it sucks” is not a reason to redesign.
|
||
author: kazu634
|
||
date: 2009-10-07
|
||
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:4813;}s:9:"hash_tags";a:0:{}s:8:"accounts";a:1:{i:0;s:7:"kazu634";}}'
|
||
categories:
|
||
|
||
|
||
---
|
||
<div class="section">
|
||
<blockquote title="Insight: “Because it sucks” is not a reason… by Ryan of Basecamp" cite="http://37signals.com/svn/posts/1963-because-it-sucks-is-not-a-reason-to-redesign">
|
||
<p>
|
||
“Because it sucks” is not a reason to redesign. “It sucks” leaves the scope wide open with no measure of success. It’s a sure way to scrap the good decisions you made along with the mistakes.
|
||
</p>
|
||
|
||
<p>
|
||
</p>
|
||
|
||
<p>
|
||
Instead, start the redesign with a question: “What is right about this design?” Use that perspective to identify specific problems and then target those exact problems.
|
||
</p>
|
||
|
||
<p>
|
||
<cite><a href="http://37signals.com/svn/posts/1963-because-it-sucks-is-not-a-reason-to-redesign" onclick="__gaTracker('send', 'event', 'outbound-article', 'http://37signals.com/svn/posts/1963-because-it-sucks-is-not-a-reason-to-redesign', 'Insight: “Because it sucks” is not a reason… by Ryan of Basecamp');" target="_blank">Insight: “Because it sucks” is not a reason… by Ryan of Basecamp</a></cite>
|
||
</p>
|
||
</blockquote>
|
||
</div>
|