Track a problem or feature

If you're a Product Manager, Researcher, UX Designer, or Engineer — There's a variety of ways to track problems or features based on what customers are saying. If you haven't already, it's useful to first understand all the sources of customer feedback. This will help you understand where feedback has come from and what you can search.

If you haven't already, create a space. Spaces allow you to build a hierarchy of feedback. That you can easily access from the sidebar. We often get asked:

Do I build my hierarchy first? or start searching and uncovering problem areas?

Either way works. Sauce is has been designed to allow for flexibility and personalisation. We understand that with other tools you may need to set up a tagging structure first and then communicate with everyone in your team — "Hey please use these tags so that we can analyse consistently" and to avoid tag duplication. But this does approach doesn't scale with growing teams, growing features, and evolving problems as your product matures.

Some tools may require you to define one-hierarchy that is defined during the setup of that tool. This is usually a set of teams, product pillars, features, reasons, or initiatives. And once that structure is set. It's usually very difficult to change. With Sauce — You don't have to worry about any of that.

Does my view impact anyone else's?

Text...

How should I structure my hierarchy?

How do I start my day with Sauce?

• Tracking a feature or problem over time

• Ad-hoc problem identification and analysis.