This is Signal vs. Noise, a weblog by 37signals about design, business, experience, simplicity, the web, culture, and more. Established 1999 in Chicago. Follow us on Twitter for more information on our products.

Good one. This helps dispel the difference between what “seems” important and the reality of the situation.

I can think of quite a few times I argued against a feature that was “important” because, though maybe it would be important to some people, none of these hypothetical people were our customers.

It’s definitely a loaded word. And always subjective.

If something is claimed as important it drags other’s attention. It better be important otherwise you lose your most important thing. Credibility !

Yes, definitely a good idea. And we don’t want to overuse it!

This advice is important.

Do not say and do what is not important. Use frequently.

This reminds me of a thought I had about django the other day. It has warnings for running commands on the database that delete tables (reset) and delete data from tables (purge), but no warning for a command that creates tables (syncdb). If syncdb had a warning, it might be easier to not pay enough attention to the warnings about actually deleting data.

Why?? And to whom??

wow how are you

Problem: the problem with problem is it is overused, so much so that it is becoming a problem word.