This message was deleted.

#1: Self-assessments. Here are examples: https://engineeringdevops.com/documents #2: Value Stream Map for bugfix, onboarding, feature delivery within application teams (customers of the Platform) #3: Measuring: number of toolset technology-related or config-related tasks in application teams backlog (should be close to zero if Platform is well designed), time to market for business features, questions which developers raise after fulfillment of Platform Service #4: Value Proposition Canvas excercise

I have all feedback piled into a big spreadsheet.. the main benefit is searchability (ex: who did I talked to last year on teamX?, who was it that said secrets management was challenging?) and ease of entering any / all data

After some research I will give a try to https://www.productboard.com/ I asked our internal PMs (for our end-user product) and this is what they use (I have licences available, but they are pretty expensive, so it might not work for you). It has nice features (customer insights) to organize customer feedback. You have integrations to collect insights from various channels (e.g. JIRA or Slack) and organize/link these feedback to features on your roadmap. This is also a road-mapping tool. I will also use it for the road-mapping feature. The main benefit I see is that the Product/Business side of our organization is already invested and familiar with this tool. So it will help for communicating with our stakeholders (e.g. Eng. Directors and Senior Leadership) as we meet them where they are, in the same tool and format they are already using.