blog.frederique.harmsze.nl my world of work and user experiences

March 31, 2013

Cloudy upgrade

Filed under: Office365,SharePoint — Tags: , — frederique @ 17:58

We are working in the cloud, in SharePoint Online. And our cloud is about to be upgraded to wave 15, i.e. ‘SharePoint 2013 Online’. We have not heard an exact date yet, but rumour has it that we’ll be upgraded in June.

This system of cloud upgrades is new to me. In other cases, we had to get into the server and do everything ourselves. Now Microsoft does all the upgrade work. And we need to find out what we should do to move along with it:

  • Test if all our configurations keep working or if anything breaks
  • List the changes in the interface and functionality that we’ll need to explain to the site owners or other users
  • Check which spiffy and useful new features we want to promote to our users
  • Prepare our communication and update our help content.

This week, we have already seen the first stages of that upgrade: below decks, the installation is already version 15. At least, when I check https://ourcompanyname.sharepoint.com/_vti_pvt/service.cnf
I see vti_extenderversion:SR|15.0.0.4454

Unfortunately, this change did cause some problems on the front end:

  • The Note Board does not work anymore
    My old comments are still visible in My Profile, but they are not displayed with the News article or Team Site home page where I had entered the comment in the Note Board
  • Metadata have dropped out of some places
    Some Content Query Web Parts have lost the metadata in the Presentation section.  And our own page layouts have lost the metadata in the property fields.
  • I cannot edit SharePoint Designer workflows anymore.
    My SharePoint Designer still works for things like conditional formatting, but I can an error message when I try to edit a workflow. I should move to SharePoint Designer 2013 for that, even months before the official upgrade.
  • MyQuickLinks.aspx has disappeared
    We use the old MyQuickLinks to manage our team site favourites, but now we get a ‘page cannot be found’ error.

Over the coming days, we’ll see if Microsoft will tweak the system or if we can do something to fix these problems.

In any cases, if you are managing a SharePoint Online environment, I recommend you keep an eye on it. We will definitely do that.

February 28, 2013

Nielsen Intranet Annual 2013 Trends in the intranet world

Filed under: Usability — Tags: — frederique @ 20:08

