Posts Tagged ‘strategy’

Content Is King – Picking the Right CMS: Part III, Commercial Open Source CMS

Tuesday, January 26th, 2010

In the last post I wrote a bit about commercial proprietary CMS.  These are “pay to play” CMS which come with licensing fees meant to compensate the company for their intellectual property.

Somewhere between commercial proprietary (100% paid) and true open source (100% free) lives commercial open source.  It should be noted there is a fine line between commercial open source and commercially backed open source.

open sources 2point0 by josh bancroft via flickr

Let me give an example:  SugarCRM is a popular CRM which has an open source version that can be installed, maintained and extended by your team and you’ll never pay Sugar a dime.  That said, there are features of Sugar which are not available in the open source version and a paid version is pushed hard by the company.  In commercially backed open source, by contrast, everything is 100% free, but the project itself has a corporate sponsor who is usually interested in offering professional services or being a certified hosting partner.  DjangoCMS is an example of this.

Concrete5 is a popular CMS that offers paid extensions to their system, and I have seen this with other CMS as well.  This is a trend I hope continues.   As with any software I use for my company, I want SOMEONE to be making money so they stay motivated and can keep the lights on.  Concrete5 is an example of a company inventing a new kind of commercial open source, fully featured open source versions with paid extensions, cool.

The advantages to commercial open source CMS are similar to those of true open source, with a few additions.  The code can be manipulated and extended by internal resources, and cost avoidance can be achieved by hosting the solution yourself.  The supporting community of developers means faster evolution of the product, and people’s monetary incentive keeps them motivated to put out quality product as well as gives them resources for things like outside security audits.

The disadvantages are fairly obvious.  Of course, the solution is not entirely free, so costs will still be incurred.  Also, you need to be careful to make sure the open source version of the solution actually has the basic features required to be useful.  Even though there is no direct cost to installing the software, it will suck to find out after spending hours on the installation that the open source copy doesn’t contain versioning.   Lowered morale, and lost confidence does have a cost, especially in IT.   Also, the usual open source suspects such as security vulnerabilities rear their head.

money grab by steve wampler via flickr

Still, I still like this model the best.  I want people to be incentivized monetarily to produce a great product, and I will always be more comfortable with organizations that have incoming revenue to offset costs and solve problems.  (Note: I don’t think incoming revenue and incoming donations are the same thing.)  The open source version gives us a chance to test drive the product and tells me something positive about the developer’s confidence in their product.

Content Is King – Picking the Right CMS: Part II, Commercial Proprietary CMS

Tuesday, November 24th, 2009

How does a business choose the right CMS on which to build their site? This blog post is part II in a series designed to outline the different tiers of content management systems available and their pros and cons.

In my last post, I defined some terms, so make sure you check out that post if, as you’re reading, you start thinking, “Wait a second, what about…”

So today, we’re going to review what is a commercial proprietary CMS.

Commercial proprietary CMS means there is a licensing fee for initial use of the CMS, as well as (typically) annual maintenance fees. It also means the code is not open to the public, and if there is the ability for third parties to make code contributions, it’s not open to just anyone.

Commercial Proprietary CMS are the oldest and typically most mature tier of content management system. Oddly enough, it’s the group I’ve had the least contact with. It’s most common to see programming languages like .Net and Java in this space, although PHP has produced a fair number of CMS in this tier.

Le kiosque de Sitecore by Frederic Harper via flickr

Le kiosque de Sitecore by Frederic Harper via flickr

Names like SiteCore and Immediacy are popular names in space (both .Net).

The advantages of this tier are fairly obvious. As mentioned earlier, these platforms are highly stable, mature, and have a great deal of experience “built in.”

What I mean is that SiteCore and Immediacy have been used on a lot of BIG websites, and presumably what they learned from those experiences are built into current releases (both are on version 6). They also come with strong corporate support, which is important to companies whose website is actually getting traffic (this eliminates most organizations) and needs to be kept online at all times. It’s always a plus to be able to call someone when something breaks. It’s also unlikely that these platforms will disappear tomorrow. This is a significant risk with open source as hundreds of communities are born and die every year.

Another significant advantage to these platforms is they tend to be secure, and their vulnerabilities are not nearly as public as some of their open source counterparts. (I’ll review this more in later posts.)

On the down side, this software can be expensive. Really expensive. Licenses can easily run $10,000 one time plus $2,000 annually. On larger installations, this number can be significantly larger. And this doesn’t even include installation. The total bill for integrating a commercial proprietary CMS into your website can run into the hundreds of thousands of dollars. But then again, what’s the only constant brand presence your company has worth to you?

Another down side is that your internal programming resources (if you have any) can’t extend these applications as easily as they can extend open source software. Everyone has heard “wouldn’t it be nice if the CMS could do X? Most of these CMS’ have certified partners that can help you write extensions, but it does not compare to the ease and cost-effectiveness of extending Open Source.

