01 / Overview

Meet Atlas

Meet Atlas

A centralized design system for reusable assets, channel playbooks, governance, and scaled guidance.

Atlas transformed scattered brand guidance, duplicated creative requests, and inconsistent handoffs into a centralized operating system for brand execution. Built for internal teams, program owners, and agency partners, the platform organized reusable foundations, channel-specific playbooks, asset libraries, governance workflows, and support paths into one shared source of truth.

40%

reduction in redundant design requests

$120K

estimated annual savings

12

Teams adopted Atlas

0

additional headcount

02 / What I did

Role and scope

I led the strategy, structure, documentation, and system design for Atlas, translating recurring production needs into a scalable brand execution platform. The work included audit synthesis, information architecture, content strategy, asset taxonomy, documentation models, governance workflows, agency onboarding paths, and stakeholder alignment.

My Role

Strategy, IA, documentation, governance, asset systems

Audience

Internal teams, program owners, designers, agency partners

Outputs

Portal architecture, playbooks, templates, support paths, governance workflows

04 / The BAd Habits

Diagnosis

I began by auditing recurring templates, campaign assets, agency handoffs, and support requests to identify where teams were duplicating effort or interpreting the brand inconsistently. The audit revealed repeated patterns across teams: similar presentations were rebuilt from scratch, agencies needed the same onboarding information, campaign assets were recreated by market, and support questions repeated across programs. Those findings became the system requirements for Atlas.

Finding
Atlas Solution

Teams rebuilt similar presentation templates, creating repeated deck structures.

Standardized presentation system

Agencies received inconsistent handoffs, causing repeated onboarding friction.

Agency starter kit and onboarding path

Campaign assets were recreated by each market, duplicating production efforts.

Modular campaign toolkit

Event graphics used inconsistent layouts, despite recurring event needs.

Event playbook and reusable templates

Data slides used inconsistent chart styles, forcing manual interpretation.

Data visualization guidance

Questions repeated across programs, signaling the same support needs.

Self-service support and ticket routing

05 / My Game Plan

Strategy

Atlas was designed around five core pillars: global foundations, areas of engagement, reusable asset libraries, agency onboarding, and governance support. Each pillar answered a different operational need. Foundations defined the brand rules. Areas of engagement translated those rules into real channels. The asset library gave teams approved starting points. Agency onboarding reduced repeated handoffs. Governance kept the system current and usable over time.

Global Foundations

Core rules for color, typography, layout, imagery, data, and accessibility.

Governance and Support

Requests, contributions, reviews, updates, and support routing.

Agency Onboarding

Starter kits, handoff paths, approval guidance, and version control.

Asset Library

Reusable templates, toolkits, design kits, and production-ready components.

Areas of Engagement

Channel-specific playbooks for presentations, campaigns, events, editorial, social, and digital.

Global Foundations

Core rules for color, typography, layout, imagery, data, and accessibility.

Areas of Engagement

Channel-specific playbooks for presentations, campaigns, events, editorial, social, and digital.

Asset Library

Reusable templates, toolkits, design kits, and production-ready components.

Agency Onboarding

Starter kits, handoff paths, approval guidance, and version control.

Governance and Support

Requests, contributions, reviews, updates, and support routing.

06 / How it's built

System Architecture

System Architecture

Atlas was organized as a central portal for brand execution. Each section gave teams a clear path from brand principle to practical execution. Users could understand the system, find the right guidance, download approved assets, onboard partners, submit requests, and reference the latest version of shared materials.

Getting Started

What is Atlas

How to use Atlas

Roles & Audiences

Agency Onboarding

Global Brand Foundations

Brand strategy

Color

Brand strategy

Color

Typography

Grid

Typography

Grid

Photography

Iconography

Photography

Iconography

Data

Accesibility

Data

Accesibility

Areas of Engagement

Executive Comms

Campaigns

Events

Editorial

Social

Digital Experiences

Asset Libraries

Presentations

Video Assets

Design Kits