A new year, a new Nielsen Norman Group Intranet Annual. As always, they have looked at a lot of intranets and picked the ones that are most useable and user-friendly. And don’t think “we use SharePoint so it does not apply to us”, as 70% of this year’s winners are on SharePoint! These some of their lessons learned and trends that resonated with me.

  • It takes time and people to make a great intranet
    In these days of tools like SharePoint that we can use out-of-the-box, creating an intranet is no big deal, right? Wrong! “Just because a tool lets you do something doesn’t mean it’s a good design solution for your users. Across the years, our winning designs have tended to be from organizations that customized an existing technology solution to fit their needs, rather than simply doing an out-of-the-box implementation. That is, team members took the time to understand the tool inside and out, and worked with the tool to meet their organizations’ needs.” [p.363]. So development of the winning intranets took 2,3 years on average and the team consisted of 18 people, including consultants.
    “It’s not fair to ask a tiny team to take on an endeavor as great as designing and managing an intranet, even if you are “simply deploying” an out-of box solution.” [p.7] You don’t just need to build something nice. You also need to embed it in the organization, finding out what the employees need, asking feedback, testing with them what works best and communicating to them what they can do with it. “Even the busiest development teams, or those with the craziest deadlines, should take time to watch people attempt basic tasks using the design” [p.363]
  • Involve the content owners from the start
    One of the classic goals of an intranet is that the employees can find relevant information on it. In that context, we often talk about the ways to find it, via the search function and smart navigation options. But there also has to be a good, up-to-date, readable and fitting story when you have found the page. The winners have made sure of that by involving the authors from the start and helping them with their work. Not just writing new stories, but also determining what needs to be migrated from the old intranet: restart from scratch or clean up the content. But whatever you do, don’t just copy over the entire garbage heap – garbage in, garbage out.
  • Manage the content well
    That attention to the content is not just needed in the beginning, but continuously: “For the past few years, great intranet teams have been emphasizing regular content updates and creating processes and workflows that religiously keep content up-to-date.” [p.25] We – and they – see a lot of intranets that fall into the trap of content pollution. Users have a hard time picking the nuggets of golden info from the heaps of garbage.
  • Findable content: Filters gebaseerd op metadata
    To find that content, users can filter it via faceted search, which is really taking off by now. That makes sense, because “one of the greatest issues with today’s intranets is that they house too much content for users to deal with in an IA or even typical search results, [so] employees are willing to manipulate results to find exactly what they want.” [p.23]
    This kind of smart search only works if the information has been labelled properly with metadata. Social tagging is a catalyst here, and we see that SharePoint’s options for entering metadata and tagging help as well, such as the term store with type-ahead functionality that makes it easy to tag consistently. But it still takes time and effort. So according to Nielsen structure and navigation is still the number one challenge for struggling intranets, and there is still too much information in silos where it can hardly be found. But the winners say that it is definitely worth the time and effort.
  • Full on social integration
    In earlier editions of the report and some intranets in my experience, commenting en tagging are isolated in a separate section of the intranet or even a separate site. But then I see that users do not visit that section and hardly anybody participates. Now you can get social and interact on all content everywhere in more and more intranets. “There shouldn’t be a sense that there is one place for users to share information, and another for them to consume information.” [p.366] Companies that are still hesitant to get too social can at least make it easy to find people with particular expertise, so that you can contact them offline.
  • Take immediate action when you have found somebody
    Using the people search, it is easy to find people and then to contact them. If you have SharePoint and Lync, this is out-of-the-box functionality that is quite helpful. And it is not only available via the people search, but you get these contact options anywhere, like in the Members web part displayed on the homepage of your team site.
  • Pseudo-personalized homepages
    Personalization of the homepage based on your role has become very popular, but it can be very tricky to keep that up-to-date and working properly. Many companies therefore they take a step back: they let the users select for example their language and company code, or the type of home page they want, like a marketing home page or a customer home page. It needs to be very clear to the users why they should select anything and how they should do it. If you do automate personalization, check with HR regularly of the profiles still make sense.
  • Integration with enterprise applications
    The winning intranets make it easy for the employees to get into other applications – they talk about apps, very hot & happening …. The apps are often put on the home page and/or in the main navigation. And you see the apps that fit your role and/or the apps that you selected. Of course then you want to be able to access those apps without logging on separately – Single Sign On.
  • Feeds from the outside world
    Intranets already had inward facing social features, now they also display Twitter, Facebook, LinkedIn and other social sites from the outside: “offering these features as part of the intranet news serves as a frequent reminder, enables speedy access, and demonstrates support for the organizations’ representation on social sites. It also sends a message to employees that they should care about what customers are saying” [p.22] I’ve seen RSS feeds from the internet before, but I also see this outward facing view get emphasized now.
  • Mobile hardly there
    For years we’ve all been saying that mobile is hot or should be hot. Last year, we were disappointed of the mobile presence in great intranets. And this year is no better: the researchers have found only one instance of a mobile application for a winning intranet: an app for de iPad, for sales people. The others do something for mobile access, but haven’t optimized anything for it, for security reasons, because it is too difficult to choose a platform, because there is no money to develop or manage it, or because they don’t know how to tackle it.
  • Collect feedback and communicate
    Build your intranet and the users will come? Not necessarily… The winners were very serious about communicating its benefits and collecting feedback from the users to improve the intranet: users can send an e-mail easily and from everywhere, fill in feedback forms, respond to discussions about the new intranet. During launch, this gets additional attention by way of a banner on important pages. And they really do something with the feedback, so that the users know it is worth responding.

January 31, 2013

Can you share your desktop?

Filed under: New world of work — Tags: — frederique @ 22:25

It’s funny how important some tools are for my daily work. And how I take them for granted… until they don’t work.

