Integrating Third Party Web Sites: Don't Forget the Template!

A common issue I come across in my work is the effective integration of third party services with the overall web presenece for an organization. And I don’t just mean the login system, although that’s been a hobby horse of mine for some time.

I mean that the visual and navigation experience of moving from the main site to a hosted service is often jarring and off putting. If your audience includes folks who are still a bit skittish online, you’ll lose them if they are not positive that the hosted site is actually yours. We can thank the phishing scammers for that.

What is a third party site? It is one that an organization has contracted with to provide a specific service, content or features that they either cannot or do not wish to develop on their main site. Job boards, search engines, discussion forums, social networking tools and blogs are all examples of these kinds of services.

The solution is to make the ability to use your overall look and feel, including navigation system, on the hosted site as a primary selection criteria. Many managers don’t explore this fully and end up with a service that has their logo on it but otherwise bears no resemblance to the main site. Exploring this fully during selection and contract negotiations will prevent a lot of user pain down the road.

And to you service providers out there, making it insanely easy to support an organization’s overall look and feel would be a good way to stand out from your competitors.

Microsoft's Hammer

Is it just me or has Microsoft Office SharePoint Server 2007 (MOSS 2007) mania taken over the IT world?

I have heard lots of buzz about this package, especially in the association industry, but I’ve yet to see the overwhelming value in MOSS’s interfaces and services over previous versions of SharePoint. MOSS is nice for collaboratively managing documents and searching but beyond that basic project work I think its interface gets in the way. It is a horrible community platform compared to many of the open source and low-cost solutions already available.

Not to mention the organizations that are diving in head first and planning on using MOSS (with MS CMS rolled in) as the total solution for their intranet and public web sites. There is a good reason that different classes of solutions have evolved for public and intranet sites: they have vastly differing requirements for most organizations.

My advice is to bide your time and carefully consider which nails you ultimately decide to whack with the MOSS hammer.

A Couple Conference Opportunities for June

There are two conferences I’ll be attending in DC in June that I wanted to let you know about. They happen to overlap but are in the same building, so you could hit them both if you wanted.

First, Jeff De Cagna is spearheading a social media unconference for association executives on June 5, 2007 at ASAE & the Center’s meeting space in the Reagan Building. The event is free and will be driven by the attendees. Simply add your name to the registration list on the web site if you wish to attend. I’m very excited this event is happening and I encourage you to attend if you are passionate about social media and/or want to learn more about it.

The second event is the Gilbane Washington DC conference on June 5-6, 2007, also at the Reagan Building. This conference focuses on content management technologies for government and non-profit organizations. Content is tracked, so there should be something for everyone. I will be facilitating a panel on integrating association and content management systems and processes. This event is not free but you can get a $100 discount by entering my last name as a promotional code when you register.

I hope to see you at one or both events!

On Launching and Marketing a Redesigned Web Site

There was an interesting thread last week on a list I subscribe to about how to best launch a major web site redesign. I ended up writing a white paper in response on how to best prepare for a web site launch from a technical standpoint: Five Critical Steps for a Successful Web Site Launch.

There was also a discussion of whether you should market the new site in advance or launch it quietly without fanfare. In my view, the decision should be driven by your overall goals and confidence in your timelines.

If the new site is the embodiment of a major initiative, making a splash with the launch may be in order. However, if you are not highly confident in your ability to stay on schedule, the soft launch will ameliorate a lot of potential risk.

Finally, when you do market the new site, focus on the new value it provides to visitors rather than the fact it is new. This sounds obvious but it is easy to lose sight of after the organization has invested so many resources in the effort.

Big Book Stores and Amazon

So, when you compare Amazon to Barnes and Noble or Borders (just on book selling), how are they fundamentally different?

All three sell online and, while Amazon is still the best, the other two have reasonably easy interfaces for selling books. What is left? Physical stores. B&N and Borders have the liability and asset of a physical retail presence in many communities across the country. However, they fail horribly to the leverage the two together to improve overall sales.

If you are looking for a physical retail store, it is likely because you want to buy a book right away. If you are willing to wait a few days, you can just order online. But if you want it right now, say before you catch a flight that afternoon, you want to know if the store near you is carrying the title before making the trek out there. Making retail inventory available for search by store seems like a no-brainer. It relieves floor staff from having to answer as many phone calls and enables customers to find out if they can buy more immediately.

However, Borders buries this feature several levels down in their site and B&N doesn’t even offer it. What a wasted opportunity.

The ideal interface, I think, would be to set a cookie for the user’s zip code at some point and then offer local retail inventory results along with online inventory.

Gee, that sounds simple. Why don’t they do it? My guess would be that their performance measures don’t reward cross-selling between physical and online operations.

Pre-requisites for a Successful Small Business Web Site

There are 6 pre-requisites for a successful small business web site. The are:

  1. Have one!
  2. It lists location, hours and contact information prominently on the home page.
  3. Services and/or products are clearly identified in general on the home page and in detail on dedicated pages.
  4. They qualify that they are the best source for whatever the business provides.
  5. The design looks reputable.
  6. They have updated their listings in the local search engines for Google and Yahoo!.

Hitting each of the above won’t guarantee success but it will prevent fundamental flaws from preventing the best possible outcomes for a business with their web site.

The above is based on part of my presentation to the American Association of Endodontists a couple weeks ago.

First Product Wiki in the Association Space?

Avectra, vendor of one of the major association management systems, has launched a public wiki to support their products.
This is the first public wiki to support an association-dedicated product that I am aware of. I think there is a good chance this will build critical mass with their customers. Association staff are going to have high incentive to contribute since this is such a major part of their management systems yet there are few to no resources, such as commercially published books, on the subject.

It might work better if the user groups dedicated to the AMS vendors launched their own wikis, maintaining some independence.

(Spotted on Wes Trochlil’s blog.)

What information should a consultant share with a client about the RFP process?

I heard from an executive recently that the consultant helping them to select their content management system had a highly qualified list of vendors they had researched and were sending requests to those who best matched their needs. So far, so good. However, the consultant refuses to share or discuss the list of vendors with the client!

This presents a few problems:

  • It shows contempt for the client on the part of the consultant;
  • It prevents the client from providing their highly valuable take on the prospective vendors as part of the selection process;
  • How does the client know they are really talking to more than one vendor?

Does your buyer agent Realtor present you with a single house? Does a car salesman show you only one vehicle, take it or leave it? Of course not.

There is no business need or ethical basis for not sharing and discussing the list of potential vendors with a client, in my not-so-humble opinion. It is simply bad practice. Any consultant doing so is not serving their client nor themselves well.

IA's Miss the Point

This thoughtful post by Christopher Fahey is a great example of how information architects tend to miss the point of their projects: The Holy Grail of Information Architecture. If you read through this post you hear a lot about process and tools and what form the ultimate deliverable from the project should take in order to be most effective. Christopher has concluded that standard deliverables aren’t the Holy Grail of an IA project but he doesn’t quite make the leap to what is: achieving the objectives of the organization.

The point of information architecture should be to help the organization in question to better achieve its goals. The output of an IA engagement should be the achievement of those business goals, not necessarily a nifty flow chart and set of wireframes. Selling widgets, providing membership value, business networking, politics, whatever the purpose of the site: IA should help to achieve those ends more effectively and efficiently. If you can provide that value simply by reviewing and discussing a site in a meeting, great! Don’t get hung up on the deliverables. Do focus on the outcomes to which you are contributing.