Tag Info

With a video, written manual, or wiki, you should think about the likelihood that a user will actually use that material. For instance, I've seen products that have had an introductory video that only 15-20% of users watched. This means that 80% of users were skipping over the video. I'd suggest trying to make the product as intuitive as possible. Much ...

I'm not sure what level of technical sophistication you were expecting, but guiders.js is a great open-source package that makes it easy to build step-by-step walk-throughs and tutorials into any web application. http://blog.optimizely.com/introducing-guidersjs-an-open-source-guider-e It is fairly easy to setup -- but the main benefit is that it allows ...

If I understand correctly, you want to outsource writing a functional spec that copies a competitors website? Really this just sounds bad all round. It is bad etiquette and probably illegal to copy your competitors work like this. It is also very poor to not even write the specification for your business yourself, outsourcing this is like saying "I have a ...

In addition to the great comments above I would like to add a strategy that we have recently found extraordinarily helpful: Integrating Live Customer Support When an existing customer is having a problem nothing is more infuriated then getting lost in pages of wikis, get pushed off onto a ticket system, or routed through complex automated voice mail ...

How are you identifying the content to put on the FAQ/Wiki? You should begin by taking the top items that you are currently handling with people which could be easily handled by users reading/viewing. Make the users go through the self-help portal to get to a real support person. Don't make it difficult, just show them related issues or other near search ...

I've found creating PowerPoints with screenshots and then doing an optional voice-over on top of them to be much quicker to do than creating a video. You can host using slidshare but in place on your site. Top tip is to keep it brief (something that is really hard to do). 30 seconds is perfect for a quick intro, 2 minutes is fine, 5 minutes is pushing it ...

A pro-forma invoice, which looks exactly like a real invoice, but it states what will be provided upon payment. You can then follow up with a bona-fide invoice after delivery which states Pail-in-full on it, assuming of course the bill is paid. See wikipedia's entry on this.

Please do not look for a third person to read your mind and come up with a fancy document. What you know about your strength and capabilities, that third person will never be able to articulate. What you can do is, hire a visually creative person one time and ask him to come with some professional looking templates for document and powerpoint. You can then ...

Please be carefully when you use such services. For example Google Drive has some things in their terms which might sound as Google would own the files (please see yourself, i just heard that). What I recently discovered and what looks pretty good is Spideroak: https://spideroak.com/ SpiderOak is a zero-knowledge encrypted data backup, share, sync, access ...

Don't? Wikis are great if you're geeky and smart and willing to spend the time digging through them. However, most people aren't. They've been burned too many times, so they don't even care if your wiki is great. Instead, bring your FAQ/documentation to them. Show it on the actual page where they're typing you a message. Or better yet, pull up matching ...

I think only you can really make the call if it is a good idea. If you are that confident that the other site you've found is the basis that you are looking for (before your changes) then maybe it doesn't matter too much. However, if you do this, who is going to be the person in your start-up who knows the product/service functionality back to back? If it ...

If your application is intuitive, it should be no more than $25 / hourly, usually less. This is how I based that: Typically, documentation is done by testers, people who use each daily build and become almost as familiar with the application as the developers themselves. The average salary for them starts at about $41,600.00 / yearly, or approximately $20 / ...