Understanding findings
What a finding is, how it's scored, and how the Findings page is laid out.
A finding is a specific, evidenced problem or request pulled out of your real conversations — Synthight's main output. Every finding links back to the tickets it was drawn from, so you can always check the source.
Unlike a topic, which is a single classification per conversation, a single conversation can surface several findings at once — see Topics vs. findings for why that distinction matters.
Where to find them
Sidebar → Findings. The page opens on two tabs: Main (active findings) and Archived (findings you've archived).
The stat cards
At the top of the page, four clickable stat cards summarize your findings:
| Card | What it shows |
|---|---|
| Total Findings | How many distinct findings exist under the current filters |
| Urgent Priority | How many are marked Urgent |
| Resolution Rate | solved / (solved + not solved), excluding unclear incidents — see Key concepts |
| Pending | Finding groups awaiting review |
Clicking a card applies the matching filter and scrolls you to the table below — it doubles as both a summary and a shortcut.
Priority and category
Each finding carries a Priority (Low, Normal, High, Urgent) and a Category:
| Category | Meaning |
|---|---|
| Usability | People can't work out how to do something |
| Friction | They can, but it's unnecessarily painful |
| Issues | Something is broken |
| Operations | A process problem on your side, not the product |
| Improvement Opportunity | An unmet need or feature request |
| Positive Feedback | Praise or a compliment worth tracking |
| Uncategorized | Not yet classified |
Filter to Improvement Opportunity before a roadmap planning cycle — that's where unmet demand shows up.
Next steps
- Topics vs. findings — the full comparison
- Filtering and sorting findings
- The finding detail page
- Understanding topics
Frequently asked questions
What exactly counts as a "finding" in Synthight?
How is the Resolution Rate stat calculated?
What's the difference between the Usability and Friction categories?
Which category should I check before a roadmap planning cycle?
Can a finding exist without being tied to a conversation?
Was this article helpful?