<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Collaboration |</title><link>https://chriswait.ing/tags/collaboration/</link><atom:link href="https://chriswait.ing/tags/collaboration/index.xml" rel="self" type="application/rss+xml"/><description>Collaboration</description><generator>HugoBlox Kit (https://hugoblox.com)</generator><language>en-us</language><lastBuildDate>Fri, 01 May 2026 00:00:00 +0000</lastBuildDate><image><url>https://chriswait.ing/media/icon_hu_1c0e9cb08cfb822a.png</url><title>Collaboration</title><link>https://chriswait.ing/tags/collaboration/</link></image><item><title>Teams Rooms and Meeting Collaboration Support</title><link>https://chriswait.ing/projects/teams-rooms-collaboration/</link><pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate><guid>https://chriswait.ing/projects/teams-rooms-collaboration/</guid><description>&lt;p&gt;Meeting spaces need to be dependable for people who simply want to join a meeting and collaborate without troubleshooting the room first.&lt;/p&gt;
&lt;h2 id="scope"&gt;Scope&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Support Microsoft Teams meeting room workflows and user experience&lt;/li&gt;
&lt;li&gt;Assist with room calendar and Exchange resource mailbox behaviour&lt;/li&gt;
&lt;li&gt;Troubleshoot invitations, lobby access, room displays and meeting joins&lt;/li&gt;
&lt;li&gt;Contribute to meeting room hardware planning and deployment decisions&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="practical-focus"&gt;Practical Focus&lt;/h2&gt;
&lt;p&gt;My focus is reducing complexity for users while ensuring room accounts, meeting processes and hardware work together reliably, especially where sessions include multiple locations or organisers.&lt;/p&gt;
&lt;h2 id="ongoing-value"&gt;Ongoing Value&lt;/h2&gt;
&lt;p&gt;Well-supported collaboration spaces reduce meeting disruption and make hybrid work easier for both onsite and remote participants.&lt;/p&gt;
&lt;h2 id="key-lesson"&gt;Key Lesson&lt;/h2&gt;
&lt;p&gt;Meeting-room technology is most successful when the configuration and the user workflow are equally simple.&lt;/p&gt;</description></item><item><title>SharePoint Administration and Access Governance</title><link>https://chriswait.ing/projects/sharepoint-administration/</link><pubDate>Sun, 01 Feb 2026 00:00:00 +0000</pubDate><guid>https://chriswait.ing/projects/sharepoint-administration/</guid><description>&lt;p&gt;Ongoing SharePoint Online administration for a nonprofit environment where collaboration needs to remain simple while access stays appropriate and understandable.&lt;/p&gt;
&lt;blockquote class="border-l-4 border-neutral-300 dark:border-neutral-600 pl-4 italic text-neutral-600 dark:text-neutral-400 my-6"&gt;
&lt;p&gt;Public case study note: internal site names, groups and permission details have been deliberately excluded.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="scope"&gt;Scope&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Support users with SharePoint and OneDrive document access issues&lt;/li&gt;
&lt;li&gt;Review and simplify permissions where appropriate&lt;/li&gt;
&lt;li&gt;Help maintain appropriate access for restricted content areas&lt;/li&gt;
&lt;li&gt;Improve user understanding of document storage and collaboration&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="approach"&gt;Approach&lt;/h2&gt;
&lt;p&gt;Permission issues are not always solved by granting more access. I first identify the user&amp;rsquo;s actual requirement, review how the content is meant to be shared and favour manageable group-based access wherever possible.&lt;/p&gt;
&lt;h2 id="ongoing-value"&gt;Ongoing Value&lt;/h2&gt;
&lt;p&gt;Clearer permission structures reduce support friction, improve confidence in shared content and make future administration easier.&lt;/p&gt;
&lt;h2 id="key-lesson"&gt;Key Lesson&lt;/h2&gt;
&lt;p&gt;Effective SharePoint administration depends on governance that remains practical for real users, not only technically correct permissions.&lt;/p&gt;</description></item></channel></rss>