Since I've started as chair, I've been using our open tickets as the basis for each meeting agenda. These tickets are generally reported by individual contributors, and reflect their personal interests and observations.

It occurred to me that what's missing is a more proactive and systematic approach to identifying issues. There are various ways we could do this: competitive analysis, gap analysis, user research, reviews in the press, and so on. Or we could maybe try a lighter approach to start with - maybe go over some key aspects of the product (hardware support, UX, app availability, reliability/stability, etc) and identify key issues that aren't being tracked.

Does that seem useful as a way to identify potential work tasks? The obvious challenge is that we're not always in a position to be able to address the issues we face.