Skills:
- Design leadership.
- User experience research
- User experience design
- User interface design
- Prototyping
- Dark Theme & UI design
- Team coordination

Tools:
- Design thinking
- Paper Prototyping
- Sketch
- Sketch Cloud
- Zeplin
- Slack
- Notion

Customer(s):

- Major Telcos

- Financial institutions 

- Retail / e-commerce

- Software / SaaS

- Manufacturing

- Energy providers 

Solution:
- Web-based application
- User authentication
- Domain connection(s)
- Real-time access
- Network monitoring
- Situational awareness
- Entity inspection
- Entity inventory
- Entity data tracing
- Entity root Cause Analysis

Enterprise Metaverse — Crafting a 0 to 1 Streaming App for Network Intelligence

While not a metaverse in the avatar-and-headset sense, this is an Enterprise Metaverse for network intelligence—a living digital twin of a Fortune 500 telecommunications provider’s national infrastructure, rendered in real-time, interacted with spatially, and used collaboratively to maintain and optimize operations at scale. This was a 0→1 innovation effort, crafted from the ground up on an advanced real-time streaming application platform. The result: a first-of-its-kind experience that transformed passive monitoring into immersive, high-impact situational awareness for executive and operational teams alike.

​​

Structure

Each project in my portfolio follows a clear, outcome-driven structure rooted in design thinking and product strategy. From uncovering the problem to delivering results, this format showcases how I approach complex challenges, collaborate across disciplines, and create meaningful impact through thoughtful, scalable design.

​

A clear way to tell this story

​

​I adopted a proven simplified framework—Context, Problem, Approach, Output, Outcome—because it offers a clear, intuitive way to communicate the full arc of a project without overwhelming the viewer. In a portfolio, clarity and structure are key. This framework distills complex design work into digestible sections that mirror how product and design teams think: beginning with the why, moving through the how, and ending with the impact. It also complements design thinking by surfacing insights, actions, and results in a linear, story-driven format that invites readers to engage deeply with the project while staying grounded in real-world outcomes:

​

• Context

• Problem

• Approach

• Output

• Outcome

​

Each of my projects follows a structured yet flexible storytelling structure and design thinking approach, tailored to the problem space and the needs of the users. This framework not only helps organize my process for clarity, but also showcases how strategic thinking, rapid iteration, and cross-functional collaboration come together to deliver meaningful outcomes. Below, you’ll find a breakdown of how the work unfolded—from understanding the challenge to delivering real-world impact.​​

​​

Context

​

Why did this project start? What was the initial hypothesis or business driver?

​

Every project begins with a unique set of circumstances, constraints, and ambitions. This section outlines why the project was initiated, who it was for, and what hypotheses or goals shaped the early thinking.​​​

​

A high stakes opportunity to partner with a Fortune 500 telco

​

The project began as a high-stakes opportunity to partner with one of the largest Fortune 500 telecommunications companies in the world. Their executive team was exploring next-generation solutions to improve national infrastructure monitoring and gain real-time visibility across vast, complex systems. This wasn’t just a dashboard refresh — it was a chance to reimagine how an entire organization could perceive and respond to data at scale. Our initial hypothesis was bold: that a unified, real-time, single pane of glass experience could dramatically improve operational awareness, reduce response times, and unlock new strategic value across their enterprise.

​

With a potential multi-year, multi-million dollar partnership on the line, we set out to prove that we could design a breakthrough interface — not just for data, but for decision-making. We believed that by visualizing live, streaming infrastructure data in an intuitive, performant way, we could transform how teams detect anomalies, respond to network events, and collaborate across domains. Our approach needed to be fast, flexible, and convincing — not only to win executive trust, but to show that we could deliver a product experience worthy of the scale and complexity of one of the most critical networks in the country.

​

Why an enterprise metaverse?

​

While the term “metaverse” often evokes virtual worlds and avatars, the core concept is about persistent, interactive digital environments that reflect and respond to real-world systems. In that sense, the single pane of glass solution we designed for Verizon functions as a true Enterprise Metaverse—a real-time operational mirror of the company's vast national infrastructure. It’s always on, always updating, and enables users to observe, navigate, and interact with millions of live entities across markets, regions, and systems. This isn’t a metaphor—it’s a living digital twin, purpose-built for awareness, action, and insight at enterprise scale.

