Archive for the ‘Intranet’ Category

« Older Entries
Kristian Norling

Video: Search Analytics in Practice

May 9 - 2012 | Kristian Norling

Search Analytics in Practice from Findwise on Vimeo.

This presentation is about how to use search analytics to improve the search experience. A small investment in time and effort can really improve the search on your intranet or website. You will get practical advice on what metrics to look at and what actions can be taken as a result of the analysis.

Video in swedish “Sökanalys i praktiken”.

The presentation was recorded in Gothenburg on the 4th of May 2012.

The presentation featured in the video:

Search Analytics in Practice

View more presentations from Findwise
Description: Search analytics done right helps to improve the search experience. A small investment in time can make your search function a lot better.  •  About: Search Analytics  •  Accountable Person: Kristian Norling  •  Author:  •  Keywords: Search analytics, search,  • 

Kristian Norling

Video interview: How to Improve the Search Experience

March 15 - 2012 | Kristian Norling

Video interview with Kristian Norling at the Intrateam Event in Copenhagen 2012. Kristian talks about his former work at VGR and what he thinks is important for improving the search experience.

Kristian Norling

Watch the video

Description: Improving the search experience on the intranet or your website is important. Kristian gives advice on how to improve the search experience.  •  About: Kristian Norling is interviewed on how to improve the search experience.  •  Accountable Person: Kristian Norling  •  Keywords: search experience intranet intrateam  • 

Kristian Norling

Search Analytics in Practice

March 1 - 2012 | Kristian Norling
Presentation made by  @kristiannorling at IntraTeam 2012, 1st of March in Copenhagen.
View more presentations from Findwise

Ludvig Johansson

Contributor vs. Consumer

October 25 - 2011 | Ludvig Johansson

A couple of weeks ago I had the opportunity to attend the Microsoft SharePoint Conference 2011, Anaheim USA. This turned out to be an intense four-day conference covering just about any SharePoint 2010 topic you can imagine – from the geekiest developer session to business tracks with lessons learned.

To me, one of the most memorable sessions where Social Search with Dan Benson and Paul Summers, in which they showed us how social behaviours can be used to influence the current rank of search. For instance, users interests entered in MySite can be used to boost (xrank) search results accordingly. This was an eye opener as it illustrated what’s possible with quite easy means. Thanks for that!

Another great session was Scott Jamison talking about Findability in SharePoint. The key ingredient in this session was to differentiate between contributor and consumer. Typically we focus on the contributor, building 100 level folder structures with names that make sense to contributor. However, we seem to forget about the consumers, who of course are the other key aspect of an intranet. It is equally important to create a good support system for contributors, as it is to focus on consumer needs. As Jamison said “why have folders for both contributors and consumers? ”. SharePoint includes endless possibilities when it comes to creating logical views built on search, tags and filtering aimed to fill the needs of the consumers.

So, keep the folders or what ever support the contributor needs, but let your imagination float free for delivering best class Findability to the consumer!

Lina Westerling

Snapshots of a User Experience course

July 7 - 2011 | Lina Westerling

In April I attended the UX Intensive course in Amsterdam, hosted by experience design firm Adaptive Path.

One thing I found interesting was the variations of participants’ work focus over the product development process. Some specialize in doing user research whereas others, myself included, cover the whole process from high-level strategy to detailed interaction design.

Looking back on the four intensive days, mixing lectures and hands-on exercises, there are some thoughts I would like to share with you, sticking to topics applicable when developing intranet and company public websites.

 

Nothing exists in isolation

“Design a thing by considering it in its next largest context – a chair in a room, a room in a house, a house in an environment, environment in a city plan”

Eliel Saarinen – Finnish architect (1873-1950)

This quote came up in the course when covering design strategy. An architect originally stated it, but it can be applied to all design areas, including websites and digital applications.

For instance, lets look at an intranet: it is definitely not used in isolation. It is part of a workflow involving several IT systems and other information channels such as face-to-face meetings. Looking only at Findwise area of expertise: the search function is undeniably an essential part of the website.

Typically, search tries to replicate/mirror the navigational structure of a site. This is reasonable, and good, but surely this relation could go the other way as well – navigation can learn from the dynamics of search and from user search behavior. Navigation and search should be intertwined, rather than being two separate ways of accessing information. Studies show that users are not either searchers or navigators; sometimes users are biased to search and sometimes to click menu items and links. Most of the times users actually combine the two methods when visiting a website. This should be considered when developing a new website – search and the rest of the site should not be developed separately.

Moreover, internal platforms for spreading information and collaboration are typically used in different contexts by different users. An example: The developer use it to up- and download day-to-day work documents whereas the general user mainly view it as a news channel to keep up to date with what is going on in the organization. Yet editors use it to publish information for other employees to access.

In large organizations, applications used by employees are typically owned by different units – units that do not talk to each other. I am convinced that all system owners within an organization have things to learn form each other. After all, they are often serving the same people and might otherwise redo work such as target group analysis. All parts will gain from communicating more across organizational borders.

Maria Johansson

