Unifying 100M customers into one app they actually wanted to open

Verizon had two apps. One for Wireless. One for Fios. Both served the same household, often the same person, and neither knew the other existed. Only 27 percent of multi-service households understood they could manage Fios in the Wireless app. The app rating was 2.8 stars. Bill payment took 4.2 minutes, twice the industry standard. Thirty-four percent of negative reviews cited the same problem: promotional banners and upsells were burying the three tasks that accounted for 86 percent of sessions. Check bill. Make payment. View data. The app was built around what the business wanted to say. The job was to rebuild it around what the customer came to do.

I ran 32 user interviews and analyzed 2,400 app reviews before opening a design tool. The diagnosis came fast.

The app had an identity problem, not a usability problem. Two divisions had built two experiences with two navigation models, two billing flows, and two visual languages. A customer with both Wireless and Fios was managing two mental models for one account. The fragmentation was organizational, not technical. The app was a mirror of the org chart.

86 percent of sessions were three tasks. Check bill. Make payment. View data usage. Everything else, the promotions, the upsells, the feature marketing, was furniture blocking the door. The app was optimized for the 14 percent of use cases the business cared about, not the 86 percent the customer came for.

Promotions were not just noise, they were actively destructive. One research participant said it plainly: "I just need to pay my bill before it is late. Where do I do that?" That question, from someone who had already downloaded and opened the app, was the indictment. The app had succeeded at acquisition and failed at the one job that mattered after acquisition.

I set four design principles publicly, before the team drew anything, and held the work accountable to them throughout.

Tasks first, promotions second. The home screen would surface the customer's top tasks, not the business's top campaigns. Promotions would earn space through relevance, not through org-chart authority. This was the fight. Marketing owned significant real estate in the existing app. The argument I made was that the 2.8-star rating was the cost of that ownership.

One account, one experience. A customer with both Wireless and Fios would see one login, one home screen, one billing interface. The two-app mental model would collapse into a single personalized view. This required cross-divisional alignment that did not exist when the project started.

Progressive disclosure over feature density. Surface the 20 percent of functionality that serves 80 percent of needs. Everything else is one tap away, not zero taps away. The instinct in enterprise apps is to show everything. The data said showing everything was why bill payment took 4.2 minutes.

Clarity over cleverness. Plain language. Transparent billing. No dark patterns around plan changes or add-ons. The previous app had been optimized to create confusion that drove support calls. We would measure success by whether support calls went down.

The redesigned app shipped across iOS and Android over a six-month build with a phased rollout. The work was not a reskin. It was a structural rearchitecture of how the app understood the customer.

The home screen became task-aware. It surfaced the customer's most likely next action based on their account state: upcoming bill, recent data usage, pending order. The promotional layer moved from the home screen to a dedicated discovery surface where it could be relevant without blocking the primary workflow.

The billing experience was rebuilt from scratch. A single interface managed both Fios and Wireless billing, surfaced upcoming charges with plain-language breakdowns, and reduced the payment flow to the minimum viable steps. The previous flow had been designed to show the customer more information at every step. The new flow was designed to show them less, better.

The unified account view consolidated Mobile, 5G Home, and Fios into a single personalized dashboard. Plan changes, device management, and service updates all lived in one place regardless of which division owned the underlying product. The customer did not need to know which division they were interacting with. That was our problem, not theirs.

We ran a 2-day design sprint early in the process, tested 6 concept directions with 12 users, and went through 4 rounds of iteration before the phased rollout. During rollout, we A/B tested aggressively. One finding reshaped the final product: less intrusive promotions did not reduce conversion. They improved it by 23 percent. The data validated the design principle the business had been most skeptical of.

The app went from 2.8 to 4.6 stars within 90 days of launch. Bill payment dropped from 4.2 minutes to 1.8 minutes, a 52 percent reduction. Billing-related support calls fell 31 percent. Monthly active users grew from 8.1 million to 10.4 million. Multi-service adoption, the metric that mattered most to the business, increased 47 percent. Net Promoter Score improved 18 points.

The number that mattered most to me was the promotions finding. The business had protected promotional real estate in the app for years on the assumption that visibility drove conversion. The data showed the opposite. When promotions moved out of the way and into a context where they were relevant, conversion went up. The instinct that marketing reach equals marketing effectiveness did not survive contact with what the customer actually wanted.

The thing I would do differently is fight harder for the unified experience earlier. The two-app problem was obvious from the first week of research, but I spent the first two months building consensus across divisions instead of shipping a prototype that demonstrated the unified model. In retrospect, the prototype would have done the consensus-building for me. The lesson: in large organizations, a working demo that shows the customer's experience is a more persuasive argument than a deck that describes it. I have started every cross-org alignment conversation with a prototype since.