lakevictoria

I’m in a similar situation (My company uses our own product internally).

The approach we take is:

- We dogfood our changes by setting up a Trello board with the tasks that need to be done and just work through it.

- Progressively rolling out changes to beta groups until we think we can go to 100%.

Not sure about the internal reporting thing though, that seems like a visibility issue into product ownership. I’m sure someone in support might have a better idea on that as they probably deal with similar problems for external feedback.

Hey, thanks for replying!

It's a web application for a fintech company. We aren't necessarily users of the application either, so we use an internal test environment where we pretend to be users. We do this because we believe that the wider team will use the product in different ways and catch things that the ones involved with the development may have not considered/missed.

The way in which we do this seems far away from optimal e.g. Context switching between different tools to raise found issues which will then be manually replicated as tasks in the hosts Jira board.