Enter password to view

 

Launch Workshop

Empowering Transformation
for SIL Global

Everything we need to align on to get your new internal comms platform live and thriving.

SIL Global · March 25, 2026 · Online

Today's Workshop

Three phases, one session.

1
Understand
Where you stand today, what you need, where the focus lies
2
Align
Walk through each workstream, discuss decisions and open questions
3
Plan
Define priorities, agree on next steps and cadence

Starting Point

What we know

The Organisation
  • 4,000+ people across 90+ nationalities, working in 80+ countries
  • Multilingual workforce. English is the default, but far from universal.
  • Structural transformation underway. New strategic goals, organisations with aligned missions joining under the SIL umbrella.
  • Growing diversity of backgrounds as new teams integrate
The Challenge
  • Cohesion, shared vision, alignment across an increasingly diverse workforce
  • Inform and inspire so everyone pursues the same goals and feels "We are SIL."
  • Enable cross-country and cross-department networking
  • Serve both static content (strategic plan, resources) and dynamic updates (Executive Director news, team stories)

Before we build

Comms Status Quo

Current landscape
  • Channels in use today email, intranet, Teams/Slack, WhatsApp, print?
  • What works well? Which channels actually reach people?
  • What doesn't? Where do messages get lost or ignored?
  • Audience segments office vs. frontline, HQ vs. field, leadership vs. all-staff
  • Content volume how much are you producing today? How frequently?
Goals for the new platform
  • Replace or complement? Is the app replacing existing tools or adding a new layer?
  • Primary use case top-down comms, community building, knowledge sharing, or all three?
  • Success vision what does "working well" look like 6 months after launch?
  • Stakeholder buy-in who needs to champion this internally?
  • Known constraints budget, timeline, IT capacity, political dynamics
Let's discuss

Walk us through a typical week of internal communications at SIL. What reaches everyone, and what falls through the cracks?

Key Question

Where does your workforce live?

The right channel mix depends on how your people work. Are they on the go, at a desk, or a mix of both?

Mobile App
Field teams, frontline workers, deskless staff. Push notifications, offline access, always in their pocket.
Web App
Desktop workers, browser-first teams. Full-screen experience alongside daily tools. No install required.
Email Digest
Low-tech reach. Automated summaries for those who won't install an app. Bridge to full adoption.
Let's discuss

What percentage of your staff works mobile vs. desktop? Where should the primary experience be?

Today's Agenda

Nine workstreams, one goal:
a successful launch.

1
Design & Branding
Your look and feel across all platforms
2
SSO & Authentication
How your users log in and sync
3
Privacy & Security
Data protection, compliance, and access control
4
Integrations
Technical setup, third-party services, and connectivity
5
Product Setup
App Config, Settings, Structure, Channels, Mixes
6
Content & Editorial
What to publish, how, and who does it
7
Adoption Campaign
Internal launch marketing and change management
→
Go Live
Phased user rollout across the organisation
8
Analytics & Success
Measuring what matters
9
Post-Launch & Optimisation
Ongoing reviews, benchmarks, and continuous improvement

Project Timeline

From kickoff to live in few weeks, not many months.

Iteration 1
Setup
Branding, SSO config, channel structure, user import
Iteration 2
Build
Content strategy, editorial workflows, feed configuration
Iteration 3
Test
Internal pilot, editor training, feedback rounds
Iteration 4
Refine
Implement learnings, customisation, iterate on feedback
Iteration 5
Launch
Phased rollout, communication plan, go-live
Let's discuss

What does your ideal timeline look like? Are there hard deadlines or events we should plan around?

Workstream 1

Design & Branding

What we need from you
  • Brand colors (primary, secondary, background) as HEX
  • Logo files (SVG preferred, PNG as fallback)
  • Brand font (.ttf file, licensed for app use)
  • App icon artwork (1024x1024px)
What we handle
  • App store assets and screenshots
  • White-label configuration across iOS, Android, Web
  • Welcome screen and login screen styling
  • Custom navigation icons if needed
Let's discuss

Do you have a brand guidelines document we can reference? Any specific requirements for the app's visual identity beyond the website?

Workstream 2

SSO & Authentication

Options
  • OAuth 2.0 / OpenID Connect most common, works with Azure AD, Okta, Google Workspace
  • SAML 2.0 for enterprise IdPs
  • Email/Password simple default, no IdP needed
  • API-based user sync for automated provisioning
We'll need to clarify
  • Which identity provider do you use?
  • Should users auto-provision on first login?
  • Any group-based access rules (departments, regions)?
  • Timeline for IT to configure the IdP side?
Let's discuss