Campaigns

Business Docs

Governance & Support

Submit a request

Contribute an asset

Review process

Version history

Support paths

07 / Documentation

Documentation Model

Rather than creating one flat documentation site, Atlas was structured for different user needs: quick reference for leaders and non-designers, guided playbooks for planners and strategists, and tactical specs for designers and agency partners. This allowed the same system to support fast decision-making, strategic planning, and production-level execution.

Quick Reference

For leaders and non-designers

  • What to use

  • When to use it

  • Simple do / don’t examples

  • Fast decision support

Guided Playbook

For program owners, planners, and strategists

  • Channel-specific guidance

  • Use cases

  • Content patterns

  • Approval expectations

Tactical Specs

For designers and agencies

  • Production details

  • File links

  • Templates

  • Accessibility checks

  • Version notes

Atlas made the same brand system usable for executives, planners, designers, and agency partners.

08 / What everyone shared

Global Foundations

The foundation layer established the core rules of the brand system, including color, typography, layout, photography, iconography, data visualization, and accessibility guidance. These pages were designed to be usable at multiple levels: simple enough for non-designers to make better decisions, but detailed enough for designers and agencies to execute accurately.

Color

Layout and grid

Iconography

Accessibility

Motion principles

Typography

Photography

Data visualization

Logo usage

Color

Iconography

Motion principles

Photography

Logo usage

Layout and grid

Accessibility

Typography

Data visualization

Typography
Display
Heading
Body
Display
Heading
Body
Caption
Eyebrow
Functional
Caption
Eyebrow
Functional
Hero
Data
Labels
Hero
Data
Labels
Layout & Grid
Grid
Spacing
Hiearchy
Responsive Behavior
Global Margins
Type Handling
Grid
Spacing
Hiearchy
Responsive Behavior
Global Margins
Type Handling
Accessibility
Contrast Ratios
Compliance Checks
Alt Text
Contrast Ratios
Compliance Checks
Alt Text
Portal Pages

09 / What each team needed

Areas of engagement

Atlas translated brand foundations into channel-specific guidance for the ways teams actually worked. Areas of engagement included executive presentations, campaigns, live events, editorial, social, digital experiences, and business communications. Each playbook connected brand principles to real production needs, common formats, reusable templates, and approval expectations.

Executive Presentations
Deck Structure
Cover System
Data Slide Rules
Narrative Pacing
Template Downloads
Handoff Checklist
Campaigns
Launch Toolkit
Modular Layouts
Messaging Hierarchy
Image Treatment
Channel Adaptations
Review Expectations
Events
Event Identity Principles
Stage Screen Layouts
Environmental Graphics
Presentation Templates
Production Best Practices
Approval Paths
Channel playbooks helped teams apply the brand consistently in the formats they used most.

10 / The Goods

Asset library

The asset library organized reusable materials by channel and task, making it easier for teams to start from approved components instead of recreating work from scratch. The library included presentation templates, campaign graphics, event materials, business templates, video assets, and design kits. This helped reduce duplicate requests and gave internal teams and agency partners a consistent starting point.

01

Presentations
Executive Communication
Program Updatees
Business Reviews
Data Heavy Reports

02

Campaigns
Launch Toolkits
Email Headers
Interal Awareness Structure
Modular Social Tiles

03

Events & Environmental
Stage Screens
Digital Signage
Wayfinding Systems
Booth Graphics

04

Video & Motion
Intro & Outro Cards
Digital Signage
Lower Thirds
Transition Kits

05

Business Documents
One Pagers
PRFAQs
Roadmaps
Leadership Briefs

11 / The Dance Card

Agency onboarding

Atlas converted repeated agency handoffs into a reusable onboarding path. Partners could understand the brand, download starter kits, review channel playbooks, check approval requirements, and confirm the latest files before production began. This reduced repetitive explanation, improved consistency, and helped external teams ramp up faster.

Objective

Understand the brand, program goals, and how Atlas is structured before you start producing work.

