Resource Stash for all things related to Software Product Management!

Esteemed readers,

I have created a resource stash for all things related to Software Product Management. It contains links to interesting articles, tools, blogs, and more. I will keep adding items to the stash and currently I am moving content from the blog to the stash.

Please keep using the stash, comment with inspiring posts, like the stashed items, and visit the linked sites. Thanks for reading this blog.

I am thinking of purchasing a suitable domain name for the stash – any suggestions?

Thank you.

-The Inspired Product Manager

20 Questions from New Scrum Master to Product Owner

What should a new Scrum Master ask the Product Manager? Here are some suggestions that also provide a view on the product manager’s duties. I do not agree with all questions and all proposed answers, but it is definitely inspiring.


Addendum: I have created a resource stash for all things related to Software Product Management!

Better decision making

I stumbled across a post about better decision making for product managers. It encourages to pose three questions for each decision with larger (expected) impact:

  1. Imagine that the option you’re currently leaning toward simply vanished as a feasible alternative. What else could you do?
  2. Imagine that the alternative you are currently considering will actually turn out to be a terrible decision. Where could you go looking for the proof of that right now?
  3. Six months from now, what evidence would make you change your mind about the choice you’ve made? What would make you double-down?

Read the explanations in the full post “How to avoid the curse of knowledge“.


Addendum: I have created a resource stash for all things related to Software Product Management!

How to spot an outstanding product manager

The post “Find, Vet and Close the Best Product Managers” is about the hiring process of product managers. It provides good examples of questions and weak and strong answers, so it is definitely worth a read.

More than that, outstanding product managers’ qualities are listed, and I fully agree:

  • Articulate what a winning product looks like.

  • Rally the team to build it.

  • Iterate on it until they get it right.

The qualities are then further explained:

  • Intellectual ability

  • Communication

  • Leadership

  • Effectiveness within the company culture

  • Knows what users want

  • Strategic/Analytical Thinking

  • Technical background

  • Entrepreneurial spirit

Addendum: I have created a resource stash for all things related to Software Product Management!

Users do not want to learn how to use your product

As a product manager, you might be tempted to assume that users want to learn how to use your product. You provide loads of documentation, a hotline, and a lot of other help for the inquiring user.

However, user are usually not as excited about your cool and fancy product like you are. They have a goal in mind and just want to reach it. If your tool is the right one, fine. If not, they will eventually choose another one (e.g. when it is too complicated to understand).

User action requires three things:

  • Necessary motivation
  • Sufficient ability
  • Effective triggers

Learn here how to provide these three requirements here.


Addendum: I have created a resource stash for all things related to Software Product Management!

Motion in UI Design

UI Design is not restricted to static display only. Motions helps designers improve user experience. The article “Motion in UX Design” explains why:

  • It drives user’s attention and hints at what will happen if a user completes a click/gesture.
  • It helps you orient users within the interface and provides guided focus between views.
  • It provides a visual feedback.

Check out the very good examples as well!

Why startups fail

Many startups fail, and now there is a study showing why they fail. Interestingly, I see two reasons on top:

  • Business model not viable
  • Money issues

The money issues are of diverse nature, though money seems to play a major role when startups fail. It is more of a concern, though, that the business model is a major reason for failure, because that could have been anticipated beforehand in most cases.

Read the full analysis here.

When to say YES to a Feature Request

Last week, I linked a very good post about how to say NO to a feature request. But then, when should you say YES to a feature request? There are a couple of questions to answer:

  • Does it fit your vision?
  • Will it still matter in 5 years?
  • Will everyone benefit from it?
  • Will it improve, complement or innovate on the  existing workflow?
  • Does it grow the business?
  • Will it generate new meaningful engagement?
  • If it succeeds, can we support & afford it?
  • Can we design it so that reward is greater than effort?
  • Can we do it well?
  • Can we scope it well?

I especially like to way to look on long-term cost.