Cutting Subordinating Conjunctions Across the Product
Across Cvent's product, sentences regularly led with "Because," "While," and "Once", constructions that bury the action and slow down scanning. I updated the style guide with a clear rule and restructuring alternatives, ran live rewriting workshops with the team, and audited existing product content. Shorter strings, faster scannability, and more consistent voice across all surfaces.
The problem
Across Cvent's product, sentences regularly started with "Because," "While," "Although," and "Once." These constructions bury the action. Users scanning a notification or error message miss the thing they actually need to do.
What changed
Updated the style guide with a clear rule and restructuring alternatives. Ran workshops where writers rewrote real examples in real time. Audited existing product content and revised alongside the team.
Real examples from the product
Before: Your virtual vendor card request for GBP 400 has been submitted. Once approved, [Mastercard] will share the card details with (abc@vendor.com), via a secure email.
After: Your virtual vendor card request for GBP 400 has been submitted. You will receive your card details at abc@vendor.com upon approval.
Before: While the report is being generated, you can continue browsing other sections.
After: Generate the report while browsing other sections.
Before: Because you missed the deadline, the registration is closed.
After: The registration is closed.
Impact
- Faster scannability. The outcome appears before the condition.
- Shorter strings improve localization accuracy and speed.
- More consistent, direct brand voice across all surfaces.