2 ms·
I think this question would work better if we knew anything about what the product is. For example, at my company, we talk a little about "dog-fooding", but ul
by frogulis 4y ago
I think this question would work better if we knew anything about what the product is.
For example, at my company, we talk a little about "dog-fooding", but ultimately our product is one that most people in the company don't need most of the time, so at best "dog-fooding" means "regularly pretending to be a user" rather than actual internal use.
- lakevictoria 4y agoHey, 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.
- frogulis 4y agoWell, in that case, a short tip: jot down issues on paper to reduce friction as much as possible, then revisit later to flesh out details and enter into Jira. Once an issue is identified, it doesn't matter so much when you figure out the details, so.. do it afterwards. I've done a similar activity with the team (as a team) and it really benefitted from having a range of experience levels. Fresh eyes + subject matter expertise = lots of issues identified.