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.

What I’ve noticed strange in Haystack:

—Why do you have a footer yet you’re never able to get to it since you constantly make the page longer

— There are so many listings that after I page down about once or twice, I simply just give up and leave the site. Visually, my eyes just begin to glaze over all the content. This will be difficult to solve though.

—There is a lot of visual noise on the site. You should have gone with one of the earlier mockups like: http://s3.amazonaws.com/37assets/svn/331-haystack-home-v02-small.png

Even if you don’t have 20, 30, 50 people giving the speech to someone not in your industy/field/specialty is a great way to get feedback.

I recently gave a speech on IT in the corporate world to a bunch of CS students, who may or may not have been aware of some of the tools used to manage and/or backup a corporate network. I gave that speech to my girlfriend who has very little understanding of how computers, networks, ad such works. Her non-specialized feedback made it so I wasn’t making assumptions about my audience.

While I agree with this statement in general, it is important to be careful that you don’t start to go overboard and start making changes to the product just so it will demo better…especially if those changes only add demo value and no real value to the end users. I’ve seen this happen more than I’d like to admit and we’ve even come up with a name for it: “Demo-driven development”. Not good.

I can see your point, I almost mentioned something about it actually.

There were some things that as a non-technical person she didn’t understand that I didn’t put in there because the assumption that they did have some technical background was true.

So true. Similar to showing someone some code you’ve been working on and having them point out all the comments that don’t make sense anymore because your eyes move right past them. The only way to see something with fresh eyes is with fresh eyes.

This reminds me of a certain product demo of Windows 98, where Bill Gates plugs a USB scanner into a computer, and gets a blue screen.

http://www.youtube.com/watch?v=UjZQGRATlwA

One thing I’ve noticed is that if I’ve left “placeholder” content in, and then I find myself having a hard time explaining it, then either somethings too complicated, or the placeholder is unnecessary.

@Bran… Where is this excess of visual noise on Haystack? I can’t see any. It just looks simple and elegant to me?

Sorry, I meant @Br y an.

Is your last name Krug?... just wondering?

@@Stephen… No.

Re Demo-driven development: if you guys believe that the prime directive is selling, selling, selling, then I don’t see what could possibly be wrong with the demo-driven development? It is a well known fact in the world of software purchasing that people who are making the purchasing decisions only care about the demos, as they will never be expected to use the products they’ve purchased. Ergo, the most important thing is to hone in on creating the most polished demo, after which you can ship any old clunker.

I agree with Bard. Demos are necessary

Web Designers are getting great leads with Haystack

I’ve gotten 6 email leads in a week. Not bad at all! thanks to Haystack

http://www.youtube.com/watch?v=UjZQGRATlwA

nice video

This goes right along with your read your copy outloud post. The more hands you get on a project or eyes you get on the demo the easier it is to diagnose any weaknesses you have.

It’s important to distinguish the difference between weaknesses and opinions thought. Sometimes giving peopel the option to give their opinion is counter productive. You will know when there is a weakness in a presentation thought.

Great Post!

Great advice!

Doing this does 2 things I think:

1—helps you to see your work as if you are one of the others (fresh eyes)

2—helps point out details to those watching the demo, allowing them to focus on each little thing and then ask questions or make comments when they don’t understand something about your work