Automating product operations as shipping velocity scaled
As engineering started shipping faster and the product team stayed small, we needed more reliable ways to prioritize customer issues, make sense of scattered feedback, and keep customer-facing teams informed. I worked on automations to reduce the repetitive sorting, while leaving the important decisions with people.
The problem
Engineering velocity went up while the product team stayed small. Customer issues, support tickets, sales calls, Slack threads, usage data, and release details were all useful, but they lived in different places and required a lot of manual sorting. The risk was simple: more things were happening than the team could reliably keep in its head.
What we put in place
Three connected systems helped take repetitive sorting and synthesis off the PM team's plate, with rules and review points that others could inspect and improve.
We made customer issue prioritization more consistent by bringing relevant context into a regular review, with the team retaining responsibility for tradeoffs and decisions.
We brought feedback from different customer-facing channels into a clearer review process, reducing repeated context gathering while keeping decisions with product teammates.
We established a recurring, customer-oriented release summary to help customer-facing teams understand what changed and why it mattered.
How we kept it trustworthy
- The scoring logic lives in fixed rules. The model explains the result; it does not quietly invent the math.
- An automated reviewer checks each triage run and flags suspicious changes, including scores that move when the underlying evidence did not.
- Major changes were tested in a shadow copy before writing back to Jira, so we could compare results and catch surprises.
What changed
- Customer issue prioritization became visible and repeatable instead of depending on whoever happened to have context that day.
- Scattered customer signal started arriving with enough context attached that PMs could decide what to do with it instead of spending the first hour reconstructing the story.
- Customer-facing teams got a regular view of what shipped and why it mattered, which closed a gap between engineering velocity and field awareness.
- The systems improved over time because reviewer corrections were turned into standing rules instead of being fixed once and forgotten.