Sharing my or your desktop is very useful to me

I collaborate with, learn from and teach information workers. The desktops we work at may technically be those table-like things, but they are mostly our computer screens. So when I want to see what they are talking about, I ask them to share their desktop with me. I don’t have to leave my table-like desktop to see what’s on the computer desktop of people who are in a different building, different city, different country or different continent.

  • When somebody in the business calls me with a strange question about a team site, they can show me where they are in the site and what behaviour they see. This may be very different from what I had imaged when they started talking.
  • When experts gives an interesting presentation, I can follow their presentation and their demo by looking at the screen they share. A picture is worth a thousands words, and a live demo that actually shows you what’s going on is worth even more. And of course I do the same thing when I am the expert giving a presentation or training.
  • In a project team meeting where we discuss a list of issues that need to be solved, we can be in different places and still have the same overview and the same live view of changes we make on-the-spot

For this purpose we used MS Communicator and Live Meeting, and now we use MS Lync.

But it doesn’t work if my Lync and your Lync bite each other

This week I was caught flat-footed when I clicked on the Lync link (huh…) in an Online Meeting invitation and got: “An error occurred”. Help!
And even worse, I was planning an important meeting about a technical subject with that same high-tech partner. So I actually had to waste time travelling to their offices and sit at a table with them, because I could not risk not sharing my desktop with them. How old fashioned is that?!

The problem was that their Lync and our Lync are not friends (ok, I mean: they are not federated). So when I click their invitation link, it opens my Lync, but my Lync does not recognize them.

Fortunately we can keep them apart

To my relief, I found a way to keep those unfriendly Lyncs apart and still see their desktop:  copy the Lync Online Meeting link from the invitation and paste it into a non-Microsoft browser (in my case Firefox and Chrome worked). This opened a web version of Lync, where I could enter as a guest.

Note to self: pasting the link in Internet Explorer does not work, because the Microsoft browser starts to be smart and recognize the Microsoft Lync stuff and then it tries to connect the unconnectable Lyncs.

So that should be the end of this error…

December 31, 2012

Happy 2013

Filed under: SharePoint — Tags: — frederique @ 14:35

I wish you all a very happy 2013!

First of all I mean the new year 2013 that is about to start with a bang – actually a lot of bangs, of fireworks and popping champagne corks. I wish you lots of fun, good health and generally all the best.

Secondly, I also wish you lots of fun and all the best with the new SharePoint 2013. We’ve already seen quite a bit of it, but this will be its official year and I hope I will see it in production in my client’s workplace.

Of course I do not expect the new SharePoint to be all fireworks and champagne. But I do think it will make us happy, by making our lives easier. And maybe even healthier, if we can stop pulling our hair out over limitations in the SharePoint 2010 cloud that we are working with now. I think the following will make me happy:

  • Manageable managed metadata with a quick edit option to edit the managed metadata of multiple list or library items in a bulk operation.
    Now we can only edit fields like choice fields in the datasheet. The centrally defined managed metadata have to be set one by one, with some possibilities to set smart defaults so that you have a head start when you upload multiple files for instance. Third party tools like Colligo’s Contributor  can handle bulk editing, but the bulk of our users does not have that tool at their disposal. Really annoying, so we look forward to the new ‘quick edit’.
  • Follow functionality that gives users quick access to the team sites they use a lot and keep an eye on people and places of interest. Now we use alerts to keep track of content and have a non-standard implementation of the old My Links for my favorite team sites. That is a bit clunky, so bring on the follow options.
  • Sharing with external users seems smoother, more integrated with “normal” sharing.
    Right now, we are struggling with external users. They are supposed to participate in some serious business solutions. But the interface for inviting them confuses the site owners. And once they are on the site, it is not easy to assign tasks to them. Can you make that better? Yes please!
  • Records management functionality that will allow us to keep our environment clean, by setting policies that help owners to clean up old content.
    Now we have prepared for this by including an expiry data field in all content, but we’ll wait for 2013 to take action in content life cycle management.
  • Configurable search results that include custom properties, so that we can roll up information across site collections and present the result nicely.
    At the moment we are stuck with search results with standard properties, as the Content Query Web part does not look across the boundaries of site collections and the search result cannot include the custom properties that enrich our libraries.
  • Advanced workflows that work, using Nintex Workflow Online. I have seen in my playground that I can add the Nintex preview “app” from the store. Definitely a new toy that I want to play with, as soon as I have a moment.
    The last month or so, this has been one of the key issue that made me pull my hair out. We only have SharePoint Designer at our disposal to build the custom workflows we need to support several of our business processes. And that is  not only slow and unfriendly, but it is also limited to about five steps. Any more steps, and you simply cannot publish your workflow anymory – it is caused by some time-out that you are supposed to circumvent by changing your webconfig, which of course is not available to us in the cloud. By stripping out everything that was not crucial I managed to squeeze in almost all required steps. And I’ve told the users that we will try again as soon as SharePoint 2013 has arrived in our workplace.