Who on your IT team will be our counterpart for SSO setup? What's the approval process for new app integrations?

Workstream 3

Privacy & Security

Privacy
  • GDPR compliance data processing, retention policies, user consent
  • Data residency where is data stored? EU hosting requirements?
  • User data handling what personal data is collected and why
  • DPA Data Processing Agreement between your organisation and tchop
  • Right to deletion how users can request data removal
  • Analytics & tracking what is measured, what is anonymised
Security
  • Encryption data at rest and in transit (TLS 1.2+, AES-256)
  • Access control role-based permissions, admin separation
  • SSO & MFA enterprise authentication, session management
  • Infrastructure cloud provider, uptime SLA, redundancy
  • ISO 27001 certified tchop holds active certification, audit reports available
  • Mobile app on private devices MDM requirements, data separation, BYOD policies
  • IT security questionnaire your internal review process and timeline
Let's discuss

Do you have an IT security questionnaire we should complete? Are there specific compliance requirements beyond GDPR?

Workstream 4

Technical Integrations

Platform setup
  • Custom sender domain for transactional emails. Requires DKIM and return-path DNS records on your side.
  • Web app subdomain e.g. community.yourdomain.com for browser access alongside the native apps
  • Microsoft Teams integration do you use Teams? We can embed tchop content and notifications directly.
  • Mobile app distribution via MDM deploy the app through your mobile device management system to managed devices
Third-party services
  • Third-party apps corporate benefits, booking services, or other tools that should be accessible directly within the app
  • HR system integration user sync with your HRIS, automated onboarding/offboarding, profile field mapping
  • Other tools CMS, intranet, calendar systems, or collaboration platforms you want to connect
Let's discuss

Which systems do you need the app to talk to? What content sources should feed into the platform automatically?

Workstream 5

Product Setup

Let's discuss

What's your initial channel structure? Which teams or groups need their own spaces? Who will be your first editors?

How tchop works

Content Structure

Four layers make up every tchop app. Each layer controls a different part of the experience.

O
Organisation
Top level. Holds all content, users, settings. Each app connects to one organisation. Strictly separated for security and privacy.
C
Channels
Flexible spaces for target groups, departments, regions, or topics. Each channel has its own users, editors, and content. Launch, archive, or delete anytime.
M
Mixes
Sections within a channel. Think feeds, topics, or pinned areas. The news feed is built from mixes. Content can be synced across them. Unlimited per channel.
K
Content Cards
The atomic unit. Every piece of content is a card. 10 different card types for different engagement needs. Cards live inside mixes.

Content Cards

12 Card Types

Article
Link to any URL with auto-scraped teaser. Opens in-app.
Long Post
Native longform with block editor. Headings, images, embeds, tables.
Thread
Discussion starter. Opens directly into comments for Q&A and dialogue.
Short Post
Simple short-form post. Like a status update, text only.
Image
Photo or graphic with optional text body. Great for user-generated content.
Gallery
2-20 images in a swipeable carousel, each with its own caption.
Video
Native video with teaser image. Plays inline or in detail view.
Audio
Audio file with native player. Perfect for podcasts and voice updates.
PDF
PDF file with auto-generated teaser from first page. Opens in viewer.
Social
Mirror content from Facebook, Instagram, X, TikTok. Links to source.
Poll
Quick surveys with multiple choice options. Results visible in real time.
Event Upcoming
Plan, organize and manage events live or online.

Workstream 6

Content & Editorial

Content types to consider
  • Articles link to external URLs, auto-scraped teasers
  • Long Posts native editorial with block editor
  • Quick formats text, image, video, audio, gallery, PDF
  • Interactive polls, discussion threads
Automation options
  • RSS feed import from existing sources
  • Social media mirroring (LinkedIn, X, Instagram)
  • Scheduled publishing and auto-push
  • API-based content ingest from your CMS
Let's discuss

What content do you already produce that we can pull in automatically? Who will own the editorial calendar?

Workstream 6

Editorial Organisation

Content ownership
  • Central vs. decentral one global team or regional editors with local autonomy?
  • Corporate content top-down comms from leadership, HR, strategy
  • User-generated content should staff be able to post? Where, with what permissions?
  • Approval workflows who reviews before publishing? Does all content need sign-off?
Operational questions
  • Editor roles who creates content day-to-day? How many editors across regions?
  • Content formats which card types fit your communication style? Articles, video, audio?
  • Publishing cadence daily updates, weekly digests, event-driven?
  • Content lifecycle does content expire? Archive strategy?
Let's discuss

Who are your editorial stakeholders? How does content flow from idea to published today?

Workstream 6