Bridging the gap between people and technology

December 6 - 2010 | Maria Johansson

Tony Russell-Rose recently wrote about the changing face of search, a post that summed up the discussion about the future of search that took part at the recent search solutions conference. This is indeed an interesting topic. My colleague Ludvig also touched on this topic in his recent post where he expressed his disappointment in the lack of visionary presentations at this year’s KMWorld conference.

At our last monthly staff meeting we had a visit from Dick Stenmark, associate professor of Informatics at the Department of Applied IT at Gothenburg University. He spoke about his view on the intranets of the future. One of the things he talked about was the big gap in between the user’s vague representation of her information need (e.g. the search query) and the representation of the documents indexed by the intranet search engine. If a user has a hard time defining what it is she is looking for it will of course be very hard for the search engine to interpret the query and deliver relevant results. What is needed, according to Dick Stenmark, is a way to bridge the gap between technology (the search engine) and people (the users of the search engine).

As I see it there are two ways you can bridge this gap:

  1. Help users become better searchers
  2. Customize search solutions to fit the needs of different user groups

Helping users become better searchers

I have mentioned this topic in one of my earlier posts. Users are not good at describing which information they are seeking, so it is important that we make sure the search solutions help them do so. Already existing functionalities, such as query completion and related searches, can help users create and use better queries.

Query completion often includes common search terms, but what if we did combine them with the search terms we would have wanted them to search for? This requires that you learn something about your users and their information needs. If you do take the time to learn about this it is possible to create suggestions that will help the user not only spell correctly, but also to create a more specific query. Some search solutions (such as homedepot.com) also uses a sort of query disambiguation, where the user’s search returns not only results, but a list of matching categories (where the user is asked to choose which category of products her search term belongs). This helps the search engine return not only the correct set of results, but also display the most relevant set of facets for that product category. Likewise, Google displays a list of related searches at the bottom of the search results list.

These are some examples of functionalities that can help users become better searchers. If you want to learn some more have a look at Dan Russells presentation linked from my previous post.

Customize search solutions to fit the needs of different user groups

One of the things Dick Stenmark talked about in his presentation for us at Findwise was how different users’ behavior is when it comes to searching for information. Users both have different information needs and also different ways of searching for information. However, when it comes to designing the experience of finding information most companies still try to achieve a one size fits all solution. A public website can maybe get by supporting 90% of its visitors but an intranet that only supports part of the employees is a failure. Still very few companies work with personalizing the search applications for their different user groups. (Some don’t even seem to care that they have different user groups and therefore treat all their users as one and the same.) The search engine needs to know and care more about its’ users in order to deliver better results and a better search experience as a whole. For search to be really useful personalization in some form is a must, and I think and hope we will see more of this in the future.

Caroline Abrahamsson

OmniFind Enterprise Edition 9.1 – new capabilities discussed over breakfast

November 28 - 2010 | Caroline Abrahamsson

During the last year a number of interesting things has happened to IBM’s search platform and the new version, OmniFind 9.1, was released this summer. Apart from a large number of improvements in the interface, the change to basing the new solution on open source (Lucene) has proven to be a genius by-pass of some of OmniFinds previous shortcomings.

The licensing model is still quite complicated, something Stephen E Arnold highlighted earlier this year.
Since a number of our customers have chosen to take a closer look at OmniFind 9.1 as a search solution we decided to host a breakfast seminar together with IBM last Thursday, in order to discuss the new features and show how some of our customer are working with it.

Without a doubt, the most interesting part is always to discuss how the solution can be utilized for intranets, extranets, external sites and e-business purposes.

Apart from this, we also took a look at some of the new features:
Type ahead (query suggestion), based on either search statistics or indexed content

Type ahead

 

 

Faceted searchi.e. the ability to filter on dates, locations, format etc as well as numeric and date range. The later is of course widely used within e-business.

Facets for e-business

 

 

Thumbnail views of documents (yes, exactly what it sounds like: a thumbnail view for first page of documents in results page)

Thumbnail of a document

Search analytics in OmniFind 9.1 holds a number of interesting statistic capabilities. Some things worth mentioning is number of queries, query popularity, number of users, average response time (ms) and worst response time (ms).

Save searches (to be able to go back and see if new information has been included), search within result sets (to further narrow your result set within a given result set) and did-you-mean functionality (spell checking) are also included.

..and improvements on the administrator side, just to mention a few:
Ability to change the relevancy i.e. to adjust and give certain types of information higher ranking
Support for incremental indexing i.e. to only re-index the information that is new or changed since the last time you made it searchable.

To conclude: IBM is making a whole lot of improvements in the new version, which are worth taking a closer look at. During the spring we are running upgrading projects for some of our customers, and we will keep you up-to-date with the different application areas OmniFind Enterprise Edition 9.1 is being used for. Please let us know if you have any particular questions or have areas that you are interested in.

Maria Johansson

Metadata in focus for our Findability solution

October 28 - 2010 | Maria Johansson