​

• It’s a real-time, spatialized, data-rich environment where live entities and systems are continuously rendered, updated, and interacted with.

• Users engage with millions of dynamic, high-value assets as if they were present and observable in a shared digital space.

• There are multiple “view modes” (dashboard vs. map), layered interactions, and the ability to explore relationships, adjacencies, and hierarchies — like navigating a real-world system in a virtualized state.

• It’s always-on, multi-user aware, and highly immersive in terms of data fidelity and responsiveness.

​

​Together, these qualities elevate the experience beyond traditional dashboards or monitoring tools. This is not just data on a screen—it’s a living system interface, giving executives and operators a shared, immersive view into the real-time state of their network. It enables faster decisions, deeper insight, and continuous collaboration—hallmarks of what the Enterprise Metaverse promises to deliver.

​

​

Problem

​

What user or business problem were we solving? What made it a "wicked" problem?

​​

Verizon faced significant challenges in monitoring its vast and complex network infrastructure in real time. Existing tools were fragmented, outdated, and required engineers to rely on multiple systems—often command-line interfaces or siloed dashboards—to piece together a holistic view of network health and performance. This created delays in incident response, reduced situational awareness, and made it difficult to identify patterns across different regions or service layers.

​

They had limited real-time visibility into their network

​

​​​​​Many organizations deal with massive amounts of streaming data. In fact, 6 out of 10 process an average of more than 100,000 messages every second through their

streaming data solutions. 5 out of 10 (21%) process more than 1 million messages per second, 2% process a staggering 10 million messages or more every second.

​

Identifying the problem in a design thinking process isn’t just about documenting pain points—it’s about uncovering the deeper, often hidden barriers that prevent users or organizations from achieving their goals. In some cases, like with Verizon, the problem is what we call a wicked problem: a complex, multi-layered challenge with no clear solution, constantly shifting requirements, and high interdependence across systems and stakeholders. These problems don’t have a single “right” answer. They demand a human-centered, iterative approach to truly understand the needs beneath the surface.​

​

Unmet Need: Live Unified Visibility

The lack of a unified interface meant that troubleshooting was reactive and labor-intensive, leading to higher operational costs and longer resolution times. Moreover, the tools in place lacked intuitive design, making onboarding difficult and limiting the accessibility of network insights to non-technical stakeholders. Simply put, there was no single source of truth or streamlined workflow to understand what was happening in the network—right now, and at scale.

​

We would need a solution that aligned with solving their pain points:

​

• High development overhead and fragmented tooling

• Slow time-to-market for data-driven features

• Lack of centralized observability and orchestration

• Engineering bottlenecks due to steep learning curves

​

Verizon didn’t just have a dashboard problem — they had a need for live, unified visibility across their national infrastructure, something no existing system could provide in real time. That was the true problem — and the unmet need.​

​

The actual unmet need, live unified visibility at scale

​

Defining the actual unmet need means going beyond what users say they want, and getting to what they truly need to succeed. For Verizon, the unmet need wasn’t just “faster dashboards”—it was real-time situational awareness at scale, accessible to cross-functional teams, with the ability to respond immediately to emerging issues. This meant reframing the problem not as a UI challenge, but as a systemic need for clarity, speed, and trust across an entire organization. Identifying and defining this need was the first step toward building a breakthrough product.

​

​​​Meeting the unmet needs of potential and existing customers has always been my focus. Leveraging existing and innovative technology in creative and new ways, to solve these customers wicked problems.​​​

​

​​​​​Many organizations deal with massive amounts of streaming data. In fact, 6 out of 10 process an average of more than 100,000 messages every second through their

streaming data solutions. 5 out of 10 (21%) process more than 1 million messages per second, 2% process a staggering 10 million messages or more every second.

​

Let's get into defining the personas and understanding the unmet needs at a much lower level, by engaging the actual people with the actual unmet needs. A deep dive into the action priorities and expected user outcomes. ​​Easier said than done, when it comes to TBs of streaming data and millions of high value assets (entities) streaming that data every millisecond to second! ​And how would one (an operator let's say) monitor all of this in real-time via his laptop or mobile device?