Lastly, there aren’t scores of developers contributing new, creative modules to these platforms every day (although scores of developers could also be viewed as a security threat). A quick glance through the extension libraries of Drupal and Joomla will give you an idea of just how much intellectual capital has been thrown at this software by its contributing members.

That’s my outline for commercial proprietary CMS. As I mentioned above, this is the category I have had the least experience with. If there’s something you’d like to add, please do.

We’ll cover true open source, and agency or professional services (in house) CMS in future posts.

Content Is King – Picking the Right CMS: Part I, Definition of Terms

Thursday, November 19th, 2009
King's solitude - La soledad del Rey by Manuel Marin via Flickr

King's solitude - La soledad del Rey by Manuel Marin via Flickr

Content is king, so it’s no surprise that content management systems have become one of software’s fastest growing industries with hundreds (if not thousands) of offerings. As the primary means for non-technical workers to update a website, web content management systems have become part of the everyday work lives for tens of thousands of employees.

So how do you choose which content management system to run with? Better yet, where should you even start looking?

If you want to make sure you’ve made the right choice, I recommend that you start by outlining the different tiers of content management systems available, and the pros and cons of each. Once you’ve decided on a tier, it will make drilling down to a particular CMS much easier.

Over the next few articles, I’m going to do just that. These articles will be geared to help a business person make a decision on which tier of content management system to investigate further.

NOTE THIS DISCLAIMER! This is not intended to be a comprehensive comparison of the feature/functionality of any particular CMS or CMS’. I’m also not trying to argue one way or another about the validity of content management systems themselves. For these articles, I’m assuming they’re a worthy investment. Let’s just run with that assumption. Maybe someday I’ll write about who really needs a CMS in the first place. That won’t be discussed during these articles.

To start it all off, we really need an operational definition of “content management system” so that we can all understand exactly what I’m writing about. For the purposes of these articles, we’re going to use the term “content management system” or “CMS” to refer to web content management systems like drupal, joomla, concrete5, etc., and NOT true enterprise content management systems like SharePoint and Confluence. The difference between them is that web content management systems only allow users to edit pages on the website, whereas enterprise content management systems help employers manage and collaborate on everything content including documents, spreadsheets, slides, and the website. In terms of a CMS, the basic functionality we’re looking for is a text editor (WYSIWYG or WYSIWYM), Navigation Manager, Form Builders, Template Engine, and File Storage. So, when you’re reading these articles, remember that we don’t mean enterprise CMS systems – so that there’s no confusion.

Now that we’ve defined what we’ll mean by “CMS” for this article, I can list the tiers we’ll discuss in upcoming posts. The different tiers of web content management (at least for my purposes) are commercial proprietary, commercial open source (there is a fine line between commercially backed open source and commercial open source), true open source, and agency or professional services (in house) content management systems.

Check back for the next article and we’ll start discussing the different tiers.

Should I Develop A New Product Or Find A Partner?

Thursday, November 12th, 2009
Handshake by Svadilfari via Flickr

Handshake by Svadilfari via Flickr

One of the smartest things you can do for your business is to determine what you do well and what you’d be better off outsourcing. Sometimes entrepreneurs feel like they have to do it all, that using an outside source to provide part of what they’re offering to customers is cheating. But really, it’s okay. It’s even expected.

Everyone has their own area of expertise – you can’t be everything to everyone. So it only makes sense to find someone who excels in what you don’t, so that you’re providing the best to your client. Recognizing your own expertise and limitations allows you to provide value to your customer. It’s not that you’re just marking up what someone else does to make middle-man profit; you know who the best source is to fill their needs, and they’re counting on the fact that you’ve done the research and have found the right solution.

It might be tempting to try to create the solution in-house – so you don’t have any external costs to worry about. But make sure you weigh all factors before you make that decision. Some questions to ask:

  • Will I truly be able to provide a service comparable to the existing providers?
  • Does my staff have the capacity to fill the tasks on an ongoing basis?
  • Will the amount I can charge for the services adequately account for the amount of time to design & implement the new product?
  • Does the new product fit my business model and brand?
  • Would finding a partner/provider negatively impact my brand message?

If your answer to any of the above is no, you should probably find a partner.

Why Your Site Bounces So Much Traffic

Friday, November 6th, 2009

If you’re looking at your site and thinking: “It really looks great – the design is wonderful; people are sure to want to visit and learn more about us now,” then you’re probably going to be in for a big disappointment.

Library Services Hierarchy by herzogbr via Flickr

Library Services Hierarchy by herzogbr via Flickr

The fact is that while design can improve a site’s performance, it can only do so on sites where the information hierarchy has already been established. People already spread their time too thin, to expect them to search your site for the relevant piece of information they need is unrealistic. They want what they want, and they want it NOW, or they’ll leave. Period.

When you’re setting up your site, the number one thing you need to consider is what your target is actually looking for, and then provide it – in quickly absorbable, bite-sized chunks. So many of the businesses I talk to are under the misguided impression that the goal of their site should be to cause people to go deeper to get what they need – if they learn more about the company, they’ll want to do business with us, right? Wrong.

