Hello Folks!
We are glad to have Suba A Kanchana as our guest for this edition’s AMA series. Suba is currently working as a VP Product at Taxdoo, Hamburg.
Suba A. Kanchana has pursued her MBA from Esade Business School. She has more than 16 years of Technology & Product experience in various industries such as E-commerce, Banking, FinTech, and TaxTech. She has previously worked at Tata Consultancy Services, Lazada Group, OUTFITTERY and Deposit Solutions across India, United States, Southeast Asia and Europe.
In this week’s edition, Suba answers people’s questions around growing PM skills in a fast-growing startup, transitioning to Product Management, dealing with product prioritization and much more.
So let's jump straight into it!
There are lot of frameworks. Sometimes you don’t even need one as long as things are clear with the vision and strategy. In my past, I have deployed 3 types of frameworks:
When someone is in mid-career PM, I assume they have the key PM competencies covered; which is mostly: logical thinking, holistic approach, stakeholder management, product discovery etc.
To summarize the steps to becoming a product leader, it goes like this:
I started in small numbers and took up 1 or 2 teams additionally before taking up a whole portfolio. Above all, start to express your interest to your product leaders and this will help open potential doors.
Let’s break it down -
It mostly depends on the type of company you are in. If you are in an early stage or seed,finding the right market fit is more important. For a hyper-growth stage one, start from the vision. Be clear about where you see your product in X years and then plan or do your hard work towards it.
Personally, I always joined a post Series-A and went towards growth stage startups for a few years. If you join a seed or early stage, there won’t be any streamlined processes. That one product person will be doing almost everything in that organisation. That's more hands-on. Normally, you try fast and fail fast. Learn and move on.
If you join post-series A or B, that’s where the rapid growth comes in. This is where it’s really important to get to know from Co-founders where the vision and product thinking is. This is a key step because Co-founders need to have a product driven attitude to have a strong product focus. Else you will end up in project management /feature teams again.
Last but not the least, join ONLY if you believe in the idea and business model.
It was never really pre-planned for me to get into PM. I came from a technology background. I quit that job and pursued an MBA in Europe and a PM job just happened. The CPO of the company looked into my profile and thought that PM is the area that would fit me better. So it was quite serendipitous.
There will be a different type of learning in each. Start-ups will most probably have a steep learning curve. But you don’t necessarily do things in the right way. You do it in a way that's needed for growth.
That's when the learnings from big product companies come into the picture. You learn the best practices, understand various processes; the pros and cons of it. You start to go deeper in a specific domain/area compared to a start-up where you have your hands on all products.
As a PM, be clear on your core competencies, strengths and goals. Sometimes the growth is so fast that you feel you are in the middle of chaos. But this is where your learning curve is so high. When the growth happens so fast, you also start to focus on certain areas. Be upfront about it and find an interesting area for you.
In certain companies, they grant a couple of hours per week for training and learning. So, they push people to allocate time amidst the workload. I normally block myself for specific learnings.
The beauty of this evolution is that you will not realize that you are learning so much until you look back. Though you can also refer to books, diff. blogs etc, I believe in learning in the job with new problems coming up too.
Actually, The Product Folks is quite cool and has a lot of resourceful info there too. Nevertheless, my favourite books depending on what you want to know:
Some of the blogs I like are medium, SVPG and most authors have their own blogs too. MTP has one as well. So, these are my go-to mostly.
Yes, internal transition has a huge advantage in that they are already part of the company and understand the business. The key point is building trust and confidence in the Product management team. This is based on the outcomes achieved. Keep a soft goal for yourself for every quarter and look back and see if it’s in the right direction.
This one is not always easy. The big advantage in my profile was that I did Software development in Banking. So that experience really helped and that’s how I was able to push myself into Fintech. If it’s the start of your career, starting with an entry-level PM job in Fintech helps. If not, before doing a career switch, you should develop self-interests in the industry and domain where you self-teach yourself. But as I said, this one is really difficult.
Companies don't necessarily expect deeper tech knowledge for Product roles. Yes, you need to know how to interact and understand the engineering teams. But focus on the core PM competencies. Pick the type of PM roles that are relatively "less" tech focused. That would help. But I think this isn’t a deal-breaker in most cases.
Nevertheless, if you would really like to develop Tech skills, start with basics such as understanding API interactions, high-level architecture flow etc.
I believe that entrepreneurs and co-founders are the first product managers in a company. As an entrepreneur, you get to have varied experiences. As a PM, start with the specific focus where you have much interest or where your strength is. For example, If you are strong in Analytics, you can be a Data PM. Whenever I come across such candidates, I always look for very specific achievements or areas rather than keeping themselves broad.
This is quite interesting and common more often than not. Always look for values that you would bring in along with the features. With B2B, you have access to lot of customer data/metrics and potential customers are clear as well. Quantify as much as possible if there is a big push and don’t forget user research. Since its limited user groups anyways, always aim for experimentation before a decision.
MBA helps, but it’s not really a prerequisite. As long as you have logical, analytical and user approach based thinking, it’s already a big advantage. In a fresher interview, I personally ask case/design questions, coupled with examples that could help them to display basic competencies. I don’t expect a bunch of proven records or deliveries.