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

March 31, 2022

How will this help us?

Filed under: Adoption,Digital Workplace,Microsoft 365 — frederique @ 20:24

Recently, I got involved in some training programmes, in which the people from a department could learn about Microsoft 365. These people were collaborating with each other, in a field different from my own: pharmacies and construction. What struck me, were their questions and even accusations: “You are from the head office and what head office tells us to do often does NOT work for our jobs in the field. So what does this mean for us, the people who are not sitting in an office all day working with Office applications? ”

My goal is not to sell as many Microsoft 365 licenses as possible, nor is it forcing users to adopt Microsoft 365 at knife point. What I try to do, is help people to do their jobs more effectively, efficiently and pleasantly. And in many cases Microsoft 365 can help with that, but if and only if they adopt it the right way. So:

  • From the one end, IT needs to make sure that the people get the tools that can actually help them. Not a one-size-fits-all toolkit & approach that does not fit their situation or their needs.
  • And from the other end, the people need to adopt the new way of working, with the new tools. For that they need to become aware of that new way of working, desire it, know enough about it, become able to do it in real life and be reinforced when they make the change. See ADKAR. And we can help them make the change, but only if the new way of working really works.

For example, I heard the following:

  • “Did your project actually ask the pharmacies what they needed, before you started pushing this change on us?”
    Fortunately, we had involved representatives from the pharmacies and done a pilot with them, so we could reassure these people. But we had not communicated this properly with the larger group, so they were still stuck in the sentiment of ‘those idiots from headquarters’ at the start of our training. Something to take into account next time.
  • “We don’t have a full computer or laptop, only a Citrix environment, without desktop applications. ”
    Fortunately, many of the Microsoft 365 application have a nice Online version. What we should have done better, is start with the story of the online versions, to fit their needs. I got catapulted into this training as a last minute resourcing fix, so I did not realise that only a few of the participants could use the desktop versions. Next time I will check, because you don’t want to talk about options that they don’t have….
  • “Why are you talking about Microsoft Teams as a ‘digital office’ for collaboration. In our pharmacies, we only have the one pharmacist who has a computer, what do you mean collaboration? ”
    Fortunately, we had also planned Teams for collaboration at the level of clusters, which made a lot more sense to them.
  • “The assistants in the pharmacies do not have individual Microsoft 365 accounts. How are we going to involve them in all this digital sharing? ”
    Good question, are aware of it. But the business still need to decide if they will get individual accounts and if they do: with which license.
  • “You show us how you can open a document in Teams and co-author it. But we are using a lot of files that can only be opened in non-Microsoft applications. We need these tools for manipulating models, schematics, plannings etc. How do we work with those files that seem exotic to you but are run-of-the mill for us.”
    Fortunately, we could show that they can synchronise the relevant libraries to their Windows Explorer and open those files from there. And yes, they were happy with the additional possibilities for opening links to work in Office files directly from Teams, for example. As long as we don’t try to suggest that this is the only type of files that they need to manage.

February 28, 2022

Microsoft 365 adoption: It is not over when it is over

Filed under: Adoption,Microsoft 365 — Tags: — frederique @ 21:36

I have been involved in the implementation of Microsoft 365 a few times. It is a project in which we get everyone into the cloud, migrate all of the information into the cloud too and activate all kinds of spiffy applications. We organise some training and set up and information portal to help our users adopt Microsoft 365. And when we have finished that, we are done. Right? Wrong!

The journey to help our people adopt Microsoft 365 does not end when we have implemented the technology and migrated everyone & everything. It even does not end when we have finished a training programme. Instead, it requires an ongoing programme. There are several reasons why you need to keep paying attention to Microsoft 365 adoption.

All changes need reinforcement

For any change, you cannot stop once people have learned how to work in a new way. You need to reinforce the change, to make sure that the people do not revert back to their old way of working as soon as they get back from their training session to the hectic hustle and bustle of their daily job.

