Showing posts with label vendor evaluation. Show all posts
Showing posts with label vendor evaluation. Show all posts

0 What Brain Research Teaches about Selecting Marketing Automation Software

I’m spending more time on airplanes these days, which means more time browsing airport bookshops. Since spy stories and soft core porn are neither to my taste, the pickings are pretty slim. But I did recently stumble across Jonah Lehrer’s How We Decide, one of several recent books that explain the latest scientific research into human decision-making.

Lehrer’s book shuttles between commonly-known irrationalities in human behavior – things like assigning a higher value to avoiding loss than achieving gain – and the less known (to me, at least) brain mechanisms that drive them. He makes a few key points, including the importance of non-conscious learning to drive everyday decisions (it turns out that people who can only make conscious, rational decisions are pretty much incapable of functioning), the powerful influence of irrelevant facts (for example, being exposed to a random number influences the price you’re willing to pay for an unrelated object), and the need to suppress emotion when faced with a truly unprecedented problem (because your previous experience is irrelevant).

These are all  relevant to marketing, since they give powerful insights into ways to get people to do things. Indeed, it’s frightening to recognize how much this research can help people manipulate others to act against their interests. But good marketers, politicians, and poker players have always used these methods intuitively, so exposing them may not really make the world a more dangerous place.

In any event, my own dopamine receptors were most excited by research related to formal decision making, such as picking a new car, new house, or strawberry jam. Selecting software (or marketing approaches) falls into the same category. Apparently the research shows that carefully analyzing such choices actually leads to worse decisions than making a less considered judgment. The mechanism seems to be that people consider every factor they list, even the ones that are unimportant or totally irrelevant.

It's not that snap judgments are inherently better. The most effective approach is to gather all the data but then let your mind work on it subconsciously – what we normal folks call “mulling things over” – since the emotional parts of the brain are better at balancing the different factors than the rational brain. (I’m being horribly imprecise with terms like “emotional” and “rational”, which are shorthand for different processes in different brain regions. Apologies to Lehrer.)

As someone who has spent many years preparing detailed vendor analyses, I found this intriguing if unwelcome news. Since one main point of the book is that people rationalize opinions they’ve formed in advance, I’m quite aware that “deciding” whether to accept this view is not an objective process. But I also know that first impressions, at least where software is concerned, can’t possibly uncover all the important facts about a product. So the lesson I’m taking is the need to defer judgment until all factors have been identified and then to carefully and formally weight them so the irrelevant ones don’t distort the final choice.

As it happens, that sort of weighting is exactly what I’ve always insisted is important in making a sound selection. My process has been to have clients first list the items to consider and then assign them weights that add to 100%. This forces trade-offs to decide what’s most important. The next step is to score each vendor on each item.  I always score one item at a time across all vendors, since the scores are inherently relative. Finally, I use the weights to build a single composite score for vendor ranking.

In theory, the weighting reduces the impact of unimportant factors, setting the weights separately from the scoring avoids weights that favor a particular vendor, and calculating composite scores prevents undue influence by the first or last item reviewed. Whether things work as well as I’d like to believe, I can’t really say. But I can report three common patterns that seem relevant.

- the final winner often differs from one I originally expected. This is the “horse race” aspect of the process and I think it means we’re successfully avoiding being stuck with premature conclusions.

- when the composite scores don’t match intuitive expectations, there’s usually a problem with the weights. I interpret this to mean that we’re listening to the emotional part of the brain and taking advantage of its insights.

- as scoring proceeds, one vendor often emerges as the consistent winner, essentially “building momentum” as we move towards a conclusion. I’ve always enjoyed this, since it makes for an easy final decision. But now I’m wondering whether we're making the common error of seeing patterns that don’t exist.  Oh well, two out of three isn’t bad.

Perhaps I could reduce the momentum effect by hiding the previous scores when each new item is assessed. In any event, I’ve always felt the real value of this process was in the discussions surrounding the scoring rather than the scores themselves. As I said, the scores are usually irrelevant because the winner is apparent before we finish.

Still, having a clear winner doesn’t mean we made the right choice. The best I can say is that clients have rarely reported unpleasant surprises after deployment. We may not have made the best choice, but at least we understood what we were getting into.

I guess it’s no surprise that I’d conclude my process is a good one. Indeed, research warns that people see what they want to see (the technical term is “confirmation bias”; the colloquial term is “pride”). But I honestly don’t see much of an alternative. Making quick judgments on incomplete information is surely less effective, and gathering data without any formal integration seems hopelessly subjective. Perhaps the latter approach is what Lehrer’s research points to, but I’d (self-servingly) argue that software choices fall into the category of unfamiliar problems, which the brain hasn’t trained itself to solve through intuition alone.


0 Raab VEST Report: Testing, Data Quality and Content Management Still Lag in Marketing Automation Products


My last post looked at data from our just-released B2B Marketing Automation Vendor Selection Tool (VEST) to understand general industry trends and identify the greatest areas of improvement. Today we’ll look at the VEST data to see what’s still hard to find. As before, the charts show three columns: change in feature availability over the past year among core marketing automation vendors; current availability among core vendors; and current availability among enterprise vendors. See the previous post for details on the calculations.

Split Tests: Formal split testing of different content versions or customer treatments is the heart of marketing optimization, but many B2B marketers still don’t have the time or resources to do it. Given the lack of demand, it’s not too surprising that many vendors don’t offer strong testing features.  Still, I feel they have something approaching a moral obligation to provide these features and encourage their use.  Note that splits within lists, the one testing capability that is fairly common, is actually the hardest for marketers to use.  Testing features are much more available among enterprise systems, whose clients are more likely to conduct tests as a matter of course.


Value-Based Selection: This is arguably the next step after dynamic content (see my previous post), since it uses calculated values rather than user-crafted rules to select marketing contents or campaign actions. Like dynamic content, it reduces the complexity of marketing programs while allowing them to be more targeted. It's still much harder to find than dynamic content although it is becoming more available.  Again, enterprise vendors have a substantial lead over the core systems.


Integrate with Direct Mail Printer: This is admittedly a small tactical issue, but it's interesting in its own way.  There’s apparently a resurgence of interest of direct mail generally and post cards in particular as a way to avoid ever-more-cluttered email inboxes and social media channels. This is one of the few features that are more common among micro-business systems than the core group.


Project and Content Management: These features are most important for large marketing departments that need coordinate work of many people. Most core marketing automation systems can track the creation and last change date of an item. But serious administration requires much more detailed control over who makes changes, approvals, and project management. As marketing programs get more complicated at all sizes of companies, these features will become increasingly important.


