I'm back at SXSW as one of the RWW contributors covering the interactive festival. This afternoon I attended Jason Fried's presentation on "Stuff We've Learned at 37 Signals". 37 Signals is a software company headquartered in Chicago, IL that started as a interactive design company and has since become one of the leading software companies for personal productivity software.
Currently over one million people and businesses use their productivity applications (including RWW, which is a paying customer of Basecamp). They also are responsible for creating and then open sourcing the popular web developer language Ruby on Rails. Jason Fried is the company's founder. As a company I've long respected, it was interested to hear him discuss some of the things he's learned developing 37 Signals.
Jason started his presentation talking about "the great unknown," which he defined as the things that hang over every entrepreneur's head when they are starting a company. For example, "what about when we have 1M customers or 100 employees." Jason encouraged people to ignore these concerns and focus on the now. He pointed out that often as entrepreneurs, we worry about the impact of our decisions rather than just making the right decision. He asserted that this is crazy, because decisions made today don't have to last forever - we "must optimize for today."
The next point was about interpersonal dynamics in the workplace and watching out for what he called 'red flags.' Red flags are basically words or phrases that end up causing problems in communications. For example, at 37 Signals they learned to be careful with the words: need, can't, easy, only, and fast. For example saying, how easy someone else's job is or that they can't ship a product without one feature.
He talked about the powerful reaction people had to Basecamp when they first released it (Basecamp is a very lightweight project management tool). They realized this was because the tool was helping other people do their job better. This has become part of their philosophy, looking for opportunities in the marketplace to "spot chain reactions and be the catalyst" around helping others.
This is actually a concept that Jason borrowed from Clayton Christensen (a famous professor at Harvard Business School) in the books Innovators Dilemma and Innovators Solution. The idea is that there exists an entire market of nonconsumers, or people who have a need but existing players aren't targeting these people. The advantage of targeting this segment is that you minimize the chance for competition from entrenched players.
At 37 Signals, Jason reported they are always asking questions to make sure they are doing the right things. Internally, this list of questions includes:
Given the firm's background, this was a lesson I found particularly interesting. Jason claimed that the "Biggest sin on the internet right now is bad copywriting ... paying too much attention to pixels and not enough attention to words." Beyond this he pointed out that words are actually less expensive to correct and improved copy will make doing the design second result in a stronger design.
As surprising as I found the last lesson, this one was probably the most obvious given 37 Signal's business. Jason pointed out that you should always "start with the easy way." The interesting and non-obvious point was that he extended this beyond product issues. For example, he recommended people start a company by setting up an LLC, until they need a C Corp.
Jason said that this is the "best business advice he's gotten in some time." It interesting because this isn't something that is intuitive, when you think about tech companies which tend to be focused on what is new and upcoming. However, Jason pointed out that principals can last. For example at 37 Signals, he said they anticipate in 10 years "simple, affordable software" will still be worth investing in.
Jason called chefs the smartest business professionals. He explained this is because they are aware that you become famous and successful by giving knowledge away. For example, chefs have cooking shows and write cook books. Yet it doesn't stop their restaurants from being successful. In fact, he claimed they are probably more successful because of their sharing.
Originally David Heinemeier Hansson (Jason's partner) and Jason didn't live in the same city. They eagerly awaited David moving to Chicago and being able to get even more done. Interestingly, when David arrived they actually found productivity decreasing. At 37 Signals, they have come to believe that this was due to the increased interruptions; and so they ended up favoring passive communication like email versus things that are more instantaneous but also interrupt your workflow.
When talking about business plans, financial projections, or features for products 37Signals believes road maps are bad, because "they lock you into the past." The only exception is APIs, because people are counting on it. Instead he said your expectation should be "do the right thing at the right time."
At the beginning of this year, 37 Signals had some infrastructure problems that resulted in a few hours of unscheduled downtime. This was widely discussed on the internet. They quickly posted about what had happened and during the technical problems kept they the homepage updated with status messages. Through this experience, it reinforced their belief that people love you even more if you are open, honest, public and responsive during a crisis.
Rather than trying to make major decisions, when possible, Jason encouraged entrepreneurs to break problems down to the atomic level. In web properties, this is especially powerful because they've been able to break features down to the atomic level and then launch them one at a time. This is good because the team can gain momentum and celebrate little launches. However, it's also good because "when you make tiny decisions, you can't make big mistakes."
Jason ended his presentation by encouraging the audience to make sure their work was significant. He talked about how meaningful he felt the products they were creating were for individuals. Before opening it up for questions, he said that "everything you do should matter."
One of the things I love most about SXSW is the transparency with which so many leaders share about their business. At last year's festival, two of my favorite panels were: Web App Autopsy and The Figures Behind the Top Web Apps.
We'd love to hear any good case studies or lessons you've learned running startups or in business. Please share them in the comments below.
Comments
Subscribe to comments for this post OR Subscribe to comments for all ReadWriteWeb posts
I'm pretty sure I was sitting right behind you, just to the left. You blogging from a Windows laptop?
Great notes, Jason really gave a great talk I really enjoyed it. Thanks for the post summing it all up :)
Rubu on Rails is not a language. It is a framework.
sounds like they're using this "new" agile development technique.
@Michael Whalen Unfortunately it wasn't me. I have a Mac Book Pro!
They created Rails, a framework (a bunch of code), not Ruby, a language which has been around since '95.
Above all they know how to balance life and work :)
Lessons #1 and #13 go well together. If you focus on making tiny decisions, and continually move forward, you will find that the great unknown becomes easier to understand. There are a lot of people out there with big ideas and no action. Much better have small ideas and lots of action.
Thanks! I was sorry I missed this one.
Numbers 2 and 3 are borrowed from Mahan Khalsa's Let’s Get Real or Let’s Not Play. He calls them "slow down for yellow lights, stop at red lights," and "helping clients succeed," and 5, 6, and 12, Mahan calls "No guessing" (which Jason has called in the past "no illusions of agreement"). It's a great book. The audiobook version is great to because it is narrated by the author, and not as word for word reading, but as a conversation.
The best "how to" list for entrepreneurs that I have seen in a long time. Goes into my Thinking bookmark, to revisit often. Thanks.
THANKS! I missed this one and it was a major regret of mine from sxsw. Nice summary
Christine
Loved #2 and #6 -- the right (or wrong) words can make all the difference. Great post, thanks.
Great tips, i love the ideas and concepts behind 37 signals, much of he said is in the Getting Real book.
Great post. I'm impressed with the 37 Signals practice of providing less rather than more. For a long time I've thought word processors have too many features. There would have to be a market for a word processor that does less. Problem is, what kind of less actually works? Which features do you leave out? It's interesting that no-one has yet produced a simple word processor that I actually really like. Too often, simple means clunky, or 'doesn't quite work'. This seems to be the opposite of what 37 Signals is about, where simple means elegant.
Great post - it must have been a great speech by Jason.
I'm a fun of 37signals and the way they approach their software development and marketing and the way they "stand out" of the crowd with their image.
I'd add to "make it matter" and "be successful in making other successful".
I developed Nozbe - a tool for Getting Things Done (GTD) and although there are zillions of to-do lists out there (there is Backpack or Tadalists from 37signals as well), my web app was to have a different approach - combine the methods by David Allen (GTD) and package them in a nice easy-to-use software, 37s-style.
It all worked pretty well for me and my users - people really liked my approach and my web app and it was great to help them get things done (Nozbe was even mentioned as one of the top 11 web apps of 2007 by Lifehack.org)
However, I wanted to give my users even more value, so I created a simple course - 10-step "Simply Get Things Done Course" to help them learn the GTD principles easily with real-life examples based on my web app.
Again, it was a good idea and I received great feedback, but not everyone had the time to read the course.
So I went one step more and created a video-course - to show how each of the 10 steps can be applied in a short 3-5 minute video each. Each video is a recording from one of the workshops I was giving, combined with a screencast from Nozbe.
This proved to be a blast - people are really thrilled with the course, they are watching the videos and learning the GTD with Nozbe and singups and conversions raised significantly after this was introduced.
So my lesson learned: Never stop adding value
Value is not just "new features" - you should give those of course as well, but value is also: advice, course, tutorial, video... just keep giving people value and they will thank you for it and will advocate your service even more. Give people as much value as possible.
Even though most Nozbe Plans cost money (there is a free version as well, of course), giving people value (more bang for their buck) means you're giving them a compelling reason to stay with you and to actually love you and your service.
Not to mention how thrilling it is to receive feedback from users thanking you big time for the value you're giving them. I love receiving these "thank-you" letters every day!
You can see the 10-step course here:
http://www.nozbe.com/page/show/site-course
My 2 cents.