In the ADKAR model that we favour, this is the R. The last stage, but definitely not the least. See also ADKAR: are our users ready to adopt our solutions?

So in the weeks and months after we organised our training sessions and went live with Microsoft 365, we should check if the new tools are being used rather than the old ones and if the people work in the new way instead of being stuck in their old ways of working. We should also make sure that it is very easy to get help, if you are not entirely sure about the new way of working. And that anyone who can set a good example does so: managers, team leads, influential colleagues, HR, Communication, IT,…

Microsoft 365 evolves continuously

Microsoft keeps adding applications and improving existing applications. So the people need to be aware of those changes, know what’s it in it for them and what to adopt them, know how to use the new & improved applications and be actually able to do so. And again get reinforced in the updated way of working.

So we should keep an eye on the Microsoft roadmap and put governance in place to determine how we deal with these updates: activate everything? Wait if it is possible to wait, and activate applications only if they are sufficiently mature and explained properly? Activate only for a specific group of trailblazers in a targeted release? And then arrange to help the people adopt the updates, for example by organising knowledge sessions like webinars on new features, publishing tips in communication channels that suit the audience (such as intranet news and departmental newsletters) and continuously updating your information portal for the details.

Our situation evolves continuously

The organisation may change, the users may change, the users’ insights and needs may change. New questions get asked. New solutions to facilitate work processes get thought out and implemented.

So you need to update the help materials you have, your information portal if you have one. This requires governance: somebody needs to be responsible for it and have a process when to update or add what information. And take it to the users: you don’t have to wait for new features from Microsoft to publish tips and organise knowledge sessions.

You also need a channel to collect feedback from the users on what should be explained or explained better: via the log of the questions that are frequently asked the servicedesk, via a network of ‘champions’, a feedback form, informal chats with users,…

New hires need to be onboarded & adopted

One of the advantages of Microsoft 365 is that many organisations use it. So when you hire new employees, chances are that they have used Microsoft 365 before, or at least parts of it. Nevertheless, these new people are unfamiliar with your specific templates and guidelines for how you use Microsoft 365 in your organisation and in your teams.

So you need to adopt these new colleagues and allow them to adopt your toolkit and your ways of working. I know, a bit of a mixed metaphor: take these new colleagues under your wing, so that they can embrace your tools and ways of working. Make them aware during the onboarding programme and show them the benefits. Offer them training if they need it. Make sure they are able to get started by creating their accounts promptly and giving them the required permissions. And again reinforce everything: managers and close colleagues and coach and guide the new people.

Support should be available continuously

Ok, maybe not continuously as in 24/7, but support cannot stop after Microsoft 365 has been launched and the implementation project is finished. Users should always be able to get proper support when something does not work or if they get lost. See also The importance of support for Office 365 adoption.

So make sure they know who to contact and that the people they contact are able to help them. For example.

  • Arrange for keyusers / champions who can help their colleagues. This approach can work well, because these champions are closer to the innocent end-users than IT. But then the keyusers need to be kept up-to-date on developments and they need direct access to expert support if they don’t know the answers to the users’ questions.
  • Make sure the helpdesk can help people: is there a clear and easy way to contact the helpdesk, does the helpdesk have the knowledge required to help the users?

Bottomline: you need to arrange for ongoing adoption capabilities, especially when you have an evolving toolkit like Microsoft 365. Or the Power Platform. Or any other platform where the users experience continuous change.

October 31, 2021

Feedback is important

Filed under: Adoption,Governance,Microsoft 365 — frederique @ 20:51

Most of us do our best, to try and offer useful solutions and help the end-users. However, nobody is perfect and no solution is perfect, especially not when it is first launched. We make mistakes, misjudge what works for the users or do not know what is most important to them. That is why it is so important to get feedback, so that we know what to improve.

Grumbling is not helpful

I have often heard users complain about things like their digital workplace (including the SharePoint sites and Teams environments they are offered), the information and training they do or don’t get from IT, or the support they mostly don’t get from the helpdesk. When I hear these complains, I try to pick them up as feedback and pass them along to the people who could help solve these problems. But if people just complain and grumble amongst each other, nothing will get fixed.

