Skip to main content

How not to waste time during online meetings... especially in corona times...


Virtual Communication

In online meetings our cognition is massively limited in comparison to a meeting in person. Communication in this context is challenging. A big part of the context and non-verbal communication is just not possible in the virtual environment; especially when we rely on audio only.

Turning the camera on not only gives the team members more context, it also enforces more focus on the meeting by avoiding side-works.

Be aware that the position of the camera on top of your screen will lead to the strange effect hat people are not looking in each others eyes. At least while talking, think about looking directly in the camera to gain a better focus and understanding of your listeners.



Agenda, Timeline and Roles

Like in any good meeting make sure to send an agenda and time planning upfront and invite only people that need to contribute to the meeting.

You should consider splitting group size depending on main purpose of the meeting:

  • Big Group: Informing
  • Small Group: Discuss
  • 1:1: Decision Making

Make sure to send a summary of the meeting to all stakeholders - also those that were not invited in the meeting but need to be informed.

The initiator of the meeting should be also the moderator and should assign the members roles like the record keeper and expert role at the begin of the meeting. 


General tips

With the lack of context, irony and humor are hard to understand and should be avoided.

In general online meetings are more exhausting than real-life meetings; this is why you might want to try to
Reserving some time at the end of the meeting to request a short resumee of all meeting members will also increase the common understanding of the meeting.



Tools



Golem.de

Comments

Most Favorite Posts

Server-driven UI (SDUI): Meet Zalandos AppCraft and AirBnB Lona

A short WTF: Joe Birch:  SERVER DRIVEN UI, PART 1: THE CONCEPT Zalando seems to follow the SDUI principle as well - defining a common design language and construct the screens on the backend while displaying them natively on the clients. They even go one step further; they implemented a mighty toolset to enable non-technical stakeholders to define their own native app screens Compass: Web tooling to create screens and bind data Beetroot: Backend service that combines the screen layout definition with the data Lapis/Golem: iOS/Android UI render engines Crazy cool! Good job, guys (when you do an open-source release?) To even move faster a Flutter based UI render engine implementation was great! See also AirBnB Lona SDUI approach Building a Visual Language Why Dropbox sunsetted its universal C++ mobile project and AirBnB its React Native implementation

CloudApp

CloudApp allows you to share images, links, music, videos and files. Here is how it works: choose a file, drag it to the menubar and let us take care of the rest. We provide you with a short link automatically copied to your clipboard that you can use to share your upload with co-workers and friends. Additionally you can view, track and delete files right from your menubar. CloudApp

Google Drive versus Dropbox

MacWorld: Online Storage Face-Off: Google Drive vs. Dropbox

CFPropertyList

The PHP implementation of Apple's PropertyList plist can handle XML PropertyLists as well as binary PropertyLists. It offers functionality to easily convert data between worlds, e.g. recalculating timestamps from unix epoch to apple epoch and vice versa. A feature to automagically create (guess) the plist structure from a normal PHP data structure will help you dump your data to plist in no time. github

App Indexing

A better search experience for apps and users with linking to in-app content. Google is working with app developers and webmasters to index the content of apps and relate them to websites. When relevant, Google Search results on Android will include deep links to apps. App Indexing

In-App Purchase Receipt Validation on iOS

A vulnerability has been discovered in iOS 5.1 and earlier related to validating in-app purchase receipts by connecting to the App Store server directly from an iOS device. An attacker can alter the DNS table to redirect these requests to a server controlled by the attacker. Using a certificate authority controlled by the attacker and installed on the device by the user, the attacker can issue a SSL certificate that fraudulently identifies the attacker’s server as an App Store server. When this fraudulent server is asked to validate an invalid receipt, it responds as if the receipt were valid. iOS 6 will address this vulnerability. If your app follows the best practices described below then it is not affected by this attack. iOS Developer Library In-App-Klau jetzt auch im Mac App Store ( Heise )

How to link to TestFlight App in iOS

There are two things you need to do. First, check to see if TestFlight is installed. Then create a new link to your app. NSURL *customAppURL = [NSURL URLWithString:@"itms-beta://"]; if ([[UIApplication sharedApplication] canOpenURL:customAppURL]) {     // TestFlight is installed     // Special link that includes the app's Apple ID     customAppURL = [NSURL URLWithString:@"https://beta.itunes.apple.com/v1/app/978489855"];      [[UIApplication sharedApplication] openURL:customAppURL]; } This special https://beta.itunes.apple.com URL will be opened directly in TestFlight. Finally, if you are using iOS 9 (or later), you need to make an addition to your Info.plist to get the canOpenURL: method to work. If your app is linked on or after iOS 9.0, you must declare the URL schemes you want to pass to this method. Do this by using the LSApplicationQueriesSchemes array in your Xcode project’s Info.plist file. For each URL scheme you wan...