An unexamined blog life may or may not be worth living, but I think that it is easier in the long run to think things through, and talk about what’s causing the pain.
There has been a bit of angst about lately amongst those I read and love - people are looking at their own situations (and those of others) and asking questions. This includes:
- DoshDosh re-visiting the NY Times “does their money make them happy” and coming to the conclusion that life is about being happy rather than rich,
- Anne Zelenka looking at the same article from a different perspective and deciding that experiences are ultimately more valuable than possessions,
- Jeri Merrell looking at her work/blog/life mix and deciding that there was only so much energy to give,
- Darren Rowse discussing the pain he went through early in his professional blogging career until he learnt to schedule posts, and
- my fine self on blogging being something done for people (not to them).
What’s it all about then?
So what is the upshot of public angstiness? Does it have a purpose beyond establishing the writer’s humanity and allowing readers in similar situations to empathise? This is a fine aim in and of itself - being able to discuss a difficult situation is a very good thing.
For extra points: it’s a bonus when a viable solution is presented to the problem - it can make all the difference in the world to read about someone who is feeling (or has felt) the same pain that you are in now, and who has something to suggest that might help.
The problem/solution pair
In the information support business, this is sometimes referred to as a problem/solution pair. This information format works well because of one simple concept: it is easier to present a solution when the problem is front-of-mind. You never need a shoelace so much as when the old one breaks.
How do you present a problem/solution pair? I think that the easiest way for both you and your readers is to tell a story. You’ll be able to speak from the heart without worrying about being clever, and they’ll find the information easier to follow (and thence gain value from it).
You can go one better and follow the old consulting report four-step:
- Summary: summarise the problem and solution in a paragraph or two
- Background: give the readers the start of the story - some context that establishes the situation in their mind
- Issue: the problem, in context of the background
- Solution: the solution itself - how your advice has helped (in this instance, it would probably be how you discovered the solution and how the reader can come to a similar conclusion).
If you were following a classic essay style then you might be tempted to add a separate conclusion sentence/paragraph, but in this case the solution is the conclusion and is probably unnecessary.
So what do you think? Is it a good idea to share the pain as a blogger?
Note: I’ve entered this post in Darren Rowse’s 31 Days group writing project.
Blogging about problems is probably the best way to vent without annoying those you love too much. If you’ve just bought a house, you may complain about home building problems or may have just discovered the mold problems in your basement. But your complaints may pay off - one of your blogging buddies just may have the perfect remedy to remove mold!
As always, many thanks for the link!
I agree with you, problem/solution is a great formula for providing value to your readers and building fresh content.
I’m not entirely sure I provided a solution in my post - although I did definitely do some creative writing exploring the problem.
I don’t yet have a solution so I’m limping along in the status quo, respecting my limitatations (like not trying to blog on a travel work day) until one avenue seems truly right.
Hi Jeri,
many thanks for the comment
I think that you are doing yourself a disservice - you did provide a solution in your post: you suggested to your readers that you couldn’t do everything and reminded them that they can’t do everything either (in a way that was personal not “preachy”). I think that each of us has to find our own solution from that point onwards.
I’m still working out my own solution - the active domaining concept holds that a domain with a working if neglected blog on it is probably worth more in the long run than one sitting on a parking (ad)server - we’ll see if this is correct or not as time goes by.
Best regards, Andrew
I think blogging sitn about the money, rather its about the fun
Hi Nick,
thank you for your comment.
I agree - it should be fun, but it can also be a way of making a living.
Cheers, Andrew
I like your style of showing a solution. It’s something I’ve tried to do on my own blog, but find that sometimes it can add a little too much writing to the post.
Going straight to the solution, with only a brief description of the problem is sometimes a necessity I find.
Hi Michael,
thank you for your comment.
Thinking about using only a brief description - all that is really necessary is the setting of context, and if a couple of words serve to set up the solution, then that is all that is really necessary. As long as it fits the story.
At work I’ve found that spending five minutes setting the context at a design session can make all the difference - and if five minutes will serve as well as thirty, then five is best of all.
Best regards, Andrew