This is the work nobody notices, until it breaks. Identity architecture rarely appears in product launches, marketing campaigns, or design showcases. Yet it quietly influences every login, every recommendation, every support interaction, and every personalized experience.
By the time I joined, Verizon had already invested years into solving identity from multiple angles. Despite meaningful progress in individual areas, the organization still lacked a unified framework for understanding customers across products, services, devices, and households. The need was widely recognized; the challenge was defining what problem we were actually trying to solve.
On the surface, identity appeared to be a technical challenge. In reality, it was an organizational one. Ownership was fragmented, incentives were misaligned, and the work often required teams to prioritize long-term customer understanding over short-term product goals. These forces made identity one of the most important, and most difficult problems to solve.
Everyone owned a piece. Nobody owned the whole.
Identity spanned nearly every part of Verizon, yet no single organization was responsible for the customer as a complete entity.
As a result, initiatives focused on optimizing products rather than understanding customers across products.
Identity was important, but never urgent.
Teams were rewarded for product-specific outcomes, not cross-product customer understanding. Success was measured by:
Identity work required coordination, patience, and long-term investment while distributing benefits across multiple teams. As a result, it consistently lost priority to more immediate initiatives.
The deeper the problem, the harder it was to touch.
Years of growth created fragmented identity systems, inconsistent schemas, and fragile integrations. Many stakeholders viewed identity work as inherently risky:
This encouraged incremental fixes instead of structural change.
The organization saw infrastructure. The customer felt experience.
Most previous efforts focused on authentication, account consolidation, or technical cleanup. While valuable, these initiatives positioned identity as a back-end capability rather than a strategic business asset.
The result was a disconnect between:
The more I investigated, the clearer it became: this wasn't a data problem or a technology problem. It was an understanding problem. Before defining a solution, we first needed to understand what was actually broken.
Leading Verizon Home gave me a unique vantage point into the ecosystem. I had experienced the consequences of fragmented identity firsthand, from authentication failures and account confusion to disconnected customer journeys across products and services. Combined with a passion for navigating ambiguity and solving large-scale systems problems, this perspective allowed me to connect customer experience, business strategy, and enterprise architecture.
The symptoms appeared everywhere, but they all traced back to the same underlying issue: Verizon understood accounts better than it understood people.
Verizon had accounts, products, and services, but no unified customer model. As people moved across the ecosystem, their information fragmented into separate records. The same person could appear as multiple customers depending on where they entered.
Verizon collected enormous amounts of customer data, yet teams struggled to connect it into a meaningful picture. We weren't missing data. We were missing relationships between data.
Identity problems compounded across customer, business, and strategic outcomes. What appeared to be isolated UX issues created ripple effects throughout the organization.
In the telecom world, the same person often exists as three different customers: the mobile subscriber, the home internet user, and the person calling support.
The system treated them as strangers.
The risks weren't immediate, which is precisely what made them dangerous. Fragmented identity rarely causes a single catastrophic failure. Instead, it quietly compounds inefficiencies, distorts decision-making, and limits an organization's ability to adapt to the future.
Customers continue experiencing fragmented journeys while teams compensate with more features, campaigns, and support efforts.
Without a shared understanding of customers, product decisions become increasingly driven by fragmented data and incomplete signals.
As competitors build intelligent ecosystems around people and households, Verizon remains organized around accounts and products.
By connecting identity, relationships, devices, services, and behaviors, every Verizon touchpoint can evolve from a transaction-driven experience into a context-aware system that understands and supports each household.
A connected identity foundation creates value at every level, from simplifying customer experiences to enabling proactive business capabilities and long-term strategic growth.
"Verizon understands my household and helps me manage it effortlessly."
"We move from reactive support to proactive intelligence."
"Identity becomes the operating system for Verizon's future ecosystem."
The value of identity isn't knowing who customers are.
It's understanding what they need before they ask.
Identity is not a login system.
It's the operating system of the
customer's digital and physical life.
We didn't need to start with a platform.
We needed to make the cost of not having one visible.
"People can't align around something they define differently."
The first step was creating a shared language and decision framework for identity.
"Make people stop debating definitions."
"People support what they can see."
Rather than pitching a future platform, we demonstrated tangible improvements through high-friction customer journeys.
"Show what's possible before asking for investment."
"People move when the cost of inaction becomes visible."
Identity needed to be tied directly to business outcomes and strategic risks.
"Shift the conversation from 'How do we build this?' to 'Can we afford not to?'"
The immediate goal was never to launch a platform. It was to create alignment around a problem that had remained difficult to define for years. The resulting framework established a shared language, a long-term vision, and a practical path forward for the organization.
This project reinforced a lesson I've seen throughout my career: the hardest problems are rarely design problems, data problems, or technology problems. They are alignment problems. Organizations often understand the symptoms long before they understand the system creating them.
Products inherit the strengths and weaknesses of the organizations that build them.
Teams cannot rally around solutions when they define the problem differently.
Some of the most valuable design work happens between disciplines, creating shared understanding across customer experience, business strategy, and technical architecture.
From reactive utility to proactive intelligence, building a connected home product that earns trust over time.