Data Quality: These are features that give marketers more control over the data that goes into their systems. Like split testing, data quality is widely recognized as important but often ignored. Availability of these features actually went down last year because several new core vendors provided below-average support. Enterprise vendors, with their more sophisticated client base, support these features fully.


Data Management: These features each reflect a certain degree of data management sophistication, although there’s a reasonable case that a separate company table doesn’t matter much in practice. The opportunity table is critical for revenue analysis, and you see here that it’s widely available. Custom tables are needed to extend the marketing database beyond inputs from the CRM system. They used to be fairly rare but are now available in more than half of the core products.   But half full also means half empty, so buyers still need to check carefully to ensure a particular vendor supports their needs.


Reviewing this list of features, only value-based selection is really cutting edge.  The rest have long been standard for consumer marketing automation products and enterprise B2B.  They're missing from core B2B marketing automation systems because most of their clients are smaller, less sophisticated companies who haven't needed them.  This may never change for vendors focused on small marketing departments.  But vendors serving larger companies will add these features as their clients discover they need them.

For more information about the B2B Marketing Automation VEST report, please visit www.raabguide.com/vest.

0 Fabulicious Workbook Helps Assess CRM Integration Features of Marketing Automation Systems

CRM integration is a fundamental feature of marketing automation.  Pretty much every system can send leads to Salesforce.com, but capabilities vary significantly once you start looking for more.   Sadly, most marketers pay little attention to these nuances until they've already selected a product.  Then they learn they hard way what they should have asked.

In hopes of avoiding these mistakes, Raab Associates has just published a workbook on assessing integration capabilities before you buy.  The workbook lays out the types of integration, types of issues to consider, how to understand your needs, and how to assess vendor capabilities. It then gives ten pages of checklists with specific features to consider. the topic.  The workbook was sponsored by SalesFusion, although they didn't influence the contents.

This is an inherently dry subject, so I made the workbook as entertaining as I could. In fact, I may have exceeded the bounds of good taste: the topic allows a surprising number of double-entendres if you work at it. If you’re planning to buy a marketing automation system, be sure to download it from the Raab Guide site (free with registration) and take a look.

Even better, attend SalesFusion's December 6 Webinar on the topic (register here).  I won’t be presenting but you'll get great information and a copy of the new workbook.

0 B2B Marketing Automation Report Is Ready...My Web Site, Not So Much

The good news is, my new B2B Marketing Automation report (more formally: the Vendor Selection Tool, or VEST) is now available. The bad news is I can't actually sell it online, despite the best efforts of Web masters on two continents. But the good news is I'm more than happy to take credit card orders directly if you send me an email or give me a call. Email is info@raabguide.com.

To recap a bit, the new report is based on a survey of 18 vendors, who answered nearly 200 questions about their products and companies. Most answers were scored from 0, 1 or 2, indicating whether a particular feature was available fully, partly, or not at all. I translated other answers such as starting price or number of employees into similar 0-2 ranges so I could combine everything in a scoring formula. See my posts over the past few weeks for details on that.

The final result was three sets of scores for each vendor. The sets represent fitness for small, mid-size and large businesses, and each set contains a product fit score and vendor fit score. The idea was to simulate the type of scoring that a typical business in each category might do in its own vendor evaluation. Of course, no one's business is truly typical, so the interactive version of the tool also lets you create your own custom scoring weights.

The core of the new report, therefore, contains two sections: scatter diagrams plotting all the vendors in a typical "industry matrix" style and individual vendor profiles.

The industry matrix puts leads at the top right, where God and Gartner evidently intended them to be, and cleverly named other groups everywhere else. The clever part is giving names that are descriptive without being insulting. I settled on:

- "alternatives" (strong product fit but weak vendor fit)
- "anomalies" (weak product but strong vendor fit)
- "long shots" (weak product fit and weak vendor fit)

The vendor profiles give more detail about each vendor, including showing the scores for components within the product fit (7 components) and vendor fit (2 components). This gives some good insight into where the rankings came from.

So far so good. As I hinted before, there's both an interactive version and non-interactive version of the report. This is partly because I don't think everyone will want to pay for the full price for the interactive version and partly because some people have had problems running the interactive version, which uses Adobe Flash within a PDF. The non-interactive version, which I'm tactfully referring to as "basic", has an introductory section with industry explanations, recommendations on a selection process, etc., plus the three industry matrix charts (for small, mid-size and large) and individual profiles on each vendor. The profiles offer some narrative and scores for the components within the larger scores: 7 components within the profit fit (lead generation, campaign management, scoring, etc.) and two within the vendor fit (company strength and sector expertise). These give some insight into where the sales came from. This is priced at $295.

The interactive version has all those elements, which are made interactive by the fact that users can change the weights assigned to the different components within the profit and vendor fit scores. You've seen some of this is the same PDFs I posted over the past few weeks. It's great fun: there are little sliders for the weights and the vendors zoom around on the chart as you move them. A wonderful feeling of power.

The interactive edition also contains three more sections:

- Item Detail, which lets you see the 200-ish individual items used in the scoring, including their definitions and the weights assigned in each of the three scoring schemes.

- Custom Weights, which lets you set your own scoring weights for the individual items. You can start with the existing small, mid-size, or large weights as a base.

- Compare (my personal favorite), which lets you pick any three vendors and see how their scores compare in any of the weighting sets (small, mid-size, large, or custom). You can see bar charts with overviews and then drill into the item-by-item details for each category. This is where you see the specific differences between vendors.

Price for the interactive edition is $795.

I'll be presenting some additional analysis based on what's in the reports over the next few weeks, and of course will make a formal announcement once the e-commerce bugs are worked out. Again, though, you're welcome to send me a note to get your copy at once.

0 Ranking B2B Marketing Automation Vendors: Part 3

Summary: The first two posts in this series described my scoring for product fit. The third and final post describes scoring for vendor strength. And I'll give a little preview of the charts these scores produce...without product names attached.

Beyond assessing a vendor's current product, buyers also want to understand the current and future market position of the vendor itself. I had much less data to work with relating to vendor strength and there are many fewer conceptual issues. From a buyer’s perspective, the big questions about vendors are whether they’ll remain in business, whether they’ll continue to support and update the product, and whether they understand the needs of customers like me.

As with product fit, I used different weights for different types of buyers. As you'll see below, the bulk of the weight was assigned to concentration within each market. This reflects the fact that buyers really do want vendors who have experience with similar companies. Specific rationales are in the table. I converted the entries to the standard 0-2 scale and originally required the weights to add to 100. This changed when I added negative scoring to sharpen distinctions among vendor groups.


