There are many templates and formats people follow while writing a PRD (product requirement document), based on the industry or the market their product is catering towards. Download this SaaS PRD template, here: SaaS PRD template - Google Docs The template has all the sections and placeholder texts helping you understand what each section is and how it has to be filled. Here’s a good article which in which Manas explains how he formulates the PRD....

2009: I graduated in Electronics and Communications engineering, and moved to Bangalore and then back to Hyderabad. I was also running a web hosting service (HeroeHost) along with 2 other friends (Mohan & Corey). 2010: Things got interesting with the web hosting service business, so I left my customer support job, stayed with parents and later sold the hosting business in 2010. 2011: Came back to Hyderabad and along with Mohan tried to float a e-commerce business, of building custom gaming desktop PCs (named it idle bazaar)....

Good product managers are more of a generalists than specialists in any organisation. Right from idea brainstorming and validation to getting the final feature shipped with good UX and KPIs monitored after launch, a product manager has her finger prints all over. While lot of PM talk revolves around the good parts, there are some grunt tasks that a product manager has do to get their feature successful. Let’s look at some of the less exciting / celebrated tasks of a product manager....

Back in the late 90s, as a child I watched few road side magic shows. Little did I know then a PM is expected to be the magician in a software organisation. Magic shows are great fun! While they don’t excite me now as much as they used to, I’d still love to watch them trying to understand how the magician connects with the audience and masterfully performs his tricks while thousands of eyes try to find the ‘how’ of the act....

What’s one thing common among all those successful product hunt launches? They started with building an audience first before launching them. Take a look around - makers kitchen, reddit, hacker news, product hunt and any other avenues where you see the launch of the tech and software products and the discussions around them - long before the product is actually “launched”, these builders talk about their products frequently. As in the comments for related posts, answering questions to gain reputation, blogging and building audience in the form of newsletter subscribers, podcasting or even engaging actively in the makers communities....

As product managers, we take decisions in our work life almost on a daily basis. Some we take by looking at our existing user data, others by the market research and few by the entrepreneurial “gut” feeling that comes with deep understanding and experience. Among those plethora of decisions we take, what if you have to decide among the following for a product feature Building it right Building it now And sometimes, Building it right, now How to choose one?...

Writing is hard. Incredibly hard. How many times have you tried to write a blog post on a general interesting topic (outside of your work task) but dropped the idea altogether? Last week there was a lunch table conversation with my friends and that’s when I realized I have this blog lying around without an update for over 30 months. I moved this blog from medium platform to a serverless infra and migrated my only two posts from Medium to here....

I’m one of those product managers who advocates that everyone in the organisation should know to code. Being a non-MBA and coming from an engineering background, I might be biased on that part. But I firmly do believe that knowledge to code helps us in bringing a better product to market. You can trust your engineers. If you do not trust your engineer everything can fall apart and it breeds a bad culture of mistrust, mud sledging and what not?...

I haven’t done customer interviews before. I avoided doing this in my earlier startups for the reason that I’m worried of talking to people one-one. What if they don’t get what I’m speaking? What if they squash the product vision and ridicule my product/feature idea just because this SaaS idea is not fine tuned to their custom requirement? Or the embarrassment of not being understood clearly of your product vision is hurting....