You’re reading Signal v. Noise, a publication about the web by Basecamp since 1999. Happy !

Why it's wise to launch softly

Matt Linderman
Matt Linderman wrote this on 18 comments

How the term “trial balloon” originated: The Montgolfiere brothers came up with a design for the hot air balloon but wanted to make sure it would really work before getting in one themselves. So they first released several unmanned trial hot air balloons. Then they sent up several farm animals to make sure the air at higher levels was safe to breathe. After that, they tried a manned expedition.

It’s a smart approach. But in the business world, a lot of people think the opposite is the way to go. They want to launch big. They want a huge PR splash right away. They want the big bang.

Too bad. You don’t need a big bang – slow evolution is what you want. Unless you absolutely must “open wide,” abandon the mass introduction strategy. Instead, launch softly.

Restaurants start off by serving friends and family before they invite the media.

Movie studios use test screenings to fine tune movies. The people behind the scenes know that until you get into the test screenings and see what people really think, you just never know.

Likewise, Jerry Seinfeld and Chris Rock try out jokes in small clubs before hitting arenas.

Authors test out material by writing magazine articles, ebooks, and/or releasing chapters online. Michael Pollan started off an article in the New York Times with these words: “Eat food. Not too much. Mostly plants.” Those same words appeared as the main theme of his book “In Defense of Food: An Eater’s Manifesto,” published a year later.

You don’t have to paint a finished picture before launching. Customers can connect the dots.

Soft launching lets you tweak and revise. You get the word out there and you gauge interest. You know what works and what doesn’t.

Plus, you get to make mistakes while you’re still in the shadows. Messing up in front of a smaller crowd means you’ll be better off when the bright lights eventually do shine upon you.

Product blog update: API developer list, iPhone app for Backpack, etc.

Basecamp
Basecamp wrote this on 2 comments

Some recent posts at the 37signals Product Blog:

Developer/API
The new 37signals API developer list
“The new 37signals API developer list is meant to be the new hub for all things 37signals API. A place where developers can discuss their experiences and challenges working with the APIs from Basecamp, Backpack, Highrise, and Campfire. We’ll try to make ourselves available as best we can to help answer questions and provide clarification on implementation”

Improving the Basecamp API
“We’ve been working behind the scenes to improve the Basecamp API. One recent change lets developers know whether the person making an API request is from a client or an internal firm.”

Highrise
The Star-Ledger: Highrise is a a new breed of CRM that emphasizes simplicity
“I particularly like the description used by 37 signals, the makers of the Highrise CRM: Highrise is a great way for business to keep track of who talked to whom, what was said and what needs to happen next. The software excels in the way it blends contact management, to-do lists and other features. You look at a contacts page in Highrise, and you have a window into your communications with that person, notes from meetings, background and any tasks related to the contact.”

Put your Highrise Dropbox address in the BCC field automatically in Mail.app
“Want to put your Highrise Dropbox address in the BCC field automatically in Mail.app? Easy Automatic Highrise Dropbox in Apple Mail offers a hack that will make it so.”

Sync your Ballpark estimates with Highrise Deals
“Ballpark, an app that lets you send estimates and invoices, now syncs with Highrise Deals.”

Backpack
TUAW: “Satchel is Backpack on the iPhone done right”
“It’s worth every penny for the true Backpack fanatic. It’s gone a long way to removing the barrier for those looking to embrace Backpack as a service, but feeling a little hamstrung by the lack of a decent mobile interface. If you love Backpack, you’ll love Satchel.”

Continued…

Rediscovering Jakob Nielsen

Ryan
Ryan wrote this on 49 comments

When I was first getting serious about web design I discovered Jakob Nielsen’s Alertbox and was totally inspired. There was something about the ascetic style, black verdana type, yellow header and scattershot of bold that just fascinated me. I pored over the site and stayed up late at night reworking projects with fresh inspiration and higher standards. I even found a company to work for that was as nerdy about this stuff as I was. And then somehow—I don’t know how—I just forgot about the guy.

Today my forgetfulness took a kick in the seat when Jason linked me to this Alertbox article. This site just doesn’t look old. It’s still fresh and clear and distinctive. And the content? Show numbers as numerals. The F-Pattern. Active versus passive voice. The first two words. It’s all rock solid. It still has that new car smell. There’s no fad in here.

Jakob Nielsen's Alertbox

Timelessness is a mark of mastery. And few things are healthier than being reminded of how your best work rests on the shoulders of people who inspired you through their example. So I’m glad I took some time today for a usability refresher from Mr. Nielsen.

