Compass and Jira and Confluence
ZeroWidth Compass or Jira and Confluence?
Confluence keeps what your company has written, and Jira runs the work. Compass maps how the business actually runs, finds what's missing and helps you decide what to change.
Claims handling procedure v3
Confluence · Claims space · Updated 2023
1. Receive the claim. 2. Verify eligibility. 3. Approve.
See the linked Jira epic for the automation work.
Owner: (left the company)
Warranty claim, intake to resolution
- Verify eligibilityWaits 2 days
- Who owns approvals now?Ask Dana
- Check eligibility automaticallyCLM-12
Each step cites the interview or document it came from
What Compass adds to an Atlassian setup.
- 1
It captures what was never written down
Compass interviews the people who do the work by link and reads the email threads you copy it on, so the map includes the exceptions a procedure page leaves out.
- 2
It models the work itself
Steps, owners, waits and hand-offs are part of the map, each with its time and cost as a range, so you can see where a process loses days.
- 3
It shows you what's out of date
Open questions stay listed until someone answers them, and steps with no owner are flagged, so a stale procedure shows up as a gap.
- 4
Changes come with a case
Each proposed change sits on the step it fixes, scored on value, feasibility and risk, with the hours it would free, before it becomes an epic.
When Compass is the right choice
- The procedure pages no longer match how the work runs.
- You want to find where time goes before you file the epics.
- Your operations teams need to say how their work runs without learning Jira.
- You want a weighed list of changes, with the tickets linked.
Job by job
Getting knowledge in
Jira and Confluence: People write pages, and Rovo searches across them.
Compass: Your team writes pages, and Compass reads documents, email threads, research reports and interviews by link, each cited.
How processes are kept
Jira and Confluence: Pages, and flowcharts Rovo can draw from a written process.
Compass: Workflows made of steps, with owners, waits and the time each takes.
Finding what's missing
Jira and Confluence: Left to whoever keeps the pages and tickets.
Compass: Unanswered questions, workflows with no owner and people nobody has talked to.
Deciding what to change
Jira and Confluence: Epics and priorities set by whoever files them.
Compass: Changes scored on value, feasibility and risk, with hours freed.
Connecting the two
Jira and Confluence: Official Rovo MCP server and REST APIs.
Compass: Each change links to its Jira issue, and Zero can read it once you connect Atlassian's MCP server.
Map it in Compass. Run it in Jira.
Most teams keep Atlassian as the system of record. Compass gives them a current picture of how the work runs and a weighed list of what to change.
- Export the procedure pages from Confluence and drop them into Compass to start the map.
- Paste a Jira issue's link on a change, and the change shows it.
- Connect Atlassian's MCP server, and Zero can read the pages and issues behind the map.
- Mark a change done when the epic ships, and record whether it happened, partly happened or didn't.
Questions
- Is this Atlassian Compass?
- No. ZeroWidth Compass maps how a business runs. Atlassian's Compass is a separate product, a catalog of software components.
- Who can see what's on the map?
- Each item can be private, shared with the workspace or restricted to named people, and the database enforces it.
Try Compass with your domain.
Start with the procedure page nobody trusts anymore.
No website? Describe what you do
If you'd like help with the first changes, talk to us.