Introduction

What motivated me to document my professional journey and share it with others?

I’ve navigated through a significant life crisis and struggled with the process of transitioning into product management. The subsequent move ‘backwards’ away from it caused considerable emotional stress and peer pressure. If I can assist anyone who finds themselves in a similar situation, I believe it would add significant value to their decisions; hence, this recounting of my journey feels worth writing. Additionally, over the years, I’ve received numerous private inquiries from individuals who, having transitioned into product management, are now discontented but feel trapped due to its perceived aura of success.

Background

What initially attracted me to the field of solution architecture?

My affinity for working with people and technology found a perfect balance in this role. The flexibility in time allocation and the ability to escape the office for customer meetings was a substantial perk, especially before the prevalence of remote work in the pre-Covid-19 era. I cherished the constant learning curve the role offered and the motivational pressure to stay at the top of my game to avoid embarrassment from competitors or clients. Lastly, I was part of a pre-sales organization where politics, although present, were relatively contained. Working in small, focused teams with account executives and colleagues from supportive functions was refreshing and the organizational structure was transparent. Successes, contributions, and performance were tied directly to monetary results, which cleared a lot of ambiguity and made it easy to identify who was truly moving the needle.

What were my primary responsibilities as a solution architect and what did I enjoy about this role?

In my role, I collaborated closely with the account executive to bring new business to existing customers and acquire new enterprise accounts across all sectors. In addition, I spoke at company events and conferences, built relationships with partners such as technology vendors and customer stakeholders, and designed technical architectures for security and infrastructure projects. I conducted product demos and proofs of concept (PoCs), and actively engaged with the global solutions architecture community to share knowledge.

Transition to Product Management

What sparked my interest in product management and led me to transition from solution architecture?

During 2016 I was working as a senior Solutions architect for RSA a security vendor, I was the only representative in Israel and the Southern Mediterranean countries. A role which gave me great flexibility and i have had great sense that i have reach the peak of my career that it would be difficult for me to do any better in a significant way, and still i was not happy with the different pillars of my life, i didn’t had great work life balance, i didn’t had a clear trajectory for financial independence or even hitting my financial goals even tough i have had doing above average for my age group and i felt that there is a glass sealing and that i was not doing things that are creating large enough impact in the world. In essence, I was wrestling with these shortcomings, sparking a desire for change. This sense of dissatisfaction was what drove me towards product management – I was seeking something different, an escape from the shortcomings I had identified in my current situation.

How did I prepare for the transition and what were your expectations about the role of a product manager?

In my mind, I was aiming to become a founder and CEO of my own company because that role presented unlimited potential. I had been influenced by the oft-cited maxim that great founders are also great product people, with Steve Jobs being the most prominent example. Therefore, I concluded that a role in product management also offered unlimited progress and potential, whether that be within the corporate world or in the entrepreneurial sphere. Given that I lacked actual product management experience, I constructed a narrative highlighting how I had contributed beyond my official sphere of influence in my prior role. I collaborated with R&D and product management teams, providing feedback on roadmaps, and conducting proofs of concept (PoCs) for new features and early access beta programs. Furthermore, I emphasized that customer interaction, including listening and conducting interviews, was a significant part of my role. Luckily, leveraging my professional network, I managed to secure a position as a Product Manager at a cybersecurity company focused on the defense sector, which was one of the most exciting days of my life.

Reality of Product Management

What were the most significant differences I experienced between solution architecture and product management?

The most glaring difference was the pace of day-to-day work. Building enterprise software is a slow and meticulous process. The journey from initial idea and PRD (Product Requirements Document) creation, through to code that passes QA and is eventually shipped to an early access customer, can easily span 3-4 quarters or more. This timeline only covers the initial version, which is typically imperfect and feature-poor, requiring further iterations. As someone accustomed to quick wins and immediate gratification of sealing deals, this pace was painstaking and frustrating.

Another difference was the necessity to be a ‘political officer’. Product managers lead without authority, acting as matrix managers. In other words, it meant constantly battling for attention and resources, negotiating timelines with R&D leaders and other product groups. This continuous engagement in political skirmishes was quite disheartening.

