Congratulations!

[Valid RSS] This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: http://blog.frederique.harmsze.nl/feed/

  1. <?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
  2. xmlns:content="http://purl.org/rss/1.0/modules/content/"
  3. xmlns:wfw="http://wellformedweb.org/CommentAPI/"
  4. xmlns:dc="http://purl.org/dc/elements/1.1/"
  5. xmlns:atom="http://www.w3.org/2005/Atom"
  6. xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  7. xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
  8. xmlns:georss="http://www.georss.org/georss"
  9. xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
  10. >
  11.  
  12. <channel>
  13. <title>blog.frederique.harmsze.nl</title>
  14. <atom:link href="http://blog.frederique.harmsze.nl/feed/" rel="self" type="application/rss+xml" />
  15. <link>http://blog.frederique.harmsze.nl</link>
  16. <description>my world of work and user experiences</description>
  17. <lastBuildDate>Wed, 31 May 2023 20:59:39 +0000</lastBuildDate>
  18. <language>en-GB</language>
  19. <sy:updatePeriod>
  20. hourly </sy:updatePeriod>
  21. <sy:updateFrequency>
  22. 1 </sy:updateFrequency>
  23. <generator>https://wordpress.org/?v=5.8.2</generator>
  24. <site xmlns="com-wordpress:feed-additions:1">56628874</site> <item>
  25. <title>Development training and guidance go hand in hand</title>
  26. <link>http://blog.frederique.harmsze.nl/2023/05/development-training-and-guidance-go-hand-in-hand/</link>
  27. <dc:creator><![CDATA[frederique]]></dc:creator>
  28. <pubDate>Wed, 31 May 2023 20:59:39 +0000</pubDate>
  29. <category><![CDATA[Adoption]]></category>
  30. <category><![CDATA[SharePoint]]></category>
  31. <guid isPermaLink="false">http://blog.frederique.harmsze.nl/?p=2200</guid>
  32.  
  33. <description><![CDATA[Recently I again saw the importance of the integrated and user centric approach in the development of, in this case, a SharePoint site template for complex document management and collaboration. The consultants from the different disciplines need to work closely each other and with the key users from the business, to achieve the best template [&#8230;]]]></description>
  34. <post-id xmlns="com-wordpress:feed-additions:1">2200</post-id> </item>
  35. <item>
  36. <title>Just send people to a standard SharePoint training?</title>
  37. <link>http://blog.frederique.harmsze.nl/2023/04/just-send-people-to-a-standard-sharepoint-training/</link>
  38. <dc:creator><![CDATA[frederique]]></dc:creator>
  39. <pubDate>Wed, 26 Apr 2023 22:37:11 +0000</pubDate>
  40. <category><![CDATA[Adoption]]></category>
  41. <category><![CDATA[SharePoint]]></category>
  42. <guid isPermaLink="false">http://blog.frederique.harmsze.nl/?p=2195</guid>
  43.  
  44. <description><![CDATA[Recently, I was asked with a colleague to just give a standard SharePoint training to a business unit. Ok, we understand that these people need to learn about SharePoint, but maybe we need to do more than just go there and deliver a standard training. Maybe even some simple things. Before you send an invitation, [&#8230;]]]></description>
  45. <post-id xmlns="com-wordpress:feed-additions:1">2195</post-id> </item>
  46. <item>
  47. <title>But do people know about it?</title>
  48. <link>http://blog.frederique.harmsze.nl/2023/02/but-do-people-know-about-it/</link>
  49. <dc:creator><![CDATA[frederique]]></dc:creator>
  50. <pubDate>Tue, 28 Feb 2023 18:55:22 +0000</pubDate>
  51. <category><![CDATA[Adoption]]></category>
  52. <guid isPermaLink="false">http://blog.frederique.harmsze.nl/?p=2190</guid>
  53.  
  54. <description><![CDATA[Build it and they will come? Well, that depends. Do the prospective users actually know what you built, where they can find it and what it is good for? Seems obvious, but I have noticed that it is not.]]></description>
  55. <post-id xmlns="com-wordpress:feed-additions:1">2190</post-id> </item>
  56. <item>
  57. <title>User manual: instruction pages in a SharePoint help site</title>
  58. <link>http://blog.frederique.harmsze.nl/2023/01/user-manual-instruction-pages-in-a-sharepoint-help-site/</link>
  59. <dc:creator><![CDATA[frederique]]></dc:creator>
  60. <pubDate>Tue, 31 Jan 2023 19:56:56 +0000</pubDate>
  61. <category><![CDATA[Adoption]]></category>
  62. <category><![CDATA[SharePoint]]></category>
  63. <guid isPermaLink="false">http://blog.frederique.harmsze.nl/?p=2186</guid>
  64.  
  65. <description><![CDATA[Many employees who need to change the way they work and adopt new tooling, like to get a user manual. Clear instructions on how to do things, that are easy to find and check when they are unsure. So in a project, the client requests that user manual. What they often envision, is a PDF file or even a printed booklet. But we prefer to offer something different. A SharePoint site with instruction pages.]]></description>
  66. <post-id xmlns="com-wordpress:feed-additions:1">2186</post-id> </item>
  67. <item>
  68. <title>Best wishes for 2023</title>
  69. <link>http://blog.frederique.harmsze.nl/2022/12/best-wishes-for-2023/</link>
  70. <dc:creator><![CDATA[frederique]]></dc:creator>
  71. <pubDate>Sat, 31 Dec 2022 13:35:29 +0000</pubDate>
  72. <category><![CDATA[Uncategorized]]></category>
  73. <guid isPermaLink="false">http://blog.frederique.harmsze.nl/?p=2180</guid>
  74.  
  75. <description><![CDATA[I wish you all the best for a happy and healthy new year.]]></description>
  76. <post-id xmlns="com-wordpress:feed-additions:1">2180</post-id> </item>
  77. <item>
  78. <title>Adopting a new intranet</title>
  79. <link>http://blog.frederique.harmsze.nl/2022/11/adopting-a-new-intranet/</link>
  80. <dc:creator><![CDATA[frederique]]></dc:creator>
  81. <pubDate>Wed, 30 Nov 2022 20:10:39 +0000</pubDate>
  82. <category><![CDATA[Adoption]]></category>
  83. <category><![CDATA[intranet]]></category>
  84. <guid isPermaLink="false">http://blog.frederique.harmsze.nl/?p=2174</guid>
  85.  
  86. <description><![CDATA[When I started working for my current employer, back in the day, I was hired in the SharePoint Competence Centre. We built intranets, in SharePoint 2003. We saw that slowly, organisations widened their definition of an intranet. It became more than a portal to publish information: a digital workplace with SharePoint Team Sites for collaboration. [&#8230;]]]></description>
  87. <post-id xmlns="com-wordpress:feed-additions:1">2174</post-id> </item>
  88. <item>
  89. <title>Leaders need to pivot in the hybrid world: Microsoft research</title>
  90. <link>http://blog.frederique.harmsze.nl/2022/10/leaders-need-to-pivot-in-the-hybrid-world-microsoft-research/</link>
  91. <dc:creator><![CDATA[frederique]]></dc:creator>
  92. <pubDate>Mon, 31 Oct 2022 17:56:49 +0000</pubDate>
  93. <category><![CDATA[Adoption]]></category>
  94. <category><![CDATA[New world of work]]></category>
  95. <category><![CDATA[Hybrid]]></category>
  96. <guid isPermaLink="false">http://blog.frederique.harmsze.nl/?p=2169</guid>
  97.  
  98. <description><![CDATA[Microsoft researched the question how hybrid is working for people and organization. They did a big survey and analysed the usage of Microsoft 365. Their key findings are that leaders need to send productivity paranoia, embrace the fact that people come in for each other and re-recruit their employees. ]]></description>
  99. <post-id xmlns="com-wordpress:feed-additions:1">2169</post-id> </item>
  100. <item>
  101. <title>Ambassador network</title>
  102. <link>http://blog.frederique.harmsze.nl/2022/09/ambassador-network/</link>
  103. <dc:creator><![CDATA[frederique]]></dc:creator>
  104. <pubDate>Thu, 29 Sep 2022 10:38:37 +0000</pubDate>
  105. <category><![CDATA[Adoption]]></category>
  106. <guid isPermaLink="false">http://blog.frederique.harmsze.nl/?p=2166</guid>
  107.  
  108. <description><![CDATA[We implement new technology and things like a new modern workplace. We try to help employees adopt it, to gain the benefits from it. But if we only address the users from a staff team at headquarters, the adoption will probably fail The new system needs to be embedded in the organization. And for that, [&#8230;]]]></description>
  109. <post-id xmlns="com-wordpress:feed-additions:1">2166</post-id> </item>
  110. <item>
  111. <title>Some notes on Miro boards</title>
  112. <link>http://blog.frederique.harmsze.nl/2022/08/some-notes-on-miro-boards/</link>
  113. <dc:creator><![CDATA[frederique]]></dc:creator>
  114. <pubDate>Wed, 31 Aug 2022 19:38:26 +0000</pubDate>
  115. <category><![CDATA[Adoption]]></category>
  116. <category><![CDATA[Miro]]></category>
  117. <guid isPermaLink="false">http://blog.frederique.harmsze.nl/?p=2158</guid>
  118.  
  119. <description><![CDATA[Yes, pun intended. I would like to share some of my notes with you, about Miro boards for digital sticky notes. We recently used a Miro board for brainstorming in a workshop with business representatives at a client. Bottomline is that it worked very nicely, but there were a few gotchas.]]></description>
  120. <post-id xmlns="com-wordpress:feed-additions:1">2158</post-id> </item>
  121. <item>
  122. <title>Little things: Employee centric communication</title>
  123. <link>http://blog.frederique.harmsze.nl/2022/07/little-things-employee-centric-communication/</link>
  124. <dc:creator><![CDATA[frederique]]></dc:creator>
  125. <pubDate>Sun, 31 Jul 2022 17:48:05 +0000</pubDate>
  126. <category><![CDATA[Adoption]]></category>
  127. <guid isPermaLink="false">http://blog.frederique.harmsze.nl/?p=2151</guid>
  128.  
  129. <description><![CDATA[When we introduce a new digital workplace or a new intranet, for example, we determine the approach to help the users adopt the new technology. Including the little things, like how we communicate with the representatives of the user groups. Make it easier for them to be engaged, and help them to help us.]]></description>
  130. <post-id xmlns="com-wordpress:feed-additions:1">2151</post-id> </item>
  131. </channel>
  132. </rss>
  133.  

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//blog.frederique.harmsze.nl/feed/

Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda