Blogging Resources: November 2008 Archives

How to write a software review

| | Comments (0) | TrackBacks (0)
As someone who works with computers and software on a daily basis, I think I'm qualified to write software reviews for products I've worked with a while.  In fact, I've done that several times.  Lately I've wanted to not just review a product, but to actually do a semi-professional job of it.  I spent tonight reading and analyzing dozens of software reviews by professional writers, from respectable sources like CNet, PC World, and the like.  I also went through a few amateur reviews in case I missed something valuable.

Software Review Structure

I used a mind mapping tool to help me organize my thoughts and observations.  In the end, I decided that my software reviews from this point on will follow the basic structure outlined below:

  • A "50-foot view" or very short overview of the review results
  • Description of the software (its purpose, functionality)
  • The installation process
  • The user interface
  • What the software is like to use
  • How it compares with other products
  • How it compares with previous versions of itself
  • What its documentation and tech support is like
  • How it's licensed and if demo/trial versions exist
  • What its technical specs are
  • What the specs are of the system you used to review the software
  • A conclusion summarizing the good and bad of the software
All of these parts aren't necessary for every software review you do.  For example, if you're looking at a program that has no competitors and you're not familiar with its earlier versions, you wouldn't bother to include a comparison to other products or to earlier versions.  Your goal will be to include as many sections as you can authoritatively speak to.

Detailed Software Review Structure

For each of the points in the basic structure, I've developed a list of questions to ask yourself (and details you may want to include) to make sure you cover that particular point thoroughly.  Again, not all of these will apply to every review you will do.  Think of them as a guideline where you can include what you think is relevant and useful given the package you're looking at, and leave out the stuff that's not applicable, useful, or worth the time to research.

Below is the "fully expanded upon" list of points in the basic review structure:

  • A "50-foot view" or very short overview of the review results
    • This should be just a very short list of bullet points, no complete sentences, and with the minimum number of words necessary to share the information.  Think of it as "If I had 15 seconds to tell someone about this software, what would I say to them?"
    • What are the product's strengths, highlights, or best features?
    • What are the product's weaknesses, problems, or frustrating details?
    • In 2-3 sentences, what would you tell someone who wants to buy this product or one like it?
    • This can include a 5-star or x-out-of-10 rating if you want it to
  • Description of the software (its purpose, functionality)
    • What does it do?
    • What features does it include?
  • The installation process
    • How long does it take to install?
    • Were there any problems installing it and getting it working?
    • Does it have any copy protection?
    • If there is copy protection, is it convenient or frustrating to work with?
    • Does it uninstall cleanly if you decide to remove it?

  • The user interface
    • Is it intuitive to use, or did you need to consult the help or manual?
    • Can keyboard shortcuts, menus, etc., be customized to suit your needs?
    • Does the interface look modern or "dated"?

  • What the software is like to use
    • How long does it take to launch the software and make it usable?
    • What file formats does it read and/or write?
    • Is there anything you found annoying about using it?
    • Is there anything you found especially fun or cool about using it?
    • Are there plug-ins, extensions, themes, or other "add-ons" you can get for it?
    • Did you find any security concerns (e.g., passwords stored in visible text form)?
    • Are there ample keyboard shortcuts?
    • Did you run into any glitches?
    • Does it integrate well with other products?
    • Is it easy to get patches/updates and install them?
    • Is any kind of automation built-in (scripts, macros, etc.)?
    • How long does it typically take you to do whatever it is the software does?
  • How it compares with other products
    • Do they have features this product doesn't?
    • Does it have features they don't?
    • Is the other product easier, harder, or about the same to use?
    • Is it more or less expensive than the other product?
    • How do the other products technical requirements (CPU, RAM, etc.) compare?
    • What's the other product's "footprint" (RAM, CPU, hard disk usage) in comparison?
    • Is it faster or slower than the competitor?
  • How it compares with previous versions of itself
    • What features have been added in this version?
    • Have any features been taken away?
    • Are any existing features harder to use now? 
    • Are any existing features easier to use now?
    • How do the technical specifications compare with the old version?
    • How does the user interface compare?
    • Is it faster or slower than previous versions?
  • What its documentation and tech support is like
    • Is the manual thorough?
    • Is the manual easy to understand?
    • Is tech support available?
    • How do you access tech support?
    • Is there an online knowledgebase on the manufacturer's web site?
    • Were tech support staff professional, courteous, and helpful?
    • How much support comes with the product, if any?
    • Does there seem to be a big user community? (Search for web forums, newsgroups, or mailing lists where people share information about the software.)
  • How it's licensed and if demo/trial versions exist
    • Is it commercial, shareware, or freeware?
    • What are the license terms?
    • Is a trial or demo version available? If so, what's missing from the trial/demo?  How long does the trial/demo last?
    • What does it cost to license?
    • Who sells licenses to the software, and who develops it?
    • Are there multiple variants (e.g., Basic, Advanced, and Pro versions)?  If so, consider a table showing which features are in which variant to help readers identify which one they need.
  • What its technical specs are
    • CPU required, recommended
    • RAM required, recommended
    • Hard disk space required, recommended
    • Peripherals required, recommended
    • Operating system(s) supported and versions supported (e.g., Windows 2000/XP/Vista, Mac OS X 10.3 through 10.4)
    • Does it need a network connection?
    • Does it need anything else not specifically listed above?
  • What the specs are of the system you used to review the software
    • CPU, RAM, hard disk, optical drive, video card, OS, etc.
    • How did the review system compare to the recommended specs
  • A conclusion summarizing the good and bad of the software
    • This should be about a paragraph or two long and summarizes the highlights of all the above points.  It should finish with a recommendation (or not) for the software relative to what you get for the money, how well it does what it's supposed to do, and so forth.
