Sample use cases

Illustrative scenarios you can reuse on your website. Tiers note where Jira or Signals matter; Tier 1 alone still delivers the forum, topic pages, and durable threads.

Tier 1+ 1. Runbook incident room

A Confluence page holds the operational runbook. During an incident, responders use the Converse Home macro on that page as the live coordination surface: timeline of replies, clear ownership in prose, and a pinned “commander’s summary” thread. After the event, the thread remains searchable next to the runbook—no lost Slack scrollback.

Outcome: post-incident review links directly to the same page the team used under pressure.

Tier 2 2. RFC & design review tied to delivery

Engineering hosts an RFC on a Confluence page with the forum macro. Discussion stays threaded and categorized. When consensus lands, a PM links the approved scope to an epic or story in Jira; issue cards in replies make status visible without opening Jira for every check-in.

Outcome: “What we decided” on Confluence stays wired to “what we shipped” in Jira.

Tier 3 3. Leadership Q&A with explicit decisions

Executives publish a quarterly strategy page with an open Q&A forum. Employees ask nested questions; leaders answer in thread. Material items are captured as signals (decision, risk, action) so follow-ups have an owner, due sense, and status—reducing vague “we’ll take that offline” outcomes.

Outcome: transparency with a lightweight record of commitments, not only narrative text.

Tier 2–3 4. Program delivery hub per initiative

A program office maintains one hub page per initiative. Workstreams post updates; cross-functional readers subscribe for notifications. With Jira enabled, each stream links its critical path issues; with Signals enabled, risks and decisions surface in roll-ups for PMO review without duplicating Jira’s full reporting stack.

Outcome: one Confluence “front door” per program with controlled depth into delivery tools.

Tier 3 5. Executive Dashboard into all the different projects.

Instead of a cluttered dashboard page, executives can build a hub page with cards for each project. With a quick glance and a click they navigate to the project main page and can see the Conversation hub, see the signals raised and their progress for completing the project.

Outcome: one Confluence "front door" for all the projects and a controlled depth into delivery tools.

Tier 1+ 6. Customer success weekly cadence

CSMs keep a hub page per portfolio segment. Each week they add a short “pulse” thread; long-form notes live on optional topic child pages for search. Imports from legacy inline comments (where supported) bootstrap history when migrating from classic Confluence discussions.

Outcome: managers scan one page for account health narrative without forcing CRM notes into Jira.

Tier 3 7. Signals at the moment of intent

A product or platform team discusses a customer pain point or defect pattern directly on the Confluence page that holds the spec or retro notes. Instead of losing the “we should track this” moment in chat, someone marks a signal (decision, action, question, or risk) on the exact topic or reply where the idea surfaced—carrying title, rationale, ownership, due sense, and status in one structured object.

When work should move into delivery, the team links or creates Jira issues from that signal so engineering lives in Jira as usual. Cross-project filters and dashboards in Jira remain the place to see all tickets and trends; Conversation hub does not try to replace that. Instead it preserves why the ticket exists and where the conversation happened, while in-product roll-ups and lists stay intentionally bounded so the hub stays fast and honest about scope.

Outcome: traceability from narrative discussion to execution tools—without duplicating Jira’s job as the system of record for issue analytics.