What do you like best?
Ease of use. You can grab a screenshot which grabs more information to share with the developer of a concern you might be seeing. The developer can see what browser, what monitor size, and see what you see since it takes a screenshot. We are able to add in as many "tickets" of what needs to be adjusted or updated. It's helpful for development to deployment for the projects that we work on. This tool impresses me for how easy it is to use.
What do you dislike?
When we were first using TrackDuck, found the way that they had the status for what was open and closed confusing. Provided the feedback directly to TrackDuck and they updated the system to accommodate what would be easier to understand for my team. So while you may not like something about TrackDuck, I'd reach out and ask them as they have been very responsive to our feedback.
Recommendations to others considering the product
If you'd like a way to communicate what changes or what you are seeing wrong - we'd highly recommend this tool as you work with your team, including your developers will love it!
What business problems are you solving with the product? What benefits have you realized?
Before TrackDuck, we used to take the feedback and place it in Word documents with screenshots, as well as spreadsheet which my team and the client's team used to convey what changes were needed. Now we result more to TrackDuck for my team, and we stick with the spreadsheet between the client and my team - so keep a running log of what we have pending. As a production manager, I'm grateful that we found a tool like this to use, as the tool is flexible with us and easy to use.