<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Baynote Blog &#187; Search</title>
	<atom:link href="http://www.baynote.com/blog/category/search/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.baynote.com/blog</link>
	<description>Intelligence Collected</description>
	<lastBuildDate>Thu, 04 Mar 2010 18:13:44 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Context Determines Relevance; Why 6sense works.</title>
		<link>http://www.baynote.com/blog/2010/02/09/context-determines-relevance-and-that%e2%80%99s-why-6sense-works/</link>
		<comments>http://www.baynote.com/blog/2010/02/09/context-determines-relevance-and-that%e2%80%99s-why-6sense-works/#comments</comments>
		<pubDate>Tue, 09 Feb 2010 19:11:26 +0000</pubDate>
		<dc:creator>Joe Vander Zanden</dc:creator>
				<category><![CDATA[Behavioral]]></category>
		<category><![CDATA[Search]]></category>
		<category><![CDATA[Social Computing]]></category>

		<guid isPermaLink="false">http://www.baynote.com/blog/?p=528</guid>
		<description><![CDATA[I recently finished reading this month’s Wired magazine and I came across an interesting 1-page advertisement by Monster.com promoting 6sense search technology.
6Sense developed out of a 2008 acquisition of search technology company Trovix.  According to a Monster press release, “6Sense patented semantic search technology utilizes intuitive, concept based searching, with a human-like understanding of the [...]]]></description>
			<content:encoded><![CDATA[<p>I recently finished reading this month’s Wired magazine and I came across an interesting 1-page advertisement by Monster.com promoting 6sense search technology.</p>
<p>6Sense developed out of a 2008 acquisition of search technology company Trovix.  According to a Monster press release, “6Sense patented semantic search technology utilizes intuitive, concept based searching, with a human-like understanding of the recruiting process and hiring needs.”<sup><a href="#_ftn1">[1]</a></sup></p>
<p>In case you’re not familiar, semantic search utilizes a concept called “disambiguation” to determine the probable meaning of sentences by building conceptual relationships between words, syllables, and related text.  However, the system cannot function in absence of what’s called the “conceptual basis” or primary logic required to begin building the conceptual relationships which govern the system.</p>
<p>But who or what determines the logic of the conceptual basis for a given semantic search system?</p>
<p>Intuitively, most people respond with an answer they find very simple, “The task at hand determines the logic of the conceptual basis”.  However, this simple and intuitive leap of the designer (the human mind) is an exceptionally difficult leap for the designed (computational system).</p>
<p>Unlike its designer, the semantic search system does not have the luxury of thinking outside of its own box.</p>
<p>Because the system relies on the wisdom of its designers to set the most appropriate logic, would it make sense to open up this process to a larger audience?</p>
<p>Given the presumably enormous amount of data and users, how many possible sub-contexts exist within the contextual premise of the initial system?  What is the probability that a conceptual basis created by a few experts will account for all of these possible combinations?  And most importantly, would differentiation at this level of granularity deliver measurable improvements to the user experience?</p>
<p>Well, I assume some level of diminishing marginal returns would arise; however, I’m confident this level of contextual granularity has probably not been reached in the case of 6Sense.</p>
<p>At the very least, I think this ad clearly communicates that successful companies are coming to realize the importance of their web channel, and therefore, the importance of relevant search and navigation.</p>
<p>And when it comes to relevance, we’re all beginning to realize that context is king.</p>
<p>I think Monster said it best. “The intelligence of the 6Sense technology contextually interprets the meaning behind words and concepts rather than relying on the narrow, literal meaning of keywords.”<sup><a href="#_ftn2">[2]</a></sup></p>
<p>I couldn’t agree more.</p>
<hr size="1" /><a name="#_ftnref1"></a> <a href="http://www.businesswire.com/portal/site/home/permalink/?ndmViewId=news_view&amp;newsId=20100201006672&amp;newsLang=en">http://www.businesswire.com/portal/site/home/permalink/?ndmViewId=news_view&amp;newsId=20100201006672&amp;newsLang=en</a></p>
<p><a name="#_ftnref2"></a> <a href="http://www.businesswire.com/portal/site/home/permalink/?ndmViewId=news_view&amp;newsId=20100201006672&amp;newsLang=en">http://www.businesswire.com/portal/site/home/permalink/?ndmViewId=news_view&amp;newsId=20100201006672&amp;newsLang=en</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.baynote.com/blog/2010/02/09/context-determines-relevance-and-that%e2%80%99s-why-6sense-works/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>My Search Sucks: Part 4 in a 4 part series</title>
		<link>http://www.baynote.com/blog/2009/11/09/my-search-sucks-part-4-in-a-4-part-series/</link>
		<comments>http://www.baynote.com/blog/2009/11/09/my-search-sucks-part-4-in-a-4-part-series/#comments</comments>
		<pubDate>Mon, 09 Nov 2009 22:52:39 +0000</pubDate>
		<dc:creator>scott</dc:creator>
				<category><![CDATA[Market Trends]]></category>
		<category><![CDATA[Search]]></category>
		<category><![CDATA[Site Search]]></category>
		<category><![CDATA[Social Sciences]]></category>
		<category><![CDATA[Social Search]]></category>

		<guid isPermaLink="false">http://www.baynote.com/blog/?p=504</guid>
		<description><![CDATA[The final installment in the 4-part series, “My Search Sucks,” discussing why search, well, sucks.
Over the past few weeks, we’ve explored how there are three key principles that explain why site search just doesn’t perform like we expect it to and what we can consider to help mitigate this.  So far, we’ve learned that:

The critical [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignleft" style="margin: 5px;" src="http://www.baynote.com/company/people/headshots/scott.jpg" alt="" width="100" height="133" />The final installment in the 4-part series, “My Search Sucks,” discussing why search, well, sucks.</p>
<p><em>Over the past few weeks, we’ve explored how there are three key principles that explain why site search just doesn’t perform like we expect it to and what we can consider to help mitigate this.  So far, we’ve learned that:</em></p>
<ol>
<li><em>The critical information we need to make search great isn’t in the document – it’s in the users’ heads.</em></li>
<li><em>Asking users to explicitly provie us information that would improve search, while a seemingly good approach, is inherently flawed.</em></li>
</ol>
<p><em>Today, we explore the third principle that shows that if we want to improve search, we need to focus on all of the things users are doing online.  What I mean here is that we need to look beyond search and at the entire site experience to truly understand what’s valuable, why it’s valuable, and in what context it’s found to be valuable. </em></p>
<p><strong>Reason #3:  Search does not exist in a vacuum.</strong></p>
<p>In order to improve search, we need to observe more than just search behavior.  Search and navigation have traditionally been seen as two separate paradigms: separate interfaces and separate systems driving them.  But in reality what’s happening?  A user is coming to your site and expressing an interest or intent through their actions.  They might have first expressed that intent through a Yahoo! or Google search that brought them to your site.  They might then express it in the pages they visit and engage with, the navigation they use, the links they click, and maybe the site searches they perform.  This expression of interest may span multiple searches and clicks.  And, finding documents that hold true value for that interest and intent may also take multiple steps.</p>
<p>Let’s think back to the “Insight/Incite” example once more.  Had we only looked at what search results users clicked on, the problem might never have been solved.  Why?  Because the valuable content was never in the results &#8211; it wasn’t there to be clicked on in the first place!  To learn what users really meant by “insight”, we had to watch their subsequent navigation, paying particular attention to the patterns of behavior that indicated engagement or that they had discovered content that was of value &#8211; even if it happened several steps after the initial search.  Observing search behavior alone is not enough!</p>
<p>What about users who don’t search at all?  What can we learn from them?  Users are actually giving us continual clues to their intent and interest with every link they click and every category they choose.  The documents that users engage with and the order in which they engage also tell us not only about relationships between documents, but intent.  If we take this valuable, implicit insight into account, then we really begin to see how this insight could be used to fix search.</p>
<p>What’s really remarkable is that once we take a step back and think of the entire online experience as a single unified expression of intent and value, we can do a lot more than fix search.  We can start to make recommendations and optimize the user experience with every interaction they make with your site; from the moment they arrive, every step they take through the site, as well as every search they perform. The true goal is to understand the user’s intent and then automatically surface documents that other like-minded peers have found valuable in that same context.  That’s the true wisdom of the crowd, and what Baynote’s Collective Intelligence Platform (CIP) is all about.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.baynote.com/blog/2009/11/09/my-search-sucks-part-4-in-a-4-part-series/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>My Search Sucks: Part 3 in a 4 part series</title>
		<link>http://www.baynote.com/blog/2009/10/30/my-search-sucks-part-3-in-a-4-part-series/</link>
		<comments>http://www.baynote.com/blog/2009/10/30/my-search-sucks-part-3-in-a-4-part-series/#comments</comments>
		<pubDate>Fri, 30 Oct 2009 16:36:24 +0000</pubDate>
		<dc:creator>scott</dc:creator>
				<category><![CDATA[Market Trends]]></category>
		<category><![CDATA[Search]]></category>
		<category><![CDATA[Site Search]]></category>
		<category><![CDATA[Social Sciences]]></category>
		<category><![CDATA[Social Search]]></category>

		<guid isPermaLink="false">http://www.baynote.com/blog/?p=455</guid>
		<description><![CDATA[There are three key principles that explain why site search just doesn’t perform like we expect it to. Over the next few weeks, I’ll dive deeper into each issue surrounding traditional search and offer my insights and experiences to help you understand why your search sucks, and how you can improve it.]]></description>
			<content:encoded><![CDATA[<p><script type="text/javascript"></script><img class="alignleft" src="http://www.baynote.com/company/people/headshots/scott.jpg" alt="" width="100" height="133" style="margin:5px;"/>Part 3 in the 4-part series, “My Search Sucks,” discussing why search, well, sucks.</p>
<p><em>There are three key principles that explain why site search just doesn’t perform like we expect it to. Over the next few weeks, I’ll dive deeper into each issue surrounding traditional search and offer my insights and experiences to help you understand why your search sucks, and how you can improve it.</em></p>
<p><strong>Reason #2:  Actions speak louder than words.</strong></p>
<p>Okay, so we’ve figured out that the critical information is not in the document.  Where is it?  Well, it’s in the users’ heads of course.  Let’s look at an example.  If we look at a work by Shakespeare—or any great work of literature—the meaning cannot be identified simply by looking at the words within it.  It’s synthesized in the reader’s mind, and different readers may derive different meanings based on their own unique makeup and experiences.  The same applies to any document.  We must look beyond the words within the document to truly understand the value.  The key question to ask is this: when and why is this document valuable to users?  Only the users themselves know the answer.</p>
<p>Now that’s all well and good, but how do we extract that knowledge from the users?  We could ask them directly, but while that might seem like a good strategy, it’s actually not.  Asking users to explicitly rank, rate, or tag documents is doomed to failure.  The core problem is one of participation.  Think back to how many times you’ve provided feedback on the web.  Most of us never have; others may have on occasion, but almost certainly not on every page visit or search result.  This participation problem leads to a few key challenges:</p>
<p><strong>A. Low coverage.</strong> A small subset of the population rates content, and when they do, the ratings only tend to  cover the most popular content.  Where does that leave the majority of our content?—the long tail.  Unranked and therefore undiscovered.  And with search, it’s not just about knowing that a document has value; it’s about whether it’s valuable for that specific search topic and that user.</p>
<p>Let&#8217;s take a deeper look at this.  Let’s say we have a bunch of ratings on a particular camera.  Sounds great, right?  Well, not really.  People like or dislike a camera for a variety of reasons.  Someone looking for a &#8220;lightweight camera&#8221; might think it stinks, while someone looking for a &#8220;cheap camera&#8221; might love it.  You can’t ignore the context of what a person is looking for, and getting explicit coverage across every topic of interest is even harder than just getting an overall rating.</p>
<p>And, when you factor in staleness of content &mdash; be it the article or the rating &mdash; then even the ratings you do have become less meaningful.  Add to that the mountains of content that are being created every day, and the problem really gets out of hand.  There’s just no way to keep up with it if we’re relying on people to go out of their way to explicitly rank, rate, and tag content.</p>
<p><strong>B. Biased.</strong> In general, the people who do participate in explicitly rating something online represent a very small subset of the population.  That means that, even for those documents and topics that do have coverage, there’s no guarantee that the knowledge imparted by users even represents the majority opinion.  In fact, it almost always represents fringe opinions that are either extremely positive or negative because those are the people motivated to be heard.</p>
<p>To read more about the bias inherent in explicit methods of capturing community wisdom, check out my <a href="http://www.baynote.com/resources/white-papers/deadly-biases/register.php">“7 Deadly Biases” whitepaper</a>.</p>
<p><strong>C. Inaccurate/Incomplete. </strong> Even when an individual decides to provide some form of explicit feedback, it often is not fully representative of even their own experience.  Let’s go back to the insight/incite example from my previous post.  Let’s say that a user decided to tag the Incite product page that was so useful.  What tag do you think they would use?  Probably “incite” or “incite phone,” right?  They would almost certainly not tag it with “insight” once they realized their mistake; but this is actually the tag that would be of most value to the community!  It might surprise you to know that social scientists are generally distrustful of people’s own accounts of their feelings and behavior!  Meta-cognition and emotional self-awareness are far more complex, and less intuitive, than people think.</p>
<p>So, if asking people to tell us what documents are valuable and why they’re of value doesn’t work, then what is the right way?  The key is to observe what people do, not what they say.  It’s both more accurate and more comprehensive.  The wisdom we are looking to tap is present in every single search&#8211;whether the searchers were successful or not.  By watching what people do, we can understand which documents are valuable and when.</p>
<p>But we need to be careful here too, because watching which search results users click on is not enough.  Clicks are a very weak indicator: just because people clicked on a result does not mean it’s valuable.  Perhaps the title was intriguing, confusing, or even misleading.  It is critical to follow the user all the way from query to success or ultimate failure—even if several steps later—and not get distracted by what they click on.  At Baynote, we track 24 different behavioral heuristics to ensure that we accurately capture where users are engaging given a particular context and intent.  And it’s not just about search; it’s about the entire online experience.  More on this in the next post.</p>
<p>Next week: Part 4 in the 4-part series, My Search Sucks! where we’ll explore how search does not exist in a vacuum.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.baynote.com/blog/2009/10/30/my-search-sucks-part-3-in-a-4-part-series/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>My Search Sucks: Part 2 in a 4 part series</title>
		<link>http://www.baynote.com/blog/2009/10/23/my-search-sucks-part-2-in-a-4-part-series/</link>
		<comments>http://www.baynote.com/blog/2009/10/23/my-search-sucks-part-2-in-a-4-part-series/#comments</comments>
		<pubDate>Fri, 23 Oct 2009 14:00:31 +0000</pubDate>
		<dc:creator>scott</dc:creator>
				<category><![CDATA[Market Trends]]></category>
		<category><![CDATA[Search]]></category>
		<category><![CDATA[Site Search]]></category>

		<guid isPermaLink="false">http://www.baynote.com/blog/?p=443</guid>
		<description><![CDATA[There are three key principles that explain why site search just doesn’t perform like we expect it to. Over the next few weeks, I’ll dive deeper into each issue surrounding traditional search and offer my insights and experiences to help you understand why your search sucks, and how you can improve it.]]></description>
			<content:encoded><![CDATA[<p><strong><img class="alignleft" title="Scott Brave" src="http://www.baynote.com/company/people/headshots/scott.jpg" alt="" width="100" height="133" style="margin:5px;" />My Search Sucks! Part 2 </strong></p>
<p>Part 2 in the 4-part series, “My Search Sucks,” discussing why search, well, sucks.</p>
<p><em>There are three key principles that explain why site search just doesn’t perform like we expect it to. Over the next few weeks, I’ll dive deeper into each issue surrounding traditional search and offer my insights and experiences to help you understand why your search sucks, and how you can improve it.</em></p>
<p><strong>Reason #1:  The critical information is not in the document.</strong></p>
<p>All full-text search technologies basically work the same way: they look for a match between the words in a user’s query and the words in the text of the documents searched.  That said, there are lots of fancy layers that can be added from simple stemming to complex natural language processing (NLP), but the fundamental assumption is that the engine can figure out which documents best meet a user’s needs by looking inside the document.</p>
<p>While this is a start, it’s just not enough. The critical information isn’t in the document; it’s in someone’s head.  But whose head is it in? Let’s look at some examples.</p>
<p>A favorite example comes to mind involving one of our customers, a large online appliance retailer.  Users were coming to their website looking for a “stove” over and over again, and the search results had “stove-top safe” kettles and pots, but no stoves.  Turns out the reason for this was that this retailer’s website was using the manufacturer terminology, “cooktops” and “ranges.”  The word “stove” was nowhere to be found.  The community was using a different vocabulary than the site.</p>
<p>Sounds like a simple fix, right?  All you need to do is to create a synonym to tell the search engine that a “stove” is the same thing as a “range.”  And sure, once you’ve found and addressed the discrepancy, customers searching for “stoves” will find the “ranges” they’re really looking for.  But what about all of those long-tail terms and content—and what about when things change?</p>
<p>Sam Mefford, an expert in the deployment of enterprise search technologies, commented on last week’s blog.  In his search practice, he sees this challenge surface on a regular basis and provided an example from one of his clients.  The company re-branded one of its products, and made the appropriate changes in its marketing materials and documentation.   Afterwards, field agents and customers could no longer find the products and information they needed, because they continued to search using the old name.  This problem took months to discover.</p>
<p>Another great example is from a customer that’s a well-known wireless provider.  They launched a new LG phone called the “Incite.”  Suddenly, one of the most popular search queries on their site became “insight.”  The search results included lots of business-type documents about how to achieve great “insight” into your business operations, but nothing that matched what users wanted – information on this exciting new phone. Sure, searching for “insight” while the product is called “incite” was technically the user’s mistake, but does that matter when you’re losing opportunities?</p>
<p>Let’s say the words do exist in the document.  It&#8217;s often not enough.  There may be 1000s of documents that contain the search terms, but which documents are the best?  A traditional search engine will assume that the one with the most occurrences of the keywords is the most valuable, but this is very often not the case.  Obviously, the technology is more sophisticated than this, but the fundamental basis is along these lines.  The most useful document may only have one instance of the keyword and therefore may be buried on page 10 of the results.  So, how do you get the most useful document to the top of the search results?</p>
<p>Manual tuning is the traditional “solution” to all of these site search issues, but as we discussed earlier, it’s nearly impossible to catch all discrepancies and adapt rapidly—not to mention the time and effort involved.  I’ve even mentioned the spirit of the solution: it’s fundamentally a recognition that the needed information is not in the document, it’s in someone’s head.  But whose head is it really in?</p>
<p>Many companies have experts that manually tune and tweak search.  But that’s a labor-intensive way to temporarily solve the problem and certainly doesn’t guarantee that the expert’s view on what’s right matches with users’.  Why take that chance?  Better to go straight to the source of the information: the user!</p>
<p>Next week: Part 3 in the 4-part series, My Search Sucks! where we’ll explore how actions speak louder than words.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.baynote.com/blog/2009/10/23/my-search-sucks-part-2-in-a-4-part-series/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>My Search Sucks!</title>
		<link>http://www.baynote.com/blog/2009/10/13/my-search-sucks/</link>
		<comments>http://www.baynote.com/blog/2009/10/13/my-search-sucks/#comments</comments>
		<pubDate>Tue, 13 Oct 2009 16:13:58 +0000</pubDate>
		<dc:creator>scott</dc:creator>
				<category><![CDATA[Behavioral]]></category>
		<category><![CDATA[Contextual]]></category>
		<category><![CDATA[Search]]></category>
		<category><![CDATA[Social Search]]></category>

		<guid isPermaLink="false">http://www.baynote.com/blog/?p=437</guid>
		<description><![CDATA["My Search Sucks!" &#8212; we hear this from prospects more than any other complaint.  Coming from consumer search experiences on the web with the likes of Google, Yahoo, and new entrant Bing, these frustrated employees wonder why they can't get better search results on their company's website and intranet.]]></description>
			<content:encoded><![CDATA[<p>&#8220;My Search Sucks!&#8221; &mdash; we hear this from prospects more than any other complaint.  Coming from consumer search experiences on the web with the likes of Google, Yahoo, and new entrant Bing, these frustrated employees wonder why they can&#8217;t get better search results on their company&#8217;s website and intranet.  Fair question.  Turns out there are a few key principles that explain why site search often sucks and how to fix it:</p>
<h3>1. The critical information is not in the document</h3>
<p>While documents &mdash; whether webpages, pdfs, or Word docs &mdash; seem like the best place to discover a match to a user&#8217;s search term, they&#8217;re not.  Processing documents is a good start, but the words within a document do not necessarily match the way a user understands the topic and phrases their question.  And even if the search term is in there, it doesn&#8217;t mean that particular document is useful.  The critical information is in the heads of users, not the documents.  The key is to understand how, when, and why people use each document.  At Baynote, we call this UseRank.
</p>
<h3>2. Actions speak louder than words</h3>
<p>
To get information from users you might think the best approach is to ask them.  Seems simple and straightforward, right?  Wrong.  Turns out that there are a number of problems with explicit means of collecting information stemming from who participates, when, and why.  As social science has taught us all along, if you really want to understand people, watch what they do, not what they say.
</p>
<h3>3. Search does not exist in a vacuum</h3>
<p>Any time someone comes to your website, they are looking for something and they give you clues to what that is through both their search and navigation behaviors &mdash; and not just what they ask for and where they go, but what they do when they get there.  Often they got to your site through an external link such as a search on the web &mdash; that’s your first clue.  Although the goal might be to solve the site search problem, observing search behavior alone is not enough.
</p>
<p>I’ll expand on each of these in more detail in upcoming posts.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.baynote.com/blog/2009/10/13/my-search-sucks/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Enterprise search is not like internet search</title>
		<link>http://www.baynote.com/blog/2009/04/21/enterprise-search-is-not-internet-search/</link>
		<comments>http://www.baynote.com/blog/2009/04/21/enterprise-search-is-not-internet-search/#comments</comments>
		<pubDate>Wed, 22 Apr 2009 06:09:07 +0000</pubDate>
		<dc:creator>Warren</dc:creator>
				<category><![CDATA[Search]]></category>
		<category><![CDATA[Site Search]]></category>
		<category><![CDATA[Social Search]]></category>

		<guid isPermaLink="false">http://www.baynote.com/blog/?p=381</guid>
		<description><![CDATA[Earlier today I came across a thought provoking blog post that compares internet search problems to those of enterprise search over at SharePoint Blogs.  The biggest point that I took away from this post is that enterprise searchers on intranets often know exactly what they are looking for. In fact, they often know that [...]]]></description>
			<content:encoded><![CDATA[<p>Earlier today I came across a thought provoking blog <a href="http://www.sharepointblogs.com/jennyeverett/archive/2009/04/16/intranet-search-vs-website-search-vs-search-engine-search.aspx">post</a> that compares internet search problems to those of enterprise search over at SharePoint Blogs.  The biggest point that I took away from this post is that enterprise searchers on intranets often know exactly what they are looking for. In fact, they often know that what they are looking for definitely exists.  While it may seem subtle, this is an extremely important distinction from internet searchers who give up on a website if they are not immediately satisfied with results.</p>
<p>Our <a href="http://www.baynote.com/social-search/content/">Social Search</a> solution works by observing the successful search and navigation paths of users in order to guide successive site visitors to their goals.  Relying entirely on keyword search solutions is insufficient.  An effective enterprise search solution will be able to detect the different search contexts that exist on an intranet.  While this number is large, it is certainly finite.  By employing a solution that can learn these contexts and detect them when clues are present, findability on the intranet can be greatly increased.</p>
<p><em>Check out our <a href="http://www.baynote.com/resources/white-papers/social-search/register.php">white paper on social search</a> on exactly how Baynote can replace or supercharge an existing search solution with inadequate results.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.baynote.com/blog/2009/04/21/enterprise-search-is-not-internet-search/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Social Search Heating up Site Search in the New Year</title>
		<link>http://www.baynote.com/blog/2009/01/08/social-search-heating-up-site-search-in-the-new-year/</link>
		<comments>http://www.baynote.com/blog/2009/01/08/social-search-heating-up-site-search-in-the-new-year/#comments</comments>
		<pubDate>Thu, 08 Jan 2009 10:36:02 +0000</pubDate>
		<dc:creator>Warren</dc:creator>
				<category><![CDATA[Market Trends]]></category>
		<category><![CDATA[Search]]></category>
		<category><![CDATA[Site Search]]></category>
		<category><![CDATA[Social Search]]></category>

		<guid isPermaLink="false">http://www.baynote.com/blog/?p=289</guid>
		<description><![CDATA[I read a great primer on Social Search yesterday on the Rise to the Top Blog.  While Social Search is often poised as a replacement of keyword based search, we prefer to take a less cannibalistic approach and position Baynote Social Search as a compliment to traditional keyword search as proven with our recent [...]]]></description>
			<content:encoded><![CDATA[<p>I read a great <a href="http://risetothetop.techwyse.com/online-innovation/coming-to-grips-with-social-search/">primer on Social Search</a> yesterday on the Rise to the Top Blog.  While Social Search is often poised as a replacement of keyword based search, we prefer to take a less cannibalistic approach and position Baynote Social Search as a compliment to traditional keyword search as proven with our <a href="http://www.baynote.com/company/news/news.php?newsID=76">recent partnership with Google Search Appliance.</a>.</p>
<p>The blog post correctly identifies two types of Social Search:<br />
1. <em>Explicit-based</em> &#8211; Solutions where search results are powered by &#8220;simple [influencers like] shared bookmarks or tagging of content with descriptive labels.&#8221;<br />
2.<em> Implicit-based</em> &#8211; A solution that is powered by the uncovering social intelligence with complex computer algorithms.</p>
<p><a href="http://www.baynote.com/social-search/content/">Baynote Social Search</a> is closely aligned to implicit-based Social Search description given, as we do not utilize explicit information like bookmarking or tagging to derive our search results.  And according to the post this turns out to be the differentiator that immunizes us from the pitfalls of social search mentioned:</p>
<blockquote><p>
<strong>Social Search Cons</strong></p>
<p>Despite the obvious benefits social search has some glaring defects too. As said earlier social search hinges heavily on human judgment. But the web today is growing at a pace which humans simply cannot match and this means there will be a lot of content that would remain unnoticed and hidden from the user. Also the tagging method through which the search works is not the ideal way of organizing web data. There is also the risk of spam because users have the freedom to directly add results to a social search engine which can be misused.  We all know the way some SEO’s behave!</p></blockquote>
<p>However, Baynote Social Search does offer the same benefits that are mentioned by the author:</p>
<blockquote><p>
Social Search Pros</p>
<p>Social search engines have potential benefits deriving from the human input qualities of social search. Some of these include:</p>
<ul>
<li>Relatively free from link spam as there is less reliance on link structure of webpages
</li>
<li>More relevant search results as each result has been selected by users
</li>
<li>The user gets more current results
</li>
<li>The user gets his precise perspective reflected in the results
</li>
<li>The human judgment that social search uses is more accurate than computer’s ability to analyze a webpage</li>
</ul>
</blockquote>
<p>It was great to see Baynote standing out as the only company mentioned that is both bringing social search to websites rather than just a general web search engine and avoiding the negative pitfalls of explicit-based social search.</p>
<p><strong>For any additional information on the Baynote Social Search Methodologies, check out our <a href="http://www.baynote.com/resources/white-papers/social-search/register.php">whitepaper &#8220;In Search for the Human Element.&#8221;</a></strong></p>
]]></content:encoded>
			<wfw:commentRss>http://www.baynote.com/blog/2009/01/08/social-search-heating-up-site-search-in-the-new-year/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mob Search &#8211; Tune into the Crowd</title>
		<link>http://www.baynote.com/blog/2008/11/18/mob-search-tune-into-the-crowd/</link>
		<comments>http://www.baynote.com/blog/2008/11/18/mob-search-tune-into-the-crowd/#comments</comments>
		<pubDate>Tue, 18 Nov 2008 22:10:08 +0000</pubDate>
		<dc:creator>kathleen</dc:creator>
				<category><![CDATA[Search]]></category>
		<category><![CDATA[Juniper Networks]]></category>
		<category><![CDATA[Site Search]]></category>

		<guid isPermaLink="false">http://www.baynote.com/blog/?p=177</guid>
		<description><![CDATA[Our latest 90 second  webcast &#8220;trailer&#8221; as created by our Creative Czar Brian, is now available.  This is about the quickest way to &#8220;get&#8221; what Baynote means by Social Search and why it&#8217;s different.  And if you don&#8217;t believe us, listen to our customer Bill Skeet from Juniper Networks tell it like it is from [...]]]></description>
			<content:encoded><![CDATA[<p>Our latest 90 second  webcast &#8220;trailer&#8221; as created by our Creative Czar Brian, is now available.  This is about the quickest way to &#8220;get&#8221; what Baynote means by Social Search and why it&#8217;s different.  And if you don&#8217;t believe us, listen to our customer Bill Skeet from <a href="http://www.juniper.net">Juniper Networks</a> tell it like it is from his perspective.</p>
<p><object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="425" height="344" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param name="allowFullScreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="src" value="http://www.youtube.com/v/7iJgIws0FIs&amp;hl=en&amp;fs=1" /><embed type="application/x-shockwave-flash" width="425" height="344" src="http://www.youtube.com/v/7iJgIws0FIs&amp;hl=en&amp;fs=1" allowscriptaccess="always" allowfullscreen="true"></embed></object></p>
<p>One of the interesting things that happened at Juniper after overlaying Baynote on top of their existing search engine  (you all know this right, no rip and replace, we&#8217;re SAAS, we&#8217;re very nice that way) is that the mix of search results shifted significantly in two main ways:</p>
<p>First of all, the Mob of Juniper site users found documents relevant to queries that the search engine couldn&#8217;t.  Humans just get things, make connections that machines can&#8217;t.  Period.</p>
<p>Second, the items that percolated to the top were more often the more technical documents that the majority of the site viewers were interested in, not necessarily all the various product pages that marketing felt they needed to create.  The Mob, of course, knew what it needed and put these items on top.  Simple.  <!--[if gte mso 9]><xml> <w:WordDocument> <w:View>Normal</w:View> <w:Zoom>0</w:Zoom> <w:TrackMoves /> <w:TrackFormatting /> <w:PunctuationKerning /> <w:ValidateAgainstSchemas /> <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid> <w:IgnoreMixedContent>false</w:IgnoreMixedContent> <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText> <w:DoNotPromoteQF /> <w:LidThemeOther>EN-US</w:LidThemeOther> <w:LidThemeAsian>X-NONE</w:LidThemeAsian> <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript> <w:Compatibility> <w:BreakWrappedTables /> <w:SnapToGridInCell /> <w:WrapTextWithPunct /> <w:UseAsianBreakRules /> <w:DontGrowAutofit /> <w:SplitPgBreakAndParaMark /> <w:DontVertAlignCellWithSp /> <w:DontBreakConstrainedForcedTables /> <w:DontVertAlignInTxbx /> <w:Word11KerningPairs /> <w:CachedColBalance /> </w:Compatibility> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> <m:mathPr> <m:mathFont m:val="Cambria Math" /> <m:brkBin m:val="before" /> <m:brkBinSub m:val="&#45;-" /> <m:smallFrac m:val="off" /> <m:dispDef /> <m:lMargin m:val="0" /> <m:rMargin m:val="0" /> <m:defJc m:val="centerGroup" /> <m:wrapIndent m:val="1440" /> <m:intLim m:val="subSup" /> <m:naryLim m:val="undOvr" /> </m:mathPr></w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"   DefSemiHidden="true" DefQFormat="false" DefPriority="99"   LatentStyleCount="267"> <w:LsdException Locked="false" Priority="0" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Normal" /> <w:LsdException Locked="false" Priority="9" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="heading 1" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9" /> <w:LsdException Locked="false" Priority="39" Name="toc 1" /> <w:LsdException Locked="false" Priority="39" Name="toc 2" /> <w:LsdException Locked="false" Priority="39" Name="toc 3" /> <w:LsdException Locked="false" Priority="39" Name="toc 4" /> <w:LsdException Locked="false" Priority="39" Name="toc 5" /> <w:LsdException Locked="false" Priority="39" Name="toc 6" /> <w:LsdException Locked="false" Priority="39" Name="toc 7" /> <w:LsdException Locked="false" Priority="39" Name="toc 8" /> <w:LsdException Locked="false" Priority="39" Name="toc 9" /> <w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption" /> <w:LsdException Locked="false" Priority="10" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Title" /> <w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font" /> <w:LsdException Locked="false" Priority="11" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtitle" /> <w:LsdException Locked="false" Priority="22" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Strong" /> <w:LsdException Locked="false" Priority="20" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Emphasis" /> <w:LsdException Locked="false" Priority="59" SemiHidden="false"    UnhideWhenUsed="false" Name="Table Grid" /> <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text" /> <w:LsdException Locked="false" Priority="1" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="No Spacing" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 1" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 1" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 1" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 1" /> <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision" /> <w:LsdException Locked="false" Priority="34" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="List Paragraph" /> <w:LsdException Locked="false" Priority="29" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Quote" /> <w:LsdException Locked="false" Priority="30" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Quote" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 1" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 1" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 1" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 1" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 1" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 2" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 2" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 2" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 2" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 2" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 2" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 2" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 2" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 2" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 3" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 3" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 3" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 3" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 3" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 3" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 3" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 3" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 3" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 4" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 4" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 4" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 4" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 4" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 4" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 4" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 4" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 4" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 5" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 5" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 5" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 5" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 5" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 5" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 5" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 5" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 5" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 6" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 6" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 6" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 6" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 6" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 6" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 6" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 6" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 6" /> <w:LsdException Locked="false" Priority="19" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis" /> <w:LsdException Locked="false" Priority="21" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis" /> <w:LsdException Locked="false" Priority="31" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference" /> <w:LsdException Locked="false" Priority="32" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Reference" /> <w:LsdException Locked="false" Priority="33" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Book Title" /> <w:LsdException Locked="false" Priority="37" Name="Bibliography" /> <w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading" /> </w:LatentStyles> </xml><![endif]--> <!--[if gte mso 10]> <mce:style><!<br />
/* Style Definitions */<br />
table.MsoNormalTable<br />
{mso-style-name:"Table Normal";<br />
mso-tstyle-rowband-size:0;<br />
mso-tstyle-colband-size:0;<br />
mso-style-noshow:yes;<br />
mso-style-priority:99;<br />
mso-style-qformat:yes;<br />
mso-style-parent:"";<br />
mso-padding-alt:0in 5.4pt 0in 5.4pt;<br />
mso-para-margin:0in;<br />
mso-para-margin-bottom:.0001pt;<br />
mso-pagination:widow-orphan;<br />
font-size:11.0pt;<br />
font-family:"Calibri","sans-serif";<br />
mso-ascii-font-family:Calibri;<br />
mso-ascii-theme-font:minor-latin;<br />
mso-fareast-font-family:"Times New Roman";<br />
mso-fareast-theme-font:minor-fareast;<br />
mso-hansi-font-family:Calibri;<br />
mso-hansi-theme-font:minor-latin;}<br />
--> <!--[endif]-->Voilà.</p>
<p>So sometimes what the Mob, via Baynote, delivers is more results (i.e. stuff an algorithm can&#8217;t find like pdfs) or sometimes fewer results (just the stuff people want) either way, the Mob delivers better results.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.baynote.com/blog/2008/11/18/mob-search-tune-into-the-crowd/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mob Marketing &#8211; Unlock the expert bottleneck</title>
		<link>http://www.baynote.com/blog/2008/10/08/mob-marketing-unlock-the-expert-bottleneck/</link>
		<comments>http://www.baynote.com/blog/2008/10/08/mob-marketing-unlock-the-expert-bottleneck/#comments</comments>
		<pubDate>Wed, 08 Oct 2008 21:27:43 +0000</pubDate>
		<dc:creator>kathleen</dc:creator>
				<category><![CDATA[Market Trends]]></category>
		<category><![CDATA[Marketing]]></category>
		<category><![CDATA[Search]]></category>
		<category><![CDATA[forrester]]></category>
		<category><![CDATA[mob marketing]]></category>

		<guid isPermaLink="false">http://www.baynote.com/blog/?p=126</guid>
		<description><![CDATA[Hats off to Brian for producing this cool trailer to our webinar Mob Marketing:  Manual Website Optimization FUGETABOUTIT!  If you&#8217;ve only got a minute, you&#8217;ll get the gist of the whole thesis of the webinar.
  
As we worked with Suresh Vittal of Forrester Research to put together the content, Jack, Suresh and I frequently hearkened [...]]]></description>
			<content:encoded><![CDATA[<p>Hats off to Brian for producing this cool trailer to our webinar Mob Marketing:  Manual Website Optimization FUGETABOUTIT!  If you&#8217;ve only got a minute, you&#8217;ll get the gist of the whole thesis of the webinar.</p>
<p> <object width="425" height="350"><param name="movie" value="http://www.youtube.com/v/pOetiCRPJrQ"></param> <embed src="http://www.youtube.com/v/pOetiCRPJrQ" type="application/x-shockwave-flash" width="425" height="350"></embed></object></p>
<p>As we worked with Suresh Vittal of Forrester Research to put together the content, Jack, Suresh and I frequently hearkened back to a similar &#8220;sea change&#8221; that happened in the early days of content management.  In 1998, we spent much of our time talking to journalist, analysts and customers about unlocking the so-called webmaster bottleneck.  If you could only put web publishing in the hands of the internal content experts, then you could eliminate this delay created by having a &#8220;webmaster.&#8221;  By 1999 when we went public, everyone got it.</p>
<p>But unlocking this bottleneck created a new bottleneck &#8211; people finding the information they needed.  Now we suffered from content overload &#8212; because organizations kept producing more and more content and there was no efficient means to make sure that the content you showed was the content people needed or the products people wanted.  Organizations tried to fix it by investing in complex search engines or analytics or profile-based personalization.  None of this fixed the fundamental problem.</p>
<p>It&#8217;s time to get rid of the expert bottleneck.  In this economy, the timing is perfect.  There are some task that will always be manual but there are others that can and should be automated.   Automate for a better user experience.  Automate for efficiency. Turn what people see on your site over to the Mob.  It might make you feel a little uncomfortble now, but so was the idea of eliminating the webmaster bottleneck in 1999.  I say FUGETABOUTIT.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.baynote.com/blog/2008/10/08/mob-marketing-unlock-the-expert-bottleneck/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Demographic behavioral targeting not impressing at Online Marketing World</title>
		<link>http://www.baynote.com/blog/2008/10/03/demographic-behavioral-targeting-not-impressing-at-online-marketing-world/</link>
		<comments>http://www.baynote.com/blog/2008/10/03/demographic-behavioral-targeting-not-impressing-at-online-marketing-world/#comments</comments>
		<pubDate>Fri, 03 Oct 2008 20:58:54 +0000</pubDate>
		<dc:creator>Warren</dc:creator>
				<category><![CDATA[Behavioral]]></category>
		<category><![CDATA[Contextual]]></category>
		<category><![CDATA[Market Trends]]></category>
		<category><![CDATA[Marketing]]></category>
		<category><![CDATA[Search]]></category>

		<guid isPermaLink="false">http://www.baynote.com/blog/?p=118</guid>
		<description><![CDATA[At Online Marketing World, we&#8217;ve been speaking to many potential clients and partners and one thing that has really resonated is the move from demographic based behavioral targeting to contextual targeting.  At Baynote, we&#8217;ve been championing contextual targeting for product and content recommendations over the last 3 years.  Initially, this wasn&#8217;t a popular [...]]]></description>
			<content:encoded><![CDATA[<p>At Online Marketing World, we&#8217;ve been speaking to many potential clients and partners and one thing that has really resonated is the move from demographic based behavioral targeting to contextual targeting.  At <a href="http://www.baynote.com">Baynote</a>, we&#8217;ve been championing contextual targeting for product and content recommendations over the last 3 years.  Initially, this wasn&#8217;t a popular position, likely due to a lack of technologies on the market being able to distinguish one context of a user from another.  However, over the last year, the success of contextual targeting and the failure of demographic based targeting has ushered in a new era, one where <strong>Context is King</strong>.</p>
<p>Yesterday, one of the conference attendees that visited our booth created a <a href="http://dvs-unbranded.blogspot.com/2008/10/social-search-making-online-store.html">blog post</a> explaining her take on targeting technologies, but on a personal level.</p>
<blockquote><p>
My favorite part of Baynote’s technology: it ignores demographics. Yes! When are people going to figure out that this is an individualistic age? Advertisers, you are wasting your dollars on serving me with endless weight-loss and dating ads. Not all 27-year old females are the same!</p></blockquote>
<p>I&#8217;d have to agree with this point, not all 27 year old females are the same.  Not simply because I&#8217;ve seen our technology benchmarked against demographic or profile based targeting technologies(which I have), but also because my 27-year old wife would have me sleeping on the couch if I said otherwise.</p>
<p><strong>If you are a new reader, or would like more background on our contextual targeting approach, check out our whitepaper <a href="http://www.baynote.com/resources/white-papers/social-search/register.php">&#8220;In Search of The Human Element.&#8221;</a></strong></p>
]]></content:encoded>
			<wfw:commentRss>http://www.baynote.com/blog/2008/10/03/demographic-behavioral-targeting-not-impressing-at-online-marketing-world/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