These weights produced a reasonable set of vendor group scores – small vendors scored best for small buyers, mixed and special vendors scored best for mid-size buyers, and big vendors scored best for big buyers. QED.


I should stress that all the score development I've described in these posts was done by looking at the vendor groups, not at individual vendors. (Well, maybe I peeked a little.) The acid test is when the individual vendors scores are plotted -- are different kinds of vendors pretty much where expected, without each category being so tightly clustered together that there's no meaningful differentiation?

The charts below show the results, without revealing specific vendor names. Instead, I've color-coded the points (each representing one vendor) using the same categories as before: green for small business vendors, black for mixed vendors, violet for specialists, and blue for big company vendors.






As you can see, the blue and green dots do dominate the upper right quadrants of their respective charts. The other colors are distributed in intriguing positions that will be very interesting indeed once names are attached. This should happen in early to mid January, once I finish packaging the data into a proper report. Stay tuned, and in the meantime have a Happy New Year.

0 Act-On Software Adds Webinar Integration to Small Business Demand Generation

Summary: Act-On Software provides a solid set of demand generation features at a small business price. This review was revised in May, 2010 to reflect developments since the original post of March, 2009.

If you look at the Web site of Act-On Software, you’ll see a typical set of demand generation features: email marketing, demand generation (equated with landing pages and forms), lead nurturing, Website visitor tracking, channel (partner) marketing, and lead scoring. Oddly, it does not highlight Act-On’s most distinctive advantage, which is tight integration with Webex for Webinar presentations.

Working with Act-On is like working with other products: users build emails, landing pages and Web forms; track activities through page tags and cookies; do scoring and segmentation with activity history and lead attributes; and pass qualified leads to Salesforce.com. The specific features to do this are reasonably powerful: for example, emails and Web pages can be built from scratch, based on templates or imported, while the templates themselves can be built from components stored in a central library. The components can include prebuilt surveys, which can be embedded in an email or linked to a separate Web form. This is more than many other products offer.

The system also offers above-average flexibility in its delivery arrangements: clients can send the email either from their own servers or through Act-On, and can display Act-On-host forms within external Web pages as iframes.

Act-On does a good job of capturing activity history and form entries. The system will track both known and anonymous visitors, using the IP address to look up the company of anonymous visitors and linking to JigSaw to show company information It can also send alerts when it sees visits from specified individuals, companies, or locations. All activities for a given lead (identified by an email address or cookie ID) can be used for scoring and segmentation. Data posted to Web forms can also be stored in a central file. Scoring rules can reference both lead attributes and activities, and are updated in real time as new data arrives. Users can also apply scores, attributes or activities to define lists that are updated in real time.

So far so good, and now we can talk about Webinars. Users can define a Webinar within Act-On, entering name, time, date, duration, password, and teleconference number, and then push this to their Webex account. They can also create a registration page and form, auto-response message, invitation emails, reminders and follow-up emails. The system will feed the registrations into Webex and pull back attendee lists, gathering all the related data within Act-On for reporting. This is a significant improvement over the usual situation, where data is scattered between the different systems.

But remember that channel marketing listed on the home page? It’s pretty limited. Dealers and similar channel partners can be assigned Act-On accounts with access to the library of marketing materials, including documents and email templates. They can also import lists and execute email campaigns. The parent company can’t use the partners’ lists (always a sensitive issue) but does have access to responders. At present, email templates are either fully locked-down (no changes allowed) or totally open. Act-On plans to refine this so the parent can allow partners to change some portions of the template and not others. Even with these changes, the channel management features in Act-On don’t compare with Marketbright or Treehouse International. (For more information, see my blog post on Marketbright and my post on Treehouse International.)

Lead nurturing supports multi-step, event-triggered email campaigns. These are defined as a sequence of steps with conditions inside each step to select different messages for different individuals. Campaign steps can also assign leads to a new list, change a data value, and wait a specified period before continuing. In addition, users can assign an exit condition to each campaign that removes leads at any step when the condition is met. This is used to end a message stream when leads are submitted to sales or qualify for a different campaign with higher priority.

Act-On describes its contents as stored in a collection of lists rather than a conventional database. I found this perplexing in my original look at the product but have decided after closer examination that it's mostly a matter of semantics. In practice, customers maintain a single “master marketing list” with all lead profiles and an activity history linked to each profile. The other lists are either segments derived from the master list or supplementary data such as survey responses that are best kept separate from the main profile. The system has standard connectors to import data from Salesforce.com (it can pull members of a specific campaign, all contacts or all leads), Microsoft Outlook, and Webex. It can also take data from Excel, comma-separated text files and its own Web forms. Data can be automatically synchronized at user-defined intervals.

The system also provides an unusal Twitter marketing feature that makes it easy to scan for prospects and send them standardized messages. See my May 2010 post on social marketing feature for details.

Pricing is based on the number of “active” contacts (defined as having an interaction or receiving a message), starting at $500 per month for 5,000 active contacts. It’s hard to compare this with other vendors, since most charge based on database size or communication volume. But it seems competitive with small business-oriented demand generation systems and lower than products aimed at larger firms. There are no set-up fees, clients can have month-to-month contracts, and you can start with a 30 day free trial. So this is a pretty easy system to buy.

Act-On also offers a sales automation system that could be an alternative to Salesforce.com. Pricing on this starts at $14.95 per month for three users and 1,000 contacts.

Act-On released its beta version in June 2008 and started selling that October. As of April 2010 it had about 80 clients. Most are small or mid-sized, but they also include Cisco, which invested in Act-On in 2008.

0 Low Cost Systems for Demand Generation

My new obsession with Twitter (follow me as @draab) has led to several messages from people who seemed to have trouble choosing between Eloqua and Marketo . This is a bit perplexing, since those products are at the opposite ends of the spectrum: Marketo being relatively low cost / limited functionality / easier to learn, and Eloqua being higher cost / richer functionality / takes more training. It shouldn't be hard to figure out which one suits you better.

