Shifting Mobile Advice Strategy from Scheduling to Relationship Support

Project Timeline & Scope

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 was beginning 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.

Why the Mobile Access Gap Mattered

Advisor appointments were not simple calendar events. They were service moments where customers received guidance, asked questions, made financial decisions, and maintained an ongoing relationship with their advisor.

When an appointment was missed, the impact extended beyond individual inconvenience. Advisor capacity was lost, follow-up work increased, and both the customer's progress and continuity of the advisor relationship were put at risk.

The missing mobile functionality was therefore not only a calendar gap. It created a service-access gap. When customers could not see or manage an appointment through a mobile channel they regularly used, the product made it harder for them to follow through and harder for the business to preserve valuable advisor time.

The Initial Request: Add Appointment Functionality

The initial request was to add a mobile toast message intended to address missed advisor appointments. At first, the organizational conversation focused on appointment functionality.

The mobile application did not give advised customers a way to see that an advisor appointment was coming up. There was no mobile appointment visibility, no clear in-app reminder path, and no mobile way to reschedule. If a customer needed to manage the appointment, they had to move to the desktop web experience or rely on another channel.

The business was seeing missed appointments, and the assumed opportunity was to add appointment-related capabilities into the mobile experience.

That was a valid need, but it was not the full strategic problem.

The Assumption Behind the Request

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

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

What the Evidence Revealed

Customer signals challenged that assumption.

I audited the existing mobile experience, reviewed public app feedback, examined retained customer conversations, and looked for recurring moments when advised customers were forced into desktop or another channel. Customers expressed frustration that important account and service tasks required them to leave mobile. Some compared the mobile experience unfavorably with desktop or web, while others encountered missing functionality or instructions that redirected them elsewhere.

The pattern was not that mature customers avoided mobile. The pattern was that customers expected mobile to support real financial needs, and they were frustrated when the experience did not.

The strategic issue was not only that the organization lacked appointment functionality. It was that mobile access for advised customers was limited by an outdated view of who those customers were and how they engaged with the brand.

---

Reframing the Problem

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.

---

Strategic Framework: Access → Engage → Complete

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 support meaningful financial and advisor-service needs.

Engage: Can customers interact with the platform in a meaningful way once they have access? Engagement meant giving customers the ability to navigate, expand, message, reschedule, or take action once they reached their information. 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.

1. Access

See and reach information on the platform of choice.

→

2. Engage

Navigate, expand, message, reschedule, or take action.

→

3. Complete Action

Finish the task and receive confirmation.

Aligning the Advice Ecosystem

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 while still creating a fragmented customer experience.

My responsibility was not execution inside one team. My responsibility was helping multiple teams move in the same direction while avoiding roadmap conflicts, platform misalignment, and 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.

---

Turning Constraints Into a Phased Strategy

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.

Customer feedback helped set the order. Seeing an upcoming appointment on mobile mattered, but what advised customers most wanted was the ability to change or schedule an appointment at their own convenience. That level of access was not available to this segment on mobile, and it was the need most closely tied to keeping advisor time from going unused.

To sequence the work, I applied a framework I had developed on earlier projects, which I call the hierarchy of data: presenting information in stages that match what people actually need, rather than everything at once. Working from that structure and the themes in the research, I broke the solution into increments that could be tested with customers and verified at each stage before the next one was built.

The team moved toward a phased strategy.

That approach allowed customers to gain meaningful access sooner while giving the organization a path toward deeper native integration over time. Rather than treating technical constraints as dead ends, the phased strategy turned them into inputs for sequencing, prioritization, and roadmap alignment.

The Phase 2 bridge is a good example. Building scheduling natively wasn't possible right away because of roadmap timing and resources. Sending customers out to a browser would have dropped them onto the website and broken the experience. Instead, we embedded only the scheduling section of the web experience inside the app and styled it to match mobile, so customers stayed in the app the whole time. It was the fastest way to bring the feature to market and test its value with customers before committing to a native build.

Retained planning artifacts also show that appointment-related work was being discussed alongside advisor information, account help, appointment cards, appointment messages, and analytics intended to track no-show reduction and satisfaction signals. That matters because the work was not isolated interface cleanup. It sat inside a broader service-access strategy.

This was product strategy work, not simply interface delivery. The direction had to balance customer need, business impact, platform readiness, delivery dependencies, and organizational capacity.