This is really tricky: I have heard IT state that everything was just fine, because nobody had complained to them. They use the squeaky wheel system: the squeaky wheel gets the oil, and the users who squeak get help. But what if the users don’t squeak in the right way to the right people? The users I talked to had given up contacting the helpdesk, because such a contact usually took a lot of time and never solved anything. And they did not know how, where or to who to make a constructive complain, also known as give feedback. Instead, they grumbled, got upset with IT and tried to find their own tools outside of the official toolkit.

But then it has to be clear how and where you can give feedback

It has to be very clear to users how they can give feedback. And preferably there should also be different ways of giving feedback, to make it easier for the users.

Offer explicit feedback options in your communication, on your information pages, in your digital workplace. For example, I have got feedback in a feedback form that was available from any page of our information portal on Microsoft 365. That included feedback about email communication from another Operating Company that we knew nothing about. But apparently our feedback form was the first thing the user found to drop his complaint.

Also make sure that the users have someone to talk to when they have feedback: the helpdesk, who then definitely should collect the feedback and pass it along to the right people. Or champions: people who can help out colleagues, because they know more about Microsoft 365 for instance, and who can pass along feedback. Or an IT business partner. I know that when I talk to end-users, I often get valuable feedback.

Microsoft knows feedback is important

In the early days, Microsoft felt like this huge, uncommunicative black box company: we just had to accept whatever they sold us. But nowadays, Microsoft actively listens to users and the community. Instead of assuming they know best, they launch a first version: a Minimal Viable Product or MVP. And then they actively ask for feedback and develop their products based on the feedback and what the users need.

Ok, I am definitely not always happy with the MVPs, that tend to be more minimal than viable. But I am happy that they take our feedback into account. For example, I was recently able to attend several Feedback Roundtable sessions at the Microsoft Airlift conference and participate in live discussions. There are feedback buttons all over Microsoft 365. And we have User Voice to suggest improvement. But something is changing in that area.

Now Microsoft has a new feedback portal

I don’t know all the details, but I had heard that Microsoft will move from UserVoice, which is a third party site, to a feedback portal built on their own Dynamics 365. And I just saw an announcement saying that Preview of Feedback for Microsoft Teams now available. So we are definitely beyond rumours now ?

The new portal looks quite a bit like UserVoice: you can find ideas that were posted, vote and comment on them. And you can submit a new idea, now called Send feedback. Ideas from the Teams UserVoice has been transferred to the new feedback portal. Maybe not all, but at least the ones I checked. At this point, the feedback I provided via the Feedback option in Teams itself does not end up in that portal. Not yet at least. See UserVoice pages for more info about the transition.

Feedback for governance and adoption in your organisation

Feedback is important to Microsoft, because it allows them to improve their services. But it is also important for your own organisation. Maybe what needs to be improved is not, say, the functionality of Microsoft Teams, but the template, the training or the support that the organisation offers.

The “old school” feedback options in Office only send feedback to Microsoft. But in Teams the feedback forms states: “By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data.”. This ends up in the Admin Center > Health > Product feedback; see Learn about Microsoft feedback for your organization.

Of course you should not only collect feedback, but analyse it an take action based on the feedback. Solve the issues that are flagged in the feedback and keep up what works well.

This is crucial for proper governance of Microsoft 365, or anything else: to ensure that is works and keeps working effectively, smoothly and safely. It is also crucial to help users to adopt the toolkit: make it their own. It allows the users to help you to help them, because they can tell you what works and what does not work in practice. And it also allows the users to feel and really be involved in the evolution of the environment, so that we are all in this together and we can make it work togehter.

July 31, 2021

What about the firstline workers?

Filed under: Digital Workplace,Microsoft 365 — Tags: , — frederique @ 22:40

