My Journey to Product
Or the romantic version of it!
Lately, I’ve been thinking about my journey to becoming a product person. I wondered why I’ve become so passionate about product development (and eventually business development) rather than “just” software development, which is where I started more than two decades ago.
After a while, I was able to draft a few insights that explain my journey so far, and I decided to share them here. Perhaps you can add something to it; maybe you’ve been trying to find your purpose. So let’s brainstorm together.
The Power of Creation
I can say without question that one of the main reasons I was drawn to software development back when I was 15 was the power to create whatever I wanted or needed. I typed a few lines of code on my 386 PC, and suddenly there was this fantastic functional menu on top of the screen. At some point, I was able to create a little program for an 8051 microcontroller, and I could make some lights turn on. Now, that’s power! At least for a teenager back in the 90s, that was just awesome.
When you realize such power, you start to dream of all the possibilities. Technology, as we all know, advances rather fast. Year after year, the possibilities are more significant than ever. That feeling I had when I was 15 never faded; if something, it grew continuously.
And the power evolves. At some point in my career, I was not only coding but also influencing how we’d solve the problems I was given. That’s when we start working as an architect. You’ve got to come up with the — supposedly — the best solution, the best architecture. And it’s very fulfilling when you see your ideas becoming a product millions of people use to, for instance, book their next hotel stay in beautiful Cappadocia.
But then, I wanted more…
Add People to the Mix
Another topic I consider myself passionate about is people, or to be more precise, the intricacies of the human being. Probably because of my inner questions about myself, perhaps because I’m inquisitive about everything. I love learning about people’s backgrounds. What’s their story, and what’s their purpose.
I was lucky enough to be in a family that has always praised a good read. I can’t go one day without reading, be it for professional or entertaining purposes. That’s a treasure, and I wish every kid on the planet had the same opportunity. It does make a difference in one’s life.
When you become an architect or a more senior software developer, and you start thinking about the people who will use your software, you realize there’s more to it than technical decisions. Decisions such as what database we should use or if we should cache the data or not. Message queues, anyone? This is crucial, but what exactly do the people care about? What is their purpose, and why do they need that software we’re creating?
Wait, something was wrong with me because… I wanted more…
Start a company? Me? This software guy?
It became quite natural to start talking with a few friends about the possibility of creating a company. Eventually, I did it. In the beginning, you start with an idea of a product (it’s not "just" software anymore). For that, you need to talk to some people. Those are your first users willing to test your barebone prototype and say it’s “awesome”, so you get enough motivation to go on.
But your first users are a “scam”. Well, not really, they’re fantastic, but they represent a tiny representation of your market. It definitely skews your “awesome” plans towards a direction that might not be the best.
That’s when other disciplines come in handy. It’s a lot of learning on such a rough journey. You do make wrong decisions, both technically and strategically. And this is good because you grow, making you think outside your comfort zone. There are customers to deal with; after all, you want happy customers. But there are other people you have to take care of, your colleagues. They’re counting on you. They’re betting their careers on your product and your leadership skills.
That experience brought a lot of questions to my life. I started questioning my abilities and skills (soft or technical). That’s when I realized it’s been all an excellent opportunity for growth. My mindset has been challenged in such ways that made me realize that I am a product person because of people. My software development background brought me here, and it became a powerful tool. A tool that I still enjoy today. However, when it comes to getting my hands dirty, I can’t think of lines of code only but the impact we’re making on people’s lives.
On Being a Product Person
I believe all product people have similar stories. They want more. It’s not enough to work on one specific task but rather do multiple things and play numerous roles. We love talking to people, brainstorming ideas, negotiating, understanding the company’s vision, and building a motivated team. A product person is a purpose seeker. A reader of the world, a problem solver, a hands-on person, a storyteller, a creator. That’s all fascinating to me. I still have lots and lots (and lots) to learn with my team and with some great product people and friends who are far more experienced than me, but now I know it’s been all worth it, and I’m on an exciting journey.
By the way, I can’t stress enough how much I owe to everyone who, one way or another, joined me on this journey at some point. I don’t think we can have a fulfilling life without great people. I’ve been lucky to be on incredible teams throughout my career.
Is it too cliché to say “the best years are still to come”? Am I romanticizing it too much? Well, the idea and purpose are always a romantic version of reality, but still, we’ve gotta lead our lives with a clear goal and purpose, even if the journey has its highs and lows. Would you agree?
Please, share your thoughts and your journey to becoming a product person. I’d love to learn with you!
