Shiva

T-Mobile: Branding internal tools

RoleBrand strategy, video, naming, AI content design

Timeline2025-2026

TeamTom Sieu (lead), Scott Thomsen (senior designer), and me

Branding internal tools and pitching them to the executives who fund them.

My part
Product videos, NORA's voice playbook, the IES identity, and naming.
Outcome
NORA launched with its video, the LESA reel reached the C-suite, and Cerebra joined the 2026 roadmap.
From the NORA launch video. Demo screens and figures removed.

Overview

We were handed internal tools: a planning platform, network automation products, an AI for care agents and an AI for cell site leases. They all worked, but each still needed executive funding.

Our job was to name and brand them and make the business case for each, mostly through video.

Most of this work is under NDA, so internal figures, names and screens are removed.

Brand architecture, from the org down to the standards hub

NORA

NORA is an AI tool that helps frontline care agents fix network problems while the customer is still on the call. It pulls answers from many separate systems and suggests the next step. We worked on how NORA talks, and on how its story was told to leadership.

The launch video

The video opens on one customer and one dropped call, then shows the agent piecing together answers from a pile of disconnected tools. The pile collapses into a single point, and NORA arrives.

Storyboard row for the opening of the NORA video, with voiceover lines under each frame
Storyboard for the opening, with the voiceover

We storyboarded every beat against the voiceover and worked through many rounds of notes. Every scene sits on magenta, the T | NORA lockup opens and closes the film, and the NORA star lands on the spoken name. Leaders from teams using NORA speak in their own words, then shrink to a headshot so their results fill the screen.

It ends on where NORA goes next: fixing issues before customers call, and a ready frontline when they do.

Writing NORA's voice

A correct answer can still be useless on a live call. We sorted NORA's real answers into good and poor. The poor ones were long and technical, buried the key issue, and packed several steps into one sentence.

So we wrote a persona for the care agent: working a tight shift, reading in fragments while a customer waits, and wary of escalations.

North star

  • Every NORA output should feel like a briefing from a knowledgeable colleague who knows what you need and respects your time, not a system log.

Guiding principles

  • Speak plainly, for the agent and the customer
  • Show only what moves the conversation forward
  • Always land on clear next actions
  • Make the last step a clean handoff
  • Structure every output the same way
  • Optimize for skimming
  • Communicate system status and what it means
NORA's guiding principles, from the playbook
Illustrative before and after of an AI troubleshooting answer. Before: dense paragraphs with the status buried and several steps per sentence. After: status at a glance, a one-line likely cause, three ranked steps each with what to say, and a note about missing data.
One answer before and after, with made-up data

The principles became a playbook for the engineers writing NORA's prompts: voice and tone, scenarios, and examples of good answers. It also covers what NORA says when it isn't sure. It says so plainly and adjusts the next steps.

A video system

Most tools sat under Veloce, the automation initiative. The videos needed to feel like one family, with the same structure and look. Only the story changed.

Openers and closers from the Veloce series. Product screens removed.

Each video opens on the T | Veloce mask reveal, with a headline whose last word swaps on the voiceover. Screens float as cards on a dark gradient lit in magenta. Abstract beats carry the business case, like spreadsheets folding into one platform. Every video ends the same way: a pull-back, a tagline and the lockup.

Once the system existed, we rebuilt the older Veloce videos to match.

ACS Planner

This video sells the venue planning platform from the Veloce case study, one capability per beat.

The ACS Planner video. Summary figures cut.

How we built each story

The people building a product see an engineering problem. Executives see budget, scale and impact. Our job was to close that gap and pitch each product as a business solution.

Assets and flows

For each video we asked the product owners what mattered most, then reframed it around the executive's question: is this worth funding? Problems became business costs, not team frustrations.

Timing storyboard and routes through the story

Every video followed the same structure: the problem, the capabilities that solve it and an ending tied to the opening.

Revisions to the structure

Product owners had strong opinions on length and features. We used storyboards to talk it through, showing where an idea would lose the audience before offering another way.

LESA

LESA (Leasing AI) reads decades of cell site leases so teams can find answers in seconds instead of by hand. The product team built the platform. We made the story, motion and lockup for its launch video.

From the LESA launch video. Internal figures removed.

We wrote several treatments, each with a different way in: the scale of the problem, the raw numbers, the history of the archive, and a leasing expert's morning. All followed the same arc: chaos, the size of the problem, the technology, and the fix.

Narrative flow, from the problem to the features

Reviews changed the message. Early drafts leaned on document scanning, but the real value was the knowledge graph linking every lease and amendment, and the experts who check what the AI pulls out. We rebuilt the middle of the video around both.

A magenta treatment ties the intro and outro together. Headlines are large and heavy, with a drop shadow so they read over busy footage. The lockup builds on the product's existing mark.

Platform features and the end card

IES

After a reorg, a new executive group called IES (Insights, Enablement and Strategy) had a mandate but no shared story. We ran a short sprint to create one.

We interviewed the pillar leaders about their roles, what success looked like, the problem IES solves, and a metaphor for it.

Interview Goals

  • What is your role within your pillar?
  • How would you describe IES from your point of view?
  • What value does IES deliver?

Discussion topics

  • What are the intent and impact of the IES pillars?
  • Why does it matter to your end users or audience?
  • How are the IES pillars connected?

Interview Questions

Pillar-Specific
  • Tell us about your role and responsibilities.
  • What is your pillar's unique value proposition?
  • What are the 2-3 KPIs that prove your pillar is succeeding?
Vision & Mission
  • What key problems is IES meant to solve?
  • What does success (the moonshot goal) look like for IES and FE&O?
  • If the moonshot goal is achieved, what becomes possible?
Business & Customer Impact
  • What customer experience improvements should IES enable?
  • What business metrics should move because IES exists?
  • How do the IES pillars connect horizontally?
Identity & Storytelling
  • What's the elevator pitch for IES?
  • What analogy or metaphor best captures what IES does?
Interview goals and questions for the pillar leaders

From those interviews we drafted themes and cut them to three: Strategic Focus, Horizontal Orchestration and Scaling for Impact. Each became a full messaging stack: vision, positioning, value, key messages and tone.

The messaging architecture. Figures redacted.

The framework was a chain: data leads to governance, governance to accountability, and accountability to predictable execution. It became the IES vision, mission and principles, delivered as a brand playbook and an executive deck.

The framework, for executives

One system, many brands

IES and its products needed to look like one organization. We built a deck template and lockups used by both IES and Veloce.

IES and Veloce title slides on the same template

We ran the same framework on Veloce. Its voice is confident and practical, grounded in results. The line: "Smarter Tools. Faster Teams. Better Network."

Cerebra

Inside Veloce, RAN Standards Studio held the templates, rules and reference data that automation runs on. The team wanted a name for what it would become.

The brief: not too literal, not too abstract, forward looking, and carrying authority. A north star for the source of truth.

The first round explored directions like Control Center, Acceleration and North Star. The second narrowed to three metaphors: a control center, a nervous system and a self-service space. Cerebra came from the nervous system, the brain behind everything else.

Naming rounds one and two

Cerebra won. Tom designed the logo and we built the lockups. It now sits on the Veloce roadmap as the standards layer.

Outcomes

  • NORA launched with a video for leadership and a voice playbook for its engineers
  • One video system across the Veloce tools, with older videos rebuilt to match
  • Scope grew from one overview video to the Veloce suite, NORA, LESA and an executive reel
  • The LESA reel was shown to C-suite leadership
  • IES launched with a brand playbook, messaging and an executive deck
  • Cerebra named and placed on the Veloce roadmap

The growing scope was the clearest sign the work was landing.