But what really concerns me is that these people are apparently limiting their consideration to just those two products. I do recognize that they are the best known vendors in the space (with apologies to Vtrenz, whose identity is somewhat blurred since its purchase by Silverpop). But there are plenty of other options, particularly for marketers with limited budgets. Marketo is certainly a fine product, but marketers should still look around before picking it by default. Here are some alternatives that will come in at or below Marketo’s published starting price of $2,400 per month (or $1,500 for their “Lite” version). (To be fair, many of the vendors below charge an installation of that can be several thousand dollars or more, while Marketo doesn't. But even including that, the first year cost for most of these will be less.) :

Manticore Technology: a full-featured demand generation product. See my 2007 blog entry for some information or buy the Raab Guide to Demand Generation Systems for a detailed review. (Just kidding...or am I?) Pricing on their Web site is quite close to Marketo’s: $1,000 a month for a limited edition and $2,400 per month for all the bells and whistles, and no extra charge for installation.

Pardot: another pretty powerful product; see my blog review from December 2008. But much better pricing at the low end $750 per month for the smallest complete system, and $1,250 per month for something that should be adequate for larger firms.

OfficeAutoPilot: this is the current incarnation of what used to be Moonray. I took a detailed look at a beta of the next release a couple of weeks ago and liked both the interface and breadth of functionality. I’m just waiting for the official release (due in for late February) to publish a detailed review. [Click here to read the review, published in April.] Pricing for a full-featured system was $597 per month—quite a bargain. Even cheaper options are available if you need fewer functions.

Treehouse Interactive: another company I spoke with recently, and another one I’m not writing about yet because they showed me some features that won’t be released for a while (early March). [Click read my March 18 review.] The company has a low profile but has been selling its demand generation product for nearly ten years. It offers a pretty complete set of features, with shortfalls in some areas balanced by strengths in others. More important to people who need it, the company offers partner management and channel sales management products that integrate with its demand generation offering. Pricing starts at $599 per month.

Infusionsoft: I spoke with them just yesterday, and there’s nothing preventing me from writing about them in detail except that I do like to sleep occasionally. Maybe next week. [I got to it on February 12. Read it here.] They aim to be a complete business operating system for very small companies (under 25 employees). So they offer not just demand generation but everything from contact management to e-commerce. However, marketing is their core function and they provide a decent set of features, although certainly not as polished as some other products I’ve mentioned. On the other hand, pricing starts at $199 per month for a 2 user system with pretty much all of their marketing features, and you’d be hard-pressed to spend more than $500 per month unless you want lots of users for non-marketing functions such as sales automation or order entry. Although you may not be familiar with them, the company is five years old and has more than 12,000 (yes, that's twelve thousand) clients.

Active Conversion: I had a chat with president Fred Yee last August although I didn’t publish a detailed review. [I did publish a real review in July 2009.] They focus on email nurturing campaigns and marketing measurement. The system didn’t do landing pages or forms when I spoke with Fred, although he tells me it does now. Pricing starts at $250 per month and averages around $500.

Act-On Software: a slightly different take, with strong Webinar support and an option to use its own low-cost sales automation system as an alternative to Salesforce.com Price starts at $499 per month. I reviewed it here in March.

Before I get any complaints from other vendors in the industry, let me stress that the systems I've listed above are ones that I know have low price points. My own consideration set also includes Marketbright, Market2Lead, MarketingGenius, LeadLife, LoopFuse, LeadGenesys, , eTrigue and SalesFusion360, although I haven't looked at all of those in detail.

Obviously you need to evaluate these products in depth before deciding which is right for you. There are free papers on the Raab Guide site that can help you organize this process and of course I do consult in this area for a living. But the point of today's post isn't that you should run a thorough selection project. It's simply that should recognize that you do have choices, and take advantage of them.

0 How Do You Classify Demand Generation Systems?

I’ve been pondering recently how to classify demand generation systems. Since my ultimate goal is to help potential buyers decide which product to purchase, the obvious approach is to first classify the buyers themselves and then determine which systems best fit which group. Note that while this seems obvious, it’s quite different from how analyst firms like Gartner and Forrester set up their classifications. Their ratings are based on market positions, with categories such as “leaders”, “visionaries”, and “contenders”.

This approach has always bothered me. Even though the analysts explicitly state that buyers should not simply limit their consideration to market “leaders”, that is exactly what many people do. The underlying psychology is simple: people (especially Americans, perhaps) love a contest, and everyone wants to work with a “leader”. Oh, and it’s less work than trying to understand your actual requirements and how well different systems match them.

Did you detect a note of hostility? Indeed. Anointing leaders is popular but it encourages buyers to make bad decisions. This is not quite up there with giving a toddler a gun, since the buyers are responsible adults. But it could, and should, be handled more carefully.

Now I feel better. What was I writing about? Right--classifying demand generation systems.

Clearly one way to classify buyers is based on the size of their company. Like the rich, really big firms are different from you and I. In particular, really big companies are likely to have separate marketing operations in different regions and perhaps for different product lines and customer segments. These offices must work on their own projects but still share plans and materials to coordinate across hundreds of marketing campaigns. They need fine-grained security so the groups don't accidentally change each other's work. Large firms may also demand an on-premise rather than externally-hosted solution, although this is becoming less of an issue.

So far so good. But that's just one dimension, and Consultant Union rules clearly state that all topics must be analyzed in a two-dimensional matrix.

It’s tempting to make the second dimension something to do with user skills or ease of use, which are pretty much two sides of the same coin. But everyone wants their system to be as easy to use as possible, and what’s possible depends largely on the complexity of the marketing programs being built. Since the first dimension already relates to program complexity, having ease of use as a second dimension would be largely redundant. Plus, what looks hard to me may seem simple to you, so this is something that’s very hard to measure objectively.

I think a more useful second dimension is the scope of functions supported. This relates to the number of channels and business activities.

- As to channels: any demand generation system will generate outbound emails and Web landing pages, and send leads them to a sales automation system. For many marketing departments, that’s plenty. But some systems also outbound call centers, mobile (SMS) messaging, direct mail, online chat, and RSS feeds. Potential buyers vary considerably in which of these channels they want their system to support, depending on whether they use them and how happy they are with their current solution.

- Business activities can extend beyond the core demand generation functions (basically, campaign planning, content management and lead scoring) to the rest of marketing management: planning, promotion calendars, Web analytics, performance measurement, financial reporting, predictive modeling, and integration of external data. Again, needs depend on both user activities and satisfaction with existing systems.

Scope is a bit tricky as a dimension because systems will have different combinations of functions, and users will have different needs. But it’s easy enough to generate a specific checklist of items for users to consult. A simple count of the functions supported will give a nice axis for a two-dimensional chart.

So that’s my current thinking on the subject: one dimension measures the ability to coordinate distributed marketing programs, and the other measures the scope of functions provided. Let me know if you agree or what you'd propose as alternatives.

0 One More Chart on QlikTech

Appearances to the contrary, I do have work to do. But in reflecting on yesterday's post, I did think of one more way to present the impact of QlikTech (or any other software) on an existing environment. This version shows the net change in percentage of answers provided by each user role for each activity type. It definitely shows which roles gain capacity and which have their workload reduced. What I particularly like here is that the detail by task is clearly visible based on the size and colors of segments within the stacked bars, while the combined change is equally visible in the total height of the bars themselves.



In case you were wondering, all these tables and charts have been generated in QlikView. I did the original data entry and some calculations in Excel, where they are simplest. But tables and charts are vastly easier in QlikView, which also has very nice export features to save them as images.

0 Fitting QlikTech into the Business Intelligence Universe

I’ve been planning for about a month to write about the position of QlikTech in the larger market for business intelligence systems. The topic has come up twice in the past week, so I guess I should do it already.

First, some context. I’m using “business intelligence” in the broad sense of “how companies get information to run their businesses”. This encompasses everything from standard operational reports to dashboards to advanced data analysis. Since these are all important, you can think of business intelligence as providing a complete solution to a large but finite list of requirements.

For each item on the list, the answer will have two components: the tool used, and the person doing the work. That is, I’m assuming a single tool will not meet all needs, and that different tasks will be performed by different people. This all seems reasonable enough. It means that a complete solution will have multiple components.

It also means that you have to look at any single business intelligence tool in the context of other tools that are also available. A tool which seems impressive by itself may turn out to add little real value if its features are already available elsewhere. For example, a visualization engine is useless without a database. If the company already owns a database that also includes an equally-powerful visualization engine, then there’s no reason to buy the stand-alone visualization product. This is why vendors to expand their product functionality and why it is so hard for specialized systems to survive. It’s also why nobody buys desk calculators: everyone has a computer spreadsheet that does the same and more. But I digress.

Back to the notion of a complete solution. The “best” solution is the one that meets the complete set of requirements at the lowest cost. Here, “cost” is broadly defined to include not just money, but also time and quality. That is, a quicker answer is better than a slower one, and a quality answer is better than a poor one. “Quality” raises its own issues of definition, but let’s view this from the business manager’s perspective, in which case “quality” means something along the lines of “producing the information I really need”. Since understanding what’s “really needed” often takes several cycles of questions, answers, and more questions, a solution that speeds up the question-answer cycle is better. This means that solutions offering more power to end-users are inherently better (assuming the same cost and speed), since they let users ask and answer more questions without getting other people involved. And talking to yourself is always easier than talking to someone else: you’re always available, and rarely lose an argument.

In short: the way to evaluate a business intelligence solution is to build a complete list of requirements and then, for each requirement, look at what tool will meet it, who will use that tool, what the tool will cost; and how quickly the work will get done.

We can put cost aside for the moment, because the out-of-pocket expense of most business intelligence solutions is insignificant compared with the value of getting the information they provide. So even though cheaper is better and prices do vary widely, price shouldn’t be the determining factor unless all else is truly equal.

The remaining critieria are who will use the tool and how quickly the work will get done. These come down to pretty much the same thing, for the reasons already described: a tool that can be used by a business manager will give the quickest results. More grandly, think of a hierarchy of users: business managers; business analysts (staff members who report to the business managers); statisticians (specialized analysts who are typically part of a central service organization); and IT staff. Essentially, questions are asked by business managers, and work their way through the hierarchy until they get to somebody who can answer them. Who that person is depends on what tools each person can use. So, if the business manager can answer her own question with her own tools, it goes no further; if the business analyst can answer the question, he does and sends it back to his boss; if not, he asks for help from a statistician; and if the statistician can’t get the answer, she goes to the IT department for more data or processing.

Bear in mind that different users can do different things with the same tool. A business manager may be able to do use a spreadsheet only for basic calculations, while a business analyst may also know how to do complex formulas, graphics, pivot tables, macros, data imports and more. Similarly, the business analyst may be limited to simple SQL queries in a relational database, while the IT department has experts who can use that same relational database to create complex queries, do advanced reporting, load data, add new tables, set up recurring processes, and more.

Since a given tool does different things for different users, one way to assess a business intelligence product is to build a matrix showing which requirements each user type can meet with it. Whether a tool “meets” a requirement could be indicated by a binary measure (yes/no), or, preferably, by a utility score that shows how well the requirement is met. Results could be displayed in a bar chart with four columns, one for each user group, where the height of each bar represents the percentage of all requirements those users can meet with that tool. Tools that are easy but limited (e.g. Excel) would have short bars that get slightly taller as they move across the chart. Tools that are hard but powerful (e.g. SQL databases) would have low bars for business users and tall bars for technical ones. (This discussion cries out for pictures, but I haven’t figured out how to add them to this blog. Sorry.)

Things get even more interesting if you plot the charts for two tools on top of each other. Just sticking with Excel vs. SQL, the Excel bars would be higher than the SQL bars for business managers and analysts, and lower than the SQL bars for statisticians and IT staff. The over-all height of the bars would be higher for the statisticians and IT, since they can do more things in total. Generally this suggests that Excel would be of primary use to business managers and analysts, but pretty much redundant for the statisticians and IT staff.

Of course, in practice, statisticians and IT people still do use Excel, because there are some things it does better than SQL. This comes back to the matrices: if each cell has utility scores, comparing the scores for different tools would show which tool is better for each situation. The number of cells won by each tool could create a stacked bar chart showing the incremental value of each tool to each user group. (Yes, I did spend today creating graphs. Why do you ask?)

Now that we’ve come this far, it’s easy to see that assessing different combinations of tools is just a matter of combining their matrices. That is, you compare the matrices for all the tools in a given combination and identify the “winning” product in each cell. The number of cells won by each tool shows its incremental value. If you want to get really fancy, you can also consider how much each tool is better than the next-best alternative, and incorporate the incremental cost of deploying an additional tool.

Which, at long last, brings us back to QlikTech. I see four general classes of business intelligence tools: legacy systems (e.g. standard reports out of operational systems); relational databases (e.g. in a data warehouse); traditional business intelligence tools (e.g. Cognos or Business Objects; we’ll also add statistical tools like SAS); and Excel (where so much of the actual work gets done). Most companies already own at least one product in each category. This means you could build a single utility matrix, taking the highest score in each cell from all the existing systems. Then you would compare this to a matrix for QlikTech and find cells where the QlikView is higher. Count the number of those cells, highlight them in a stacked bar chart, and you have a nice visual of where QlikTech adds value.

If you actually did this, you’d probably find that QlikTech is most useful to business analysts. Business managers might benefit some from QlikView dashboards, but those aren’t all that different from other kinds of dashboards (although building them in QlikView is much easier). Statisticians and IT people already have powerful tools that do much of what QlikTech does, so they won’t see much benefit. (Again, it may be easier to do some things in QlikView, but the cost of learning a new tool will weigh against it.) The situation for business analysts is quite different: QlikTech lets them do many things that other tools do not. (To be clear: some other tools can do those things, but it takes more skill than the business analysts possess.)

This is very important because it means those functions can now be performed by the business analysts, instead of passed on to statisticians or IT. Remember that the definition of a “best” solution boils down to whatever solution meets business requirements closest to the business manager. By allowing business analysts to perform many functions that would otherwise be passed through to statisticians or IT, QlikTech generates a hugh improvement in total solution quality.

0 Independent Teradata Makes New Friends

I had a product briefing from Teradata earlier this week after not talking for nearly two years. They are getting ready to release version 6 of their marketing automation software, Teradata Relationship Manager (formerly Teradata CRM). The new version has a revamped user interface and large number of minor refinements such as allowing multiple levels of control groups. But the real change is technical: the system has been entirely rebuilt on a J2EE platform. This was apparently a huge effort – when I checked my notes from two years ago, Teradata was talking about releasing the same version 6 with pretty much the same changes. My contact at Teradata told me the delay was due to difficulties with the migration. She promises the current schedule for releasing version 6 by December will definitely be met.

I’ll get back to v6 in a minute, but did want to mention the other big news out of Teradata recently: alliances Assetlink and Infor for marketing automation enhancements, and with SAS Institute for analytic integration. Each deal has its own justification, but it’s hard not to see them as showing a new interest in cooperation at Teradata, whose proprietary technology has long kept it isolated from the rest of the industry. The new attitude might be related to Teradata’s spin-off from NCR, completed October 1, which presumably frees (or forces) management to consider options it rejected while inside the NCR family. It might also reflect increasing competition from database appliances like Netezza, DATAllegro, and Greenplum. (The Greenplum Web site offers links to useful Gartner and Ventana Research papers if you want to look at the database appliance market in more detail.)

But I digress. Let’s talk first about the alliances and then v6.

The Assetlink deal is probably the more significant yet least surprising new arrangement. Assetlink is one of the most complete marketing resource management suites, so it gives Teradata a quick way to provide a set of features that are now standard in enterprise marketing systems. (Teradata had an earlier alliance in this area with Aprimo, but that never took hold. Teradata mentioned technical incompatibility with Aprimo’s .NET foundation as well as competitive overlap with Aprimo’s own marketing automation software.) In the all-important area of integration, Assetlink and Teradata will both run on the same data structures and coordinate their internal processes, so they should work reasonably seamlessly. Assetlink still has its own user interface and workflow engine, though, so some separation will still be apparent. Teradata stressed that it will be investing to create a version of Assetlink that runs on the Teradata database and will sell that under the Teradata brand.

The Infor arrangement is a little more surprising because Infor also has its own marketing automation products (the old Epiphany system) and because Infor is more oriented to mid-size businesses than the giant retailers, telcos, and others served by Teradata. Perhaps the separate customer bases make the competitive issue less important. In any event, the Infor alliance is limited to Infor’s real time decision engine, currently known as CRM Epiphany Inbound Marketing, which was always Epiphany’s crown jewel. Like Assetlink, Infor gives Teradata a quick way to offer a capability (real time interaction management, including self-adjusting predictive models) that is increasingly requested by clients and offered by competitors. Although Epiphany is also built on J2EE, the initial integration (available today) will still be limited: the software will run on a separate server using SQL Server as its data store. A later release, due in the first quarter of next year, will still have a separate server but connect directly with the Teradata database. Even then, though, real-time interaction flows will be defined outside of Teradata Relationship Manager. Integration will be at the data level: Teradata will provide lists of customers are eligible for different offers and will be notified of interaction results. Teradata will be selling its own branded version of the Infor product too.

The SAS alliance is described as a “strategic partnership” in the firms' joint press release, which sounds jarring from two previous competitors. Basically, it involves running SAS analytic functions inside of the Teradata. This turns out to be part of a larger SAS initiative called “in-database processing” which seeks similar arrangements with other database vendors. Teradata is simply the first partner to be announced, so maybe the relationship isn’t so special after all. On the other hand, the companies’ joint roadmap includes deeper integration of selected SAS “solutions” with Teradata, including mapping of industry-specific SAS logical data models to corresponding Teradata structures. The companies will also create a joint technical “center of excellence” where specialists from both firms will help clients improve performance of SAS and Teradata products. We’ll see whether other database vendors work this closely with SAS. In the specific area of marketing automation, the two vendors will continue to compete head-to-head, at least for the time being.

This brings us back to Teradata Relationship Manager itself. As I already mentioned, v6 makes major changes at the deep technical level and in the user interface, but the 100+ changes in functionality are relatively minor. In other words, the functional structure of the product is the same.

This structure has always been different from other marketing automation systems. What sets Teradata apart is a very systematic approach to the process of customer communications: it’s not simply about matching offers to customers, but about managing all the components that contribute to those offers. For example, communication plans are built up from messages, which contain collateral, channels and response definitions, and the collateral itself may contain personalized components. Campaigns are created by attaching communication plans to segment plans, which are constructed from individual segments. All these elements in turn are subject to cross-campaign constraints on channel capacity, contacts per customer, customer channel preferences, and message priorities. In other words, everything is related to everything else in a very logical, precise fashion – just like a database design. Did I mention that Teradata is a database company?

This approach takes some practice before you understand how the parts are connected – again, like a sophisticated database. It can also make simple tasks seem unnecessarily complicated. But it rewards patient users with a system that handles complex tasks accurately and supports high volumes without collapsing. For example, managing customers across channels is very straightforward because all channels are structurally equivalent.

The functional capabilities of Relationship Manager are not so different from Teradata’s main competitors (SAS Marketing Automation and Unica). But those products have evolved incrementally, often through acquisition, and parts are still sold as separate components. It’s probably fair to say that they not as tightly or logically integrated as Teradata.

This very tight integration also has drawbacks, since any changes to the data structure need careful consideration. Teradata definitely has a tendency to fit new functions into existing structures, such as setting up different types of campaigns (outbound, multi-step, inbound) through a single interface. Sometimes that’s good; sometimes it’s just easier to do different things in different ways.

Teradata has also been something of a laggard at integrating statistical modeling into its system. Even what it calls “optimization” is rule-based rather than the constrained statistical optimization offered by other vendors. I’m actually rather fond of Teradata’s optimization approaches: its ability to allocate leads across channels based on sophisticated capacity rules (e.g., minimum and maximum volumes from different campaigns; automatically sending overflow from one channel to another; automatically reallocating leads based on current work load) has always impressed me and I believe remains unrivaled. But allowing marketers to build and deploy true predictive models is increasingly important and, unless I’ve missed something, is still not offered by Teradata.

This is why the new alliances are so intriguing. Assetlink adds a huge swath of capabilities that Teradata otherwise would have very slowly and painstakingly created by expanding its core data model. Infor and SAS both address the analytical weaknesses of the existing system, while Infor in particular adds another highly desired feature without waiting to build new structures in-house. All these changes suggest a welcome sense of urgency in responding quickly to customer needs. If this new attitude holds true, it seems unlikely that Teradata will accept another two year delay in the release of Relationship Manager version 7.

0 Neolane Offers a New Marketing Automation Option

Neolane, a Paris-based marketing automation software vendor, formally announced its entry to the U.S. market last week. I’ve been tracking Neolane for some time but chose not to write about it until they established a U.S. presence. So now the story can be told.

Neolane is important because it’s a full-scale competitor to Unica and the marketing automation suites of SAS and Teradata, which have pretty much had the high-end market to themselves in recent years. (You might add SmartFocus and Alterian to the list, but they sell mostly to service providers rather than end-users.) The company originally specialized in email marketing but has since broadened to incorporate other channels. Its email heritage still shows in strong content management and personalization capabilities. These are supplemented by powerful collaborative workflow, project management and marketing planning. Like many European products, Neolane was designed from the ground up to support trans-national deployments with specialized features such as multiple languages and currencies. The company, founded in 2001, now has over 100 installed clients. These include many very large firms such as Carrefour, DHL International and Virgin Megastores.

In evaluating enterprise marketing systems, I look at the five sets of capabilities: planning/budgeting; project management; content management; execution, and analysis. (Neolane itself offers a different set of five capabilities, although they are pretty similar.) Let’s go through these in turn.

Neolane does quite well in the first three areas, which all draw on its robust workflow management engine. This engine is part of Neolane’s core technology, which allows tight connections with the rest of the system. By contrast, many Neolane competitors have added these three functions at least in part through acquisition. This often results in less-than-perfect integration among the suite components.

Execution is a huge area, so we’ll break it into pieces. Neolane’s roots in email result in a strong email capability, of course. The company also claims particular strength in mobile (phone) marketing, although it’s not clear this involves more than supporting SMS and MMS output formats. Segmentation and selection features are adequate but not overly impressive: when it comes to really complex queries, Neolane users may find themselves relying on hand-coded SQL statements or graphical flow charts that can quickly become unmanageable. Although most of today’s major campaign management systems have deployed special grid-based interfaces to handle selections with hundreds or thousands of cells, I didn’t see that in Neolane.

On the other hand, Neolane might argue that its content personalization features reduce the need for building so many segments in the first place. Personalization works the same across all media: users embed selection rules within templates for email, Web pages and other messages. This is a fairly standard approach, but Neolane offers a particularly broad set of formats. It also provides different ways to build the rules, ranging from a simple scripting language to a point-and-click query builder. Neolane’s flow charts allow an additional level of personalized treatment, supporting sophisticated multi-step programs complete with branching logic. That part of the system seems quite impressive.

Apart from personalization, Neolane doesn’t seem to offer execution features for channels such as Web sites, call centers and sales automation. Nor, so far as I can tell, does it offer real-time interaction management—that is, gathering information about customer behavior during an interaction and determining an appropriate response. This is still a fairly specialized area and one where the major marketing automation vendors are just now delivering real products, after talking about it for years. This still puts them ahead of Neolane.

Execution also includes creation and management of the marketing database itself. Like most of its competitors, Neolane generally connects to a customer database built by an external system. (The exceptions would be enterprise suites like Oracle/Siebel and SAP, which manage the databases themselves. Yet even they tend to extract operational data into separate structures for marketing purposes.) Neolane does provide administrative tools for users to define database columns and tables, so it’s fairly easy to add new data if there’s no place else to store it. This would usually apply to administrative components such as budgets and planning data or to marketing-generated information such as campaign codes.

Analytics is the final function. Neolane does provide standard reporting. But it relies on connections to third-party software including SPSS and KXEN for more advanced analysis and predictive modeling. This is a fairly common approach and nothing to particularly complain about, although you do need to look closely to ensure that the integration is suitably seamless.

Over all, Neolane does provide a broad set of marketing functions, although it may not be quite as strong as its major competitors in some areas of execution and analytics. Still, it’s a viable new choice in a market that has offered few alternatives in recent years. So for companies considering a new system, it’s definitely worth a look.

0 What Makes QlikTech So Good?

To carry on a bit with yesterday’s topic—QlikTech fascinates me on two levels: first, because it is such a powerful technology, and second because it’s a real-time case study in how a superior technology penetrates an established market. The general topic of diffusion of innovation has always intrigued me, and it would be fun to map QlikView against the usual models (hype curve, chasm crossing, tipping point, etc.) in a future post. Perhaps I shall.

But I think it’s important to first explain exactly just what makes QlikView so good. General statements about speed and ease of development are discounted by most IT professionals because they’ve heard them all before. Benchmark tests, while slightly more concrete, are also suspect because they can be designed to favor whoever sponsors them. User case studies may be most convincing evidence, but resemble the testimonials for weight-loss programs: they are obviously selected by the vendor and may represent atypical cases. Plus, you don’t know what else was going on that contributed to the results.

QlikTech itself has recognized all this and adopted “seeing is believing” as their strategy: rather than try to convince people how good they are, they show them with Webinars, pre-built demonstrations, detailed tutorials, documentation, and, most important, a fully-functional trial version. What they barely do is discuss the technology itself.

This is an effective strategy with early adopters, who like to get their hands dirty and are seeking a “game changing” improvement in capabilities. But while it creates evangelists, it doesn’t give them anything beyond than own personal experience to testify to the product’s value. So most QlikTech users find themselves making exactly the sort of generic claims about speed and ease of use that are so easily discounted by those unfamiliar with the product. If the individual making the claims has personal credibility, or better still independent decision-making authority, this is good enough to sell the product. But if QlikTech is competing against other solutions that are better known and perhaps more compatible with existing staff skills, a single enthusiastic advocate may not win out—even though they happen to be backed by the truth.

What they need is a story: a convincing explanation of WHY QlikTech is better. Maybe this is only important for certain types of decision-makers—call them skeptics or analytical or rationalists or whatever. But this is a pretty common sort of person in IT departments. Some of them are almost physically uncomfortable with the raving enthusiasm that QlikView can produce.

So let me try to articulate exactly what makes QlikView so good. The underlying technology is what QlikTech calls an “associative” database, meaning data values are directly linked with related values, rather than using the traditional table-and-row organization of a relational database. (Yes, that’s pretty vague—as I say, the company doesn’t explain it in detail. Perhaps their U.S. Patent [number 6,236,986 B1, issued in 2001] would help but I haven’t looked. I don’t think QlikTech uses “associative” in the same way as Simon Williams of LazySoft, which is where Google and Wikipedia point go when you query the term.)

Whatever the technical details, the result of QlikTech’s method is that users can select any value of any data element and get a list of all other values on records associated with that element. So, to take a trivial example, selecting a date could give a list of products ordered on that date. You could do that in SQL too, but let’s say the date is on a header record while the product ID is in a detail record. You’d have to set up a join between the two—easy if you know SQL, but otherwise inaccessible. And if you had a longer trail of relations the SQL gets uglier: let’s say the order headers were linked to customer IDs which were linked to customer accounts which were linked to addresses, and you wanted to find products sold in New Jersey. That’s a whole lot of joining going on. Or if you wanted to go the other way: find people in New Jersey who bought a particular product. In QlikTech, you simply select the state or the product ID, and that’s that.

Why is this a big deal? After all, plenty of SQL-based tools can generate that query for non-technical users who don’t know SQL. But those tools have to be set up by somebody, who has to design the database tables, define the joins, and very likely specify which data elements are available and how they’re presented. That somebody is a skilled technician, or probably several technicians (data architects, database administrators, query builders, etc.). QlikTech needs none of that because it’s not generating SQL code to begin with. Instead, users just load the data and the system automatically (and immediately) makes it available. Where multiple tables are involved, the system automatically joins them on fields with matching names. So, okay, someobody does need to know enough to name the fields correctly – but that’s just all the skill required..

The advantages really become apparent when you think about the work needed to set up a serious business intelligence system. The real work in deploying a Cognos or BusinessObjects is defining the dimensions, measures, drill paths, and so on, so the system can generate SQL queries or the prebuilt cubes needed to avoid those queries. Even minor changes like adding a new dimension are a big deal. All that effort simply goes away in QlikTech. Basically, you load the raw data and start building reports, drawing graphs, or doing whatever you need to extract the information you want. This is why development time is cut so dramatically and why developers need so little training.

Of course, QlikView’s tools for building reports and charts are important, and they’re very easy to use as well (basically all point-and-click). But that’s just icing on the cake—they’re not really so different from similar tools that sit on top of SQL or multi-dimensional databases.

The other advantages cited by QlikTech users are speed and scalability. These are simpler to explain: the database sits in memory. The associative approach provides some help here, too, since it reducing storage requirements by removing redundant occurrences of each data value and by storing the data as binary codes. But the main reason QlikView is incredibly fast is that the data is held in memory. The scalability part comes in with 64 bit processors, which can address pretty much any amount of memory. It’s still necessary to stress that QlikView isn’t just putting SQL tables into memory: it’s storing the associative structures, with all their ease of use advantages. This is an important distinction between QlikTech and other in-memory systems.

I’ve skipped over other benefits of QlikView; it really is a very rich and well thought out system. Perhaps I’ll write about them some other time. The key point for now is that people need to understand QlikView using a fundamentally different database technology, one that hugely simplifies application development by making the normal database design tasks unnecessary. The fantastic claims for QlikTech only become plausible once you recognize that this difference is what makes them possible.

(disclaimer: although Client X Client is a QlikTech reseller, they have no responsibility for the contents of this blog.)

0 Accenture Paper Offers Simplified CRM Planning Approach

As I’ve pointed out many times before, consultants love their 2x2 matrices. Our friends at Accenture have once again illustrated the point with a paper “Surveying and Building Your CRM Future,” whose subtitle promises “a New CRM Software Decision-Making Model”.

Yep, the model is a matrix, dividing users into four categories based on data “density” (volume and update frequency) and business process uniqueness (need for customization). Each combination neatly maps to a different class of CRM software. Specifically:

- High density / low uniqueness is suited to enterprise packages like SAP and Oracle, since there’s a lot of highly integrated data but not too much customization required

- Low density / low uniqueness is suited to Software as a Service (SaaS) products like Salesforce.com since data and customization needs are minimal

- High density / high uniqueness is suited to “composite CRM” suites like Siebel (it’s not clear whether Accenture thinks any other products exist in this group)

- Low density / high uniqueness is suited to specialized “niche” vendors like marketing automation, pricing or analytics systems

In general these are reasonable dimensions, reasonable software classifications and a reasonable mapping of software to user needs. (Of course, some vendors might disagree.) Boundaries in the real world are not quite so distinct, but let's assume that Accenture has knowingly oversimplified for presentation purposes.

A couple of things still bother me. One is the notion that there’s something new here—the paper argues the “old” decision making model was simply based on comparing functions to business requirements, as if this were no longer necessary. Although it’s true that there is something like functional parity in the enterprise and, perhaps, “composite CRM" categories, there are still many significant differences among the SaaS and niche products. More important, business requirements different greatly among companies, and are far from encapsulated by two simple dimensions.

A cynic would point out that companies like Accenture pick one or two tools in each category and have no interest in considering alternatives that might be better suited for a particular client. But am I a cynic?

My other objection is that even though the paper mentions Service Oriented Architectures (SOA) several times, it doesn’t really come to grips with the implications. It relegates SOA to the high density / high latency quadrant: “Essentially, a composite CRM solution is a solution that enables organizations to move toward SOAs.” Then it argues that enterprise packages themselves are migrating in the composite CRM direction. This is rather confusing but seems to imply the two categories will merge.

I think what’s missing here is an acknowledgement that real companies will always have a mix of systems. No firm runs purely on SAP or Oracle enteprise software. Large firms have multiple CRM implementations. Thus there will always be a need to integrate different solutions, regardless of where a company falls on the density and uniqueness dimensions. SOA offers great promise as a way to accomplish this integration. This means it is as likely to break apart the enterprise packages as to become the glue that holds them together.

In short, this paper presents some potentially helpful insights. But there’s still no shortcut around the real work of requirements analysis, vendor evaluation and business planning.

0 Data Visualization Is Just One Part of a Dashboard System

Following Friday’s post on dashboard software, I want to emphasize that data visualization techniques are really just one element of those systems, and not necessarily the most important. Dashboard systems must gather data from source systems; transform and consolidate it; place it in structures suited for high-speed display and analysis; identify patterns, correlations and exceptions; and make it accessible to different users within the constraints of user interests, skills and authorizations. Although I haven’t researched the dashboard products in depth, even a cursory glance at their Web sites suggests they vary widely in these areas.

As with any kind of analytical system, most of the work and most of the value in dashboards will be in the data gathering. Poor visualization of good data can be overcome; good visualization of poor data is basically useless. So users should focus their attention on the underlying capabilities and not be distracted by display alone.