IXL Learning · 2022–2026 · Brand Systems

Brand Foundations

The color, type, and logo systems behind fourteen brands, and the governance that kept them true.

Brand Foundations at IXL: the color, type, and logo systems behind fourteen brands
Product

IXL, Takeoff, LevelUp, Rosetta Stone, Vocabulary.com, and the wider IXL family

My Role

Owner of the brand layer. Color, type, logos, trademarks, print standards

Team

Graphic Design, Digital, Marketing, Product, Legal, and external print partners

Timeline

2022 to 2026, still in use after my last day

Brand Systems Color Standards Typography Design Ops Multi-brand

Live artifactOpen the IXL Brand System guide ↗

00 · The System

One brand family, fourteen ways to get it wrong.

The IXL Learning brand family: fourteen brand lockups from IXL and Rosetta Stone to Carson Dellosa, with the shared brand layer of color, type, logo, trademark, and print underneath
The family at a glance: fourteen brands, fourteen audiences, one brand layer held consistent underneath.

IXL Learning runs a family of brands: IXL, Takeoff, LevelUp, Rosetta Stone, Vocabulary.com and more. 14 brands, each with its own audience, its own surfaces, and its own reasons to drift.

Read it the atomic way: atoms (color and type), molecules (the logo lockups, the icons and illustration), organisms (the template catalog), and the ecosystem of ownership that keeps all of it alive.

The rebuilt IXL brand guide, logo chapter: monogram and corporate lockup cards, logo colors with PMS values, do and don’t lists, and the background rules from white to the Blue 900 knockout
Inside the guide: the logo chapter, from the monogram and corporate lockup to the background rules.

And this page has a companion: the system itself, rebuilt as a living brand guide, fourteen sections from principles to governance, set in the real Roboto Slab and Open Sans.

Style guides across the IXL family: a grid of brand logos from IXL and Rosetta Stone to TPT beside their one-page style guides, each on the same skeleton with its own palette and marks
The layer in practice: every family brand’s style guide on the same skeleton, each with its own palette and marks.

I owned the layer underneath all of them. As the owner of graphic and marketing design, I held brand consistency and quality control across every print and marketing project, and partnered with the designers on the digital side to keep the same look aligned on screen, so all 14 brands stay consistent as one family. Color standards, typography, logo and trademark systems, and the libraries every designer built from. Not the campaigns. The thing the campaigns stand on.

This page is about that layer, and about the part people forget: a standard nobody maintains is just a snapshot.

One note on scope. The chapters that follow walk the process through the IXL brand itself, the flagship, because it is the clearest way to show how the layer works. The other family brands ran on the same foundations and the same governance, but this study does not break them down brand by brand.

The brand layer is invisible when it works and expensive when it does not.

01 · Why It Exists

Nobody knew which file was the real one.

The design org at a glance: thirty-plus designer figures with one highlighted in IXL blue and gold for graphic and marketing design, beside the streams of marketing, brand, and print work that all ran through that one person
Thirty-plus designers, one graphic and marketing design line. Everything on that line ran through one person.

IXL’s design org was thirty-plus designers under one design director, almost all of them in product and UX, plus illustration and digital art. Graphic design was me. Two more graphic designers arrived later through acquisitions, but they stayed with their own product lines.

Owning the graphic and marketing design line was written into the role from the first week. What I inherited was not a system. It was a pile of folders, and every piece of marketing, brand, and print output ran through one person and the contract designers I directed.

So most days started the same way. The in-house team, our external vendors, and the contract designers all asked me a version of the same question, and I answered it one person at a time.

Work was assigned to whoever had capacity that day. With no template to start from, two designers given the same brief built it two different ways, and the versions multiplied from there.

There were two ways to handle that. Keep answering, or go upstream and remove the reason people were asking. I spent the next four years on the second one.

Three symptoms, one cause.

Findability

Source files scattered

Templates lived in personal Drive folders, old tickets, and people’s heads. Version history was a conversation, not a system.

Consistency

Color drifted per surface

The same brand blue was one value on screen, another in a brochure, and a third on a 20 foot booth wall. Nobody had converted it on purpose.

Governance

Logos multiplied

Fourteen brands, several product lines, and no shared rule for sizing, clear space, or where the trademark symbol belongs.

Root cause

If a designer cannot find the correct file in thirty seconds, they will make a new one.

02 · Principles

Four rules, load-bearing.

Everything in this system falls out of four principles. They were never written as a poster; they were enforced as habits, which is why they held.

The four IXL design principles as cards: one source fourteen brands, governed not guarded, print and screen agree, duplicate never overwrite
The four load-bearing rules, set in the guide’s own type and spot illustrations.
01

One source, fourteen brands

Every brand reads from the same library. Nothing canonical lives in a personal folder.

02

Governed, not guarded

Named owners and open reviews instead of gatekeeping. Asking beats guessing.

03

Print and screen agree