By providing what the visitor needs quickly and up front, you’ll demonstrate an understanding of their needs. They can learn more about you later – if they decide they need more incentive. Determine what it is about your company that is most compelling, and what your target absolutely needs to know to do business with you. Put that in the premium position on your site – on your home page. Then, develop a hierarchy for everything else you think the visitor wants to know, and what you want them to know, with what the visitor wants always coming first.

Remember, it’s all about QUICK, QUICK, QUICK, and what the visitor wants to know. Having additional support content can be good, but as secondary & tertiary pages the visitor can discover if they so desire. Determining what’s most important to impart is the key to reducing your bounce rate.

How’s your hierarchy working?

Internet Marketing Webinar from AIADA and ADT

Tuesday, June 9th, 2009

Learn how to get more from your internet marketing budget at this seminar on Tuesday, June 16, 2009 – 2:00PM EDT.

It’s FREE, only 30 minutes, and will offer strategies to help automotive dealers more effectively execute internet marketing strategies and budget. This webinar will cover:

  • Online inventory
  • How is inventory displayed in classifieds
  • Where are your efforts focust
  • Getting the most real leads online

Find out more about this seminar and sign up here.

IKIWISI – How to solve the "I'll know it when I see it" dilemma

Tuesday, March 3rd, 2009

IKIWISI!
“I’ll know it when I see it!” That seems to be the current mantra in software/web development.  It means stakeholders don’t know what they want their final web product to be until they see it.

Software and web developers have tried to accommodate these make-it-and-we’ll-see requests through technologies like the WYSIWYG (what you see is what you get) editor.  Products like Protoshare, IRise, and Axure have taken this a step further, creating clickable prototypes which not only gives stakeholders a visual representation of what the site will look like, but can also provide an indication of how it will “breathe” – or to put it in other words, what it will be like for a user to traverse the site: Will it be intuitive? Crowded? Does prioritization of items on the home page make sense? You get a basic answer to these questions with these products.

But it’s an uphill (and unnecessary) battle to try to take specs, create the product in its entirety, show the stakeholder the final version, and expect a quick approval. In fact, since most people (including sophisticated software developers) don’t know what they want until they see it, there’s a good chance that all your work will end with a, “Hmmm. No. That’s not it. Try again.”

So how do you solve the puzzle of what your customers really want, so that you can both be profitable?

I think the solution is to create the final product iteratively.  This high-level chronology is what I use to create websites, and it’s worked well. The process goes like this:

  1. Create the Site Map: This includes agreeing on the goals of the homepage, and should incorporate the most recent specs. Without a site map one has almost no framework to work from. The site map will also help you see how the pages relate and will give you an idea of flow through the site. (You will need to communicate that flow through discussions.)
  2. Design the homepage and any pages with unique functionality or unique user interface.  This can includes search pages, search results pages, user input pages (forms), etc. Share the designs, make sure that the customer agrees with the overall look and feel. Details can be worked out as you’re moving forward.
  3. Begin building the “shell” of the website with live links/navigation and on a server that all stakeholders can easily access.  Usability testing (at least informally) can begin to take place at this point.  If you expect stakeholders to start understanding what they want at this point, you’ll realize that they’re going to request changes.  It’ll still be early enough in the process at this point where you can embrace those changes – which will make your client very happy.
  4. Code the remaining functionality of the site.  Unit tests can be written between steps 3 and 4 if that is something your organization engages in. Upon completion of the coding, all unit tests should be passed, and post-production testing should take place. I like to show the client the un-skinned functionality to make sure we’re on the right track.
  5. Skin the site.  That is, do any visitor-side programming that needs to be done (CSS/HTML). Make the site look pretty.  Get final approval from the stakeholder.
  6. Push the site to live.

Following this order in production of a site can help eliminate the IKIWISI issue from killing your man hours. And remember, keeping stakeholders in the loop throughout the whole process will save developers/designers hundreds of hours of re-dos, redesigns, revisions, etc.

Social Media Today

Thursday, February 19th, 2009

I just got forwarded a BusinessWeek article: “Debunking Six Social Media Myths.”

While I agree with most of the premises for running a good social media campaign, I think there’s some additional points that need to be made about marketing planning in general:

First, traditional marketing is not dead. You need the right mix. Get your strategy straight before you start.

Second, let’s not forget branding and your own website. If you have a social media program in place and your website doesn’t convert, there’s really no point. In fact, before I’d spend money on a social media program, I’d make sure my site is not only converting, it’s pulling people for repeat visits. If you’re not giving them new content on your site regularly, is there any reason for them to come back? And if they’re not coming back, how are you convincing them to work with you?

Third, just because a lot of other companies are jumping on the social media bandwagon doesn’t mean it’s right for you. Get your plan together before you expend effort and budget on this.

Finally, if you do endeavor to get a social media plan together and follow the advice in the BusinessWeek article on how to do it, you still are going to need someone on your end to answer questions and interact with those responding to your efforts. Make sure you have that in the budget before you run with it.

What are your thoughts?