38 Tweetables From The 37 Signals Master Class

About This Blog

This site is for  entrepreneurs.  A full RSS feed to the articles is available.  Please subscribe so we know you're out there.  If you need more convincing, learn more about the site.



And, you can find me on Google+

Connect on Twitter

Get Articles By Email

Your email:


Blog Navigator

Navigate By : 
[Article Index]

Questions about startups?

If you have questions about startups, you can find me and a bunch of other startup fanatics on the free Q&A website:


Subscribe to Updates


30,000+ subscribers can't all be wrong.  Subscribe to the OnStartups.com RSS feed.

Follow me on LinkedIn


Current Articles | RSS Feed RSS Feed

38 Tweetables From The 37 Signals Master Class


The following is a guest post from Noah Kagan.  Noah was the lucky winner in the OnStartups contest to win a free ticket to the 37signals sold-out master class

Thanks to Dharmesh I was very lucky to attend the sold out 40 person class in Chicago. DHH, Jason and Ryan broke the day into 3 parts. How they worked, design theory and feedback on clients sites. fried dhh

I've NEVER gone to a $1,000 event so I was mostly curious to see who else spent that much money. The audience was comprised of aspirational entrepreneurs, a fair amount of web dev shops and even my friends at YouNeedABudget.com.

Overall, I would say it was a great experience. They even ripped apart my new site RewardLevel.com in front of the class which provided invaluable advice. Most surprising was the emphasis on copywriting over design.

I think for some in attendance it's easy to get wrapped up in the hype of 37Signals and the idea that you have to do your business like them to be successful. I think for the most part they have brought a fresh / clear attitude to building a company and learned a lot I wanted to share with you below.

38 Tweetables From 37 Signals

If you like one or more of these, you're encouraged to tweet them using the conveniently provided link.

Building Great Products

1) Always start off with what's the problem? [tweet]

2) Never go with your first instincts. [tweet]

3) Limiting yourself on tools will enable you NOT to add more things than necessary. [tweet]

4) On your webpage, reduce time spent on non-core features. [tweet]

5) The most important thing for designing is copywriting. [tweet]

6) Realize, the level of fidelity is wrong for the stage. Don't go big when all you need is basics. [tweet]

7) The product is the one with the ego. The product has to be right. Take nothing personally. [tweet]

8) Lack anything final. Design is just one battle. [tweet]

9) When you take months to do something you add months, focus on time limitations and only the core wins. [tweet]

10) Trade with people if they feel strongly about certain decisions. [tweet]

11) Real simple examples work better than marketing speak. [tweet]

12) Never do lorem ipsum blah blah. [tweet]

13) Try it and look at the data for decisions. Don't be attached to your decision. [tweet]

14) Treat all customers the same. No favoring. You never know how much they'll be worth. [tweet]

15) Set tight time frames, solve the simplest problems. [tweet]

16) Leaving software unfinished is the natural state of software. [tweet]

17) Bring out the scope hammer. Taking too long, means we are doing too much. [tweet]

18) We wrote out everything we wanted to do next year, then over lunch we killed that. Things change. [tweet]

Design Theory

19) Try to understand the difference between features and problems! [tweet]

20) Make sure you understand the problem. Ideally, its a problem you are facing yourself. [tweet]

21) What do you want me to do on this page? Focus on that. [tweet]

22) The power of 3. Keep teams small and effective. [tweet]

23) Let me make the best use of my time, don't stop me with meetings. [tweet]

24) Ask a person to draw the screen from memory and only the most important things will be remembered. [tweet]

25) Use a thick marker during design since you can only focus on the key things. [tweet]

26) We judge a lot about how good a design is by how long it takes to implement. [tweet]

27) Users always come with feedback in the form of solutions, not problems. Try to understand root issues. [tweet]

28) Everyone we hire gets screened for being a good writer, including engineers. [tweet]

29) Epicenter design. What is the most important thing on the page? [tweet]

30) Rebuild pages from the most important thing out. See where you get to the point where it gets complicated. [tweet]

31) Mobile development is great for design. Since you are limited and only put on the essentials. [tweet]

32) Copywriting is significantly undervalued! [tweet]

Random Nuggets

33) Charge from day one. If its not good enough then there is not enough value. [tweet]

34) Our whole business is beating email by an inch. [tweet]

35) Email is the most popular software application in the world. [tweet]

36) Don't use RSS readers. Go to the sites when you want. Helps focus. [tweet]

37) Short bursts of working together are more effective than full-time together in the office. [tweet]

38) The 37signals logo is a guy saying hi. [tweet]

This article was written by Noah Kagan who runs http://RewardLevel.com. A site that rewards your customers for signing up for your service. Follow him on twitter.com/noahkagan

Posted by Dharmesh Shah on Wed, Dec 01, 2010


Thanks Darmesh these tweetables are simple and to the point - certainly got me thinking, back to basics.

posted on Wednesday, December 01, 2010 at 1:50 PM by Glenn Hinds

This is a great post, thanks for sharing.

posted on Wednesday, December 01, 2010 at 1:56 PM by Chantal Ireland

A lot of this list really isn't useful without context. 
For example, "Never do lorem ipsum blah blah". What does that mean? I know what it mean, because I follow 37 signals, and have read their blog/books. But most people will have no idea what that means. 
And again, #8 "Lack anything final. Design is just one battle.".  
Sounds really deep. No idea what it means though. 
#26 - We judge a lot about how good a design is by how long it takes to implement. 
"How quickly it is implemented" you mean? 
140 characters might be great for twitter, but we've lost too much information here.

posted on Wednesday, December 01, 2010 at 2:01 PM by Sandeep Ghael

Agreed that more context would be useful.  
If anyone else that participated in the event would like to write a guest post, that would be awesome. I think the community would appreciate it -- I know I would.

posted on Wednesday, December 01, 2010 at 4:53 PM by Dharmesh Shah

"Charge from day one. If its not good enough then there is not enough value." Huh? Besides not making sense, I think the message was supposed to be "charge for it, even if it stinks right now."

posted on Wednesday, December 01, 2010 at 5:30 PM by Richard

I saved $980 when I bought Rework :)

posted on Wednesday, December 01, 2010 at 11:31 PM by Aymeric

What exactly is wrong with RSS readers?

posted on Thursday, December 02, 2010 at 3:07 PM by Richard

These guys are so arrogant, if they ever stumble the world is going to beat them down.

posted on Thursday, December 30, 2010 at 1:23 PM by Dogeye

The tweetables are so on point. You rock Darmesh! The whole site is superb.

posted on Sunday, January 09, 2011 at 4:26 PM by Perfect Financial Sector

Comments have been closed for this article.