These days, we are all doing our best to provide employees with a great digital workplace, so that they can work from anywhere. This has been particularly important during the pandemic, when many of us worked from home. But of course this is only true for the knowledge workers or office employees. Firstline workers or frontline workers do real life jobs, which they cannot do from home. And they hardly get any attention when it comes to the digital transformation.

What do we mean by firstline workers

I am not trying to give a watertight definition of firstline workers, or frontline workers as they are also called. But basically, they are the people who in many organizations do the real work, in the real world. As opposed to the people who work on a computer all day.

Microsoft says: “Frontline workers are employees whose primary function is to work directly with customers or the general public providing services, support, and selling products, or employees directly involved in the manufacturing and distribution of products or services.”

So firstline workers are, for example:

  • In retail, the cashiers and people on the shop floor, whose job it is to help the customers.
  • In hospitals, the nurses who spend most of their days taking care of patients.
  • In a construction company, the carpenters and other people who actually construct the houses.
  • In maintenance organizations, the mechanics who go out and fix machines.

As opposed to the people who mostly work on a computer:

  • Staff in HR, Finance and of course IT who support the business
  • People like managers, project leaders, planners, calculators, coordinators who need to make sure that they firstline workers can do their job helping customers or patients in the real world, or building and maintaining real world things.

Ok, of course in other organizations – like the consultancy company where I work – just about everybody is an office worker. We all work on a computer most of the day. Many of us work with our clients a lot, but as far as I am concerned that does not make use firstline workers. Why do I say that? Because it would confuse the issue.

Why am I talking about the firstline workers now

In domains like retail, manufacturing and construction, about 70-80% of the employees are ‘real life’ firstline workers. And about 70-90% of the digital transformation efforts focus on the few office workers. The firstline workers are left out.

Of course, if your main tool is for instance a hammer, rather than a computer, a digital transformation would impact you less. But if you are passed over entirely, you will miss out. For example:

  • You may miss essential communication and be left out of the loop when the office workers are engaged.
  • You may not get staff support quickly and easily.
  • You may not have the right and up-to-date information at your fingertips, which you need to do your job.

Some lessons I learned

While I was working for a construction and maintenance company, I mostly worked for and interacted with office workers. Of course. But I did talk to some firstline workers and office workers who were the first line behind the firstline workers. So here the firstline workers are not the ones who are in direct contact with the customer, but the people who build the product. Their primary tool is, for example, a hammer. Not a computer, although some had an account and a computer or smartphone.

Here are some things I learned. Of course these also apply to office workers, and there are some very computer savvy hobbyist firstline workers. But nevertheless, you need to introduce new digital offerings even more carefully to your firstline workers.

  • Think carefully what the different groups of firstline workers need
    For example, the carpenters working at the construction site for a new building will get their news in the shed from the bulletin board pinned to the wall and from their foreman, so they may not want a digital news channel. But maintenance engineers who drive all over the country by themselves need to get their news in another way. Some carpenters like to consult the plans on an iPad, because then they can zoom in. But they find it easier to compare plans on paper, because that does not work on the small tablet screen.
    So find out what the firstline workers need and how digital tools could help. If an app can help them, develop it. If the old-school paper & word of mouth solution works best, fine.
  • Don’t offer digital stuff as an added burden. Make it useful for them
    I talked to a carpenter who had a laptop just for his timesheets. He did not want to fill in his timesheets anyway – nobody likes that – and now he got this annoying laptop to make it even worse than it was when he did it on paper. A maintenance engineer was grumbling that he got a new app to administer the work he did for each client. The administration was getting more extensive and complicated and he just wanted to fix the machines he was assigned. Then what’s in it for them?
    So if you give firstline workers digital tools, make sure you are not burdening them with additional administration and complications just to make the lives of others easier. Something needs to be in it for them too.
  • Do not assume that they will understand the digital stuff you offer.
    In that organization, IT decided everybody had to install Office Pro Plus on their computers themselves and activate Multi-Factor Authentication (MFA), based on a few instructions. This caused problems for many office workers, but the firstline workers I talked to were completely at a loss. One guy was a great carpenter, but he got stuck when he had to set up MFA and I tried to help him out. First of all, I called him back in the evening, when he could use the computer his wife has for Facetiming with the grandchildren, so that he could see the screen with the settings properly. And then it turned out he did not know his Office 365 password. Oops…
    So if the firstline workers have to do something digital, make sure they get adequate help, as in: help that really helps them and not a document with some complicated instructions.
  • Make the digital stuff as easy as possible
    The firstline workers are outside in the rain at a construction site, in the bowels of some big machine covered in grease, on the shop floor with their hands full. And they want to get on with building the house, fixing the machine or stacking the shelves. Not necessarily optimal circumstances to fiddle with digital tools.  
    So don’t make them install things that can be installed automatically, make apps super user-friendly and optimize them for the devices and network conditions they have at their disposal.

