UX Flow

STORYBOARDING FUNCTIONALITY OF
A WEB PHONE

Key scenarios and notes for engineering

How we work is often shaped by where we work. The culture and the players involved…the dates and deadlines we’re working towards. For the Web Phone, I worked as I did at previous companies earlier in my career. I merged user flow and wireframing efforts with design. I refrained from focusing on cosmetics and remained loyal to completing high-fidelity wireframes, along with the specs necessary for Engineering to begin their efforts. The final designs would come as a fast followup.

Opposite Waterfall, this is an agile style of working. Low-to-mid fidelity designs focusing on scenarios we need to build for. Transferring and Conferencing were of critical importance as they were the most complex of UX scenarios, and the features most requested by users and labeled required for any viable release.

Related Work

DESIGN SYSTEM

Regardless of how unique or radical any new feature might be, this component library is vast and rubbery enough to scale up, while clear designations, specs and guidelines insure consistency remains intact.

Related Work

TALK, TEXT, MEET AND FAX FOR SMALL BUSINESS

Conversational AI solutions were customized and integrated into these Phone.com customer landing pages, offering call handling features such as Virtual Reception, Voice-to-Text Call Recordings with generated Call Summaries and Action Items, and Automated Voicemail Transcriptions.

Related Work

PUSHING ACCESSORIES TO INCREASE REVENUE

There was a huge opportunity lost on Phone.com sales of device accessories. These products had been treated without real consideration, and discoverable only by a manual search by the user. The solution was bringing in a more disruptive UX approach.