And in the mean time: happy new year!!

Happy New Year

Happy New Year!

November 30, 2012

What happened to the Title?

Filed under: SharePoint,Usability — Tags: , — frederique @ 22:24

SharePoint document libraries have separate fields for the file name (Name) and for a Title. That makes perfect sense to me, because they have different requirements:

  • The Name needs to be a unique file name, so that you do not overwrite a previous document.
    So for libraries with many documents and especially libraries with many contributors, we recommend a naming convention such as including your initials and the date. This is the ‘system field’
  • The Title need to be clear for people who try to find the file and to determine if this is the file they want to open.
    So you should enter a clear and clean title that does not contain codes and additions that make it less readable. This is the ‘people field’.

In “old” SharePoint, the Title field was clickable
We used the Title field in all views. The reader could click on the Title to read the file, the contributor could open the item menu from the Title to edit it in MS Office. The unique but unwieldly Name was invisible to normal users.

In “new” SharePoint, it is the Name field that is clickable
You have no option but using the .Name field in all your view, because otherwise nobody can read or use the file in any way… The only use I see for the Title field, is for the search engine.
This is the case in SharePoint 2010 but also in SharePoint 2013. I do hope that it is a temporary mistake in the trial cloud that I am looking at.

The file Name and Title

The Title is visible, but it is the Name that is clickable

In the SharePoint 2010 Online version that we are working in now, the Title field often is mandatory, because it is important for the search. But users are getting rather annoyed, having to fill in a field that has no immediate use in the site itself.

I know that there are scripts and workarounds to get a clickable Title field. But I would rather stick with out-of-the-box functionality than risk inconsistency and unstability from some band-aid.
What I don’t know why it is now the Name rather than the Title that is the active field.

What happened to the title? Why did it lose its clickability and – basically – its usefulness?

October 31, 2012

Multiple options for multiple lines of text

Filed under: SharePoint — Tags: , — frederique @ 22:32

Working with the business to facilitate their processes using SharePoint Online, we see that they have different needs for capturing and presenting information. For example, some teams need to efficiently edit the information in different items in one go, in a supplier list for instance. Other teams really need to track who said what,  in comment fields in an incident log for instance.

Fortunately we have different solutions, even with something as basic as a multiple lines of text field in a list.

Options in a multiple lines of text field

When I create a multiple lines of text field in a list, I have different options:

  • Formatting options: plain text, rich text (with fonts, lists and links) or enhanced rich text (which can include pictures and tables)
  • Versioning: append text yes or no.  
    If you switch on versioning in your list, you can use versioning on your multiple lines of text field: append text to the old text instead of risking you overwrite it.

Field with these different options look like this in the individual list item:

The list overview the looks as follows:

Editing the list in the datasheet view does not work for the enhanced fields where you enter images. But you can edit the rich text fields in the datasheet, if you know shortcut keys for it, as the ribbon does not apply to the cell in the datasheet.