Resources
  • Brand mission, tone of voice, and program objectives

  • How Atlas is organized and where to find each resource

  • Roles, access permissions, and key points of contact

12 / rules of the road

Governance

Atlas included governance workflows to keep the system accurate, current, and scalable after launch. Requests, contributions, and updates were routed through a structured process: triage the need, determine whether it was a new asset, duplicate request, system update, or support question, then publish approved changes into the appropriate location with version history. This allowed Atlas to evolve without becoming another unmanaged library of files.

Request or contribution submitted

A new need enters the governance queue.

Classify the need

New asset · Duplicate request · Updates · Brand question · Agency support

Decision

Add · Create · Update · Redirect · Decline with rationale

Document and notify

Log the release in version history, then notify affected users.

Triage

Confirm urgency, completeness, and the right review path.

Owner / steward review

Reuse, alignment, QC , accessibility, relevance, and maintenance cost.

Publish update

Release the approved change in the appropriate location.

13 / everyones invited

Support and contribution model

To keep Atlas scalable, support requests and user contributions were organized into clear categories. Teams could ask brand questions, request assets, flag outdated files, submit reusable patterns, or route agency support needs through the system. This created a feedback loop between real user needs and system updates.

Support Categories

Brand question

Which template should I use? Can I use this color combination?

Asset request

I need a campaign banner in this format.

Agency support

Where should the partner start? Which files are current?

Contribution

We created a useful module. Can it be added to Atlas?

Issue report

This file is outdated. This link is broken.

Contribution Model

Identify the need

Contributor identifies need

Submit a request

Submits asset, pattern, or guidance request

Steward review

Steward reviews reuse, alignment, quality, accessibility, relevance, and maintenance cost

Resolve the request

Add to library · Merge · Return for revision · Decline with rationale

Publish the outcome

Publish and document

14 / sanity

Versioning

Atlas was designed as a living system. Updates were documented through version history so teams could understand what changed, why it changed, and how it affected their work. Versioning helped prevent outdated files from circulating and gave teams confidence that they were using the latest approved materials.

Release History

Version / Update / Reason / Impact


v1.1 / Added event signage templates / Repeated requests from regional events / Reduced custom signage requests

v1.2 / Updated data visualization guidance / Inconsistent chart styling in leadership decks / Improved consistency

v1.3 / Added agency starter kit / Repeated onboarding friction / Faster partner ramp-up

v1.4 / Retired outdated campaign templates / Duplicate files caused confusion / Cleaner asset library

15 / who listened

Adoption

Atlas became a shared operating model across 12 programs. The system supported teams working on executive communications, campaigns, events, editorial programs, social content, leadership presentations, training materials, business reviews, and digital experiences. Because the platform was organized around real workflows, teams could adopt the parts of the system most relevant to their work while still operating from the same shared foundation.

Executive communications

Regional campaigns

Internal events

Editorial programs

Social content

Leadership presentations

Employee engagement

Recruiting communications

Training materials

Business reviews

Environmental graphics

Digital experiences

16 / what changed

Impact

Atlas became a shared operating model for brand execution across teams and programs. The system helped teams reuse approved assets, reduce duplicate production, onboard partners faster, and maintain consistency across campaigns, presentations, events, and digital communications.

40%

40%

fewer redundant design requests

$120K

$120K

estimated annual savings

12

12

programs adopted Atlas

0

0

additional headcount required

17 / The Juice

Results

Atlas moved the organization from static brand guidelines to a living operating system. By combining reusable assets, channel playbooks, governance workflows, and support paths, the system gave teams a practical way to execute the brand consistently at scale. It created a shared infrastructure for doing the work — not just a reference for how the work should look.

Brand Rules

PDF guidelines
Manual interpretation
One-off handoffs
Inconsistent outputs
No feedback loop

Living Operating System

Web portal
Channel playbooks
Asset library
Governance workflow
Support tickets
Version history
Contribution model
Feedback loop

01 / Overview

Meet Atlas

