Reworking the Meeting User Interface of Blizz

The so (from me) called “User Focused Decision Process”: Focus on and address user needs in strategy, ideation and communication. Everything is based on research, findings and identified pain points which are then validated and prioritized followed by an ideation phase. Marketing can start creating campaigns based on the most important job stories and communicate stories correlating to the identified pain points. Thus they can create a coherent storytelling. In the end, the main goal is to do the right things! :-)
Multiscreen-ready! Blizz works on any desktop and mobile device and has a coherent user interface, which is similar but not identical on the various platforms (Windows, macOS, iOS, Android, and web browser).

We listen and consider the specific jobs of our users

We continuously test and consider what users tell us. For example, some had problems using the correct audio input and output channel (“Can you hear me?”). So, we developed and implemented a feature that triggers a device selection dialog when a new device is added (or removed), making it almost impossible for a user to select and/or use a wrong output channel.

The Blizz Device Detection Dialog supports users in using the right hardware (for example when they plug-in a new headset).
Sketches and variants that we discussed in the team, with users and stakeholders during the development of the device detection dialog. We have done many iterations. Developers started implementing based on high-fidelity mock-ups.

The process

Initially when I joined TeamViewer and Blizz, there was already an existing online meeting platform that worked quite well. It was based on the TeamViewer main product. The goal for the Blizz project was to rework this platform completely and meet the needs of our (existing and potential new) users as best as possible.

An early sketch of the new Blizz Meeting User Interface (presenter view)
No concept without pen and paper :-) Various sketches as a basis for discussions, mock-ups or prototypes, showing the general layout, the content arrangement, detailed and specific views for desktops and mobile devices.
Status quo after the public release. Me and my colleagues testing and using Blizz. More images here:

We want to make it easy for new users

We test, collect feedback, and listen to our users. We are continuously improving. We (normally) release monthly (Windows, Mac, iOS and Android have their own release cycles) so we can react to user feedback in short iterations. We have a lot of ideas (too many!) and plenty of potential features in the backlog (also many :-). The challenge is to choose and prioritize the most relevant ones. That’s when we apply our user-focused job-oriented mindset, which helps us a lot. And, when we have to make quick decisions and prioritize a large amount of topics without getting lost in details, we us the MoSCoW Voting method, for example. If you are interested in the process, just comment below. I’ve already prepared an article on that.

Starting a meeting should be easy. Users want to be able to make direct phone calls with Blizz so they call and invite participants on their smartphones. And, you can even mix VoIP and normal phone calls — which is a relevant and highly desired need of a lot of online meeting users.



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Wolfram Nagel

Wolfram Nagel


UX Designer (@TeamViewer), UI Architect, JTBD Practitioner, Author of “Multiscreen UX Design”, Initiator of the “Design Methods Finder”. I love my 👪 and ⚽️🚵📸