Case Study  ·  Enterprise DesignOps  ·  2026

Scaling a Global Sales Team — Without Losing the Room

Change management, DesignOps transformation, and Google Workspace migration for an enterprise sales organization resistant to leaving PowerPoint behind

Role

DesignOps Director

Scope

Global enterprise

Tools

Google Workspace

Result

60% faster builds

Design Ops cover — Google Slides deck open on laptop with geometric background

The Real Problem

The tools weren't broken. The people didn't trust the new ones.

The technical brief was clear: migrate a global sales organization from PowerPoint to Google Workspace, build a governed Single Source of Truth, and eliminate off-brand collateral. But the real problem had nothing to do with software.

The sales team was experienced, high-performing, and deeply skeptical. They had built their workflows around tools they trusted, over years. The transition wasn't just a technical migration — it was asking people who were under constant commercial pressure to change the way they worked, on a timeline they didn't control, with tools they had never used.

A system no one adopts is not a solution. That insight shaped every decision that followed.

"I could build the most architecturally perfect Google Slides system in the world. If a senior sales director wouldn't open it, none of it mattered. The change management was the project."

Resistance Type 1

Tool fear

Sales teams feared the learning curve of real-time collaboration tools after years of PowerPoint muscle memory.

Resistance Type 2

Version chaos

Fragmented local servers and hard-drive files meant every team was working from a different version of the deck.

Resistance Type 3

Ad-hoc overload

Without governed templates, every pitch required a custom design request — creating an unsustainable bottleneck.

Workflow Transformation

From spaghetti to a single straight line

The before state wasn't just inefficient — it was invisible. No one could see where the bottlenecks were because every team had their own path to a finished presentation. The after state replaced that entropy with a single governed flow: Sales Request → SSOT Template → Client-Ready Pitch.

Before and after workflow diagram — legacy ad-hoc chaos versus centralized DesignOps SSOT flow

Before: ad-hoc workflow with no governance, resulting in roadblocks and version chaos. After: a single SSOT template pipeline — Sales Request to Client-Ready Pitch in three steps.

The System Architecture

A foolproof environment where teams can't accidentally break the brand

The technical foundation was built in two interlocking layers. First, a brand-compliant UI kit using Arial as the universal enterprise fallback — eliminating font rendering failures across client operating systems globally. Second, a Master Slide architecture with locked Theme Builder constraints, so teams could populate content freely without any risk of corrupting the layout grid or visual hierarchy.

The design intent was specifically not to build something that required design expertise to use. The system had to be foolproof for a sales director in a different time zone, under deadline pressure, working alone.

Brand guidelines sheet — Arial typography hierarchy and TELUS color palette

Brand guidelines — Arial as global enterprise fallback, TELUS Purple/Green/Accessible Green/Thunder color system, documented for all non-designers.

Google Slides master slide Theme Builder — layout and slide architecture

Master Slide Theme Builder — locked layouts that protect the grid. Teams add content; the system protects the brand.

Google Slides sales deck open on laptop — design principles slide with principle cards

The 100+ slide global sales deck master — modular principle cards that regional teams populate without design involvement.

Single Source of Truth

One Drive folder to replace a dozen hard drives and three legacy servers

The SSOT was deployed as a strictly governed Google Drive environment — structured into six asset categories: Fonts, Guidelines, Icons, Logos, Photography, and Templates. Every approved asset lived in exactly one place. Every deprecated local file became irrelevant the moment the Drive was live.

The architecture decision that made adoption stick: view-only permissions by default. Teams could access everything, use everything, and customize within the templates — but they couldn't modify the masters, overwrite approved assets, or accidentally break the governance structure.

Google Drive TELUS Digital Brand folder — Fonts, Guidelines, Icons, Logos, Photography, Templates

The SSOT Drive structure — six governed folders replacing fragmented local servers. One location. Always current. Always correct.

Dos and Don'ts governance card — use vetted templates vs use old hard drive files

Brand governance card — distributed at training sessions. Translates complex governance rules into three actionable Dos and three clear Don'ts.

Change Management & Adoption

Training a C-suite to collaborate in real time — without making them feel managed

The most technically sophisticated DesignOps system fails at the human layer if adoption is treated as an afterthought. I ran targeted training sessions across four distinct audience groups — Sales, Solutions, Product Marketing, and C-Suite Executive Assistants — each calibrated to that team's specific workflow and resistance points.

For the C-Suite track in particular, framing mattered more than content. Executives aren't resistant to new tools because they can't learn them — they're resistant because they have no margin for confusion under pressure. Every session was structured around their most high-stakes use cases, not a generic product walkthrough.

After formal training, I maintained open 1:1 coaching channels and real-time G-Chat consultations — because the questions that determine long-term adoption don't happen in training rooms. They happen at 9pm the night before a major pitch.

Google Slides deck in use — sales team presentation with governed template structure

The system in use — a governed template that any sales team member can deploy independently, without a design request, at any hour.

Operational ROI

The numbers that made the C-suite stop asking for their old system back

60%

Reduction in presentation build time across global departments

0

Ad-hoc design requests after full adoption — teams self-serve entirely

100%

Brand compliance on all high-stakes B2B pitches post-migration

These weren't vanity metrics. A 60% reduction in build time for a global sales team means more pitches, faster response to opportunities, and fewer hours lost to formatting — directly translating to commercial output. The elimination of ad-hoc design requests freed the design function to do strategic work instead of emergency slide repairs.

Deliverables

The complete system — from architecture to adoption

01

100+ slide master deck

Modular global sales deck in Google Slides with locked master architecture — fully self-serviceable by non-designers.

02

Enterprise UI kit

Arial-based brand system with TELUS color tokens, icon library, and photography guidelines for cross-platform consistency.

03

SSOT Google Drive structure

Governed six-folder asset architecture replacing local servers — view-only permissions with full team access.

04

Change management program

Four-track training program for Sales, Solutions, Product Marketing, and C-Suite EAs — tailored to each team's workflow.

05

Brand governance card

Dos/Don'ts reference distributed at all sessions — translating governance rules into plain-language field guidance.

06

Ongoing coaching channel

Real-time 1:1 G-Chat support maintaining adoption through the critical post-launch period.

DesignOps Change Management Google Workspace Sales Enablement Presentation Systems SSOT Architecture Brand Governance Enterprise Training Information Architecture