I am glad that we start looking at and talking about the needs of the firstline workers. I am very much a knowledge worker myself – don’t give me a hammer, as I will probably hit my thumb. But talking to firstline workers who got mangled under IT’s rollout of Office 365 made it clear to me that we can’t just ignore their needs. Microsoft has also made this step: see Microsoft 365 for frontline workers. Now let’s see what we can do to make their jobs easier, safer and more pleasant.

April 30, 2021

Teams Meetings are getting more and more user friendly

Filed under: Microsoft 365,New world of work — Tags: , — frederique @ 15:37

Nowadays, I spend a a large fraction of my week in Teams Meetings. I am meeting online with colleagues, clients and even fellow enthusiasts in non-work seminars. The meetings can be one-on-one, in small groups or in large groups. So I am happy that the tools to conduct such meetings keep improving, even though we all have to live through glitches sometimes.

Recently, Microsoft has added some options to Teams that I like: live reactions, dynamic view and PowerPoint live. Let’s take a look.

Live reactions

Especially in large meetings, with many people, live reactions are a nice way to give feedback in a compact but very visible way.

  • As an attendee, I like the way I can express my admiration, for example, without cluttering up the chat conversation.
  • And as a presenter, I like getting immediate feedback, even though I cannot keep an eye on the details of the chat. Then at least I know that my attendees haven’t all fallen asleep or left to grab some coffee.

Interestingly, the live reaction options only include positive sentiments. There is no button to shout “Boo!” Maybe Microsoft assumes that only great presenters will present in Teams, or that only charitable people attend them…

On the other hand, Microsoft used a different tool than Teams for the recent Ignite conference. There we did have a thumbs down icon for live reactions. Unfortunately, that button was placed right next to the switch for closed captioning. So in the discussion we saw a lot of questions why there were so many thumbs-down, and apologies from people who accidentally pressed that button. So maybe it is safer not to have a thumbs down option in Teams.

Dynamic view

In an online meeting, we often try to keep an eye on several things at once, including:

  • The information that is being presented. In my case, this is usually the desktop I share to show functionality, or a PowerPoint slide deck.
  • The video feed of the presenter. I am by no means a movie star, but I always switch on my webcam when I am presenting, because that makes my presentation more personal and easier to follow for the attendees.
  • Video feeds of other participants. When we attend a big meeting, we usually switch off all video feeds except the presenter’s, to avoid overloading the network and the tool. But in small-scale interactive meetings, seeing each other in the video feeds does make the discussion more lively and clear.
  • The chat, especially if it is not possible for (some of) the attendees to unmute their microphone and contribute directly. This is the case in large meetings, where this would result in a mess, but also in meetings with people that are in a very noisy room or – on the contrary – in a room where they are not allowed to make any noise speaking.

So it is important that all of the relevant elements are combined efficiently within the Teams meeting screen.

The Dynamic View that recently appeared in our tenant does just that, in a clearer and smarter way than before. For example, it displays the video feeds on the right hand side of the screen. Until you open the chat pane in that location, and then the video feeds move to the top of the screen.

