Archive for the ‘Uncategorized’ Category

How I use Twitter for Work

Monday, February 15th, 2010



Publishing Decision Tree V2

Originally uploaded by sggottlieb

I just read Philippe Parker’s thoughtful response to Janus Boye’s provocative post “How I use Twitter for Work”. Both these articles, plus my recent experience at PodCamp Western Mass, made me a little more conscious of my strategy and techniques for social media. As you can see from this geeky flow chart, I have put some thought into what I publish where. But I had thought less about who to follow.

My official Twitter policy was to only follow people that “inform and/or entertain me.” Because I use Twitter mainly for work, my bias certainly leans toward the “inform” side. Although, I do appreciate a good snark once in while, I have un-followed people who fill the timeline with mostly personal stuff. If I found myself automatically skipping over someone’s tweets because I was expecting something mundane, I un-followed him/her. If a Facebook friend re-published their Twitter stream into Facebook, I un-followed him/her on Twitter. These tactics kept my following count to a manageable number of 150. When I say manageable, I mean I am not overwhelmed by the volume of updates but I don’t go back and read every tweet when I am away from Twitter for an extended period of time.

At PodCamp, I finally learned the value of lists. By using private lists for work, friends, fun, and news, I can follow more people but handle the traffic differently. When I am really busy, I just track my work list and my @replies. I glance at my friends and fun lists when I have more time but I never go back more than a few hours in the timeline. My news list takes the place of personal portals for the day’s highlights. Since sorting this stuff out, my following count has grown to 164 with no real impact on time consumption.

The biggest change is in how I use RSS. With my new Twitter strategy, I check my reader less frequently and am able to skip over posts that I already found on Twitter. At this point, Twitter brings me timely (either because it is news or because everyone is talking about it) posts quicker. The un-tweeted RSS entries are still important to me for general learning and background knowledge. I expect that, over time, people will promote everything they write on Twitter. This has already happened with sites like CMSWire. Now FeedBurner gives you the option to automatically tweet every entry in your RSS feed. When a Twitter feed becomes identical to the RSS feed, I tend to un-follow/unsubscribe to one depending on how timely the information tends to be.

This system is working well for me now but I am sure that it will continue to change as the medium evolves. I am interested in learning other people’s techniques. The tag #howiusetwitter seems appropriate and free.


Writing Titles for SEO

Monday, January 11th, 2010



SEO Unfriendly Pithy Titles

Originally uploaded by sggottlieb

Normally I don’t worry too much about search engine optimization when I write blog posts. My writing is as much for organizing my own thoughts as it is to drive site traffic. My philosophy on search engine optimization is to produce good content and avoid hindering search engines indexing my site. Good content is clear, well organized, and useful. Not hindering search indexes means being text-rich, minimizing broken links, returning the appropriate status codes, and keeping HTML simple. I am not going to trick anyone to come to www.contenthere.net but if I have something that would useful to someone, I want it to be found.

After reading the title of a recent blog post (“The biggest thing since wood pulp”), I realized that I was breaking my own very lax rules. My attempt at a pithy title was effectively hiding what the article was about: a possible consequence of the Internet’s disruption of the newspaper business. I looked at my recent posts (see screenshot) and realized that I do this quite a lot. One of my worst offenses is “Doubt,” which offers an alternative to to matrix-based decision-making. Most people probably assume that I am talking about the movie of the same title. Another example is “Another Flower War”, which is about a dispute between Magnolia the CMS and Magnolia the social bookmarking site. I know this title was misleading because I was getting comment spam for garden supply retailers.

Pithy titles may be effective in print media when the reader has already made the investment to browse through the publication and is looking for things that spark his interest. They may be marginally effective by causing a curious RSS subscriber to click through. But they are totally counter productive in a search result. Even if the search engine thinks that your article might be relevant to the query, the searcher is likely to assume that your article was listed in error as he scans the results. You have just done the searcher a disservice because you have hidden the answer to his problem.

