This guide explains how work moves from signals (calls, tickets, paste) to atomic evidence, recurring insights you validate, problems or bets you size together, solution ideas you explore, and initiatives when you commit on the roadmap.
That path uses workspace context (company background, product definition, goals) so priorities stay grounded. Set it up in Workspace context.
To bring evidence in (connectors, bulk imports, files, or paste—e.g. Zoom, Zendesk, and more), use Evidence → insights and the documentation hub.
Types in the product
- Signal
- Evidence
- Insight
- Opportunity
- Idea
- Initiative
The opportunity tree shows insights, ideas, and initiatives in one place under each bet.
How workspace context helps
Personas, products, OKRs, KPIs, features, and market notes live in workspace context. Agents and planning use that layer so evidence, insights, and bets stay aligned with how you describe the product and the business.
Workspace context explains flat versus named context in more detail.
Signals and evidence
When you import a call transcript, a support ticket, pasted notes, or a file, Zentrik keeps that material as a signal: one place with the source, the text, and processing status. Processing extracts one or more atomic evidence items from that Signal. Each Evidence item stays linked to its source and can support several Insights, Opportunities, Ideas, or Initiatives.
Patterns (insights)
Zentrik uses related Evidence to suggest and update Insights: reviewable patterns that explain what is recurring, which evidence types dominate, which customers are represented, and which evidence matters most. When volume grows, add taxonomy and use themes on the map (Taxonomy & themes).
Problems and bets (opportunities)
When several Evidence items and Insights point at the same customer problem, gap, or strategic bet, you group them in an opportunity. That is where teams compare notes, attach impact or value thinking, and decide what is worth turning into concrete solution work. For day-to-day habits in this stage, see Insights → opportunities.
Solution ideas
Ideas are possible answers: a customer request (“we need this integration”), a sketched approach, or a fuller concept. They link back to the Opportunities, Insights, and specific Evidence items that justify them. When the team is ready to ship, an idea can move forward into an Initiative.
The product can suggest related links or draft gaps after you save an opportunity or insight; you choose what to keep.
Open an idea to see how it links to opportunities and insights on the tree.
Committed work (initiatives)
An initiative is a project on the roadmap: specs, tasks, status, and delivery. When leadership commits, work lives here. Its links to the specific Evidence that supports its scope stay visible, even when the Initiative is based on only part of a broader Insight.
Seeing it together
The opportunity tree is the main canvas where evidence, bets, ideas, and promoted projects appear side by side. Use it when you want one view of how a theme flows from signal to roadmap.
Troubleshooting
Check these steps against what you see in your workspace. If something differs, note your workspace name and the screen, then contact us.
One card is doing too many jobs
Keep verbatim customer material on the Signal, atomic source-backed claims as Evidence, recurring patterns as Insights, shared problem framing on Opportunities, and solution shapes on Ideas. If one record mixes those roles, split it or relink so each step stays clear.
We have a solution request but no shared problem frame
Add an opportunity (or link the idea to one) so the team agrees what problem the solution is solving before you commit an initiative.
Continue from here
Related guides
Did this guide answer your question?
Your response helps us prioritize missing or unclear documentation.
Still stuck?
Send your question to Zentrik support. This guide will be included automatically.