How building a voice and tone system — and rewriting every onboarding, journey, badge, and score message — turned a mandatory Office 365 adoption tool into a platform employees actually wanted to use.
Context
TCS was migrating its entire workforce to Office 365. The tools were ready. The licenses were provisioned. But simply deploying software doesn't make people use it — or trust it. O365 Engage was built to close that gap: a gamified, journey-based learning platform where employees earned points, unlocked badges, and progressed through personalised learning paths as they adopted new tools. My job was to write every word of it — and before that, to decide what kind of voice should speak those words.
User Research Signals
Interviews with early adopters and pilot group surveys identified a consistent pattern: the problem wasn't the tools — it was the relationship between employees and the tools. Every failed adoption attempt shared the same root cause: it felt like an IT directive, not a personal journey.
I know I should be using Teams, but every time I open a "training module" I feel like I'm back in a compliance course. I just close it.
Engagement Drop-offThe instructions are always so formal. "Please navigate to the following path and select the applicable option." I just want someone to explain it like a person would.
Tone DisconnectI don't feel like I'm making progress. I don't know what I've done, what's next, or why it matters. It all feels like a list of tasks someone else made for me.
No Sense of ProgressDiagnosis
Enterprise gamification creates a specific UX writing tension: the product must feel engaging and energetic, but also credible and useful. Too casual and users dismiss it as gimmicky. Too formal and it becomes another training module. Every copy challenge lived in that gap.
Points, badges, and leaderboards are mechanics. What makes them feel meaningful is the language surrounding them — the invitation to start, the acknowledgment when you succeed, the nudge when you stall. Before a single journey was written, the platform needed a voice to write them all in.
Foundation
Before writing a single journey description or badge name, I defined the voice and tone system that would govern all copy on the platform. This gave the product team a shared framework for every future decision — and gave me the creative brief I needed to write with confidence.
Tone Map
Voice is constant. Tone shifts. The tone map answered a question every copy decision on the platform faced: for this specific type of message, how fun vs. serious and how concise vs. detailed should the writing be?
The tone map positioned each content type on the Fun–Serious and Concise–Detailed axes, giving the entire team a shared reference for copy decisions.
Copy Execution · 01
The first screen a new user sees should answer one question: why should I care? The original welcome screen answered a different question — "what is this product?" That's not what earns the user's next tap. The rewrite led with value, used outcome language, and made the benefits feel personal and immediate.
Copy Execution · 02
The journey card is the product's most critical conversion moment — it's where the user decides whether to tap START or scroll past. Early descriptions listed topics like a curriculum outline. The rewrite led with the outcome the user would achieve, then added just enough context to build confidence, not overwhelm.
Copy Execution · 03
Numbers on a scoreboard don't motivate people — the story around those numbers does. The completion and score screens were the platform's biggest emotional payoff moments. The original copy delivered data. The rewrite delivered meaning: where the user had come from, where they stood, and what was worth doing next.
Copy Execution · 04
The platform delivered role-based journeys tailored to each employee. But the copy didn't reflect that tailoring — users saw the same generic heading regardless of who they were. A single copy change transformed the feel of the entire home screen.
System-Level Copy
These weren't individual fixes — they were the application of a consistent voice across every state of the platform. The tone map and voice definition meant that every future copy decision had a framework to refer to.
Outcomes
The O365 Engage platform shipped with the rewritten voice and tone system, the revised journey descriptions, and the updated onboarding and achievement copy. The results tracked over six months across the pilot rollout.
O365 Engage taught me that enterprise gamification lives or dies on the quality of its language. The badges, the points, the leaderboard — none of it lands unless the words around it feel earned, human, and intentional. And none of that is possible without first deciding, clearly and collectively, what voice the product speaks in.