To some extent, some open source projects share in this problem. Sometimes open source project names are taken from an obscure (nerdy) cultural reference or something to do with the history of the project. Sometimes project names are just intended to be fun. I remember an Optaros colleague telling me how silly he felt when he was talking to a CIO and suggested that they use Wackamole for network monitoring. A lot of insiders have to try and recommend a project with a silly name for it to get credibility in the mainstream.

Overly clever titles are an inside joke that excludes potential new readers. It’s a little like giving a tourist directions that reference where a Dunkin’ Donuts shop used to be. These names are useful in getting the attention from the old guard but they exclude the newbies. This may be an intentional community dynamic where new members need to demonstrate their commitment in order to get accepted and longstanding members feel bonded by their shared knowledge. But, if the goal is to bring outsiders in, the name of the project or an article should be clear and not overly silly and obscure.


Shortened URLs and spam filters

Thursday, October 15th, 2009

One of the more frustrating things about email these days is spam filtering. It stinks to miss important messages that your spam filter thought you shouldn’t see. It is even worse when your message gets caught by someone else’s spam filter. The latter case makes you paranoid whenever someone doesn’t get back to you. You start thinking “did he get my message? Should I send it again?”

Just this morning, a spam filter rejected and sent back one of my emails with the following text:

Heuristic analysis has classified your e-Mail as spam and delivery has been refused. We apologize if your message was misinterpreted. Please check your entire message for any restricted content and then attempt a resend. You may also request addition to our list of pre-approved senders.

“Heuristic analysis” was probably an overstatement. It was probably just looking for keywords. But what could I have written in my email about scheduling a business meeting that would have triggered the rejection? Well, I am relatively certain that the issue is this…. In my email signature (and, in this case, the body too) I have a shortened link (is.gd) to my Google calendar so that the recipient can see when I am free. Personally, I thought this was a great idea because I work with clients who use Exchange or other groupware to schedule meetings when everyone is free. This technique allows the meeting organizer visibility into my calendar without my needing to join their calendaring system. I used a shortener because the link is really long. I use plain text emails so the length of the URL matters to me.

I still think exposing my calendar is a good idea so I figured out a work around. Google allows you to embed a calendar in another page so I just embedded it in page on http://www.contenthere.net that can easily be linked in an email. I am hoping this will lead to a drastic reduction in spam accusations.

What your intranet needs is a publisher!

Monday, June 1st, 2009


J. Jonah Jameson

Originally uploaded by OntologicalDoubt

While I work with companies from many different industries, most of my clients media and publishing companies. I like working with publishers for many reasons — not the least of which is the fact that this is an industry in transition and it is exciting to see my clients innovating and re-inventing themselves. But the main reason publishers are so interesting to work with is that they, more than any other industry, understand the value of content. It is their business. While you could make the argument that a publisher’s key asset is its audience (not the content), it is the content that attracts the audience. Publishers push their organizations to produce content that an audience wants to read and then look for ways to monetize that audience.

Compare that with other types of companies. How many marketing organizations think of their website copy as only a modest improvement over the Latin text that the web designer left behind? Internal content is worse. Updating the intranet is the last priority for the average knowledge worker. People have more gratifying responsibilities than contributing to a web site that nobody wants to read. In most companies, employees are not recognized for their intranet contributions. Take, for example, a knowledge base. If you have a brilliant piece of information, depending on where you work, it may be better to share it with individuals you know and have them “owe you” than to leave it to rot a in a place where nobody will benefit from it.

Companies fool themselves when they think that if the tool makes contributing easy, staff will all of the sudden think contributing content is their number one priority. You might get a slight uptick of activity when you deploy a new publishing system, but after the novelty wears off, people will go back to their old habits. Writing content is hard work no matter how “fun” the tool is to use. Employees will gravitate to work that is either easier to do or more rewarding (that is, things that are measured by their bosses).