If you manage to follow this basic structure, you'll write a review that's thorough, detailed, and useful.  Your readers should find pretty much whatever they're looking for in that review.

The above structure probably would not work well for video games or hardware.  It's oriented more toward application software and utilities.  I'm planning to develop a separate structure for game reviews which I'll share at a later time.

Writing Resources for Bloggers

| | Comments (0) | TrackBacks (0)
No matter how strong our command of language might be, there are times when we're searching for the right way to say something, questioning our use of a word or phrase, or finding ourselves in need of advice.  Below are some resources I've used in the past:

Becoming an Idea Magnet
As the author puts it 'Ideas really are everywhere. The art is in training your mind to see the ideas and pull them in before your thoughts pass by them to make your mind into an idea magnet of sorts.'
Blogging Basics
This article from Technorati provides a sort of FAQ to the whole blogging concept for new and practicing bloggers alike.
EFF's Guide to Safe Blogging
This article from the Electronic Frontier Foundation provides some suggestions for keeping your blogging safe, avoiding getting fired for blogging, etc.
Finding and Writing Fresh Blog Content
This article from Performancing.com talks about how to find and write fresh content for your blog.
How to Write a Better Weblog
Writing suggestions to make for successful blogging.
Top 7 tips to write an effective business blog
This article provides the top 7 tips for writing an effective business blog from the folks at BlogWrite for CEOs.
What to write about (from Performancing.com)
This article talks about finding ideas to blog about.


Brainstorming for Bloggers - The Grid Method

| | Comments (0) | TrackBacks (0)
You probably don't write your blog just for the sake of writing. You're hoping that readers will come to your blog, read what you have to say, and appreciate it.  One way to come up with ideas to blog about is to put yourself in the reader's shoes.

Most blog posts do one of the following (if not more than one):

  • Share information about a subject
  • Share a viewpoint
  • Challenge an assumption
  • Provide entertainment
  • Empower readers to do something
  • Compare and contrast two things
  • Speculate about something that might happen
If you're looking for ideas for articles to post on your blog, the "grid method" may help you.  Start by making a grid on a piece of paper, or in a spreadsheet, or using whatever medium you're comfortable with.  Down the left side of the grid, write the individual items in the bulleted list above.  Across the top of the grid from left to right, write in the subject areas of your blog, or subject areas you might like to write about.  Let's say that on your blog, you tend to talk about your pet cat, your computer, and food:

 CatsComputersFood
Share information   
Share a viewpoint
Challenge an assumption     
Entertain     
Empower readers to do something     


To complete the exercise, you just need to fill in the blocks with something that combines a topic from your blog with one of the common post types. The result might be something like this:
  Cats Computers Food
Share information Things every new cat owner should know  How to select a good motherboard  How to make a delicious, tender pot roast 
Share a viewpoint Why cats make better pets than dogs Why I prefer AMD CPUs to Intel CPUs A review of "Good Eats" on the Food Network
Challenge an assumption Some cats actually like water and getting wet Generic memory is just as good as name-brand memory  More expensive cuts of steak aren't necessarily better
Entertain How I drive my cats nuts with a laser pointer 101 things to do with useless old floppy disks  The humiliating night I sent back my gazpacho soup because it was cold
Empower readers to do something How to teach your cat to use a toilet instead of a litter box How to choose the right components and build a powerful PC for less A step-by-step guide to making the perfect pumpkin pie

