So much this.
A few bits I've noticed over 25+ years in the industry:
- Tell me what your product is. What it does, where it works, how it does it, what it requires. Is it a physical product (or is it shipped in one), an interactive application, a Web service, a programming language / tool?
- Tell me what the fuck it is EVERY GODDAMNED TIME YOU COMMUNICATE ABOUT THE PRODUCT. It doesn't have to be long or detailed, you can link to your detailed description in the communication. But your press releases, emails, Tweets, blog posts, marketing collateral, etc., are going to get passed around, word-of-mouthed, and/or pulled out of drawers (or browser history / searches) for weeks, months, and years to come. Make them work for you.
- The Economist's practice of briefly introducing any individual, no matter how famous or obscure, is a wonderful practice of microcontent contextualization. "Using the Economist house style offers an elegant alternative, wherein virtually all people and organizations are identified explicitly, no matter how prominent. For example, you might see 'Google, a search giant', 'GE, an American conglomerate', or 'Tim Cook, boss of Apple'." http://redd.it/1x8yky
- Tell me how to try it out. Preferably for 60-90 days (a 30 day cycle can go far too fast. I've been very, very impressed with New Relic's "use it for free, convert upmarket for additional features" model, and it's apparently worked well for them. For small accounts, their cost of sales is effectively nil (and for large accounts, COS is always a PITA). But for those large accounts, you've got a proven track record with the prospect, and they really know what they're getting.
- Put your tech docs front and center. As a technical lead / director, my questions are "how the fuck do I make this thing work", and if you can't tell me
- It's been observed many times that those who have the best appreciation for how a product works are those who use it directly, and secondly, those who either service it or support those using it. John Sealy Brown's The Social Life of Information addresses this with both Xerox copier repairmen and support staff. Use this to your advantage two ways: let these people share and collaborate, even if informally For the repairmen, this was a morning coffee break turned out to be a hugely valuable cross-training and troubleshooting feature. For phone support, after an "expert system" and changes in technology separating phone reps from technicians, researchers noted two reps who consistently provided good advice: one was a veteran from the earlier stage, the other a recent hire who sat across from the other and learned from her. Similarly, user support groups (mailing lists, Web forums, Usenet groups), in which users interact and share knowledge with one another directly (Hacker News would be an instance) are often (though not always) far more useful than direct tech support.
- Provide clear pricing information. This has been noted from Jacob Nielsen on forward as the information people are most interested in.
- Make damned sure that whatever process or workflow you've created online works, and for as many possible end-user environments as possible. Keeping interfaces as simple and legible as possible is a huge bonus.
- Remove distractions from your transactional webpages. Once someone's homed in on a product, focus on that, though you may mention alternatives or (truly useful) related products. Every additional piece of information on the screen is an opportunity to confuse and lose the sale. I've been restyling many websites simply for my own use (1000+), and simply removing distracting elements produces a far more productive environment.
- Ensure your pages are legible. Backgrounds should be light, foregrounds light (and where, with extreme reluctance, you invert these, separation should be clear). DO NOT SCALE FONTS IN PX. On far, far too many devices this renders as unreadable, particularly from older (e.g., more senior w/in the organization) readers. Grey-on-grey is just cause to fire whomever suggested or required it. See ContrastRebellion: http://www.contrastrebellion.com/
- Don't organize your website according to internal corporate structures. Your website is an outward facing tool, and should address the needs of users, not of internal departments. Lenovo's laptop site organization would be highly typical of this: I want a Linux-capable, large-display, full-keyboard, trackpoint device. The rest I generally don't give a shit about, and its product line confuses me every fucking goddamned time I try to buy something there (usually every 2-3 years). I'm not a sufficiently frequent customer that I keep up with every last change, but I've spent thousands of dollars on IBM/Lenovo products, as an individual (hundreds of thousands to millions as an enterprise customer).
And of course: test all of this, don't simply take my word for it. But yes, I've walked from far, far, far too many product pages, from free software projects to Fortune 10 companies to edgy app devs.
Life's too fucking short for that shit.