Virgin Media O2 — Design Sprint and Problem Framing training for enterprise technology teams

The specific challenge of innovating in B2B enterprise technology

Most design and innovation methodology was developed in consumer product contexts. The feedback loops are short: you build something, put it in front of users, and learn quickly. The customers are individuals whose experience you can simulate in a testing session. The failure modes are visible and relatively contained.

B2B enterprise technology operates under different conditions. Virgin Media O2's private wireless network solutions are deployed in transport hubs, manufacturing facilities, and hospitals — environments where the "user" is an operations manager, a logistics coordinator, or a clinical team, and where the problem being solved isn't an inconvenience but a meaningful operational challenge. Getting a solution wrong in those contexts doesn't produce a bad review. It produces disrupted operations, safety incidents, or failed deployments that take months to unwind.

That's the context in which Virgin Media O2 decided to invest in Problem Framing and Design Sprint training in July 2022.

What the training was designed to address

As a leader in private wireless networks — including the first UK telecoms company to offer a 5G standalone private network — Virgin Media O2 works with clients across sectors that have fundamentally different operational environments, regulatory requirements, and definitions of what a solution needs to do.

The challenges the teams were trained to address included operational efficiency and worker safety: two areas where the cost of proposing an underdeveloped solution is real, and where the gap between what a technology can do in principle and what a specific client environment actually needs is often significant.

This is the underlying problem that made Problem Framing and Design Sprint training a relevant investment. When you operate across multiple sectors — transport, manufacturing, healthcare — and each sector has its own operational logic, its own stakeholders, and its own constraints, you can't afford to arrive at a client conversation with a generic solution looking for a fit. You need a disciplined process for understanding what the specific problem actually is before proposing what the technology should do.

Problem Framing gives teams that process. It creates the structure for moving from a client's expressed need — which is often a symptom of something more specific — to a precise problem statement that defines what a solution would actually need to address. In B2B enterprise technology, where the sales cycle is long and the implementation stakes are high, that precision upstream saves significant cost downstream.

Why Design Sprints work differently in an enterprise B2B context

Design Sprint methodology compresses the cycle from defined problem to tested solution direction into a structured few days. For consumer products, the testing step typically means putting a prototype in front of end users and observing their responses.

In B2B enterprise technology, the testing step is structurally more complex. The people who make purchasing decisions are not always the people who use the solution. The operational environment can't be fully simulated in a testing session. And the constraints — technical, regulatory, operational — that determine whether a solution is viable often live in the client organization rather than in the building where the sprint is happening.

What Design Sprint training gives B2B enterprise teams is not a template to follow but a discipline to apply: the habit of testing assumptions about what the client actually needs before those assumptions are embedded in a developed solution. That discipline — building something that can be tested early, getting it in front of the people who will use or evaluate it, and treating the feedback as the point of the exercise rather than an interruption to delivery — is as valuable in enterprise contexts as in consumer ones, and perhaps more so, because the cost of testing late is higher.

For Virgin Media O2's teams working across transport, manufacturing, and healthcare, this meant developing the capacity to rapidly ideate, prototype, and test solutions with real clients in each sector — not after months of development, but before significant technical or commercial commitments were made.

What Problem Framing and Design Sprint training produces together

The Virgin Media O2 engagement covered both methods in sequence, which is the configuration that produces the most complete capability.

Problem Framing training develops the capacity to define the right challenge before any solution work begins. For teams that routinely arrive at client conversations with a technology capability and need to identify where it genuinely solves a real problem, this is the upstream discipline that determines whether the sprint that follows is working on the right thing.

Design Sprint training develops the capacity to move efficiently from a defined problem to a tested solution direction. It gives teams the tools to prototype at the level of fidelity needed to generate useful feedback — not a finished product, but a representation of the solution concept that a client stakeholder can respond to with enough specificity to inform the next decision.

Together, the two methods create a complete loop: define the problem with precision, then validate a solution direction before committing to full development. For enterprise technology teams that work on complex, multi-sector challenges with long development cycles and high deployment stakes, that loop is the difference between building what a client actually needs and building what a client initially described.

The output the training was designed to produce was an internal capability that could be applied across sectors — a reusable approach to problem-solving that didn't need to be rebuilt from scratch for each new client engagement. In that sense, the investment in training was also an investment in scalability: equipping teams to apply the same disciplined process in transport as in manufacturing as in healthcare, adapting to each sector's specifics without losing the structure that makes the process reliable.

What this means for enterprise technology teams

The Virgin Media O2 case reflects a pattern that shows up across large B2B technology organizations: the technical capability to build sophisticated solutions exists, but the internal process for determining precisely what to build — and testing that direction before committing resources — is underdeveloped.

This gap is not unique to telecoms. It appears wherever the gap between what a technology can do and what a specific client environment actually needs is wide, and where the cost of closing that gap late in the development cycle is high. Enterprise software, industrial technology, infrastructure, and professional services organizations all operate in versions of this environment.

Problem Framing and Design Sprint training doesn't solve the complexity of operating across multiple sectors with different client environments. What it does is give teams a repeatable process for navigating that complexity at the problem definition and solution validation stages — the two moments where misdirection is most costly and most avoidable.

For organizations considering this investment, the question worth asking is not whether the methodology is relevant to their context but where in their current process the most expensive errors get introduced. The answer, in most enterprise technology organizations, is early: in the gap between what the client says they need and what the team actually builds toward.