To get to this point, you have to ask yourself:

  1. What do your users want?
  2. How do they feel?
  3. What are they struggling with?

This is where most product managers stop —

but there’s MORE to it than that.

For each problem, I stay five times “why” to uncover the real reason.

  • The first answer is why they’re telling me about their problem in the first place.
  • The second answer is why they’re telling me about their problem now.
  • The third answer is why they’re telling me about their problem when we’re talking about something else entirely.

And so on…

Ask “why” five times about each issue until you get to its root cause.

The goal here is to discover what’s causing them pain so we can find ways to resolve it.

Maayan Galperin,

Product Manager

--

--

A release note is a document that describes the technical features of new or updated software.

These documents usually include information about:

  • The version number and date of release for each update or upgrade
  • List of the new features and their impact on end-users
  • List of bug fixes and their impact (“fixed a bug that prevented/ caused/ allowed …”)
  • Known issues, limitations, and bugs — especially for internal use (e.g., the customer support department)
  • Known incompatibilities with other programs or devices

The distribution methods of the document vary between different products and other users.

Common channels include:

  • In the product itself
  • Emails
  • Blog posts & social media
  • Google Play & App Store

Maayan Galperin,

Product Manager

--

--

Maayan Galperin

I believe that knowledge and practical tools are the keys to success in all areas of life. This is what I research, implement, train, and teach others to do.