My profile page at Google showed the “I wore more than one hat at Google”-badge. Here are work samples from that time.

3 times I brushed up UI text

The Moma team owns Google’s internal search engine. As their technical writer, the Moma help center was my responsibility for a year. I mainly added and changed help articles, but sometimes I helped them out with UI copy.

Splashscreen

Shipped work should be celebrated. This splash screen deserved a more upbeat tone.

‘Availability’ is a new feature for Moma Teams pages, designed to let other Googlers know when a Googler is traveling or at another location. I corrected a typical mistake because ‘Calendar’ and ‘Trips’ are products.

Clearing confusion around productivity bot

For tedious tasks like setting up an out-of-office reply, the Moma team had developed a bot. Everyone addressed it inconsistently, though. I emailed the team: “Let’s prevent some clean-ups down the road and treat Operator like a first name.”

3 actions to help Techstop switch out of legacy mode

As a writer on the strategic comms team within Googler Engagement (GE), my focus was on advocating strategic comms and supporting the Techstop team. Techstop is where Googlers go to have their computers fixed.

Fact: Techstop is shifting to a remote support model

In-person support doesn’t scale and needs to uncouple from Google’s overall growth. Service requests are increasingly routed through go/techstop instead.

Problem: Comms is playing from behind

The shift is happening, but changes aren’t communicated. Techstop is still promoted as a perk of working at Google. All the while Techstops are closing or their service hours are reduced.