Last week Kristian Norling wrote a blog post about how they work with metadata at Västra Götalands Regionen (VGR). In the beginning of his post he states that metadata is boring, but extremely useful. A teacher in statistics that I had in college used to say that statistics is the most boring thing there is. It’s the things that you can do with statistics that makes it really interesting. So I agree with both of them, the metadata (or statistics) in itself is quite boring, but the things you can do with it is what makes it all worth it. The quality and structure of information must also be in focus when creating Findability solutions that aim to provide easy access to all information inside and outside the firewall.

Findwise is currently working on improving our findability solution which is our intranet. When we investigated our own business and user needs we learned that there is a need for a more flexible way of organizing information so it can be found from different entrypoints as well as in different contexts. Therefore one of the things at the heart of our intranet (except the search functionality off course) is metadata. As a fast growing  (and changing) company we find it hard to create and maintain one single information hierarchy that is intuitive and self-evident to all our employees.  Instead we are working with a taxonomy with a simple set of categories and concepts. All content is tagged with what, where and who.

Who describes which people or groups are allowed to see a document. It can be everyone, a single person or a group of people such as the finance department, or a project team. Since knowledge sharing is very important for our organization most of the information is open for everyone to see and use.

Where describes which sites the content should be visible on. A single document can be visible on several sites. So if contact details for a customer is relevant to show on several projects for that customer the same content can be displayed on all the different project sites, without us having to store duplicate versions of the content.

What describes the concepts the content relates to. These concepts include customers, projects, products & competences, information types as well as categories that are created through the means of user generated tagging. This way one single document does not have to belong to one specific site or folder, but can be displayed in several different and all relevant locations on the intranet. Thanks to this use of metadata it is also possible to use the different categories for search and faceted navigation. For example I can view all design specifications from different customer projects that include the concept faceted navigation, or all information about how to work with search analytics with the search platform Autonomy IDOL. The concepts and the information becomes the focus instead of the location where it is stored.

In the first stage this will be done manually as content is added to the intranet. In the future it would also be of interest for us to utilize the same type of service that we developed for VGR, for our own content. But instead of using controlled vocabularies such as MeSH we use our own taxonomy and the power of search technology to suggest or automatically add appropriate customers, projects and categories for a document. A first step in this will probably be to use entity extraction techniques to identify and automatically tag already existing documents with concepts such as customers and search platforms.

We hope to share our experiences from this project with you in the future. In the mean while I recommend that you read Kristian’s post about how they use different types of keyword metadata at VGR.

Caroline Abrahamsson

Information flow in VGR

October 17 - 2010 | Caroline Abrahamsson

The previous week Kristian Norling from VGR (Västra Götaland Regional Council) posted a really interesting and important blog post about information flow.
Those of you who doesn’t know what VGR has been up to previously, here is a short background.

For a number of years the organization has been working to give reality to a model for how information is created, managed, stored and distributed. And perhaps the most important part – integrated.

Information flow in VGR

So, why is this important?
In order to give your users access to the right information it is essential to get control of the whole information flow i.e. from the time it is created until it reaches the end user. If we lack knowledge about this, it is almost impossible to ensure quality and accuracy.

The fact that we have control also gives us endless possibilities when it comes to distributing the right information at the right time (an old cliché that is finally becoming reality). To sum up: that is what search is all about!

When information is being created VGR uses a Metadata service which helps the editors to tag their content by giving keyword suggestions.
In reality this means that the information can be distributed in the way it is intended. News are for example tagged with subject, target group and organizational info (apart from dates, author, expiring date etc which is automated) – meaning that the people belonging to specific groups with certain roles will get the news that are important to them.

Once the information is tagged correctly and published it is indexed by search. This is done in a number of different ways: by HTML-crawling, through RSS, by feeding the search engine or through direct indexing.

The information is after this available through search and ready to be distributed to the right target groups.
Portlets are used to give single sign-on access to a number of information systems and template pages in the WCM (Web Content Management system) uses search alerts to give updated information.
Simply put: a search alert for e.g. meeting minutes that contains your department’s name will give you an overview of all information that concerns this when it is published, regardless of in which system it resides.

Furthermore, the blog post describes VGRs work with creating short and persistent URL:s (through an URL-service) and how to ”monitor” and “listen to” the information flow (for real-time indexing and distribution) – areas where we all have things to learn.
Over time Kristian will describe the different parts of the model in detail, be sure to keep an eye on the blog.

What are your thoughts on how to get control of the information flow? Have you been developing similar solutions for part of this?

Caroline Abrahamsson

Search as an integrator of social intranets

September 12 - 2010 | Caroline Abrahamsson

Wikis, blogs, microblogging, commenting, rating…we all know the buzzwords around the “Social intranet” by know.
If the first trend was about getting people to use the new technology, the second seems to be about making sense of all the information that has been created by now.

I sat down with a number of our customers the other week to talk about intranets and internal portals and everyone seemed to face one particular challenge: making sense of the collaborative and social content. How do we make this sort of information searchable without losing the context?  And how do we know who the sender is? (more…)

« Older Entries