rk.

Rameez Kakodker
PTOTD#66

Do not confuse Customer requirements for Product requirements.

Thoughts on the PTOTD

Customer requirements that are posed as solutions to the problem they’re facing are incorrect indicators of the underlying problems. e.g. If the customer demands that a new CTA be added to a particular screen on the app, don’t just add it. Find the underlying problem that is being solved. It might be that the functionality already exists, but isn’t apparent! You’ll need to revise your customer journey after you quantify the problem faced.

Whenever you get requirements from the customer-facing teams, always look for the problem they’re solving.

You may also like

  1. Balance out forward planning & backward planning when building your product.
  2. Every feature you bring into your product is a choice for the customer. Remember the Choice Overload bias and map the potential user impact
  3. If your roadmaps are decided at the beginning of the year and do not change with customer/business priorities, you might be a corpo product manager.
Join 100s of other Product Managers in reading & discussing this PTOTD: