Topics In Demand
Notification
New

No notification found.

Low code for Product Managers
Low code for Product Managers

December 1, 2022

208

0


Listen to this article



Our founder, Jinen Dedhia recently attended product-con (a conference for product folks) & he had an opportunity to chat with product managers across the length and breadth of tech companies across the world. Sure KPIs of product managers have nothing to do with delivering features or engineering them. However, there is a business case for product managers for using low-code tools. Let's dig in –

1. NPS or CSAT is one of the commonly found KPIs of product managers. As a PM your controllable are a better quality product for a better outcome. However, there are things beyond product usage. For instance — your customer wants his subscription plan paused or upgraded/downgraded by raising a support ticket. Such tickets attribute to ops overheads and need engineers' time to resolve such tickets. To make it scalable — you need engineers to build tools to either make things self-serve or enable support to resolve queries. Such ops features seldom have a high priority on them.

2. Custom features for specific customers — as your customer base grows you would see incremental demand for features. While you have the luxury to prioritize them however demand for features from strategic accounts can’t be ignored as your sales/account team wants them not to be a show stopper.

Allocating resources for features for NPS/CSAT is often met with resistance as their priority gets debated and this leads to deprioritization. Low code tools are now becoming powerful to build these features for self-serve completely outside the product and embed them right inside the product and thereby cutting the dependency on the traditional engineering line and yet enabling such features to improve their CSAT/NPS.

In the case of high-value customers demanding a specific feature is often met with counter arguments from engineering. However bright chances are sales will push for this and they would win. Now, this is a problematic space for two reasons:

1. you may or may not have a soft commitment from the prospect

2. your investment to bring the feature alive and the opportunity cost of not really building the feature you were looking at building

These two cases are where he has seen product managers really open to the possibility of building them with low code. While 90% of 1st cases are possible to build with Low code, the probability for 2nd case might be 50%. There is an obvious benefit here of using low code

1. build things faster

2. build with lesser resources

It would be interesting to learn the perspective of product managers out here. Looking forward to your comments/feedback.

Originally published at https://www.linkedin.com.


That the contents of third-party articles/blogs published here on the website, and the interpretation of all information in the article/blogs such as data, maps, numbers, opinions etc. displayed in the article/blogs and views or the opinions expressed within the content are solely of the author's; and do not reflect the opinions and beliefs of NASSCOM or its affiliates in any manner. NASSCOM does not take any liability w.r.t. content in any manner and will not be liable in any manner whatsoever for any kind of liability arising out of any act, error or omission. The contents of third-party article/blogs published, are provided solely as convenience; and the presence of these articles/blogs should not, under any circumstances, be considered as an endorsement of the contents by NASSCOM in any manner; and if you chose to access these articles/blogs , you do so at your own risk.


© Copyright nasscom. All Rights Reserved.