Navigating New Frontiers: Why I Chose Microsoft and What I've Learned So Far

This post answered the questions “What made you join Microsoft? What have you found to be useful from your experience outside of Microsoft to bring to your new role? What have you learned at Microsoft that you wish you knew or could have put to practice in a prior role?”.

Why I Joined Microsoft

In 2022, during a reflective parental leave after 15 years in the tech industry, I stumbled upon a post by Reid Hoffman discussing the future of work. He highlighted artificial intelligence (AI) as a critical domain to watch. My journey with AI began at Telenor Digital in 2015, where we leveraged machine learning to personalize mobile data pricing—a practical application that sparked my interest beyond theoretical knowledge.

Subsequently, at Diffia and Kahoot! , I continued to explore AI to enhance healthcare outcomes and personalize learning experiences, respectively. However, it was the role at 微软 that offered an intriguing convergence of my interests in product strategy and AI, particularly through the lens of large language models (LLMs).

Before joining, I met with leaders at Microsoft Development Center, Norway, who were exploring new opportunities using large language models (LLMs). This was 3 months before ChatGPT’s launch and the widespread recognition of GPT technologies, and the potential to shape product strategies with these tools was both novel and exciting.

My career has always been about pioneering new ventures, whether within startups or larger corporations. The opportunity at Microsoft to delve deeper into AI and develop new strategic initiatives seemed like the perfect next step in my professional evolution. This role promised not only a chance to expand my expertise in AI but also to significantly influence emerging technologies at the forefront of innovation.

Valuable Lessons Brought to Microsoft from Previous Roles

My tenure particularly at several startups, including Kahoot and Diffia, taught me critical lessons about product development that I've brought with me to Microsoft. A pivotal realization was that most products don't fail due to technical infeasibility or lack of business viability but because they fail to resonate with users. They often don't solve a pressing need that users are willing to pay to address. This insight came from firsthand experiences of moderate successes and notable failures.

Another fundamental lesson was the importance of distribution. A product’s success is not solely about its features; its reach and adoption are equally crucial. At Kahoot, despite the product's simplicity at the time of my joining, its massive user base of over 70 million was a testament to this principle. This extensive reach made it relatively easier to monetize through user conversion rather than investment in costly advertising.

These experiences have equipped me with a unique perspective within Microsoft, especially valuable given that many PMs here have primarily grown their careers internally, often focusing intensely on engineering aspects such as scalability and maintainability. In contrast, my approach integrates a strong emphasis on market fit and user engagement—areas that are sometimes overshadowed by technological considerations.

Additionally, my direct interactions with hundreds of users have honed my ability to discern their unexpressed needs, a skill that seems rare in larger corporations where direct user contact is often delegated to specialized departments. My diverse background across industries like healthcare, education, telecom, e-commerce, and media enhances my ability to empathize with a variety of customers, further enriching my contributions to Microsoft.

Key Learnings at Microsoft: Writing Culture and Influencing Without Authority

One of the most significant practices I've embraced at Microsoft is the strong culture of writing. Previously, I was familiar with the concept from Amazon's practices but hadn't truly seen it in action. At Microsoft, especially within the Microsoft 365 Core team, writing is foundational. Our strategic reviews start with a written narrative read by all participants, which is then discussed in detail. This method contrasts starkly with my past experiences in startups where the pace often made documentation seem obsolete upon creation and decision-making was rapid and informal.

Writing forces precise articulation of thoughts and ensures uniform understanding across all stakeholders, whether or not they can attend meetings. This practice preserves context and facilitates more informed decision-making, a method I now see as invaluable compared to the less structured approaches of my past roles.

Another critical skill I've developed is the ability to influence without authority. Microsoft’s complex organizational structure requires engaging numerous stakeholders who you have no direct control over. This skill involves not only presenting ideas compellingly but also aligning diverse teams towards a common goal across various levels of the organization.

These skills—meticulous documentation through narrative writing and influential leadership without direct authority—are pivotal in a vast company like Microsoft. They have reshaped how I approach my role and would have been incredibly beneficial in my previous positions, potentially amplifying my impact even further.