Proof of Concept - The Fog of War of company onboarding
The Fog of War of company onboardingIssue 204: How a Real-Time Strategy game concept teaches you new hire onboarding
When you start a new company, onboarding is a crucial phase to get right. The previous three times I’ve onboarded to a new company has been in a leadership role at a company already established. Onboarding is not simply following the artifact your new employer gives you. It’s a two-way street. The higher role you enter at a new company, the more important it is to onboard to the company well, because you only have one first impression with your new employer and colleagues. The Fog of WarI describe onboarding as navigating the Fog of War—a game concept. The "Fog of War" in Real-Time Strategy (RTS) games is a game mechanic that conceals portions of the game map from the player until their units explore those areas. This creates an element of uncertainty and strategic depth, as players must scout and gather information about enemy positions and terrain. The concept was first introduced in the game Herzog Zwei, released in 1989. Notable examples of RTS games that have incorporated this mechanic include the Warcraft series, Starcraft, Age of Empires, and my favorite of all-time, Command & Conquer. These games use the Fog of War to enhance the strategic complexity by requiring players to balance exploration, defense, and offense without having complete information about their opponents' actions. The Fog of War is my metaphor to onboarding to a new company. You start at an empty point and the onboarding document the company gives you is the game instruction manual. It’s a great resource, but doesn’t have to be the only one you use to play the game. The natural action might be to clear out the entire fog of war first to get a full landscape of the map. Because you have not uncovered the Fog of War does not mean things aren’t happening. You have to quickly bridge the gap between expanding what you know and anticipating what might happen. Capturing all the historical context is an impossible task It’s important to build context as you a new company. I advise you to do the traditional listening tours, intro 1:1s, and scout the Fog of War to gain as much insight from the people who lived them directly. However, one mistake I see people make is trying to capture the historical context of the company before taking action. One of the reasons you were brought in is the ability to act quickly with precision. You are unproven regardless of your experience Regardless of the experience you bring, you’ll remain unproven until you gain your new team’s trust. Whether it’s a new sailor on a fishing vessel, free agent joining a new football club, or a squad member in the military, current teams already have a way of working and previous working experience together. Being the new factor on the team means it’s key to find ways to provide value and execute with the team. My onboarding plan for every companyEven though most companies provide an onboarding doc when you join, you should come up with your own. It’s not because of lack of confidence that the company can do it, but based on your experience, there are likely things you know you want to learn. First, my onboarding starts at the first interview. Interviewing at companies is not only a way for them to interview you for the role, but for you to interview if they are a good fit. From the first call with the recruiter and hiring manager, I’m already asking questions about the challenges and opportunities coming in. My favorite question is, “What am I getting myself into?” It’s good for both sides to have honest conversations and it results in better satisfaction on both ends. If a company doesn’t disclose any problems, I’m skeptical of why they need me to join. Conduct desk research about the company. I will be explicit that I don’t like to reach out to people directly in respect of their time. You can learn quite a bit from online research about the company to map out where you might be impactful. A few examples of what you might research are:
Once you join the company, speed run the Fog of War. Get a good sense of what’s important to learn without having it consume your first several weeks. It’s important to onboard well, but equally as important to make an impact. I often tell my team that I start with a lot of assumptions, which are not decisions, but a method to move quickly. However, I’ll refine the assumptions based on the context I learn, including chatting with them. As a new team member, it’s important to share with them what you’re thinking about or what your point of view is, even if you don’t have a definitive determination yet. You can always update your assumptions based on new information. To understand the boundaries quickly, I navigate the most important parts of the Fog of War seeking:
There is likely a reason you were hired and it’s important to emphasize your external value immediately. We might feel cognizant of not wanting to step on toes and assimilate to the new company. However, you were hired to bring your external skill and perspective. Don’t forget that. Since it’s impossible to turn yourself into a tenured employee of the new company, you gain wins by bringing your external value to them immediately. This might be the institutional knowledge you have in an industry or craft. It could be your skill in building teams. Identify that and push hard in those areas. Successful onboarding is the company’s onboarding + yoursTo be abundantly clear, the onboarding your company provides is extremely valuable. Remember to think of it as the game instruction manual. Bring your own knowledge and experience to the table annd onboard yourself. For certain roles or company types, the ability to onboard fast and act is key. To recap, my onboarding method is:
You only onboard once (YOOO?). The next time you join a company, design your own onboarding to navigate the Fog of War. You're currently a free subscriber to Proof of Concept. For the full experience, upgrade your subscription. |
Older messages
Crafting a talk
Sunday, July 14, 2024
Issue 203: Developing an idea worth sharing ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
Reflections from Config
Sunday, July 7, 2024
Issue 202: Thoughts from the annual Figma conference ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
Spotlight: Kate Syuma
Sunday, June 30, 2024
Issue 201: A conversation on scaling at Miro, Growthmates, and advising ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
The 100 Series
Sunday, June 23, 2024
Issue 200: Looking back at Issues 101-199 ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
Web experiences during the age of LLMs
Sunday, June 16, 2024
Issue 199: What does the future of website building look like? ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
You Might Also Like
Behind the Design of Jennifer Garner’s Home
Thursday, September 5, 2024
View in your browser | Update your preferences ADPro Garnering Praise This week, it's all eyes on Jennifer Garner, whose uber-chic urban farmhouse was just revealed as AD's October cover story.
Accessibility Weekly #412: Combating Access Trauma
Wednesday, September 4, 2024
September 3, 2024 • Issue #412 View this issue online or browse the full issue archive. Featured: Combating access trauma "The first thing I heard was, 75655356878796656432190.JPG. I immediately
Mayer Rus’s Favorite Fireplace in LA
Tuesday, September 3, 2024
View in your browser | Update your preferences ADPro Post Labor Day, it always feels a little like we in the design world are heading back to school, with reunions happening at gallery openings,
How to write pitch subject lines editors *actually* open
Tuesday, September 3, 2024
this example is from Vice news. ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
#472: Enterprise UX
Tuesday, September 3, 2024
Healthcare UX, complex applications and how to run UX research in complex, legacy-ridden enterprise environments. Issue #472 • Sep 3, 2024 • View in the browser Smashing Newsletter Guten Tag Smashing
171 / Manifesto for creating great branding & design
Monday, September 2, 2024
Product Disrupt Logo Product Disrupt Half-Monthly Aug 2024 • Part 2 View in browser Welcome to Issue 171! I'm reading Million Dollar Weekend by Noah Kagan these days. Honestly, I'm not into
The parallels of job seeking and dating
Sunday, September 1, 2024
Issue 210: Reflecting the similar arcs and tips on both ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
What Is It About Noguchi?
Thursday, August 29, 2024
View in your browser | Update your preferences ADPro Light Work Next year marks the Noguchi Museum's 40th year in operation, and even though we're now decades past the artist and designer's
Why we rebuilt Balsamiq Templates
Tuesday, August 27, 2024
How we rethink major features, like Balsamiq Templates. ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
Faye Toogood’s Magic Ingredients for Company Culture
Tuesday, August 27, 2024
View in your browser | Update your preferences ADPro After eight years working in a townhouse in London's Shoreditch district, “the charm was becoming problematic,” says Faye Toogood of the small-