Sign In

Abishek Viswanathan

Chief Product Officer, President | Apollo.io, Qualtrics, Zynga

Abishek Viswanathan is a design-led, data-driven product executive with over 19 years of experience in driving product strategies, roadmaps, and execution plans.1 He is currently working on a wide product portfolio as Chief Product Officer, based in the San Francisco Bay Area.1

Previously, Abishek held significant roles at prominent companies:

  1. Chief Product Officer at Apollo.io (January 2023 - Present)12
  2. CPO/GM at Qualtrics (2017 - February 2023), where he played a key role in scaling the product and platform teams from a $170M business to over $1B in ARR1
  3. Director of Product Management at Zynga (January 2013 - December 2017)1
  4. Senior Product Manager at Amazon.com (April 2012 - September 2012)1

Abishek holds an MBA from the University of Washington's Foster School of Business and a BTech in Electrical and Electronics Engineering from the University of Kerala.1 He is known for his action-oriented approach, emphasis on collaboration, and consensus-driven decision-making.

As a product leader, Abishek has been involved in various successful initiatives, including growing and scaling product teams, developing revenue-driving products, and leading high-growth businesses.13 He is passionate about creating exceptional user experiences and mentoring emerging leaders in product management.3

Highlights

Aug 17 · linkedin

Retention is an output metric. Meaning, several activities and input metrics feed into retention. It is one of the most important KPIs in B2B, specifically paid user retention. If paid user retention isn't a straight line (also defined as Gross Dollar Retention in the 90s or Net Dollar Retention > 100), your users aren't getting repeat value - the product/service is not sticky enough to grow infinitely. You have to work doubly hard to replace the leak at the bottom of the bucket.

Off late we've seen far too many people show slides on how they moved customer retention (or in the B2C world - Day 30 retention) significantly, and when you hear someone say that, you have the right to be skeptical (they are likely not an operator, but great at slides).

They are likely reporting on the success of some other team that spent days and months

  1. Personally onboarding customers
  2. Mapping out the customer journey, and identifying all the friction points that prevents them from getting value
  3. Carefully removing all of the UX and tech debt that the product has accumulated over time and simplifying the path to immediate "wow"
  4. Cataloging all the different user types and the use cases of the product that drives unique landed value (not indirect value)
  5. Led a cross functional team (eng, CS, marketing, support) as a single threaded owner- that took massive risks to implement new, drastically different "hybrid" flows - both with humans in the loop as well as combining that with in-product UX overhauls
  6. Failed 3-5X in the process until they reached one or more input metrics - # of customers fully setup, # of customers getting value once, # of customers getting value multiple times.
  7. Ruthlessly measuring everyday, obsessing over customer anecdotes - what did a user say this week about how quickly they got value and was it useful

The path to improving retention is a labyrinth. Very often you have to be patient and try testing several hypotheses to see one or many of those input metrics move and not glorify "retention".

#retention #NRR #GRR

Aug 9 · linkedin

Some of the best products that have been built required builders to:

  1. Run 100s of interviews (most often getting a 50/50 polarized viewpoint from user - half of them love it and half of them hate it)
  2. Run onboarding and customer success themselves.. onboarding users to the product and meet daily/weekly to see when/if they are getting value
  3. Personally be the first line of response to incoming support requests

This allows the builder to deeply empathize with the users, understand and identify how the primary use case is faring and what new use cases are emerging and most importantly, develop deep instinct about the problem area.

So why does this not work in a larger company?

We end up hiring on the basis of ratios - for 10 engineers we need a PM.. for 100 engineers, we need 10 PMs. Every additional PM brings in more creativity and more products, for which we need more PMs.. And so this happens:

  1. Customer research goes to a central research team (builders are not as close to the problem area anymore)
  2. Onboarding goes to established customer success functions (builders are not close to solution and how effective it is anymore)
  3. Customer service becomes the first line of defense for support (builders are not close to edge cases or intended/unintended uses of the product anymore)

Going forward, we'll start seeing different company structures:

  1. Leaner teams with larger ratios (1:20 product management: engineering, 1:10 design:engineering)
  2. More ICs, fewer managers
  3. More cross functional builder teams (product + ops + cs + support) reporting to a GM

The TLDR is that the PM function needs to go back to its roots - do first hand research, personally onboard customers and be deeply involved in support calls. Some of this is already happening, but its going to be happening more often going forward.

#redefinePM #backtobasics

Related Questions

What are some key strategies Abishek Viswanathan has implemented at Apollo.io?
How did Abishek Viswanathan's experience at Zynga influence his product approach?
What makes Abishek Viswanathan's design-led and data-driven approach unique?
Can you provide examples of Abishek Viswanathan's successful product roadmaps?
How has Abishek Viswanathan's background in engineering influenced his product management style?
Abishek Viswanathan
Abishek Viswanathan, photo 1
Abishek Viswanathan, photo 2
Add to my network

Location

San Francisco, California, United States