How rewriting the language of a 7-step Office 365 onboarding portal — status alerts, error messages, step labels, and support copy — turned confusion into confident action for thousands of TCS employees.
Context
TCS Modern Workplace was the self-service portal guiding TCS employees through a company-wide Office 365 migration. It managed license assignment, domain verification, device registration, and Teams onboarding — across thousands of users in multiple geographies. The infrastructure was robust. But the moment something went slightly off-script — a pending license, a domain conflict, a delayed step — the portal's language completely failed the user. No clear ownership, no plain-English explanation, no next step.
User Signals
These weren't edge cases. They were the everyday experience of employees trying to complete onboarding on their own — without being able to decode what the system was telling them.
I got a message saying my domain account is inactive — but I've been using it all week. I didn't know if I needed to call IT or just wait.
Status AmbiguityThe banner said "manual intervention is required." I didn't know who was intervening or when. I raised three support tickets before someone explained I just had to wait.
Ownership Confusion"Domain Readiness" and "Asset Readiness" — I had no idea what these steps meant. I wasn't sure if I'd done them or if the system had done them for me.
Unclear Step LabelsDiagnosis
Each failure operated at a system level — across every state the portal could enter. Fixing one screen wouldn't fix the experience. Every layer of language had to shift.
Every failed status message, every jargon-heavy step label, every disclaimer-first support chat was the system optimising for its own internal logic — not for the person trying to navigate it. The fix wasn't more information. It was the right information, in the right voice, at the right moment.
Approach
The strategy wasn't to add more copy — it was to swap out copy that created confusion for copy that built confidence. Four principles guided every rewrite.
Process
The work started with direct user observation — sitting alongside employees as they navigated onboarding for the first time. Every moment of hesitation, every support ticket raised, every question asked of IT was a data point. The wireframes came next: rough sketches to validate the step structure before committing to final copy.
Copy Execution · 01
The "Awaiting License" banner was the first thing users saw when something went wrong. It was written from the system's point of view — naming an internal state — instead of from the user's point of view, which needed to know: what happened, who's fixing it, and do I need to do anything?
Copy Execution · 02
The 7-step checklist was the spine of the entire onboarding journey. But the labels were written from the IT system's perspective — describing what the system needed — not from the employee's perspective, describing what they were about to do. The result: steps that felt alien to someone joining TCS for the first time.
Step list — before and after. The revised labels use verb-first, user-perspective phrasing that tells employees exactly what they're about to do.
Copy Execution · 03
The original success banner ("Your Office 365 license is active!") was technically accurate but motivationally flat. It confirmed the fact without channelling the user's energy into the very next step they needed to take: setting up Microsoft Teams.
The rewritten success state closes the loop on the license and immediately opens the path to the next step — with an estimated time, removing the hesitation of "what now?"
Copy Execution · 04
The onboarding support widget's opening line — "Howdy, this is not live support" — broke the experience at the most vulnerable moment: when a user was stuck and needed help. The mismatched casual tone ("Howdy") combined with an abrupt disclaimer eroded trust before any actual help could be offered.
System-Level Copy
These weren't isolated fixes — they were a consistent vocabulary shift across the entire portal. The goal: if a user read any copy on any screen, they would feel informed and capable, not confused and blamed.
Outcomes
The copy changes shipped as part of the broader Modern Workplace portal redesign. The results validated what the user research had suggested: the confusion wasn't the product — it was the language around it.
The Modern Workplace project taught me that enterprise software has a particular blindspot: it often speaks to the system's state, not the user's situation. "Awaiting License" tells the server's truth. "We're working on your license — you'll hear from us in 48 hours" tells the user's truth. UX writing's job is always to close that gap.