-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
0dcd2bb
commit 0688602
Showing
2 changed files
with
33 additions
and
0 deletions.
There are no files selected for viewing
33 changes: 33 additions & 0 deletions
33
content/posts/2024-world-of-warcraft-remote-teams-leadership/index.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
--- | ||
title: "What World of Warcraft taught me about remote team leadership" | ||
date: 2024-04-26T14:11:49+02:00 | ||
categories: ["Management"] | ||
draft: true | ||
--- | ||
|
||
I often state (half-jokingly) that I have over 20 years of experience leading remote teams. I've been at it since I was 16, playing World of Warcraft. | ||
|
||
Without this spoiler, you would probably have been impressed. | ||
|
||
But even with this spoiler, remember that this is a serious affair. For the players, being the first of a realm to kill a boss meant something. | ||
|
||
I was in the leadership of the guild and had led numerous raids. I played it quite successfully back then, and it was not less competitive than establishing a digital product in a market. | ||
|
||
We had to coordinate 40 people, not just during the scheduled raid times, which occurred several times a week. In between them, everyone needed to do their homework, prepare the in-game character with necessary potions, or be informed about strategies. | ||
|
||
Here are the lessons learned: | ||
|
||
- **Interpersonal Relationships Matter**: A team needs to function as a unit. You have to like each other. | ||
- **Not Everybody is Made for Remote Work**: Good communication skills are essential. | ||
- **Team Is Crucial:** Rely on the Reliable and boot the troublemakers. You need good taste in people and to coach those with potential (who have skill + reliability). | ||
- **Tools Are Crucial**: Back in WoW, we had add-ons to aid us through our battles. Now, it is essential to master the "remote stack" (Slack, Miro, Confluence, Google Docs, etc.). | ||
- **Objectives Are Essential**: Strategy is critical. The world is vast, and the context is ever-changing (basically, with every patch level). Often, there were multiple options to bring a raid group to the next level. | ||
- **Work-life balance**: You might think this wasn't an issue back then, but it was. People had families, friends, and hobbies. Their raid group needs to match their personal life as well. In remote teams, choosing an employer that fits the individual lifestyle is even more crucial. | ||
|
||
This playful yet pointed approach to remote team management might make you smirk. Still, don't underestimate the lessons learned from leading virtual legions through pixelated peril—it's serious business. | ||
|
||
If I could choose who would join one of my product teams nowadays, I would always choose the multiplayer veteran. | ||
|
||
![](raid.jpg) | ||
|
||
**Fun Fact:** This experience runs so deep that I must bring it up every decade. In 2014, I also wrote a reflective article on this [on my private Blog](https://klaus-breyer.de/in-eigener-sache/generation-schlachtzug-was-vom-raiden-im-kinderzimmer-blieb/942) (in German). |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.