​

Working closely with all Verizon AI&D stakeholders, and interviewing network operators allowed the design and development team insights into what Verizon really needed.

​

Focus on real people, throughout the entire process

​​

Rather than starting with abstract system requirements or generalized pain points, we focused on the actual people inside the organization — the operators, analysts, and decision-makers who struggled daily with fragmented tools and delayed data. By engaging directly with these users, observing their workflows, and asking deeper questions, we uncovered unmet needs that weren’t immediately visible in surface-level conversations. Their challenges weren’t just technical — they were cognitive and operational: too many dashboards, too little clarity, and no unified source of truth. This shift in perspective was key. By understanding the real work and mental models of the people behind the problems, we were able to define a solution approach grounded in their reality — one that simplified complexity, surfaced timely insights, and ultimately made their jobs easier and more impactful.

​

Personas: Executives & Engineers

​

Verizon wanted a separate app experience for both Executives and Engineers. Ok, so two baseline personas with two very different perspectives and interests when it came to network infrastructure monitoring.

​

Executives and engineers, both with actual unmet needs

​

The Executive based experience, was to be an ultra-low latency nationwide & locale greater situational awareness (for proactive exec monitoring & action) to allow executives real-time continuous insights across the entire nationwide system 

​

• Quickly monitor, explore, and discover at all market levels within a single unified single pane of glass app 

• Monitor in real-time continuously nationwide network performance, across all submarkets

• Receive real-time notifications for non-performant (w/ severity levels) entities within the network

• Quickly travel between a dashboard (default) view and a second map view mode​

• Leverage the existing entity model for search & filtering, navigation, and greater situational awareness

• Search, filter and navigate quickly (per the established entity model hierarchy) to any market, sub-market or LT market levels 

• Switch quickly between market levels, sub-markets and LT markets

• Look “under the hood”, regarding the underlying technology, platform and entity model

​

Simplicity does not proceed complexity, but follows it​​

​​

The awe-inspiring sands of simplicity exist on the far shore of that fearsome sea of complexity. One (safer to travel in teams) must travel through that complexity to arrive at the far shore of simplicity.

​

Aligning actual unmet needs of the customer, their actual user operator tasks and responsibilities, to view, component and application UI design priorities. A major telecommunications provider had limited visibility of their network infrastructure - requiring several hours to measure service quality. The lack of real-time information made it difficult for field service crews, IT departments, and customer service representatives to work collectively towards improving customer experience in a highly competitive market. Major telecommunications companies are not the only companies that require more real-time visibility into their networks in order to provide a higher quality of service to their customers. Financial institutions, e-commerce, software/SaaS provider, manufacturing, and energy provider companies all have the same need.

​

Many organizations deal with massive amounts of streaming data. In fact, 6 out of 10 process an average of more than 100,000 messages every second through their

streaming data solutions. 5 out of 10 (21%) process more than 1 million messages per second, 2% process a staggering 10 million messages or more every second. 

​​

An actual wicked problem exists

​

Before engaging Swim (later Nstream), Verizon faced a classic wicked problem: making sense of massive, real-time network data spread across siloed systems, teams, and tools. There was no unified view of the live network state—only fragmented dashboards, delayed reports, and reactive decision-making. The complexity of their infrastructure, combined with the speed and volume of data, made it nearly impossible to achieve true situational awareness or respond to issues as they emerged. What they needed wasn’t just another analytics platform—it was a radically new approach to visibility, clarity, and action.

​

The inability to build real-time continuous applications on this massive amounts of streaming data has become a real problem for many companies. The unmet need is real and without these real-time applications, these companies are at risk of not providing quality customer service and experience.

​

Verizon's inability to continuously monitor their network infrastructure in real-time not only limited their proactive decision making capabilities, but also limited their ability to get ahead of network problems before they became much bigger "problems" affecting thousands and potentially millions of customers.

​​

​Now that we have defined our personas we are ready to move into the approach phase. In the approach phase I walk through my design thinking approach—how I gathered insights, collaborated with stakeholders, and iterated toward a solution.