A centralized design system for reusable assets, channel playbooks, governance, and partner support.

Atlas transformed scattered brand guidance, duplicated creative requests, and inconsistent handoffs into a centralized operating system for brand execution. Built for internal teams, program owners, and agency partners, the platform organized reusable foundations, channel-specific playbooks, asset libraries, governance workflows, and support paths into one shared source of truth. The system reduced redundant design requests by 40%, saved an estimated $120K annually, and was adopted across 12 programs without adding headcount.

40%

reduction in redundant design requests

$120K

estimated annual savings

12

Teams adopted Atlas

0

additional headcount

02 / What I did

Role and scope

I led the strategy, structure, documentation, and system design for Atlas, translating recurring production needs into a scalable brand execution platform. The work included audit synthesis, information architecture, content strategy, asset taxonomy, documentation models, governance workflows, agency onboarding paths, and stakeholder alignment.

My Role

Strategy, IA, documentation, governance, asset systems

Audience

Internal teams, program owners, designers, agency partners

Outputs

Portal architecture, playbooks, templates, support paths, governance workflows

03 / The Work

Challenge

Brand guidance existed, but it was difficult to operationalize at scale. Teams across markets and programs were recreating similar materials, agencies were being re-onboarded for recurring work, and assets were often scattered across different documents, folders, and handoff processes. The problem was not simply a lack of guidelines. The real challenge was that teams needed a practical way to find, use, adapt, and govern brand assets across campaigns, presentations, events, editorial, and digital experiences. Atlas needed to turn static guidance into a reusable operating system.

Before Atlas

Scattered folders
Static guidelines
Repeated agency handoffs
Duplicate template requests
Inconsistent campaign assets
Unclear approval paths

After Atlas

Central portal
Reusable foundations
Channel playbooks
Approved asset library
Agency onboarding path
Governance and support workflow
Versioned source of truth

Atlas replaced fragmented production habits with one shared operating model for finding, using, and governing brand assets.

04 / The BAd Habits

Diagnosis

I began by auditing recurring templates, campaign assets, agency handoffs, and support requests to identify where teams were duplicating effort or interpreting the brand inconsistently. The audit revealed repeated patterns across teams: similar presentations were rebuilt from scratch, agencies needed the same onboarding information, campaign assets were recreated by market, and support questions repeated across programs. Those findings became the system requirements for Atlas.

Teams rebuilt similar presentation templates, creating repeated deck structures.

Standardized presentation system

Agencies received inconsistent handoffs, causing repeated onboarding friction.

Agency starter kit and onboarding path

Campaign assets were recreated by each market, duplicating production efforts.

Modular campaign toolkit

Event graphics used inconsistent layouts, despite recurring event needs.

Event playbook and reusable templates

Data slides used inconsistent chart styles, forcing manual interpretation.

Data visualization guidance

Questions repeated across programs, signaling the same support needs.

Self-service support and ticket routing

05 / My Game Plan

Strategy

Atlas was designed around five core pillars: global foundations, areas of engagement, reusable asset libraries, agency onboarding, and governance support. Each pillar answered a different operational need. Foundations defined the brand rules. Areas of engagement translated those rules into real channels. The asset library gave teams approved starting points. Agency onboarding reduced repeated handoffs. Governance kept the system current and usable over time.

01

Global Foundations

Core rules for color, typography, layout, imagery, data, and accessibility.

02

Areas of Engagement

Channel-specific playbooks for presentations, campaigns, events, editorial, social, and digital.

03

Asset Library

Reusable templates, toolkits, design kits, and production-ready components.

04

Agency Onboarding

Starter kits, handoff paths, approval guidance, and version control.

05

Governance and Support

Requests, contributions, reviews, updates, and support routing.

06 / How it's built

System Architecture

Atlas was organized as a central portal for brand execution. Each section gave teams a clear path from brand principle to practical execution. Users could understand the system, find the right guidance, download approved assets, onboard partners, submit requests, and reference the latest version of shared materials.