Just about that quickly, you've managed to come up with ideas for 15 blog posts.  If you cover more topics on your blog or come up with more categories for blog posts than I did, you'll have a lot more ideas on your grid.

Brainstorming for Bloggers - The Bounce Method

| | Comments (0) | TrackBacks (0)
The "Bounce Method" is a very simple trick I've used to great effect in my blogging.  After I've written a post about a particular subject, or even while I'm trying to flesh out that post in my mind, I'll bounce the idea off a friend, family member, or co-worker (maybe even several friends or co-workers).  In the course of discussing that particular topic, the other person will help me find flaws in my logic, remind me of things I missed, give me additional talking points, or (once in a great while) convince me it's not such a great idea after all.  The next time you're having trouble figuring out what to say or how to say it, talk it out with someone else.  They might give you the perspective you're looking for.

Brainstorming for Bloggers - Idea Scouting

| | Comments (0) | TrackBacks (0)
One reason I'm rarely at a loss for something to blog about is that I'm always scouting for ideas.  Sometimes I'll be asked a question that I've answered for someone else in the past, like "What do you think about X?"  When I get home that night, it might just inspire me to write down everything I know about that subject in a blog post.  Not only does this give me some interesting (hopefully) material, it can also help me to flesh out my thoughts on a particular subject and respond even more authoritatively the next time someone asks (or I can just refer them to the blog and be done with it).

Brainstorming for Bloggers - The List Method

| | Comments (0) | TrackBacks (0)
If you typically blog about a particular subject, regardless of what it is, this method may help you to come up with articles to help show readers your command of that subject, establishing yourself as an authority.

Begin with the main topic of your blog.  For example, let's say your blog is about cats.  You start by writing down the word "cats" on a sheet of paper.  Below that, create a list of things you know about cats: what they like to eat, how they keep clean, how they like to be petted, where they like to sleep, what scares them, what arouses their curiosity, how to deal with shedding, etc.

For each of the listed topics, list what you'd like your readers to know about that particular thing.  For instance, building on our example, under "what they like to eat" you might list things like tuna, canned cat food, dry cat food, whipped cream, melons, or whatever your cat happens to enjoy eating. 

You can use this method to drill down as deeply into your subject matter as you like.  Once you have what feels like a pretty solid list, go back over your existing blog posts and see what areas you've already covered, and what you haven't.  You might find, after checking, that you never actually talked about the time your cat jumped up on the kitchen counter and ran off with a piece of fresh melon.  That might make for an interesting or humorous post.

The "list of lists" may jog your memory for things you've always wanted to write about but have never gotten around to.

Brainstorming for Bloggers - The Extension Method

| | Comments (0) | TrackBacks (0)
Here's a simple brainstorming tip that can help you to have a more authoritative and complete blog...

Bring up a web browser and point it to your blog.  Make a list of your last 5-10 entries, either the titles or the "gist" of the entry.  For each entry in your list, ask yourself how you could expand on that point?  Is there something you brushed on in the post that isn't explained as well as you would have liked?  Does it make you think of some other topic area you haven't covered on your blog?  Have commenters to the article asked intriguing questions you should answer with a follow-up post?

This "extension" method of brainstorming can help you recognize content areas that might be lacking from your blog, and opportunities to cover earlier points in greater detail.

Analyzing Your Blog's Traffic

| | Comments (0) | TrackBacks (0)
Conversion Rate Experts, an organization devoted to helping businesses turn web visitors into customers, published an interesting guide to free tools that can help you analyze the traffic to your blog or web site.  The list of tools includes Google Analytics, Crazy Egg, ClickTale, Google Talk Chatback, SurveyMonkey, 4Q, and others. 

Based on my past experience, I would encourage you not to use all those tools at once.  For a while, I ran a web-based cartoon site.  To analyze my traffic, I used a handful of tools like the ones listed on the linked article.  When I went to promote my cartoons on various web forums, my announcements were often followed by (inaccurate) remarks by other forum visitors who had gone there and had gotten browser security warnings about various JavaScripts being in use there.  They (incorrectly) assumed that these warnings implied that my site was infected by some sort of virus or malware, and warned others not to visit it... even though there were no viruses or malware on my site.  So my advice would be if you choose to use some of the listed tools, use them sparingly for a short time to analyze your traffic, and don't use more than 1-2 at a time.  Otherwise you run the risk of misinformed or novice users thinking there is something "weird" happening with your site.

December 2008: Monthly Archives