Assuming that enterprise content has value and is worth managing, there needs to be someone in the organization responsible for maintaining that value. Enterprise content needs someone to represent the audience and ensure that they are being served. Enterprise content needs a publisher. Pardon the geeky comic book reference but think of Peter Parker’s (aka Spiderman) obnoxious boss J. Jonah Jameson (pictured above). He relentlessly pushes his staff to create content that he knows his readers want to read. Granted, nobody wants to work for a jerk like that. But is it any better to work for someone who doesn’t care about what you produce?

In the media and publishing world, Clay Shirky theorizes that the role of the publisher is becoming unnecessary. The Internet has solved the journalist’s problem of reaching an audience. But that assumes that the journalist wants to become his own publisher. The blogging phenomenon has seen just that. Bloggers (citizen journalists) put up their own websites and invest large amounts of time building and cultivating their audiences. They look at traffic stats; they think about wording for SEO and click through; they tag; they obsess over establishing their personal brand. They didn’t do this just because the blogging tools were easy to use. The first generation of blogging tools stunk. But the first generation of bloggers really wanted to publish and they were just happy for the opportunity. Inconveniences and poor usability were not going to hold them back from having their voices on the Web.

Many Enterprise 2.0 advocates predicted the same thing would happen inside the firewall; that employees would self publish with the same zeal on the Intranet as they did on their personal blogs if they had similar tools available to them. It didn’t happen — not because they couldn’t figure out the tools but because they were too smart about managing their time. They knew that they would gain more during their 9-5 work day from doing other things. They satisfied their inner publisher during nights and weekends at home where they could reach a much larger audience and own their content. If they could get away with it, they would sneak in a post to their personal blog from their cube.

There is only so much you can do to motivate your employees to “want” to publish on your Intranet. You can make it part of their job description; you can recognize their efforts. But you will probably not be able to create the hunger for attention within your firewall that will unleash that entrepreneurial publisher spirit. If they have that spirit within them, it will be expressed on their personal blogs. To get your employees to act like journalists, you need a J. Jonah Jameson type. Maybe not as abrasive, but just as passionate. Have your internal publisher imagine that he is in a circulation war with a competing intranet and that he should do whatever it takes to capture and enthrall subscribers. Just tell him to 86 the cigar; he will never get that approved by HR.

CMS Gallery on del.icio.us

Monday, September 10th, 2007

I subscribe to a bunch of open source WCM mailing lists. Occasionally, someone announces a new site that he/she built on top of the platform. When I read this, I usually tag the site on del.icio.us with a tag like <cmsname>gallery. For example: “bricolagegallery”. Many open source WCM project sites already have nice reference site galleries with descriptions about the technology used. I find del.icio.us tagging useful for sites that are not on the public galleries. Here are some tags that you might find useful:

If you have a reference site that you would like to put up on a CMs project gallery, you should send an email to their mailing list. If there is no gallery or you just want to put something up right away, tag it in del.icio.us.

SDL International to Acquire Tridion

Tuesday, April 24th, 2007

SDL International just announced that they will acquire Tridion. This is very interesting news because The Netherlands based Tridion seems poised to make quite an impact on the North American mid level WCM market. They have just started to aggressively market in the States and the product is already popping up on selection short lists that typically include Ektron and SiteCore. SDL is a combination software/services company focused on global information management. Not long ago, they acquired Trados.

Boston Alfresco Meetup – March 12th

Thursday, March 1st, 2007

Russ Danner, from the Christian Science Monitor, is hosting a Boston Alfresco User Group meeting at the Monitors offices in the heart of Boston’s back bay. This originally modest idea has grown into quite a big event with presentations from Rivet Logic, Optaros, and Alfresco (maybe). I posted the details of the event on Upcoming.org but here are the highlights to save you a click:

When
Monday, March 12, 2007
11:00 AM – 3:00 PM

Where
Christian Science Monitor
200 Massachusetts Ave
Boston, Massachusetts 02115

Parking
$5

Lunch
Free if you RSVP to dannerr [at] csps.com

