We just renamed the team, I am a part of.. We went from "Tech, Owned & Data" to "Digital Experience." On paper, it's just words. In practice, it changed nearly everything about how we operate, what we're asked to do, and how seriously the wider business takes our work.
I want to talk about why naming matters so much for internal teams, and what I learned from getting it right after years of getting it wrong.
The problem with the old name
"Tech, Owned & Data" was accurate. We did handle technology, owned channels, and data. But accuracy isn't the point of a team name — positioning is.
Here's what stakeholders heard when I said "Tech, Owned & Data":
- "Tech" → these are the IT people, call them when something breaks
- "Owned" → they manage the website, probably some social media
- "Data" → they pull reports when I need numbers for a presentation
None of that was wrong, exactly. But none of it captured what we actually did, which was shape the entire digital experience across markets, build the content and AI strategy, and drive business outcomes through owned channels. The name created a ceiling for our perceived scope.
A team name isn't a description. It's a pitch. Every time someone reads it on an org chart, they're making assumptions about what you can and should be involved in.
Why "Digital Experience" works
"Digital Experience" does three things the old name didn't:
It centres the customer. "Experience" is inherently outward-facing. It signals that we care about what the end user encounters, not just the machinery behind it. This shifted how product teams thought about involving us — from "can you build this page" to "how should this experience work."
It's broad enough to be ambitious. Experience covers content, technology, search, AI, analytics, and the connections between them. Nobody questions why a Digital Experience team is involved in an AI visibility project or a content strategy workshop. With "Tech, Owned & Data," I spent half my time justifying why we had opinions about content.
It's recognisable outside the company. Try explaining "Tech, Owned & Data" to a prospective hire. Now try explaining "Digital Experience." One requires a five-minute backstory. The other is instantly understood.
The ripple effects
What surprised me was how much changed without us pushing for it. Within three months of the rename:
- We were invited to strategic planning meetings we'd never been part of
- Two cross-functional projects listed us as stakeholders by default
- Recruitment became noticeably easier — candidates understood the role from the title alone
- Team morale improved because people could finally explain to their families what they did
That last one sounds trivial, but it isn't. Pride in your team's identity matters. When your mum asks what you do at work and you can say "I work in Digital Experience" instead of "I'm in Tech, Owned & Data... it's complicated," that changes how you feel about showing up on Monday.
How to know it's time
If any of these sound familiar, it might be time:
- You spend more than 10% of stakeholder conversations explaining what your team does
- People route requests to you that should go elsewhere (or miss routing requests that should come to you)
- Your team's name doesn't appear in strategic planning documents, even when your work directly contributes
- New hires take weeks to understand the team's scope and positioning
What we would do differently
We might have waited too long. We treated the name as cosmetic when it was structural. If we could go back, we would have renamed earlier and be even more deliberate about the launch.
Names are levers. In an organisation where attention is scarce and assumptions are formed in seconds, the words on the org chart matter more than most leaders admit. If your team name is holding you back, change it. It's one of the highest-leverage, lowest-cost moves you can make.