Every color ships with hex, RGB, CMYK, and PMS. Parity is designed, never hoped for.

04

Duplicate, never overwrite

The template location is read-only by convention. Version safety is a habit, not a hope.

03 · Atoms · Color

Color was the first thing that had to be true.

I built the color system as a file, not a document. CMYK color spaces went into the IXL Main Library and the Takeoff Library in Figma, with .ase swatch files attached, so any designer could pull the palette straight into Illustrator or InDesign instead of typing values by hand.

The IXL color system: five Pantone-style swatch cards with hex, RGB, CMYK and PMS values, beside the .ase swatch file and the two Figma libraries
Five brand colors, every value a surface needs: hex, RGB, CMYK, and the PMS anchors that survive a supply chain. Shipped as .ase and Figma libraries, never as a PDF.
Color ramps from 100 to 900 for blue, green, teal and orange, the three token tiers, and the deuteranopia-safe pair
Ramps and tokens: 100 to 900 per hue, three token tiers, and the deuteranopia-safe pair verified in Color Oracle before it shipped.

Print and screen parity

Brand color was defined in RGB. Large format output is CMYK. I converted the palette once, centrally, checked it on press, and published both values as one system rather than letting each vendor guess.

Pantone as the anchor

For anything with an ink, a coating, or a molded part, PMS is the only value that survives the supply chain. I bought the books, built an ink and paper sample library, and specified PMS per component on dimensional product.

Colorblind verification

One template used color to carry meaning, which meant it failed for red-green colorblind students. I built a deuteranopia-safe pair and verified it in Color Oracle before it shipped.

The IXL palette under deuteranopia simulation: each brand color shown as the original on top and the Machado 2009 simulation underneath, with blue and yellow staying separable
The palette without green cones: original on top, deuteranopia simulation underneath. Blue and yellow stay separable.
  • CMYK, Pantone, and .ase libraries published in Figma, downloadable by any designer
  • RGB to CMYK conversion done once, centrally, instead of per project
  • Deuteranopia-safe pairs verified before shipping
  • The revised core palette was adopted by both the print and digital teams

04 · Atoms · Type

Type had to work in eleven languages.

Typeface migration

The core curriculum system moved off Open Sans. I ran the evaluation across Report, New Hero, Calibri, Museo Sans and Museo Slab, then migrated a system spanning thousands of pages without breaking the layouts already in production.

The IXL typography system: Roboto Slab and Open Sans specimens, the typeface migration candidates with Museo Slab chosen, multilingual coverage and the K-5 handwriting faces
Roboto Slab and Open Sans on top, the Museo Slab migration across thousands of pages in the middle, and the eleven languages underneath.

Multilingual type

The brand shipped in Spanish, French, Chinese in both traditional and simplified forms, and Ojibwe. I moved the Rosetta Stone editions to Noto Sans for coverage, and corrected Chinese tone mark sizing, which looks like nothing and reads as wrong to every native speaker.

Type for five year olds

Kindergarten through grade 5 needed handwriting-model faces that match how children are taught to form letters. Choosing those is a pedagogy decision wearing a typography costume.

06 · Molecules · Visuals

The same hand, from a doodle to a toolbar.

Color and type make a brand recognizable. Illustration and icons make it feel drawn by one hand. This layer had the same disease as the rest of the system: assets scattered across decks, no shared rules, and every new project re-inventing the style from whatever it could find.

The IXL visual language: doodle marks and spot illustrations, the three illustration gradients, the spot scale ladder, and the two icon tiers with brand value icons, the editorial set, and product UI icons
Rebuilt from the guide’s icon and illustration chapters: one shape language, the doodle and spot libraries, the gradients, and both icon tiers.

The illustration language is flat vector, no outlines, no texture. Shapes are rounded and organic, soft two- or three-stop gradients stand in for shading, and one warm accent keeps each scene from going cold. The master doodle sheet was split into 73 individual marks and the spot library holds 68 flat objects, so a designer places one asset at a set size instead of cropping a corner off a sheet.

Icons run in two tiers. Brand icons are line art in a single brand hue with a 20 percent fill of the same hue, for culture and careers surfaces. UI icons are monochrome on a 24px grid and inherit text color. The editorial set was deduped from a 134-icon master down to 58 essentials, one icon per concept, no near-twins.

The rules stay small and strict. Icons never carry meaning alone, they pair with a label. Gradients belong to illustration only, UI surfaces stay flat. And no spot mark scales past 128px, past that it becomes a scene.

07 · Organisms · The Catalog

One document, thirty templates, every surface.

The catalog is the artifact the whole design org worked from. 30+ templates, organized by what someone is actually trying to make, not by which team happened to own the folder.