AI-Powered Workflows

Where you stand today
  • How do you use AI in communications today?
  • Any existing tools or workflows involving LLMs?
  • Where do you see the biggest potential for AI support?
  • Concerns around AI-generated content and trust?
What tchop brings
  • Intelligent workflows AI-assisted content creation, translation drafts, smart tagging
  • Custom agents via MCP connect your own Claude or LLM agents directly to tchop through our Model Context Protocol integration
  • Pre-built agents auto-generated summaries, podcast creation from written content
  • Rapidly evolving this is one of our fastest-moving areas with major features on the near-term roadmap
Let's discuss

What would be your dream AI use case for internal communications? Where would automation save the most time?

Workstream 6

Email & Newsletters

Your current setup
  • Existing newsletters? Internal email comms, frequency, audience, tools used
  • Open rates and engagement are people reading? What's working?
  • Distribution lists how are recipients managed? Manual, HRIS-synced, self-service?
  • Content overlap does email duplicate what's on the intranet or other channels?
What tchop can do
  • Automated digests daily or weekly email summaries of app content, zero manual effort
  • Newsletter from feed auto-generate newsletters from published cards, curated or algorithmic
  • Push-to-email bridge reach users who haven't installed the app yet
  • Targeted delivery different digests per channel, department, or region
  • Analytics opens, clicks, and conversion to app engagement
Let's discuss

Do you want the app to replace email newsletters or complement them? What's your email fatigue level across the organisation?

Key Topic

Multilingual Content

The Challenge
  • 90+ nationalities, English not spoken by all staff
  • Same message needs to reach everyone, regardless of language
  • Editorial capacity is limited. Translating everything is not realistic.
  • Risk of content silos if languages are separated too strictly
Possible Approaches
  • Separate language channels per region or language group, curated independently
  • Mixed-language feeds with language tags so users can filter
  • Core content in English with translated versions linked or synced across mixes
  • AI-assisted translation for speed, human review for key messages
  • Visual and video-first formats that work across languages
Let's discuss

Which languages are essential at launch? How do you handle translations today? What content must be translated vs. what can stay English-only?

Workstream 7

Adoption Campaign

Phased rollout
  • Phase 1: Pilot editors and power users, gather feedback, iterate
  • Phase 2: Soft launch one department or region, test communication flows
  • Phase 3: Full rollout organisation-wide, supported by comms campaign
  • User import CSV bulk upload, API sync, or SSO auto-provisioning
Internal launch marketing
  • Teaser campaign build anticipation before launch. Countdown, previews, sneak peeks.
  • Leadership endorsement visible support from Executive Director and senior leaders
  • Multi-channel announcement email, intranet, town hall, QR codes, posters
  • Change management address "why another tool?" head-on. Frame the value, not the features.
Let's discuss

What's your best channel for reaching all staff? Is there an upcoming event that would be a natural launch moment? Who are your internal champions?

Workstream 8

Analytics & Success Metrics

Built-in analytics
  • Active vs. engaged users over time
  • Content performance by type, mix, and tag
  • Push notification reach and open rates
  • Session duration and frequency by platform
Defining success together
  • What does a successful launch look like for you?
  • Adoption target: % of users active after 30 days?
  • Engagement target: interactions per user per week?
  • Business goal: what should this platform replace or improve?
Let's discuss

What are the three numbers you'd want to show your leadership after 90 days?

Roles & Responsibilities

Who does what?

Task Your team tchop
Brand assets (logo, colors, font) Owner Support
SSO / IdP configuration Owner Guide
App build and store submission Owner
Channel and mix structure Together Together
Product setup and configuration Together Together
Content strategy and editorial plan Together Together
Editor training Owner
Internal comms for rollout Owner Templates

Workstream 9

Post-Launch & Optimisation

Ongoing review cadence
  • Week 2 after launch first health check. Adoption numbers, early feedback, quick fixes.
  • Month 1 review content performance, user activation rates, editor confidence
  • Quarterly business review strategic alignment, KPIs vs. targets, roadmap planning
  • Annual strategy session evolving the platform with your organisation's needs
What we provide
  • Dedicated Customer Success your named contact for strategic guidance and best practices
  • Industry benchmarks how your engagement compares to similar organisations
  • Feature adoption coaching unlock new capabilities as your team matures
  • Platform updates regular releases, new features, and roadmap transparency
  • Support channels direct access via email, chat, and scheduled calls
Let's discuss

What review cadence works for your team? Who should be in the room for ongoing check-ins?

What's Next

Let's turn this plan into a
powerhouse for SIL's transformation.

Thank you.

We're excited to build this together.