Hybrid Work Policy
& Tooling Audit

The Situation

Like a lot of organizations, this client built their remote work stack under pressure in early 2020 — fast decisions, minimal evaluation, and no one asking whether the new tools would conflict with what was already in place. Two years later, they were paying for Microsoft 365 (with Teams), a legacy Zoom contract that renewed automatically, and Google Workspace that one department had adopted independently and refused to give up.

When we came in, their IT director's biggest complaint wasn't the tools — it was that nobody knew which tool to use for what. Staff were holding meetings across three platforms depending on who sent the invite. Files existed in SharePoint, Google Drive, and a shared server drive. And the shadow IT Slack workspace, with over 40 active users, was running business-critical conversations entirely outside IT visibility or data retention policy.

The Challenge

• Three active video conferencing contracts billing concurrently — Teams, Zoom, and Google Meet via Workspace
• Two primary file storage platforms in active use with no clear owner or governance: SharePoint and Google Drive
• A shadow IT Slack workspace with 40+ active users and business-critical channels, unknown to IT leadership
• No written policy stating which tools were approved for which purposes
• Significant annual spend on tools with measurably low adoption rates
• Upcoming Microsoft 365 renewal with no internal consensus on whether to expand, downgrade, or switch

The Approach

This kind of engagement is as much organizational as technical. The tooling decisions were straightforward — the harder work was understanding why people had reached for different tools in the first place, and making sure the consolidation didn't just create new friction.

• Discovery interviews: Met with department leads and frontline staff (not just IT) to understand actual workflows — which meetings they were using which platform for, where files actually lived when they needed them fast, and what the shadow Slack was actually being used for. Turned out it was primarily program staff coordinating around a tool they found easier than Teams.
• Usage data pull: Pulled admin console analytics from all three platforms — active users, meeting counts, storage consumption, licensing utilization. Most Teams licenses were provisioned but unused; Zoom was actively used by about 30% of staff; Google Meet was almost never opened.
• Contract review: Reviewed all SaaS agreements, auto-renewal terms, and per-seat costs. Identified the exact renewal dates and minimum cancellation notice windows — two contracts had auto-renewed already; one was still in the notice window.
• Consolidation matrix: Built a tool-by-tool keep / migrate / cut recommendation with rationale, cost delta, and migration effort estimate. Recommended consolidating on Microsoft 365 with Teams as the single video platform, migrating Google Drive content to SharePoint, and formally adopting Slack by migrating to an IT-administered workspace.
• Change management sequencing: Wrote a phased rollout plan that prioritized the low-effort cuts first (cancelling Google Workspace at next renewal), gave program staff lead time before the Slack migration, and included a communication template for announcing each change to staff.