Organisational Alignment During Restructuring
When PayPal UK prepared to become an independent company after separating from eBay, the challenge was not just rebranding. It was understanding how the organisation actually worked as a whole - and building the coherence needed to operate as a standalone company. What began as a review of customer touchpoints became a full organisational diagnostic, revealing how departments connected (or didn't) and where the real operating model differed from the one on paper.
A global payments company preparing for independence with six departments pulling in different directions
In 2014, PayPal was preparing for one of the most significant corporate separations in recent history. After more than a decade as part of eBay, PayPal would become an independent, publicly traded company - a process formally completed in July 2015.
For PayPal UK, the separation meant more than a new ticker symbol. The organisation was actively working to establish its own identity - a new brand platform had been developed and the ambition was to have every part of the organisation reflect it. But there was a significant gap between how PayPal wanted to present itself to the world and how it actually operated day to day.
The ambition was clear. But the scale of customer operations made it a genuinely difficult thing to achieve. PayPal UK was sending around 2 billion customer interactions a year, produced by over 120 internal authors spread across six departments - Marketing, Operations, Customer Service, Credit, Collections, and Compliance - along with 58 external agencies. Across 19 different types of customer touchpoint, these had grown organically over years within eBay's broader structure, each department developing its own standards and practices independently.
The result was an organisation with a strong aspirational identity in its marketing but a very different experience in its day-to-day customer interactions. Functional departments - the ones handling the touchpoints customers actually received most often - had developed their own patterns over time, quite separate from the brand. As PayPal prepared for independence, the question was how to bring all of these together into something coherent.
Understanding what customer touchpoints reveal about organisational alignment
The goal was not to fix the content. It was to understand what the pattern of disconnection across customer touchpoints revealed about the operating model beneath.
Every interaction a customer received was the visible output of decisions, processes, ownership structures, and coordination - or the absence of all of these. Mapping those touchpoints systematically across every department would show where the organisation was aligned and where it was fragmented.
For a company preparing for independence, this mattered enormously. Organisational alignment is not just about efficiency - research from PwC found that highly aligned organisations were 1.76 times more likely to outperform their competitors. PayPal could not afford to enter independence with an operating model that pulled in six different directions.
The work needed to answer three questions. Who owns what - which departments and agencies are responsible for which customer touchpoints, and where does ownership overlap or fall through the gaps? How do customers actually experience the organisation - not through the lens of a single department, but across every interaction they receive? And what would a coherent operating model look like - one where every customer touchpoint reflects a single organisational identity?
Mapping organisational alignment across six departments and 58 agencies
Rather than working within a single department - the typical approach when something looks like a content or brand problem - the work cut across all six. This was a deliberate choice. If customer touchpoints are produced by six departments independently, you cannot understand the pattern by looking at any one of them in isolation. The whole picture only appears when you treat them as a connected system.
Mapping the real operating model
The first step was a comprehensive audit across all 19 types of customer interaction - from marketing to transactional to collections. For each, the work mapped who created it, who owned it, which agency (if any) was involved, what standards applied, and how it connected to other touchpoints in the customer journey.
This mapping revealed what the org chart could not. Departments were duplicating effort without realising it. Customer journeys crossed departmental boundaries with no coordination - a customer could receive a warm, personal marketing message one day and a cold, legalistic collections notice the next, with no awareness within the organisation that these were part of the same relationship.
The 58 external agencies added another layer of complexity. Each worked to their own brief from their own department, with no visibility of what other agencies were producing for the same customers. The customer experienced a single company. The operating model behind it was anything but single.

Building a shared framework
With the audit complete, the work shifted to designing a shared framework that could bring coherence across all six departments. The temptation with this kind of work is always to centralise - to create a single team that controls everything. But centralised control does not scale when you have 120+ authors across six departments and 58 agencies. The framework needed to be practical enough that people would use it because it genuinely helped, not because someone was checking.
The framework included a style guide built from the audit findings, showing what worked across departments and what did not. Redesigned templates for all 19 types of customer touchpoint, each adapted for its specific context while maintaining consistency. A content checklist that authors across every department could use as a practical tool. And training sessions delivered across teams to build internal capability rather than creating ongoing reliance on external support.

Embedding through internal adoption
The framework was designed to be owned internally. PayPal's own teams led the rollout through a structured internal initiative, taking it to every department through a series of roadshows. This was not a set of guidelines handed over and forgotten - it became part of how the organisation worked.
The internal adoption mattered as much as the framework itself. For organisational alignment to last beyond a project, it needs to be something people use because it helps them, not because they have been told to. By building capability across teams rather than centralising control, the work gave PayPal the tools to maintain alignment as the organisation continued to evolve after independence.
A clear picture of how the organisation actually operated
The work gave PayPal UK something it had not had before: a clear, honest picture of how the organisation actually operated - seen through the eyes of customers, not through the lens of any single department.
With that picture in place, the organisation could make deliberate choices about how it worked. The shared framework created standards across all 19 types of customer touchpoint, while the internal adoption programme meant teams had the capability to maintain that coherence themselves - without depending on external support.

Perhaps most importantly for an organisation about to become independent, the work connected departments that had previously operated in parallel. The audit had made the overlaps and gaps visible. The framework gave people a practical reason to coordinate. And the internal rollout created relationships across teams that had not previously had a reason to talk to each other.
Organisational alignment during restructuring is not a nice-to-have. It is the thing that determines whether a new entity works as a coherent whole or remains a collection of parts that happen to share a name.
Why organisational alignment during restructuring starts with what customers see
The most significant insight from this work was not about customer experience, although customer experience improved. It was that the pattern of customer touchpoints - who sends what, to whom, with what standards - is a diagnostic tool for understanding how an organisation actually operates.
Every gap between departments, every duplicated process, every inconsistency in how customers were treated was visible in the touchpoint data. The customer-facing interactions were a mirror reflecting the operating model behind them.
For any organisation going through restructuring - whether that is a demerger, a merger, or a significant reorganisation - this insight is powerful. You do not need to audit every internal process to understand where alignment breaks down. You can start with what customers see, and work backwards.
Ready to think differently about your organisation?
Whether you're diagnosing root causes, redesigning for the future, or building on what already works well - we'd love to hear about your organisation.