What option for what purpose

Looking at the standard options for a multiple lines of text field in a list, we see the following pros & cons and uses:

  No append text Append text
Plain text + Simple, so best chance of success in other browsers
+ Edit in datasheet
+ Name and date & time stamp shown for version
+ No version added if nothing is changed to the field
+ Edit in datasheet works (but behaves differently: previous comment not cleared from the field)
  – Only capital letters and starting a new line to structure text in the field
– If you need see when you said what, add your initials and the date manually
– Only capital letters and starting a new line to structure text in the field
– Not visible in list view (only :”View Entries”)
 Use for: Efficient adding and editing (in datasheet) of basic information: simple descriptions or one-off comments that do not require versioning Short comments in e.g. an incident log where different roles have different fields and where it is important to record who said what when.
     
Rich text + Structure your information easily via a field ribbon (e.g. bulleted lists, bold)
+ Edit in datasheet (but without ribbon, so hit ctrl b to make a word bold for example)
 + Name and date & time stamp shown for version
+ Edit in datasheet works (but without ribbon and behaves differently: previous comment not cleared from the field)
  – If you need see when you said what, add your initials and the date manually – Version added and name and date displayed even when that person did not add anything to this field
– Not visible in list view (only :”View Entries”)
Use for: Structuring your information via layout (e.g. bulleted lists, bold font) Capturing what participants do or don’t say in e.g. a shared comments field when managing an issue.
     
Enhanced rich text + Opportunity to structure and enrich at will + No version added if nothing is changed to the field
  – No edit in datasheet
– A bit less clear how to edit: No ribbon directly with the field, so use the full ribbon at the top of the item.
– No edit in datasheet
– Not visible in list view (only :”View Entries”)
– History may take up a lot of space in the display form
Use for: Free text description of an item that may contain pictures etc. (If the description gets very big and the other fields get less important, use a page for it) Rich updates in e.g. an incident log where different people as descriptions and pictures of what they have seen at different stages.

How to configure it

So how do you configure this? Create a multiple lines of text field and select the type of text to allow and if you want to append changes (i.e. have versioning in the field) yes or no:

September 30, 2012

SharePoint 2013: Working on it…

Filed under: SharePoint — Tags: — frederique @ 21:20

Hey, that’s my line! But the 2013 version of SharePoint also tells me that it is working on it, when it is loading a page or processing a change.

Working on it...

Working on it...

It is good to know that my team site is working on it. And it is even better that the team site allows me to be working on the content that I come here for.

One of my gripes with the team sites we now have in SharePoint 2010 (Online) is that my working area is too small.The Quick Launch menu is very useful, but it is in the way when I have list and libary views with many columns.
In the new SharePoint 2013, you can click on the icon Focus on content. That moves the menu out of the way, so can use the full width of the screen as a working area:

Team Site with context

Team Site with context

Focus on content

Focus on content

The interface for working on your documents has changed a bit as well. Instead of that menu that you can pull from the arrow that appears when you hover over the title or filename, we now have these dots… that indicate that you can do something… working on it…

August 31, 2012

Let’s not cut the tree in half to fix the swing

Filed under: Usability — frederique @ 20:01

I had a flashback to the tree swing the other day. I felt like we were about to cut the trunk of the tree to fix a problem in SharePoint Online… NOOOOOO!  Fortunately we didn’t actually go there. Instead of continuing on the path of complication, we doubled back and simplified.

Thank you http://www.projectcartoon.com ! By the way, there are a few interesting new options in the classic tree swing project cartoon I hadn’t seen before, including a butterfly effect for its performance under load and the iSwing. And here’s another nice and very extended series of cartoons of what different teams can do to that poor tree swing, including health & safety inspectors…

It’s a balancing act
Our starting point in the development of this SharePoint Online intranet was to use the platform as much as possible “as is”. No development in the sense of programming. No customizations; just deciding which elements of the product we should take out of the box and how we should configure them and put them to use. This starting point makes sense, given the fact that we are in the cloud and we want to float along with any updates and upgrades.But we have flown way beyond that starting point now.