People want to know how I started Teach For America straight out of college, and honestly, my greatest asset was my inexperience. It proved absolutely critical at many junctures. When I declared in my thesis that I would try to create this corps myself, my thesis adviser pronounced me “deranged.” When he looked at my budget of $2.5 million for the first year, he asked me if I knew how hard it was to raise $2,500, let alone two and a half million dollars. But aided by my inexperience, I was unfazed by these reactions. When school district officials literally laughed at the notion that the Me Generation — this was the label for my generation — would jump at the chance to teach in urban and rural communities, their concerns, too, went unheard. My very greatest asset was that I simply did not understand what was impossible.

Matt Linderman on Jun 8 2009 16 comments

A reminder of how simple business can be when you don't make it complicated

Jason Fried
Jason Fried wrote this on 68 comments

Yesterday I found a flyer on my front door.

I’ve been staring at a project in my backyard for a few weeks. Staring hasn’t gotten it done. So I figured I’d see what it would cost to have these guys do it.

I called them. 10 minutes later the guy came by. He was down the street on another job. We walked out back. I told him what I needed done. He looked around for 20 seconds and said $300. I said “deal.”

That’s it. No proposal. No “I’ll get back to you tomorrow”. No “Let me see how much the materials will cost and I’ll drop an estimate in your mailbox next week.”

Just $300. Deal. When can you start? Wednesday. How long will it take? A few hours for a few guys.

He knows his business. I know what my time is worth. End of transaction. It was so damn refreshing.

I know everything can’t be done like this, but often it seems like we’ve slid down a path of formality with so many things that really don’t need it. Extensive contracts, delays, red tape, precise cost estimates based on precise amounts of materials, “let me think about it and I’ll get back to you,” etc. Essential? Sometimes yes, but most of the time probably not.

I remember the tail end of our time as a web design company. When we started we did 20 page proposals. I remember pulling all nighters getting a proposal ready. Pages and pages of stuff. What a waste of time.

Towards the end we were doing one page proposals. It didn’t seem to matter. We were going to get the job or we weren’t. Over six years I never saw a connection between length and detail of proposal and winning a job.

Same thing with contracts. Sometime we hire an outside contractor or specialist to give us a hand on a project. Our contractor agreement used to be 8 pages long. Lawyers wrote it. Our current contractor agreement is one page long. I wrote it then showed it to our lawyers. They said it was fine. Done.

I know it seems like a stretch to compare lessons from a door flyer for a small landscaping job to 10 page legal contracts for 3 month long expensive web design projects. But maybe it isn’t.

The moment a man begins to talk about technique that’s proof that he is fresh out of ideas.


Raymond Chandler
Jason Fried on Jun 5 2009 25 comments

Forbes profile of David and 37signals

Matt Linderman
Matt Linderman wrote this on 22 comments

The Pied Piper of Pay [Forbes] is a piece that profiles David…

You can tell a lot about a culture by the sort of person it ostracizes. David Heinemeier Hansson, 29, a successful tech entrepreneur, is something of an outcast in Silicon Valley. Here are the pronouncements that have earned him his banishment: Companies should not be ashamed to charge for their products. They should expect to be able to make money off their customers. Finally, they can’t use volume to turn losses into profits…

“Startups these days are getting all the wrong lessons,” says Hansson. “[They think] that all that matters are users, that they should take on plenty of debt from venture capital investments because something magical will come along at some point and everything will be okay. But you can’t make up something in bulk that is a losing prospect to begin with. Isn’t that self-evident?”

Read the rest of the piece to see what DHH thinks of Twitter and Facebook.

(Note: There are a few inaccuracies in the piece, most notably that Ruby on Rails is a 37signals product which impacts our financial success. Not so, it is an open source framework.)

Last week's 37signals retreat in Kohler, Wisconsin

Matt Linderman
Matt Linderman wrote this on 17 comments

Last week we had a 37signals retreat in Kohler, Wisconsin (the company that makes faucets and plumbing fixtures also has a resort). We got to catch up, plan ahead, meet the newest members of the team, took the Kohler factory tour (some pretty amazing stuff happens to get those faucets, tubs, and toilets made), dined at a cabin in the woods, made lots of trips to Sheboygan to eat at the excellent restaurants of chef Stefano Viglietti, and went canoeing.

And by the way, contrary to popular belief, this is NOT how 37signals handles feature requests…

What does a Community Manager do? I see a lot of job postings and mentions of this position, but I’m not entirely sure what the role is. How does it different from customer support/service? Is it a component of that role? A dedicated role? Would love to hear from anyone who does it or who has hired for it in the past. Thanks!

Jason Fried on Jun 3 2009 28 answers