When Informal Tools Reached Their Limit:
Communication Tool Migration & Change Management for a Distributed Workforce
This case examines how a phased tool migration and deliberate change management approach redesigned communication without breaking delivery.
Fragmented Communication at Scale
A partner organisation relied on a large freelance workforce coordinated primarily through a well known chat tool. Over time, communication had spread across multiple disjointed workspaces and channels, many of which were poorly documented and difficult to govern.
Questions were frequently lost, repeated, or misunderstood. Knowledge was scattered across private messages and channels with unclear ownership. Critically, the chat tool sat entirely outside the partner’s core web application, creating a separation between work and communication that increased friction and risk.
As scale increased, so did concern around data control, transparency, and efficiency.
Why the Status Quo Became a Risk
Several issues made continued reliance on Slack untenable:
-
Data leakage was increasingly unavoidable across unmanaged workspaces
-
Important questions and blockers were difficult to track or audit
-
Unnecessary communication slowed down actual productive work
-
Leadership lacked visibility into recurring issues raised by freelancers
-
Knowledge gaps and performance issues were obscured rather than surfaced
Without intervention, these problems would persist and compound as the workforce grew.
"As scale increased, informal communication created risk, inefficiency, and blind spots"
Why Change Had Failed Before
Previous attempts to rationalise or replace the chat tool had stalled.
No one had a complete picture of how many workspaces existed, which contracts or accounts they belonged to, who had access to what, or what the true cost was. Ownership was unclear, dependencies were poorly understood, and there was no confidence in what would break if changes were made.
From a technical perspective, the setup was deeply complex. From a human perspective, freelancers were comfortable with the chat tool and resistant to change, particularly when alternatives were perceived as more restrictive.
This combination of technical sprawl and behavioural resistance is why the problem had remained unresolved.
The Mandate
The brief was simple on the surface: get rid of the chat tool.
In practice, the constraints were significant. Communication could not be disrupted, costs needed to be reduced rather than increased, and any new tooling had to work within real platform limitations. A failed rollout would risk halting day-to-day operations.
The real task was not tool replacement, but redesigning how communication worked at scale.
The Real Problem Beneath the Tool
The chat tool was not just a messaging platform. It had become a proxy for several unresolved operational issues.
Open, unstructured communication made it easy for freelancers to bypass approved sources of information, increasing noise and reducing utilisation. Time spent asking repetitive questions displaced time spent on actual work.
Because communication was unstructured, it was impossible to systematically identify where knowledge was missing, which workflows were unclear, or where ownership was breaking down. This prevented any meaningful continuous improvement loop.
Replacing Slack without addressing these dynamics would simply recreate the same problems in a new tool.
Redesigning Communication, Not Just Migrating It
Before implementing anything, we assessed communication needs through surveys, focus groups, and a review of freelancer responsibilities.
Based on this, we designed structured communication flows within Intercom that prioritised self-service and clarity. Freelancers were guided through multiple-choice pathways that surfaced relevant information before allowing direct contact with leads. Free-text communication remained available, but within a framework that reduced unnecessary escalation.
This structure made communication intentional rather than reactive.
A Phased Rollout Built for Safety
The rollout was deliberately phased.
Intercom was soft-launched to a subset of freelancers while Slack remained available as a fallback. During this phase, we collected usage data, identified routing issues, and refined chat flows based on real behaviour rather than assumptions.
Slack served as a safety net. If anything failed, freelancers could revert immediately, and the test group could be re-onboarded without disruption. Only once confidence was high was Slack gradually decommissioned.
This approach also enabled A/B-style testing, allowing decisions to be grounded in evidence rather than opinion.
Managing Change with a Distributed Workforce
Change management was treated as a first-class concern.
Freelancers were given advance notice, clear documentation, verbal walkthroughs, and repeated opportunities to provide feedback. Where feedback highlighted real friction or gaps, changes were made. Where it conflicted with organisational goals, the reasoning was explained transparently.
Crucially, there was always a visible backup plan. This reduced anxiety and resistance, even among those initially opposed to the change.
Impact at a Glance:
• Migrated approximately 300 freelancers from Slack to in-app messaging
• Consolidated fragmented workspaces into a single governed communication system
• Reduced unnecessary communication and improved utilisation
• Eliminated unmanaged data exposure across external workspaces
Impact and Results
The transition completed without major incidents.
Communication became cleaner, more consistent, and measurable. Unnecessary messaging declined, and the right issues reached the right people more reliably. Built-in analytics made it possible to identify recurring problems and improve documentation and workflows over time.
From a user experience perspective, freelancers no longer needed to manage a separate tool in a different tab. Communication was embedded directly into the work environment.
From a security and governance perspective, data leakage risk was significantly reduced, and communication standards could be enforced consistently.
Why This Matters
Tool migrations fail when they focus on technology instead of behaviour.
This case demonstrates that successful change requires preparation, clear ownership, phased execution, and a genuine openness to feedback. Moving too fast, ignoring resistance, or underestimating operational complexity introduces unnecessary risk.
When communication is designed deliberately, it becomes a lever for efficiency, control, and continuous improvement rather than a source of noise.
When Growth Broke Delivery