A Stack is basically a Web Directory. A Web Directory is a collection of data organised into categories. It specializes in linking to other web sites and categorizing those links. The concept of the Web Directory is as old as the Internet itself, but was revived by Bram Kanstein when he created Startup Stash. Startup Stash is Web Directory focused on Startup tools and resources and is the most upvoted Product on Product Hunt to date. Product Hunt is community that surfaces the best new stuff, everyday.
The possible reason for such a big success of the Stacks is the fact that in an era for overload of information it has become crucial to curate information. Curating information means collecting and organizing information by giving it an ordered and new meaning.
I have previously created a Content Marketing Stack, focused only on Content Marketing. You can have a look at some other Stacks by heading to Bram's Collection on Product Hunt: The Revival of the Startpage Directory.
Is a Stack, or Web Directory if you did not read above, that focuses on the Skills needed by a Software Product Managers.
I have composed this Stack with the following type of people in mind:
People completely new to Software Product Management - Have patience and determination and read all the Basic Theory Resources in every section.
People that have some experience in Software Product Management - Read the Advanced Theory Resources in every section. Or simply study the resources in the categories that you feel you need improvement.
As Michael Wolfe wrote: "You may want to take some courses, read some books, or go to some conferences along the way, but only to the extent that they actually make you better, not as a credential in their own right. Don't worry about credentials that certify that you are good. Work on actually *being* good."
I have an experience of 5 years in Software Product Management. During this time, I have continued to read books in the field (you can find links to my summaries within the Stack). This collection is a list of resources that I have personally studied or are in my Read List and made me improve my Skills.
The process of picking the books I choose to read is kind of long. I want to invest some time before actually starting a book that is 500+ pages. The process takes into consideration many sources: University Courses from the Top Universities, suggestions from "influential" Software Product Managers, reviews around the Web and, last but not least, Product Hunt.
Of course I'm open to adding new resources to the stack, but I want to focus on quality rather than quantity. Each resource add something very specific to the great picture. If you think something is missing or wrong, click on "Suggest" in the footer.
A Stack, as "revived" by Bram, is a collection of "resources & tools". My interpretation or resources is "theory". In my personal opinion, theory is very important. I'm not a big fan of the popular way startups behave nowadays: too much focused on experiments and growth and not on a strategy. In this way you just burn money, and eventually it ends. Theory is more important than tools, because once you learn the concepts, it does not matter which tool is the perfect one. The Stack has always theory at the top and the most important tools at the bottom. I'm not focused on quantity, but on quality. Product Hunt does a great job of featuring the best new tools everyday, you don't need this stack for that.
Software Product Management Stack has been upvoted on Product Hunt more than 1000 times, including Product Managers that work at these companies:
