I alluded to this a few days ago, but I have a new role. Starting today, I am back at Microsoft. I’ve joined the Microsoft Identity division as a Principal PM and will be helping drive the efforts to build the best identity Software Development Kits (SDKs) and tools for developers that use services such as Microsoft Azure Active Directory and the Microsoft Account.
Not too long ago, I was reading Charlie Kindel's "You're Thinking of Your Career Trajectory Wrong" and it reminded me of yet another trope that somehow is very commonplace, at least in the tech industry - your career is not a sprint, it's a marathon. It comes from a well-intentioned desire to communicate the fact that careers should be looked at through the long-term lens, which makes sense - we rarely hear the story of someone being right out of college and then becoming a Vice President of Product at a Fortune 500. It's all about the long game. But it also sets a lot of folks for failure early on.
Talk about making some life changes in a short period of time! I am genuinely pumped to be coming back to something that is near and dear to my heart - developer relations.
It finally happened - after almost five years of sticking with macOS and a MacBook, I gave up and built my own desktop computer.
You are a PM. You work for a big company or a startup. You are tasked with determining the direction for your product, so you enthusiastically embark on the journey to talk to as many customers (or potential customers) as possible to determine what their needs are and how your product can help them in the long-run. After months of painstakingly collecting feedback, you emerged victorious with a PowerPoint deck that says: “We need a bigger button in the toolbar to let people renew their subscription easier”.
It’s 2018, and it’s time we understand that SMS 2-factor authentication is not a good way to double-check the users’ credentials. It’s been shown many times that phone numbers can be compromised.
2018 is (almost) upon us and many people are making new resolutions for what they want to achieve in the new year. I wrote about some of my high-level goals as well. The one piece missing in it is the how description, and for that I decided to write this post. Just like the overview post, I want to make this a yearly tradition - a set of tips on how to maximize productivity, based on learnings from the previous year.