Robert Wetting

Information & Communications Technology

Office 365 SharePoint SharePoint Online Office 365 SharePoint Productivity Office 365 Office 365 Governance Microsoft Teams SharePoint user adoption Change Management Digital Workplace Digital Transformation Microsoft 365 Microsoft Microsoft Office365

Leeuwarden, Friesland, Netherlands

Robert Wetting

CEO and consultant Onz365

Robert is a Microsoft 365 Adoption consultant, Functional business consultant and the founder of Onz365. I help clients to get most out of their Microsoft 365. To fully use the possibilities of the Microsoft 365 platform, user adoption is the key to success. 20% of an implementation is technical, 80% is about changing organizational culture and working methods. Robert helps companies to successfully adopt Microsoft 365, with unconventional methods based on the Prosci ADKAR model.

He recentlys worked on projects for the The Directorate-General for Public Works and Water Management, Province of Fryslân, Province of Flevoland, Municipality of Almere, Municipality of The Hague, NHL Stenden University of Applies Sciences and Groningen Seaports. 

Current sessions

Will my M365 implementation ever be ready? The Amsterdam Information Model might help you out!

I regularly receive the question: When is a Microsoft 365 implementation complete? This is obviously a subjective question and it varies from organization to organization.
Is there perhaps a checklist for this? Using the Amsterdam Information Model by Rik Maes, we are going to make a checklist to determine when an implementation at your organization could be complete.
From the perspective of business, information/communication and technology we will look at three levels to see which topics could be covered.
This may sound boring, but through an interactive session we will discuss the topics and see if the participants recognize this in their daily work.

How your executive sponsor and his management team are going to hurt your Teams project

After months of hard work, your Teams project is live! The Teams and it's SharePoint sites are a co-creation of your projectteam's expertise and business requirements. Champions and key users helped you to built a solution based on the user voice of the organization. You even tested and ran a pilot with a selection of end users. Here the first problems emerge. Despite all your efforts and some enthusiastic champions, the pilot is failing. End users aren’t using the tool and don’t feel the urge to start. Now it’s impossible to get best practices. And you didn’t even start implementing SharePoint in the organization. Sounds familiar?
Of course you’re aware of the important role of sponsors in projects like these, so you started yours by finding one. From the beginning your sponsor supports the project and makes the right funds available. In this interactive presentation we’ll discuss the role of sponsors and the way they can harm your project (despite their initial support), ways to identify potential problems and take the right (counter)measures. The role SharePoint can play in this process we’ll highlight as well.

Completing Microsoft Teams implementations after Covid has gone

With the arrival of the Covid epidemic, suddenly what we had not thought possible for years became possible.
Teams and SharePoint sites were introduced and accepted in a short time where in the past it often took a lot of time. Because we worked from home there was less time and attention for the individual knowledge and skills of the employees. Now that we are going back to the office we need to fix or bring things in order for which there was no time during the Covid epidemic.
In this presentation I will show how Teams and SharePoint can still be implemented with the human touch.

10 Non technical pitfalls that will make your Microsoft 365 implementation fail

As Microsoft itself often says, only 30 percent of a Microsoft 365 implementation is about technology. The remaining 70 percent is about people.
About the employees and the processes they carry out. When discussing failed Microsoft 365 projects, we often talk about technical reasons.
However, there are many non-technical reasons why a Microsoft 365 project ultimately fails.
In this presentation, I will show you 10 pitfalls that will cause your Microsoft 365 project to fail without any technology involved.