The information that I want to share – the PowerPoint presentation or the demo – stays at the center of the stage. When I open the meeting up for discussion, I usually stop sharing, so that the video feeds take center stage and we can see each other more clearly during the discussion.

PowerPoint Live

In some meetings, I do most or all of my presentation with a PowerPoint slide deck. The interface for sharing a PowerPoint presentation in a Teams Meeting has been improved recently as well. It is called PowerPoint Live.

When I explicitly share a PowerPoint presentation in the Teams Meeting, the attendees see the slide I am talking about. But as the presenter, I also see my notes about that slide to the side, and thumbnails of the neighbouring slides at the bottom. And the thumbnails of the video feeds at the top. It is clear to me what is shared (namely: that slide), because it has the same red line around it as my screen has, when I share that.

One thing that does not work yet, in PowerPoint Live: animations to transition between slides and build up the elements on the slides. Sometimes the animations work, but most of the time everything gets dropped on the page all at once. When you backtrack, using the back button, the elements do disappear one by one, but I wanted them to appear one by one when I move forward. Oh well, it will be fixed soon, probably.

 

So the experience in our online meetings is improving all the time. Partly because we are getting better at them, but also because the tooling is getting better. We haven’t seen all of the improvements announced by Microsoft at Ignite in March yet, but we are seeing more and more of them. Hopefully more if the goodies will arrive soon, from What’s New in Microsoft Teams | Microsoft Ignite 2021.

February 28, 2021

Microsoft 365 Learning Pathways: some lessons learned

Filed under: Adoption,Microsoft 365 — frederique @ 23:59

Microsoft 365 offers a lot of applications that can help our users get their jobs done. But in order to take full advantage of the tooling, they need to understand what the possibilities are and how it all works. So we want to provide our users with an information portal, where they can find that out. But Microsoft 365 evolves all the time: new applications are added, existing applications are improved and expanded, new connections are added, tying these applications together. So how do we keep that information up-to-date?

We used to set up information portals and fill them with relevant content, but it is rather time-consuming to keep those up-to-date. It usually came down to one person managing the site. And when that one person leaves the company or gets another role, the information portal starts to fossilize…

Microsoft Learning Pathways helps us to outsource a lot of that work to Microsoft: they update the toolkit, and they update the information about the toolkit. See also Microsoft’s documentation Microsoft 365 learning pathways. I’m setting up Microsoft Learning Pathways for some clients, so let’s take a look at some lessons I learned when I got down it.

1.It is an information portal, rather than Learning Management System

When I started talking about Microsoft 365 Learning Pathways with HR people who are really in the learning business, they had expectations based in the name, that it would be a full Learning Management System, with courses, testing, tracking, certification and everything. It’s not.

Microsoft 365 Learning Pathways is more like an information portal, where you can find information about the applications and instructions on how to use them. Users consult the portal when they want to learn something.

So it went down a lot better when I called it an information portal. It actually is based on the Communication Site template, so it looks like the other information portals that we had in our environment.

Microsoft 365 Learning Pathways home page

Microsoft 365 Learning Pathways home page

2.The learning content is hierarchically structured with reusable assets

The content is organised in a structure that is mostly hierarchical, though the actual content can be used in different branches of that topic tree. The high-level structure is fixed, but we can add lower levels ourselves. 

The M365 Learning Pathways structure of Categories, Subcategories and Playlists

The M365 Learning Pathways structure of Categories, Subcategories and Playlists

  1. All of the information offered in Microsoft 365 Learning Pathways is organised in three main Categories for the end-usersGet started, Scenarios, ProductsPlus a category Adoption tools that is more geared towards Owners.
    We cannot add our own category.
  2. Within those Categories, we have Subcategories: the different scenarios and different products, like SharePoint.
    We can add our own Subcategories
    This hierarchy is strict: each Subcategory belongs to only one Category. 
  3. Within the Subcategories, we have Playlists. For example: Intro to SharePoint OnlineShare and sync with SharePoint. 
    We can add our own Playlists
    This hierarchy is strict: each Playlist belongs to only one Subcategory. We can create a copy of a Playlist to include it in another Subcategory though. 
  4. Within the Playlists, we have Assets. For example: What is SharePointFind and follow sites and news. The Assets contain the actual content
    We can add our own Assets.
    We can re-use an Asset in as many Playlists as we want.

