I’m serving as a the TL of a team that took ownership of a couple of customer facing backend services (data pipelines that power APIs). These APIs are accessed directly by our customers, and also power a UI that less tech savvy customers can use. Basically a product backend team.

Right now it’s really difficult to understand where we are at as a team and how healthy, accurate, used, etc these data pipelines are. Some scenarios to why this is a problem: – product will come to us and say “we’re getting ‘a lot’ of complaints from customers that the data they’re getting bad results” then we rerun the query and get different but better results than what the customer is reporting – some pipelines don’t have integration tests and can fail causing us to spend a ton of time fixing them but we don’t have any record of how often the failures are and how much we need to improve – some of these pipelines are less used in the API and we don’t know whether it’s because they give poor results or cuz of a bad product market fit. – only way we know what new products to work on is based on what are PMs feeeel like customers want or intuition – many more things

As a result I want to create an initiative for our team to be more data driven. Unfortunately, I have no idea what this should look like. I’m a new Tech lead and haven’t really been given a great example of what a proposal like this should look like. Looking for advice on : – how to find the best metrics to evaluate – how to present this data (alerts vs monitoring dashboard vs just making data aviliable via SQL) – how to ensure metrics can help see gaps in product market fit, and how we can build new products – any advice on how to approach this from a people perspective – any other advice

Thanks so much! Any input is helpful

submitted by /u/iphananatic31313
[link] [comments]