Before working in telecom, David Lashen studied history — with a focus on how large systems form, collide, and evolve over time. Economic forces, political structures, and technological shifts rarely happen in isolation — they move together, often in unpredictable ways. That systems-level curiosity eventually led him to telecom, an industry where complexity is unavoidable, and decisions ripple across millions of customers. In this conversation, David reflects on how it shaped his path into service providers — and how that perspective guides his work today.
Thinking About Networks as Living Systems
INTERVIEW WITH DAVID LASHEN, SR. DIRECTOR STRATEGIC ACCOUNTS, 12 YEARS OF EXPERIENCE AT CHARTER COMMUNICATIONS
What drew you from studying history into working with modern networks?
I studied history in college, with a focus on 19th-century American history. What always fascinated me was how large systems evolve over time — economic systems, political systems, technological systems — and how small shifts can lead to much bigger consequences down the line.
While studying the American Civil War, I was less interested in the individual battles and more focused on what built over time – how policy decisions, economic structures, and communication breakdowns compounded over decades. It shaped how I think about complex systems, and how decisions made far upstream can have significant downstream effects.
Telecom is one of the most complex systems you can work in. Decisions don’t exist in isolation, and the impact of those decisions can ripple across millions of people.
Looking back, that interest explains why telecom ended up being such a good fit for me. It’s one of the most complex systems you can work in. Decisions don’t exist in isolation, and the impact of those decisions can ripple across millions of people. That kind of complexity has always interested me.
When you first started working inside service providers, what surprised you most about how these systems operate day to day?
What stood out very quickly was how much of the work is about managing complexity rather than solving isolated technical problems. Networks operate at massive scale, and everything is interconnected — devices, platforms, teams, processes.
You might be working on what looks like a narrow issue, but it’s always tied to customer experience, operational constraints, and long-term planning. That reality shapes how decisions are made and why progress often requires coordination across many different groups.
When you look at the telecom market today, where do you see the most pressure building?
I mostly know the US telecom market, and I think it’s ripe for consolidation. Smaller operators are getting acquired, and even some large ones merge. Convergence is happening across mobile, fiber, and cable, so I expect to see more M&A over time.
Beyond financial pressure, there’s also a growing challenge around differentiation. In a converged world, competing on bandwidth alone isn’t enough. Service providers need ways to stand out through experience — especially across Wi-Fi, streaming, gaming, and video conferencing.
How did that pressure to differentiate through experience show up in your day-to-day work at Charter?
For us on the Wi-Fi Product team at Charter Communications, differentiating through experience meant having far better visibility into the home network — and that quickly made device identification one of our biggest challenges.
As operating systems adopted MAC randomization, it became much harder to understand what was actually happening on the home network. That loss of visibility directly affected our ability to deliver features and support customers effectively.
We were already using CUJO AI at the time, and its Device Intelligence made a real difference. It allowed us to identify devices on home networks at scale without relying on fragile identifiers.
What stood out to me even then was that the technology was clearly built for service providers. It fit naturally into how operator networks run and scaled without creating additional operational burden — which is rare.
At what point did you realize you wanted to move beyond a single network and focus on solving customer problems for service providers more broadly?
Over time, I realized that the part of my role I enjoyed most wasn’t just building products — it was product discovery. I liked working with customer problems, business outcomes, and technology together.
Having worked directly with CUJO AI for years as a customer, I had already seen a company solving operator problems with technology that actually worked in production.
When the opportunity came to join the team, it felt like a natural evolution. Here, I can help solve customer problems not just for a single operator, but at scale for many service providers.
Looking back at your time on the operator side, what kind of insight did you feel was missing most?
Without question, better insight into real customer experience. Network metrics alone stopped being enough.
What really matters is whether customers can reliably stream, play games, or participate in video conferencing. That’s what quality of experience captures — and tying that experience back to network behavior is critical for service providers today.
Did your perspective change once you started working on the vendor side, supporting many service providers instead of one?
Working on the vendor side gave me a much deeper appreciation for the realities service providers operate within. Operators are managing enormous complexity, with many teams involved in every decision.
As a vendor, you have to respect that reality. Service providers are busy, under pressure, and constantly balancing competing priorities. The challenge is understanding where you can genuinely help — and where you need to stay out of the way.
Where do provider–vendor partnerships tend to feel the most strain when complexity increases?
Issues tend to arise when complexity isn’t managed carefully. When problems occur — which they inevitably do — the way they’re handled matters.
From the operator side, it’s frustrating when escalation paths aren’t clear or when vendors struggle to explain why something is happening. What builds trust is having teams that dig in quickly, understand the problem deeply, and work methodically toward resolution.
Having seen this from both sides, what makes the biggest difference in building trust during difficult moments?
Trust is built when teams respond quickly, explain clearly, and stay engaged until the issue is fully resolved.
After everything you’ve seen — from studying history to working inside networks at scale — what do you think people most often underestimate about large systems?
Large systems reward patience and punish shortcuts. The lag between cause and effect can be long, but once you understand that dynamic, you start designing decisions much more carefully.
People underestimate how long change takes in large systems. There’s almost always a significant lag between cause and effect. In economic or political systems, people expect policy decisions to improve daily life immediately, when in reality it can take years for those changes to take hold. The same is true in large-scale networks – moving from an idea to a production deployment at scale can easily take one to two years. By the time change becomes visible, the system has already been shaped by countless upstream decisions.