DEUNAN BERKELEY
Senior Content Designer / Senior UX Writer
TRACKING CHANGES
Cross-group Enterprise Features
Audience: Enterprise, IT Administrators
​
My Role: Senior UX Writer
​
Challenge:
Avoiding repeats of text changes in multiple approval cycle.
Solution:
Text change table with historical column.
Cross-team communications
Some features involve teams outside the org contributing their specific terms, or approvals, on a piece of UX writing. Such was the case with this example, M365 Main Admin Center's Settings feature, specifically, Microsoft Whiteboard. (There are 56 features at the time of this work.)
​
Because of multiple approval paths and overlapping emails, meetings, and the like, I created a single entry for each setting in Microsoft OneNote, and added the latest screenshots and text change tables to each one, to help us track everything. (I also put in bug numbers, but that spans more than one bug database.)
​
This really sped up the team on small fixes and tweaks, and helped us anchor what text was discussed already and what wasn't suggested yet.
​
Whiteboard
​
This was a special exception to most of the classic restrictions on text in the UI because of a special halfway state for the feature. Which involved extra teams and people to insure the wording was exactly right.
BEFORE
AFTER