Getting Started

What is Atlas

How to use Atlas

Roles & Audiences

Agency Onboarding

Global Brand Foundations

Brand strategy

Typography

Photography

Data

Color

Grid

Iconography

Accesibility

Areas of Engagement

Executive Comms

Campaigns

Events

Editorial

Social

Digital Experiences

Asset Libraries

Presentations

Campaigns

Video Assets

Business Docs

Design Kits

Governance & Support

Submit a request

Contribute an asset

Review process

Version history

Support paths

07 / Documentation

Documentation model

Rather than creating one flat documentation site, Atlas was structured for different user needs: quick reference for leaders and non-designers, guided playbooks for planners and strategists, and tactical specs for designers and agency partners. This allowed the same system to support fast decision-making, strategic planning, and production-level execution.

Quick Reference

For leaders and non-designers

  • What to use

  • When to use it

  • Simple do / don’t examples

  • Fast decision support

Guided Playbook

For program owners, planners, and strategists

  • Channel-specific guidance

  • Use cases

  • Content patterns

  • Approval expectations

Tactical Specs

For designers and agencies

  • Production details

  • File links

  • Templates

  • Accessibility checks

  • Version notes

Atlas made the same brand system usable for executives, planners, designers, and agency partners.

08 / What everyone shared

Global foundations

The foundation layer established the core rules of the brand system, including color, typography, layout, photography, iconography, data visualization, and accessibility guidance. These pages were designed to be usable at multiple levels: simple enough for non-designers to make better decisions, but detailed enough for designers and agencies to execute accurately.

Color
Typography
Layout and grid
Photography
Iconography
Data visualization
Accessibility
Logo usage
Motion principles
Typography
Display
Heading
Body
Caption
Eyebrow
Functional
Hero
Data
Labels
Layout & Grid
Grid
Spacing
Hiearchy
Responsive Behavior
Global Margins
Type Handling
Accessibility
Contrast Ratios
Compliance Checks
Alt Text
Contrast Ratios
Compliance Checks
Alt Text

09 / What each team needed

Areas of engagement

Atlas translated brand foundations into channel-specific guidance for the ways teams actually worked. Areas of engagement included executive presentations, campaigns, live events, editorial, social, digital experiences, and business communications. Each playbook connected brand principles to real production needs, common formats, reusable templates, and approval expectations.

Executive Presentations
Deck Structure
Cover System
Data Slide Rules
Narrative Pacing
Template Downloads
Handoff Checklist
Campaigns
Launch Toolkit
Modular Layouts
Messaging Hierarchy
Image Treatment
Channel Adaptations
Review Expectations
Events
Event Identity Principles
Stage Screen Layouts
Environmental Graphics
Presentation Templates
Production Best Practices
Approval Paths
Channel playbooks helped teams apply the brand consistently in the formats they used most.

10 / The Goods

Asset library

The asset library organized reusable materials by channel and task, making it easier for teams to start from approved components instead of recreating work from scratch. The library included presentation templates, campaign graphics, event materials, business templates, video assets, and design kits. This helped reduce duplicate requests and gave internal teams and agency partners a consistent starting point.

01

Presentations
Executive Communication
Program Updatees
Business Reviews
Data Heavy Reports

02

Campaigns
Launch Toolkits
Email Headers
Interal Awareness Structure
Modular Social Tiles

03

Events & Environmental
Stage Screens
Digital Signage
Wayfinding Systems
Booth Graphics

04

Video & Motion
Intro & Outro Cards
Digital Signage
Lower Thirds
Transition Kits

05

Business Documents
One Pagers
PRFAQs
Roadmaps
Leadership Briefs

11 / The Dance Card

Agency onboarding

Atlas converted repeated agency handoffs into a reusable onboarding path. Partners could understand the brand, download starter kits, review channel playbooks, check approval requirements, and confirm the latest files before production began. This reduced repetitive explanation, improved consistency, and helped external teams ramp up faster.

Objective