A third contrast was the lack of clear metrics for performance, unlike in solution architecture where sales targets directly measure contributions. In product management, many uncontrollable factors can impact product success, such as the sales organization, other product managers, R&D’s implementation of features, or the marketing organization.

The exposure to corporate decision-making was another stark difference. Being part of this process in a large corporation, yet often lacking the power to significantly influence it, was highly frustrating. Working in scrum implies releasing a version that may initially disappoint, then quickly iterating on it. In large corporations, however, the iteration process tends to be sluggish.

There’s also a lack of technology diversity in product management. One tends to laser-focus on a specific product or, at worst, a set of features within the product. This high level of specialization was something I did not enjoy, as I prefer to continuously learn and diversify my knowledge.

At the time, pre-Covid-19, there was an expectation for teams to work together in the office. As someone who disliked being office-bound, this was a source of frustration for me.

Were there any aspects of product management that I found particularly challenging or different from your expectations?

To reiterate the points above, the political nature of the role, the slow pace of work, and the inability to drive changes for the product as I saw fit were particularly challenging. Additionally, I encountered an unsettling sense of arrogance among team members who felt they knew better than the customers or the R&D teams. Although these thoughts were rarely vocalized, the vibe was palpable and left me feeling misaligned with the group in terms of values and spirit.

The Decision to Return to Solution Architecture

What were the key factors that led me to decide to transition back to solution architecture?

The accumulation of frustrations, which manifested as low energy, reduced motivation, and heightened anxiety, began to spill over into my day-to-day life. At a certain point, I recognized that a change was necessary. Initially, I thought the issue was with my place of employment, so I transitioned to a large international American vendor. When I experienced a replay of similar challenges, I understood that the problem likely lay with my fit for the job. This realization was a considerable disappointment, given that I had spent several years as a PM and genuinely appreciated the prestige that came with the role. Yet, I decided that alignment with my values was more important than preserving my ego. To move forward, I had to retreat. I reached out to my contacts from my previous solutions architect roles and landed a regional specialist position at VMware.

Do I have any regrets or second thoughts about this decision? If so, how did I overcome them?

I harbored no regrets. The moment I made the move back to the role of a solution architect, I felt a sense of returning home, and the anxiety I had been experiencing dissipated. The challenge of feeling a ‘glass ceiling’ remained, as I hadn’t found a solution for it. However, I was able to address this by securing a technical role with a potentially high upside at Microsoft, which is what I am doing today and, so far, it’s going well but this is requires a dedicated blog post.

Lessons Learned from the Journey

What are the main lessons I learned from my experience in product management?

Not everything that glitters is gold. Avoid making long-term decisions driven by ego. Identify what you truly love and continuously build your skills around that. If things don’t pan out as expected despite your best efforts, demonstrate the flexibility to reassess, rollback if necessary, and move forward.The next time I take on a product management role, it will be as a founder of my own company where I hope to truly influence my product roadmap.

How has this experience influenced my perspective on your role as a solution architect?

In my opinion, being in a customer-facing role is one of the best and most undervalued jobs in the corporate world.

Advice for Others Considering a Similar Career Path

What advice would I give to other solution architects considering a transition to product management?

Ensure you are considering the transition for the right reasons. Seek insights from friends and colleagues who have made the transition and reflect on how they feel about their choice. Try to understand and visualize the challenges I’ve experienced and imagine how you would respond to them. Then, make your decision. However, it’s important to note that I’ve seen many individuals flourish in the role of product management and truly enjoy their work – you could be one of them.

Concluding Thoughts

Looking back, what are the positive takeaways from my experience, even though you decided to return to solution architecture?

Despite my decision to return to solution architecture, the experience offered invaluable lessons. I gained a deeper understanding of how an R&D organization functions and developed my ability to effectively communicate with developers. It also sharpened my skills in truly listening and understanding customer pain points and needs. Overall, the experience expanded my horizons significantly.

What my your hopes for your future career trajectory?

I plan to continue my journey in technical business development, with a further lean towards its business aspect, where I expect to see continued career growth. Additionally, I am exploring the possibility of relocating to a different country later in my career to further broaden my horizons.