Tracfone FWA Experience

FWA hero screens

Role: Senior Product Designer

Team: 1 Lead Product Designer, 1 Senior Product Designer

Users impacted: 80,000

  • Overview

    The Tracfone Fixed Wireless Access (FWA) experience provides new users with a seamless way to set up, register their device, and activate service at home without requiring support. This solution leverages the existing eCommerce flow.

    Challenge
    The FWA launch required an MVP purchase journey that would require several new screens and flows, while having a smaller than usual development resource.

    Solution
    Designed a lightweight, streamlined flow that clarified plan selection and accelerated launch readiness across engineering, product, and sales teams.

    ConstraintsThe FWA project had to be delivered with a smaller than usual development team, requiring careful prioritization and efficient design solutions. The release timeline was tight, necessitating rapid iteration and close collaboration across all stakeholders.
  • Map the Flow

    Map the entire flow upfront with product and engineering to clarify dependencies, edge cases, and ownership before designing.

      Design Decisions Design Strategy

    • Identify stakeholders
    • Ensure I'm added to all relevant communication channels
    • Ensure I'm added to scrum ceremonies
    • Set up regular check-ins with the team
    FWA service blueprint and journey mapping

  • Reusable Principles

    To speed up design and development, I focused on creating reusable patterns across the entire flow to maintain consistency, reduce design time, and accelerate development. This was especially important as we had to cut scope with a smaller engineering team.



    FWA design patterns Using bootstrap Grid we were able to define the responsive behavior of the cards and text, which allowed us to reuse this pattern across the entire flow and maintain responsiveness without needing to design multiple breakpoints.

      Design DecisionsDesign Strategy

    • Move directly into medium‑fidelity
    • Prototype faster
    • Reduce engineering complexity
    • Reusable text field states
    • No new components
    • Maintain responsiveness from day one
  • Happy path prototype

    Creating a prototype that showed scrolling and interactions would help get alignment from development partners who were joining the team at different points. It also helped reassure design leadership that we had a clear plan for the core flow and would be able to execute on it without major issues. This was especially important as we had to cut scope with a smaller engineering team and needed to make sure we were all aligned on what we were building.

    FWA happy path
    Validate the “Happy Path” early a focused prototype helped us validate the core flow quickly. It surfaced issues early, reduced rework, and aligned stakeholders on what “good” looked like.

      Gain alignment

    • Keep prototype updated
    • Make it visible to all stakeholders and easy to decipher
    • Show scrolling behavior
    • Show reusable text field states
  • Cross-team collaboration

    Collaborated with the development team to prioritize features and make design changes that reduced development work. With resources at 1/3 of original capacity, I worked closely with engineering to understand constraints, adjusted designs for feasibility, and streamlined the approval workflow with content strategists to maintain Tracfone's voice while delivering high-impact features efficiently.

    FWA happy path

      Design DecisionsDesign Strategy

    • Prioritize features and screens based on engineering capacity
    • Design within technical constraints to ensure feasibility
    • Maintain open communication with engineering to quickly address issues and adjust designs as needed
  • Continuing Dev Support

    As development progressed, I continued to support the team by providing detailed Figma designs and interactive prototypes. This ensured that the development team had clear and accurate references for implementation and trusted the designs. Prototypes also helped show developers how something should function and interact, saving time and reducing meetings.

    Supporting new screens

      Design DecisionsSupporting Dev

    • Keep Figma organized and up to date for easy developer reference without waiting for updates.
    • Use prototypes to demonstrate function and interaction, saving time and reducing meetings.
    • Maintain open communication with the development team to quickly address issues and adjust designs as needed.
    • Rapidly create additional screens as stories are groomed during online launch.
    • Organized Figma file allows leadership to track progress without requiring daily updates.
  • Textfield States

    There was already a robust design system component library, the issue was that the devs didn't use it and had got used to just creating new ones. I focused on using the ONLY textfield selector and leveraging the different states to support many more use cases.

      Design DecisionsStandardization & Efficiency

    • Aligning the development team on the proper use of text field states.
    • Speed up development by reusing existing text field states.
    FWA service blueprint and journey mapping
  • After the in-store launch, the FWA purchase experience was extended to online channels, requiring entirely new pages.

    FWA mobile-first interface examples

      Design DecisionsDesign Direction

    • Navigation to the FWA flow was added to the global navigation and marketing pages. During the launch, a partnership with AARP and other organizations helped promote the new feature. We needed to move fast and get prototypes approved by marketing partners.
    • Plan: this required a new pattern to add to the existing checkout process. We had an opportunity to create a new pattern for the cards while adding a marketing element.
    • Device: this required an entirely new page, would need to be a flexible, easy-to-update design.

    Originally, this content was a part of an ad campaign but as priorities shift it became clear we would need to create these assets.

    FWA mobile-first interface examples
  • Branding Updates

    During the FWA launch, the Tracfone brand was updated. I worked closely with the design leadership and content teams to ensure that our FWA experience reflected the new brand guidelines without causing delays to our launch timeline.

    FWA mobile-first interface examples
  • Results

    The FWA launch was a success. We shipped with a streamlined purchase experience that users loved, thanks to our solid design system and reusable patterns that accelerated both design and development. The mobile-first approach was key to reaching our audience, and keeping the purchase flow simple and clear drove better conversions. Close collaboration with stakeholders and the engineering team prevented scope creep and kept us on time. The result was a seamless launch across 62 stores, driving 80k device sales, +8% conversion, and 22% faster transactions than similar flows.