Understand the brand, program goals, and how Atlas is structured before you start producing work.

Resources
  • Brand mission, tone of voice, and program objectives

  • How Atlas is organized and where to find each resource

  • Roles, access permissions, and key points of contact

12 / rules of the road

Governance

Atlas included governance workflows to keep the system accurate, current, and scalable after launch. Requests, contributions, and updates were routed through a structured process: triage the need, determine whether it was a new asset, duplicate request, system update, or support question, then publish approved changes into the appropriate location with version history. This allowed Atlas to evolve without becoming another unmanaged library of files.

Request or contribution submitted

A new need enters the governance queue.

Triage

Confirm urgency, completeness, and the right review path.

Classify the need

New asset · Duplicate request · Updates · Brand question · Agency support

Owner / steward review

Reuse, alignment, QC , accessibility, relevance, and maintenance cost.

Decision

Add · Create · Update · Redirect · Decline with rationale

Publish update

Release the approved change in the appropriate location.

Document and notify

Log the release in version history, then notify affected users.

13 / everyones invited

Support and contribution model

To keep Atlas scalable, support requests and user contributions were organized into clear categories. Teams could ask brand questions, request assets, flag outdated files, submit reusable patterns, or route agency support needs through the system. This created a feedback loop between real user needs and system updates.

Support Categories

Brand question

Which template should I use? Can I use this color combination?

Asset request

I need a campaign banner in this format.

Agency support

Where should the partner start? Which files are current?

Contribution

We created a useful module. Can it be added to Atlas?

Issue report

This file is outdated. This link is broken.

Contribution Model

Identify the need

Contributor identifies need

Submit a request

Submits asset, pattern, or guidance request

Steward review

Steward reviews reuse, alignment, quality, accessibility, relevance, and maintenance cost

Resolve the request

Add to library · Merge · Return for revision · Decline with rationale

Publish the outcome

Publish and document

14 / sanity

Versioning

Atlas was designed as a living system. Updates were documented through version history so teams could understand what changed, why it changed, and how it affected their work. Versioning helped prevent outdated files from circulating and gave teams confidence that they were using the latest approved materials.

Release History

Version / Update / Reason / Impact


v1.1 / Added event signage templates / Repeated requests from regional events / Reduced custom signage requests

v1.2 / Updated data visualization guidance / Inconsistent chart styling in leadership decks / Improved consistency in reporting

v1.3 / Added agency starter kit / Repeated onboarding friction / Faster partner ramp-up

v1.4 / Retired outdated campaign templates / Duplicate files caused confusion / Cleaner asset library

15 / who listened

Adoption

Atlas became a shared operating model across 12 programs. The system supported teams working on executive communications, campaigns, events, editorial programs, social content, leadership presentations, training materials, business reviews, and digital experiences. Because the platform was organized around real workflows, teams could adopt the parts of the system most relevant to their work while still operating from the same shared foundation.

Executive communications

Regional campaigns

Internal events

Editorial programs

Social content

Leadership presentations

Employee engagement

Recruiting communications

Training materials

Business reviews

Environmental graphics

Digital experiences

16 / what changed

Impact

Atlas became a shared operating model for brand execution across teams and programs. The system helped teams reuse approved assets, reduce duplicate production, onboard partners faster, and maintain consistency across campaigns, presentations, events, and digital communications.

40%

fewer redundant design requests

12

programs adopted Atlas

$120K

estimated annual savings

0

additional headcount required

17 / The Juice

Results

Atlas moved the organization from static brand guidelines to a living operating system. By combining reusable assets, channel playbooks, governance workflows, and support paths, the system gave teams a practical way to execute the brand consistently at scale. It created a shared infrastructure for doing the work — not just a reference for how the work should look.

Brand Rules

PDF guidelines
Manual interpretation
One-off handoffs
Inconsistent outputs
No feedback loop

Living Operating System

Web portal
Channel playbooks
Asset library
Governance workflow
Support tickets
Version history
Contribution model
Feedback loop