10% familiarity, 1,860 people to bring along
Only 10% of the team — office and offshore combined — had prior Slack experience. The rest would need training, support, and time, with resistance expected to be highest among older employees and offshore crews.
| Group | People |
|---|---|
| Office employees | 1,017 |
| Offshore crew | 843 |
| Total workforce | 1,860 |
| Already tech-adept (10%) | 186 |
| Actual target group for rollout | 1,674 |
Adoption doesn't move the same for everyone
Younger employees
Faster adapters, familiar with similar tech, mostly office-based (business dev, operations). Modeled adoption: 70–80%.
Older employees
More likely to resist, prefer email/WhatsApp, concentrated in protective services and admin roles. Modeled adoption: 40–50%.
Crew members
Face real connectivity and environmental constraints onboard/offshore, and need extra hands-on support. Modeled adoption: 50–60%.
Three scenarios, not one forecast
| Scenario | Avg. adoption | Core assumption |
|---|---|---|
| Pessimist | 35% | High resistance from older staff + offshore crew; training falls short |
| Realist | 55% | Moderate training effort, mixed results, some resistance persists |
| Optimist | 75% | Strong leadership push, incentive-driven training, minimal resistance |
Every scenario kept the same staggered rollout logic: office teams first, offshore crews roughly two months later, with dedicated 24/7 technical support built in for connectivity issues at sea.
Six predictable failure modes, six mitigations
| Risk | Mitigation |
|---|---|
| Split communications (teams stay on WhatsApp/email) | Clear transition timeline + company-wide Slack usage policy + department "Slack Champions" |
| Offshore connectivity problems | Offline access / message caching, infrastructure audit, "Slack Lite" for low-bandwidth use |
| Slow adoption among older staff | Tiered training by familiarity level, peer mentors, incentives for early adopters |
| Overwhelm from Slack's feature set | Step-by-step onboarding, bilingual (EN/ID) tailored guides, progressive feature rollout |
| Longer-than-expected transition | Phased implementation with clear milestones, pilot program before full rollout |
| Usage drop-off after initial push | Engagement metrics tracking, refresher training every 3–6 months, dedicated support channel |
What success was defined as
Rollout plan
Type: Consultancy Project · Level C2 · Maritime workforce (Wintermar), office + offshore