The template catalog: six groups with counts, real print band artwork, a named owner on every group, and a source file link on every entry
Rebuilt from the real catalog, page previews included: the same groups, entries, owners, and the duplicate-never-overwrite reminder. Names redacted to protect former teammates.
GroupCountExamples
Marketing collateral9Implementation guide, research report, brochures, case study, folder, slides
Multi-page publishing11Workbooks, student and teacher guides, analytics booklet, onboarding packet
Digital & social5Email template, blog post, social post, signature
Event & conference4Backdrop, booth design, conference banner, swag
Document templates5Proposals and assessment reports across four brands
Brand foundations3Logo identity assets, color palette, print guideline

Every entry links to a file. No entry links to a person’s memory.

08 · The Ecosystem

A system nobody maintains is a snapshot.

The catalog works because it has rules, not just links. Three of them do most of the work.

Governance artifacts: the duplicate-never-overwrite warning banner, the named owner list, the template request form, and the production file checklist
The three rules that do most of the work: the warning banner, the named owners, and the way in.
Version safety

Duplicate, never overwrite

Written at the top of the document, in the warning color, where nobody can miss it. The template location is read only by convention.

Ownership

A named owner per group

Unsure which file is current? Ask a specific person, named in the document: Ting for marketing collateral, Leo for digital and social, Sam for access. A system with no name attached decays.

Growth

A way to request what is missing

A request form for templates that do not exist yet. The catalog was built to grow, not to be finished.

Intake

Templates fix the output. Intake fixes what arrives.

I took over graphic design intake and reassignment, then defined the project types the queue actually contained, so a request arrives already knowing what kind of work it is and which template it starts from. The tools are part of the rules: print lives in InDesign and Illustrator, digital lives in Figma, booklets in InDesign only, written into the catalog itself.

  • Project types defined for the queue: print collateral, digital PDF, multi-page publishing, illustration, digital and social, document templates, event and conference
  • Each type points at a template in the catalog, so work starts from a known file instead of a blank one
  • I researched how another team inside the company ran their board and proposed the same workload breakdown for ours. That part was still in progress when I left

The production file checklist

A defect made it onto a 1,000 copy print run. I wrote a production file checklist and put it into the review round, before anything goes to press. It was later approved by our external print partner and adopted for their work with us.

A standard your team has to remember is a standard your team will forget. Put it where the work happens.

I built it, then I gave it owners.

I built the Graphic Design Library, the template catalog, and the request intake. Then I did the part that decides whether a system survives: I put names other than mine on pieces of it.

I brought in the two managers whose designers were already touching graphic design work. Leo managed our digital and social contract designers, so those surfaces went to him. Mara’s reports handled illustration and icons, so that went to her. The brand layer underneath stayed with me.

AreaOwnerScope
Color standardsTingCMYK, Pantone, and .ase libraries. Print and screen parity
Logo & trademarkTingPrint logo folder, sizing and clear space rules, registered mark usage
TypographyTingTypeface selection and migration, multilingual type
Print standardsTingProduction file checklist, print guidelines
Request intakeTingProject types, assignment, and reassignment
Template catalogTing, with LeoTing: marketing collateral. Leo: digital and social
Illustration & iconsMaraAsset library and usage guides

Owning the boring layer is how you end up inside every other team’s project.

09 · In the Wild

The difference is what people stopped asking me.

BeforeAfter
Which brochure template is the right one?Catalog entry, live link, source file
What is our blue in CMYK?Published .ase, downloadable from the library
Can I use the logo at this size?Sizing and clear space rules, in the folder with the files
Print defect found after the runChecklist in the review round, before press
Templates in personal Drive foldersOne location, one named owner per group

None of these were design problems. All of them were costing design time.

What the system gave back

Before, a brand or library update reached people one group at a time. I posted it separately to each team that needed it, then answered the same question again for whoever missed it. The system replaced that with one update to the core library and one announcement in a shared channel.

These are my own estimates, not a time study.

  • 10 to 15 minutes a day reading standups for library updates and brand questions. Still worth doing, but no longer the only way an update travels.
  • 30 to 60 minutes a day answering the same questions from stakeholders, vendors, and contract designers.
  • Two standing meetings, the weekly design meeting and the retro, largely stopped spending time re-explaining brand updates.

The point was never the time. It was that the answer stopped depending on whether I was online.

10 · Impact & Learnings

The system outlived the projects.

14

brands held to one standard

30+

templates governed

11

languages the type system covers

15

designers working from the libraries

  • The revised core palette was adopted by both the print and digital teams as the standard
  • The production file checklist was approved by our external print partner
  • The refreshed LevelUp identity became the standard across print, digital, and social
  • The catalog is still the entry point for every new contract designer

Standards only hold if they are easier than the workaround.

Three things I would tell myself at the start.

  • Ship the file, not the document. A PDF of brand guidelines gets read once. An .ase in the library gets used every day.
  • Name an owner or the system decays. The most useful line in the whole catalog is the one that says who to ask.
  • Build the way in before you finish. The request form mattered more than any single template, because it let the system absorb what I had not thought of.

The measure of a brand foundation is not how good the guidelines look. It is how rarely anyone has to open them.