← Selected Work

Case Study

From stranded artifact to living standard: Schwab UX writing guide

How migrating a fragmented, hard-to-find SharePoint document into the design system drove a 10x increase in monthly visits — and became the foundation for an AI-assisted writing tool.

Organization

Charles Schwab

Scope

UX writing standards, Everest design system

Role

Senior manager, UX content strategy

Status

Live in Everest


A writing standard nobody could find

Schwab's UX writing guidance existed — technically. Across 10 to 15 pages of a SharePoint site, writing standards had accumulated over the years, contributed piecemeal by different teams with different priorities. The result was a Frankenstein document: internally inconsistent, full of self-referential links that went nowhere, and full of references to parts of the broader ecosystem, including accessibility guidance and disclosure standards, that were no longer current.

But the biggest problem wasn't the content. It was discoverability. If you didn't already have the SharePoint link or know exactly what to search for, you were unlikely to find it at all. The writing guide was getting roughly a dozen visits a month. Most of the organization was operating without a shared standard, whether they knew it or not.

A standard nobody uses isn't a standard. The goal wasn't just to improve the content — it was to get it somewhere people would actually go.


Lean, integrated, and built for what's next

The strategy was to migrate the writing guide into Everest, Schwab's design system, as a lightweight, purposeful UX writing standards document that lived where designers and writers already worked. Rather than reproducing the sprawl of the SharePoint site, the new guide would be tightly edited: complementary to the component-level text guidance already in Everest, opinionated about house style, and structured for both human readers and AI consumption.

That last requirement mattered. From the start, the guide was designed not just as a reference document but as a knowledge base — content structured cleanly enough to power AI-assisted writing tools.


Territorial stakeholders, new tooling, and a first for the design system

The content work was the straightforward part. The organizational work was not. The existing SharePoint artifact had contributors who felt ownership over it — content strategy peers who had shaped it over time and had strong opinions about what a writing guide should say and where it should live. Getting alignment required acknowledging that history while making a clear case for why the old approach wasn't serving the organization.

Getting the guide into Everest required negotiating with the design system team, gatekeepers who maintained strict standards for what entered the system and how. This wasn't adversarial, but it wasn't frictionless either. Making the case that UX writing standards belonged in the design system — and earning the access and process support to put them there — took sustained effort.

It also required bringing the broader creative direction team into a new way of working. Contributing to Everest meant working in GitHub and a documentation site — tools the team hadn't used before. This was new territory, and navigating it meant learning in public while keeping the project moving.


10x visits. A new precedent. An AI drafting partner.

10×
Monthly visits — from ~12 in SharePoint to 100+ in Everest
First
Creative direction content in the Everest design system
Live
AI writing agent built on the guide, in active use
Open
Door opened for broader standards team to move into Everest

Since launching in Everest, the writing guide has gone from roughly a dozen monthly visits to over 100. Discoverability, not content quality, was the primary barrier to adoption. The guide is now where designers and writers work, which means it actually gets used.

Beyond the artifact itself, the project set a precedent. The writing guide was the first creative direction content to land in Everest. That process proved the model. The broader standards team now has a path into Everest that didn't exist before.

The guide's clean structure has also made it immediately useful as an AI knowledge base. An AI writing agent built on the standards is already in active use as a drafting partner, with integration into VSCode-based AI prototyping workflows currently in development, closing the loop between content governance and AI-assisted content creation.