Making a complex subscription ecosystem feel simple

One customer journey. Multiple systems behind it.

Customers do not think in terms of platforms, systems, business units, or technical ownership. They do not know which system holds the subscription record or where one technology hands off to the next. They simply expect the brand experience to work.

The subscription service introduced a genuinely useful model for replenishing printer consumables — ink and toner arriving without anyone having to remember to reorder. Delivering that convenience, though, asked customers to move across several touchpoints and the systems beneath them: brand and product content in Brother's primary web ecosystem, enrollment and subscription management in a separate subscription platform, and an account and authentication layer connecting the two.

Each piece was reasonable on its own. Together they created seams — moments where the journey handed a customer from one system to another and quietly hoped they would not notice. The opportunity was to reduce those seams and create a journey that felt intentional from discovery and education through authentication, enrollment, account access, subscription management, and ongoing replenishment.

That made this two problems at once. It was a customer experience challenge, and it was an organizational integration challenge — because the seams in the experience traced the boundaries in the organization, and closing one meant closing the other.

Connecting the experience across disciplines.

My role was digital experience leadership and cross-functional orchestration. I helped connect the customer journey across UX, business requirements, content and copy, technology, authentication, and the subscription platform experience — holding the end-to-end path in view while individual teams worked on their part of it.

Practically, that meant translating business and technical requirements into a coherent experience, identifying where customers would encounter friction before they encountered it, establishing what the intended journey actually was, and keeping teams aligned around the experience we were collectively trying to create rather than the deliverables we each owned.

The experience crossed organizational and technical boundaries.

No single team owned the entire journey. Each group owned a real and legitimate piece of it, and the customer experienced the sum of all of them.

• UX/UI
• IT and engineering
• Business stakeholders
• Product and program leadership
• Copy and content
• Authentication and account experience
• Subscription platform
• Broader web ecosystem
• Subscription and consumables business logic

A decision in one area could immediately affect another. Authentication affected account access. Business rules affected what the UX could promise. Platform constraints affected what could be designed at all. And copy had to explain a service whose mechanics crossed systems, in language that never asked the customer to care about that fact.

The real challenge was making those dependencies visible early enough to act on, and getting teams to solve for the whole experience instead of optimizing only their individual piece. Every local optimum was defensible. The customer only ever met the total.

Designing the journey, not just the individual touchpoints.

The work moved from a set of separate requirements toward one designed journey. That shift was mostly a matter of changing what we looked at together: not the next screen or the next ticket, but the path a customer takes from first hearing about the service to receiving their fourth shipment without thinking about it.

• Mapping the experience across digital touchpoints
• Connecting business requirements to UX decisions
• Identifying friction between platforms and account experiences
• Helping integrate identity & SSO into the intended customer journey
• Coordinating content and copy with UX and technical implementation
• Bringing teams together around shared experience decisions
• Treating authentication as part of the experience rather than a technical requirement
• Connecting the subscription platform experience with the broader web ecosystem
• Creating clarity around dependencies, ownership, handoffs, and customer impact

Authentication is the clearest example. Signing in is where a connected experience either proves itself or falls apart, so enterprise SSO was treated as an experience decision with a technical implementation — not a technical decision with experience consequences discovered later.

“The customer shouldn't have to understand our organizational or technical architecture to use the service.”

Translating between business, experience & technology.

Most of the leadership work was translation. Business teams understood the subscription proposition and the operational requirements behind it. IT understood the constraints, the integrations, and what the platforms could reasonably carry. UX understood customer behavior and where friction accumulates. Content had to make the whole thing understandable in a sentence or two.

Each of those perspectives was correct within its own frame. My role was helping them converge into one experience: facilitating alignment across groups that rarely shared a room, surfacing dependencies early enough that they were choices rather than surprises, challenging decisions that created unnecessary customer friction, and keeping conversations anchored in the complete journey rather than any one team's deliverable.

A more connected subscription experience.

The subscription and replenishment journey became more connected. Enterprise SSO was incorporated into the account and authentication experience, reducing friction at the point where customers had previously been most likely to stall, and the touchpoints between subscription and account management were brought closer together.

The subscription platform and the broader digital ecosystem came into better alignment, which made the consumables subscription clearer to customers and less costly to change. The durable outcome, though, was organizational: stronger coordination across business, UX, content, and technology, and a shared habit of evaluating decisions against the whole journey.

Turning complexity behind the scenes into simplicity for the customer.

A customer journey rarely respects an org chart or a system architecture. This work demonstrates the ability to connect business strategy, UX, content, authentication, technology, and operations around one experience — translating between disciplines and ensuring the complexity behind the scenes does not become complexity for the customer.

• Digital Experience Strategy
• Cross-Functional Leadership
• Customer Journey Optimization
• Subscription Experience
• UX Leadership
• Platform Integration
• Identity & Authentication Experience
• Product & Program Leadership
• Web Operations