Swift

Wednesday, February 7th, 2007

swift, originally uploaded by sggottlieb.

If you run Windows, it is easy to overlook the Safari web browser when testing a web application. Ideally, you can use this limitation as an excuse to buy a Mac. However, if your employer doesn’t buy it, consider the Swift Browser. It uses the same rendering engine used in Safari but runs on Windows. I installed it and, although it is very poor functionality-wise, it worked. Hint: to get the address bar, you may need to click the tiny triangle in the upper right side of the page (see screenshot).

How to Post on an Open Source Mailing List

Sunday, February 4th, 2007

I was going through some slide presentations on my computer and I stumbled upon a deck that my friend Renaud Richardet presented on my panel at the 2006 Boston Gilbane Conference. Renaud talked about how to join a community and gave some tips on getting help from a mailing list. Looking at some lists that I subscribe to, it looks like this advice needs to get out more. If you find no one is answering your questions, it might not be the community. It might be you. Sometimes someone will (perhaps brusquely) rebuke you for poor forum manners. Other times you might be ignored or (worse) silently blacklisted. To prevent this from happening, I suggest you practice the following habits:

  • Lots of projects have guidelines for using the mailing list. Read them and follow them. They often include some good advice like you see here.
  • Do your homework before posting on the list. Search the archives. Read the documentation. Only ask after you have tapped existing resources and came up blank – not because you are too busy to try. Everyone else is busy too.
  • Indicate the work that you have done in your post by saying things like “I followed these instructions (with link) and this is what I am seeing” and “I tried the following approaches.”
  • Give as much background information as possible including what you are trying to do, the version of the components you are working with, your platform, code snippets, and excerpts from your log files (BTW, be sure to edit down your log files to remove confidential information such as passwords etc.).
  • Even if your problem is urgent, don’t treat the community like they are your paid help. Avoid demanding language in ALL CAPS, etc. No tantrums allowed.
  • If you are really stuck, many projects have IRC channels that may give you more a immediate response. It is a good idea to hang out in these channels to get to know the community and learn. Sometimes the conversation may lean toward the social/fun side. Feel free to participate.
  • If your request does not get a response, reply to your message with more information that shows you are still working on the problem and are trying different things. This will also bubble your message to the top so that more people can see it.
  • Remember to thank anyone who responds – even if they have the wrong answer.
  • Frequently there are independent consultants participate in the lists. Consider hiring one if you are really stuck. Think of it as spending a fraction of the money you are saving by not buying an annual support subscription. If you find yourself frequently needing hands-on help, consider building a formal relationship with a support provider.
  • If you figure out the problem on your own, reply to your message with the answer.
  • If you see people with similar problems, engage them to work together to figure them out.
  • Consider publishing the information that you could have used in the documentation wiki of the project.

If you follow these guidelines, you do more than just help yourself. Well worded questions and good follow up make the mailing list archive a richer resource for others to search. If you are already an expert in the community, try to be as patient with the n00bs as possible and gently coach them on list etiquette. Community karma swings both ways.

DAM Lifesavers?

Friday, February 2nd, 2007

This AP Story talks about an initiative to expand the 911 emergency program to accept videos and images. It sounds like a great idea to put the ubiquity of cell phone cameras and mini video cameras to use. Not only would the thousands of words expressed by a picture be effective in explaining the facts to the 911 operator, these images could be valuable evidence in legal trials that might arise from the emergency. However, there is concern about the ability of the already extended 911 system to handle all the images and videos that might be reported. In addition to uncertainty about adequate network bandwidth, 911 operators need the tools and processes to evaluate and catalog all the visual content that they receive – a perfect application for a Digital Asset Management solution.

The article does not name vendors that they are talking to but this would be a very cool case study. The solution would have to be optimized for rapid-response usability and also records retention. This kind of Digital Asset Management implementation might also push the state of the art in automated image interpretation (is this a fire or a hit and run? is the person in the picture a convicted felon?).