PM's are gold or garbage, there is almost no in-between. You want on boarding, monetization, metrics, goals attempted, successes and most importantly "what fai

PM's are gold or garbage, there is almost no in-between. You want on boarding, monetization, metrics, goals attempted, successes and most importantly "what failed". Let me say "metrics" again, what are they measuring, how, and what is and isn't working in NUMBERS. (If you don't have these god help you) While your looking at things from a customer perspective, you should be looking at things from a storage perspective. Where ever your data is stored, it is likely you can auto generate a schema from some sort of tool. Make these, print them out, hang them on the wall. Why dead trees? Because your going to wanna write notes on it, if you can't it's useless. Why does storage matter? Because knowing what is there, and was there and how its laid out are going to give you massive clues as to how the system evolved! Column order in a lot of DB's is a hint at what came later. Is current critical data tacked on to the end of a table? Is there something you THINK you should be there sparsely populated because it is unused today or simply not required. Wireframes are fast an easy, even if you do them one paper and scan them in later. I can't say enough how much having movable pieces for your work flow can help. Doing these as your learning and getting feedback on what's missing from that PM is going to give you massive insight and expose dark corners and missing thinking.