@Lou Bichard I share some practices+tools but really the tools are not designed for a specific PM job but also serve other purposes
1. Personas - I found these extremely important even though they sound obvious for all PE members, until they are explicitly state and described solutions never consider for whom we build
2. Problems vs Featuers - Rally (our tool for planning reIease and interactions etc); I collect different inputs, feedback, requirements and translate them into problem being solved rather the just another feature in a backlog
3. User stories - Rally; even though the platform work sounds technical, almost every time I work with PE team I am able to find a user, job and outcome he wants to behind the work
4. Discovery - all of the above are subject of discovering through interviews and research
5. Data - this is spread and built in into almost every system we use, Jira, BitBucket, Rally, K8S, GCP, custom metrics built into different tools (there's no even single report to dig into data it's very spread) + GoogleAnalytics in some UI tools, but we measure CLIs as well
6. Brainstorming - Mural especially solving the problem with different solutions and then prioritizing
7. Interviews - I use OneNote for making notes and sometimes record the meeting to get back later on (I actually never get back 🙂 )
8. Domain - OneNote in general is a great tool for organizing notes and since this domain is very wide good organization of notes is critical
9. Communication with users - MS teams looks promising although we only start with that
Not sure if that helps