Suggestions
Pankaj Yawalkar
Product Manager, Founder
Pankaj Yawalkar is a Senior Product Manager at Lanvera, recognized for his extensive experience in product management across various sectors, including FinTech, EdTech, and eCommerce. He is skilled in Lean and Agile methodologies, market analysis, and data-driven decision-making. His professional background includes a strong focus on scaling products and optimizing workflows.123
In addition to his role at Lanvera, Pankaj has a diverse skill set that encompasses expertise in eCommerce workflows, platforms, and APIs. His work reflects a commitment to leveraging technology for enhancing product performance and user experience.23
Highlights
What does a successful product look like? To me, it is a product that lets my user take her daughter to the 6 pm soccer practice with satisfaction of having achieved what she wanted to get done that day.
A product that does this checks so many boxes. It has understood the user, the buyer, and their needs and wants. It has achieved a product market fit and got the pricing strategy right to be in front of the user. It is easy to use, performant, scalable, and supports the user.
The organization that created it has got its priorities right and is solving the right problems. It has achieved alignment around the product vision and has a good sense of direction. It has created systems that support users and listen to them.
Having all this in one place is not easy but critical if the product has to succeed.
Often, scaling a product from 1 to 100 seems like multiple 0 to 1 builds. This is especially true in the B2B SaaS space. There is a constant tussle between revenue, customer churn, and product vision.
Here are a few things I try to do to keep these one-off feature requests to a minimum
- Try to find the reason behind the request. Often, a different but genuine requirement lurks behind the feature request and is shared by multiple potential clients. Solving that underlying requirement can add value to the product.
- Check for people and process issues: Many times, requests stem from long-established processes, workflows, and aversion to change. Addressing those, assuaging fears, and providing workarounds that fit into the long-term vision can help.
- Ask for worst-case scenarios: Asking customers what they would lose in the absence of those features and what the cost would be is helpful. In some cases, it makes customers look internally and find that they don't need what they are asking for.
What do you do? How do you handle one-offs?
