The business initially asked for a mobile notification to address missed advisor appointments.  My investigation revealed a larger problem: advised customers lacked reliable mobile access to the information and actions needed to maintain their advisor relationships.

The work began around March 2022 with an initial request to add a mobile toast message intended to address missed advisor appointments.

The work continued through October 2023. Phase 1 launched in December 2022, Phase 2 launched in May 2023, and Phase 3 began as I transitioned out of the work.

The engagement crossed multiple advice-service verticals, each operating through its own product team, roadmap, and delivery dependencies.

The hidden assumption was that mature retirement and advised customers were primarily desktop or tablet-web users.

Mobile was often treated as a secondary channel for these customers, especially when the task involved retirement accounts, advisor relationships, or premium advisory services. That assumption shaped what was prioritized, what was delayed, and what mobile was expected to support.

Surface problem: How do we improve appointment scheduling?

Reframed problem: How do we support advisor relationships wherever customers choose to engage?

That distinction mattered.

If the team treated the work as scheduling, the solution would focus on reminders, appointment details, and rescheduling paths. Those capabilities were necessary, but they were not enough to explain the business and customer stakes.

The deeper issue was access and relationship friction. Customers could not effectively maintain aspects of their advisor relationship through a mobile channel they regularly used. When appointment visibility, rescheduling, preparation, and advisor context depended too heavily on desktop or disconnected channels, the relationship became harder to sustain.

That reframing moved the work from feature delivery to product strategy.

I created an Access → Engage → Complete framework to guide prioritization and alignment conversations.

Access: Can customers see and reach advisor services through the channels they regularly use? Access meant recognizing that mobile was not a convenience layer for these customers. It was an important access point that customers expected to meet meaningful financial and advisor service needs.

Engage: Can customers interact with the platform in a meaningful way once they have access to it? Engagement meant giving customers the ability to navigate, expand, message, reschedule, or take action once they reached the information they needed. If a customer knew they could not make an appointment, the product needed to make rescheduling easier than silence.

Complete: Can customers finish the task they came to complete and receive confirmation that it was done? Completion mattered because customers did not come to the app only to view information. They came to satisfy a need. That might mean completing a transaction, rescheduling an appointment, sending a message, or getting confirmation that an action was finished.

All three layers needed to feel easy, low-friction, and fast. If the experience became too complicated or took too long, customers were more likely to abandon the task or return to another channel. The framework helped move the work away from a narrow feature conversation and toward a relationship-support strategy.

The strategy work required coordination across multiple advice-service verticals, each with its own team, roadmap, priorities, and delivery dependencies.

That structure created a systems challenge. Each team could make reasonable decisions within its own lane, yet still create a fragmented customer experience.

My responsibility was not execution inside one team. My responsibility was to help multiple teams move in the same direction while avoiding roadmap conflicts, platform misalignment, and a fragmented customer experience. That meant identifying dependencies, surfacing where one team's roadmap could create constraints for another, and helping product managers understand that alignment work was not a design preference.

It was risk-management work tied to customer outcomes, platform readiness, delivery sequencing, and business metrics.

The customer did not experience the organization as separate verticals. They experienced one mobile product. If Personal Advice, Digital Advice, Wealth Management, Ultra-High-Net-Worth Experiences, and related service areas moved independently, the product could reinforce the very fragmentation the work was supposed to solve.

An example of exploration of options to provide precence of appointmets on native mobile

The ideal future state was a native mobile appointment-management experience.

But the organization was working within real platform constraints. API limitations, technical dependencies, resource realities, and companion-product roadmaps affected what could be delivered and when.

The strategic tradeoff was not simply between a perfect native experience and a compromised experience. The real decision was whether to delay customer value until the platform caught up, or deliver a phased solution that could reduce friction sooner while preserving the longer-term native direction.