Projects

Three projects, thinking included.

Get a glance at some of the work I've done over the years. Expand any project to read the full context, deliverables, and impact.

AI · Agent design · Voice & tone

  • AI
  • Agent design
  • Voice & tone

The problem

Atlassian content designers were slowed down by repetitive UX and documentation tasks. Identifying and applying standards was time-consuming, leading to occasional inconsistencies even among experts. Frequent "micro-copy requests" — one-off requests for documentation updates or UI edge cases from engineering — further disrupted their workflows.

Simultaneously, the content design team restructured into separate UX and documentation groups, effectively reducing UX content design staff. To compensate, product designers, product managers, and developers were encouraged to handle more UX writing.

What I made

An internal AI agent to draft UI copy and short-form documentation updates, edit content for voice and tone, and answer content standards questions. We integrated the agent into a dedicated Slack channel, as well as in our internal Confluence instance.

  • AI agent trained on Atlassian content standards
  • Slack integration for real-time copy requests
  • Confluence integration for longer-form drafts
  • Voice & tone guardrails and evaluation rubric
Screenshot of the Content Assistant guidebook in Confluence, showcasing both written and video guidance on how to use the AI agent
Screenshot of the Content Assistant guidebook in Confluence, showcasing workflow diagrams of how different personas can use the AI agent. Also included are example prompts for each recommended use case

What changed

90%

faster microcopy turnaround

Top 30%

of most-used AI agents

80%

content drafts using the agent

Screenshot of the Content Assistant agent in Slack

Information architecture · UX writing · Content auditing

  • Information architecture
  • UX writing
  • Content auditing

The problem

When enterprise planning app Jira Align was newly acquired, the most pressing customer pain point discovered by our new product design team was ease of use. The complexity of the navigation in particular was the most mentioned pain point, causing negative customer sentiment toward the app. When users entered for the first time, they didn't know how to begin to get the information they needed or even find out what pages were available.

What I made

  • Redesigned navigation system with simplified information architecture (IA)
  • Exhaustive launch strategy
  • Overhauled interactive training simulation and documentation sets
  • New help articles and videos
  • Onboarding and changeboarding flows and associated designs
Screenshot of an article in Zendesk, titled Navigate Jira Align. The article includes written, video, and diagram guidance to explain how to use the navigation

What changed

2x

more task completion on the first try

10%

reduction in task abandonment

300+

help resources updated

Screenshot of the Jira Align homepage with the first screen of an onboarding flow introducing the new navigation system

Multimedia · Content strategy · Video production

  • Multimedia
  • Content strategy
  • Video production

The problem

Historically, Atlassian's content design team had been opposed to video. In the past, their videos were maintenance-heavy, requiring extensive changes whenever the UX changed. Meanwhile, customers had been begging for videos in the documentation for years.

Even though the company wanted to deliver what customers needed, they had to ensure any multimedia additions would be high-quality, easy to create, and simple to maintain.

What I made

  • Content standards and best practices for writing and editing videos in documentation
  • Reusable video planning templates
  • A maintenance-light video to serve as an example of what "good" looks like
Screenshot of a Loom video, titled Focus permissions overview, with a video transcript on the right.

What changed

  • Established content design video investment for FY2026 and beyond
  • Aligned standards to educate a team of ~30 content designers
Screenshot of the beginning of Atlassian's video standards. The body of the page includes best practices on when to create video, with additional sections for technical, writing, and tooling best practices.