Digital transformation becomes sustainable when it changes the operating model
Many organizations can redesign a website, launch new features or modernize a commerce stack. Far fewer turn digital into a durable business capability. That shift happens when transformation moves beyond the front end and reshapes how the business is organized, how decisions get made and how value is measured.
Pandora’s journey offers a useful leadership lesson. What began as an effort to improve e-commerce evolved into a broader reinvention of how digital, technology, data and business teams work together. The result was not simply a better digital channel. It was a new operating model built for growth, faster learning and closer alignment between customer experience and business outcomes.
When digital is treated as an IT project, growth stalls
At the outset, Pandora was operating with a highly regionalized model. Different markets saw themselves as owners of e-commerce, while digital was still viewed as a supporting capability rather than a core engine of the business. That made progress harder. Regional complexity created duplication. Priorities competed. And because digital was not yet embedded in the business model, it struggled to command the organizational attention needed to scale.
This is a common pattern. Companies often fund digital as a program, but continue to run the enterprise through legacy structures, incentives and decision forums. The website changes, but the operating model does not. In that environment, transformation remains fragile. It depends on a few motivated leaders rather than a repeatable system for making decisions, building products and learning from customers.
The more sustainable move is to treat digital not as a channel enhancement, but as an organizational redesign challenge. That means clarifying ownership, aligning stakeholders around growth and creating the conditions for teams to learn and improve continuously.
Build a digital and technology function, not a disconnected set of teams
One of the most important moves in Pandora’s story was structural. As digital matured, the business combined digital with IT, data and analytics, and business intelligence into a new digital and technology function. That was more than an org-chart exercise. It changed the canvas of transformation.
Bringing these capabilities together created a stronger connection between customer experience, enterprise systems, data flows and decision-making. Instead of optimizing isolated touchpoints, the business could think more holistically about the machine underneath the experience: planning systems, logistics, platforms, analytics and the integration layer that connects them. This is where transformation starts to compound. Front-end improvements become more valuable when they are supported by a better back end, cleaner data and clearer accountability.
For executives, the lesson is clear: if digital is expected to drive growth, it needs institutional weight. It needs leadership authority, integrated capabilities and a mandate that reaches beyond marketing or e-commerce. Sustainable transformation requires a function that can connect commercial ambition to technical execution.
Engineering credibility matters more than many leaders think
Another defining choice was to put engineering at the heart of the organization. Too often, technology leadership is dominated by coordination, procurement and vendor management. Those capabilities matter, but they are not enough when digital becomes central to business performance. To move faster, simplify complexity and modernize the core, companies need leaders who can understand architecture, challenge technical trade-offs and build credibility with engineering talent.
Pandora recognized this and invested in engineering leadership, talent and environment. The digital hub in Copenhagen became a focal point for building that credibility. It created a place where product, technology and digital talent could work with energy, identity and shared purpose. Over time, the hub expanded, consolidating more technology teams into a single environment.
This matters because operating model change is not abstract. It depends on talent choices. Businesses that want digital to become a core capability must create conditions where strong engineers want to stay, lead and solve meaningful problems. That includes visible leadership support, modern ways of working and a culture that treats engineering as strategic, not merely operational.
Regional alignment is a leadership discipline
Global businesses rarely fail because they lack ideas. More often, they fail because they cannot align local urgency with enterprise coherence. Pandora’s regional complexity made that challenge explicit. Markets wanted different things. General managers had legitimate demands. During the pandemic, ideas arrived quickly and from everywhere.
The answer was not to suppress that energy. It was to channel it. Pandora organized around clusters and created regular rhythms for collaboration between the digital team and regional stakeholders. Weekly and monthly test-and-learn cadences helped markets bring forward ideas, evaluate them properly and decide what should move into the core platform.
This is an important operating principle. Regional stakeholders should not be treated as obstacles to standardization. They are often the source of the strongest signals about customer needs and commercial opportunities. But those signals only become useful when there is a mechanism to evaluate them consistently, test them rigorously and scale what works. Alignment is not about central control alone. It is about creating a disciplined system for distributed learning.
Teach agile through delivery, not just training
Many organizations talk about agile as a methodology. Fewer use it as a vehicle for cultural change. Pandora’s approach was practical: teach agile by doing the work. As the business responded to new market demands, it set up rapid development processes that allowed teams to build and test multiple propositions in parallel. That approach did more than accelerate release cycles. It helped business stakeholders understand what agile really means.
This is one of the most overlooked leadership lessons in transformation. Culture rarely changes through presentations alone. It changes when people experience a better way of working firsthand. When teams see faster feedback, clearer prioritization and visible customer impact, agile stops being a vocabulary exercise and starts becoming a business habit.
Executives often ask how to create buy-in for new ways of working. One answer is to attach them to real delivery. Choose a business priority that matters, create a cross-functional team around it and let stakeholders see how product thinking, iterative development and measurable outcomes produce better decisions.
Replace HIPPO decisions with test-and-learn
Perhaps the most important shift in Pandora’s operating model was moving from opinion-led prioritization to evidence-led prioritization. Business leaders were not always good at predicting which features would succeed. That was not a failure. It was a reality check. In a fast-moving market, certainty is overrated. Learning speed matters more.
By building a regular test-and-learn system, Pandora created a multiplier for long-term performance. Ideas could be evaluated based on data rather than hierarchy. Tests could be designed for statistical validity. Winning concepts could be fed into the main platform. And the organization could avoid defaulting to the highest-paid person’s opinion.
This is where sustainable transformation becomes visible. Prioritization changes. Governance changes. The role of leadership changes. Leaders are still responsible for direction, ambition and investment. But they no longer need to be the source of every answer. Their job becomes creating the conditions for better answers to emerge from the system.
Organize around growth, products and measurable outcomes
Pandora’s leadership also made a deliberate choice to bias decisions toward top-line growth. That became a first filter for prioritization. Growth initiatives came first, followed by improvements to the machine underneath. That sequencing matters. It anchors transformation in value, not activity.
Combined with a stronger product mindset, this creates a more resilient model for change. Product thinking shifts the conversation from one-time projects to continuous evolution. Teams are not asked simply to deliver a release. They are asked to improve a capability over time, understand the stakeholder need behind it and measure outcomes that matter.
For transformation sponsors, this is the bigger takeaway. If digital is now part of how the business grows, serves customers and operates at scale, then the organization itself must be designed differently. It needs integrated teams, credible engineering leadership, shared data foundations, stakeholder alignment and a governance model built on experimentation and measurable value.
From program to capability
Digital transformation becomes sustainable when it stops being owned as a temporary initiative and starts being run as a core capability. That is the deeper lesson. New experiences matter. Modern platforms matter. But lasting advantage comes from the operating model that supports them.
For CEOs, COOs and transformation sponsors, the question is not simply how to launch the next feature or channel. It is how to build an organization that can keep learning, keep improving and keep translating digital ambition into business performance. That requires structural choices, leadership choices and cultural choices.
When those choices are made well, digital no longer sits at the edge of the enterprise. It becomes part of how the enterprise works.