top of page
Image by freddie marriage


AT&T, 2011


Video Conferencing Enterprise Solution




UX research project.

The goal is to provide an enterprise online conferencing segment users with the best Video and Screen-sharing experience under unknown network conditions. User disconnections from events as a result of low bandwidth should be handled. 

My role is UX Researcher role.

To comply with my non-disclosure agreement, I have omitted and obfuscated confidential information in this case study. All information in this case study is my own and does not necessarily reflect the views of AT&T.

Research Strategy

First of all, the main players were determined:

  1. Video -  supported in three sizes QCIF, CIF, and VGA.

  2. Screen sharing - of two kinds: synthetic data as  PowerPoint presentations or Word documents or nature pictures as nature photos. The different kinds of data influence compressed file size.   

  3. Periodicity - could be every 30 sec like. 

  4. Intensity - when the presenter turns the pages could be or full-screen data updated or part screen update.

  5. File transfer during screen sharing and/or video

Research Goal

The goal is to phrase the criteria of the decision-making in order to improve the user experience.


The criteria should be phrased based on the technical spec of the system:


  1. Ability to send video in different resolutions;

  2. Ability to share the screen in different detail levels;

  3. Ability to define prioritization of the different content transfers;


and the most common scenarios of data distribution during events

Players qualities

File transfer
Short term

Long term

Long term



Roy is a technical writer. He uses our platform for Video conferencing several times a week.

He works from his home and his bandwidth is not so perfect and his user experience is negatively affected.


Rina is a manager in a high-tech company. She uses our platform for Video conferencing several times a day.

She works from her office so usually, her bandwidth is very good but sometimes she needs to download large files and it creates a bandwidth usage peak.


For the most common transferred data types (like PowerPoint presentation, Word document, nature pictures, CAD document, Desktop, etc)  weight should be measured  in a compressed state for the full or partial page update;

Different data transfer combinations to be tested: video with screen sharing, video with file transfer, screen sharing with video, and file transfer...

Peak detection should be separately analyzed with permanently low bandwidth

Visual changes should be smooth enough to keep it unnoticeable as much as possible.

Screen Sharing Scenarios

Video Scenarios

How I create criteria






saving network behavior

network behavior analytics

Hypothesis: hold video

Goal: freeze prevention

Freeze prevention

  1. Remove video packets up to the next keyframe a few times before freeze  

  2. Hold the video for a few seconds on the server’s queue before freezing.

In the first case, we see a few short-time videos stuck before the video freezes or releases, in the second one we see one longer video stuck. We should choose one of these options.

Freeze forcibly

  1. The server keeps information regarding the percentage of video, sharing, and file transfer.

  2. This information will be used to decide freeze stream or hold video. 


  1. Send dummy packets from the server for user’s bandwidth detection

  2. Analyze user’s history on the client and update server

  3. We can recover frozen video forcibly at the sharing stop. 



  • Resolved Peak

  • Unresolved Peak

  • The unresolved peak for X times during Y time

  • The unresolved peak for X times  during Y time with new input

  • The unresolved peak for X times  during Y time with PA input


Decision-making criteria phrased for:​

  • Streaming (20%-80%) and video (60-250 Kbps per video) quality downgrade criteria.​

  • Failure cases with not balanced decision-making conditions is handled.

  • This case may put the system into the "hysterics" condition when the freeze and recovery are happening frequently. 

  • Several downgrade steps before feature freeze or close. ​

  • All scenarios are tested well during laboratory tests with Shunra. ​

  • Recovery cases criteria.

  • User experience is perfect and user disconnections from events are prevented. 

bottom of page