The goal of the intranet is to help the employees do their jobs. And the standard out of the box functionality is just not good enough for an intranet of hundreds of team sites that help thousands of employees collaborate, share knowledge and follow their business processes efficiently. Fortunately, we can actually talk to the users down the hall, so we don’t have to guess as much as the cartoon projects working for the swing customer…

So we had to customize. And then deal with the complications caused by the customizations. It’s a balancing act, between functionality and usability on the one hand, and maintainabillty and feasibility on the other hand.

Oh well, we not only have a tree swing, but also a see-saw and a tightrope in our playground…

July 31, 2012

SharePoint 2013: looking forward to it

Filed under: Office365,SharePoint — Tags: — frederique @ 22:54

I do not get excited by new tools just because of their gleaming newness. But I have to say that I am definitely interested by the new SharePoint 2013. I was able to get my own playground via Microsoft’s Office 365 Enterprise Preview and Jasper showed us around in a O365UG session last week. And within just a few clicks I saw functionality that we had just been discussing that very day and that required serious work on our current SharePoint Online based on SharePoint 2010:

  • Sites you’re following gives me shortcuts to the site that I actually use a lot. The sites that I created were automatically listed here, I can indicate for a site that I want to follow it, and apparently I get suggestions for sites that I may want to follow. I haven’t seen on what basis these suggestions are made. We were just looking for a way to flag sites as favorites that I want to access easily and from which I want to roll up content.

    Following sites

    Following sites in SharePoint 2013

  • Quick Edit for bulk editing managed metadata: We just had to manually change the properties of over three hundred items one by one, accompanied by a constant stream of “you’ve got to be kidding me…”, because you cannot edit managed metadata in the datasheet. But lo and behold, the new sharepoint has ‘Quick Edit’ (Thanks for pointing this out Jeroen!)
  • Embed code, like youtube videos and other snippets. Our current SharePoint Online strips out embedded code. In the new one, there is a button in the ribbon for it. Now we just need to figure out how to include non-secure content into our secure page…

    Embed code

    Embedding code in SharePoint 2013

I am looking forward to getting these and other extra tools in our toolbox. Hmmm, when will we get it? We’re on SharePoint Online, where we hope we get upgrades without too much of a hassle…

June 30, 2012

How many people visit what – Intranet statistics

Filed under: Office365 — Tags: , — frederique @ 21:29

The first parts of our new SharePoint Online intranet are in use, so we want to know what works and what doesn’t. We ask our users what they think about our new intranet. But we also want some statistics, such as: how many people visit which sections of the new intranet.

Unfortunately, Office 365 does not have analytics functionality at this stage. Third party tools like Axceler’s ControlPoint cannot offer these analytics until Office 365 makes the numbers available. And we’d rather not let Google enter our secure intranet to do its analytics.

Until we have something better, we have some usage details per site

  • Unsupported – These are not supported and not entirely correct. At the very least the page views and visits per day are sometimes shifted a day. But they give us some sense of the site usage.
  • Shortcut – As they are unsupported, there is no link in the site settings, so we use a shortcut:
    https://[ourcompany].sharepoint.com/_layouts/usageDetails.aspx
  • Seperately per subsite – You need to check the usage details separately for every subsite.
  • Last 30 days only – The numbers are only available for the last 30 days. So we copy them to a file to keep a longer sense of our intranet history.
  • Numbers of page views and of unique visitors– The usage details tell us how many visits we get per day in the different sections, and that they are  increasing.

    Usage details - Number of Unique Visitors

  • Top pages– We can see which news articles, which videos are viewed most.  Blog articles and discussion items are not pages, so we can only check how often their overview page is visited.

    Usage details - Top Pages

This gives us some sense of site usage. But we are definltely looking forward to some serious analytics that are less time consuming and more informative.

« Newer PostsOlder Posts »

Powered by WordPress