The M365 Learning Pathways structure: the Playlists contain Assets.

The M365 Learning Pathways structure: the Playlists contain Assets.

3.The M365 Learning Pathways web part displays the content

What makes it the Learning Pathways instead of just a regular Communication site is the Learning Pathways web part that displays the actual learning content to the users.

As a user, you an browse the playlists: click on a playlist to open it and then browse the asset using the Next button or the pulldown menu.
Please note: we’ve experienced that not all users see that they can navigate through the playlist. So we have added a line of instruction at the top of the web part.

Browse the Assets in the Playlist using the Next button or the menu.

Browse the Assets in the Playlist using the Next button or the menu.

As the owner, you configure what you want to display on a particular page: the top level allowing the users to drill down the categories, subcategories and playlists. Or maybe a particular Playlist or even one Asset.

Configuring the M365 Learning Pathways web part to display the top level.

Configuring the M365 Learning Pathways web part to display the top level.

Configuring the M365 Learning Pathways web part to display a particular Playlist.

Configuring the M365 Learning Pathways web part to display a particular Playlist.

4.The Assets are bite-sized pieces of content stored elsewhere 

The Assets with the actual content consist of introductory videos and instruction videos of maximum a few minutes each, plus a short text version of the instructions. Some Assets are text only. By the way, the videos do not all have the same style: some have a voice-over, others do not talk but give their explanation in written text labels.  

Each Asset is a URL in the catalogue. Either in the portal, elsewhere in your Microsoft 365 environment or elsewhere on the internet. The standard content provided by Microsoft all lives on the internet, at https://support.office.com 

5.The content gets updated quarterly by Microsoft 

Microsoft updates the content four times a year; they don’t have fixed dates. For example, they will announce a list of content updates next week during Ignite (March 4th 2021) via Driving Adoption – Microsoft Tech CommunitySo the information about new features does not become immediately available in Learning Pathways. We have to wait for the next update. 

When the content is updated, it gets streamed to our Learning Pathways automatically. Not need to pull it in, because the Microsoft’s content lives on their site. 

6.Standard Playlists don’t work for us, so we use custom Playlists 

You can use the standard Microsoft Playlists offers in the catalogue. However, we found that they did not work for us. Usually we want to add something, remove something, change the sort order, change a title. And you cannot change anything in a standard Playlist. 

So we create custom playlists, often starting from a copy of a standard Playlist. In a custom Playlist, you determine the details of the Playlist as a whole, like the title, the summary and the image. Please note: you can select the level and audience, but you cannot add any choices. That is a pity, because most audiences don’t make sense to innocent users. 

A custom Playlist, with some standard Assets and custom Assets.

A custom Playlist, with some standard Assets and custom Assets.

In the custom Playlist, you can search for and add existing Assets.  

Add existing Assets to the custom Playlist: standard Assets and custom Assets.

Add existing Assets to the custom Playlist: standard Assets and custom Assets.

Or you can add your own Assets: add a title and a URL, for example of a page created in the portal. The custom Assets are indicated with the people icon in the Playlist.

A custom Asset: a page created in the same portal.

A custom Asset: a page created in the same portal.

7.Microsoft has more Assets than you can find in the catalog 

I could not find everything I needed in the catalogue. Fortunately, Microsoft has more Assets online, so I did not have to create the content myself. 

So, yes: Microsoft 365 Learning Pathways is very helpful. But is not “automagically” providing us a learning portal that meet our needs with one push of the button. We still have to do some manual work. 

Powered by WordPress