Story
Atlassian
Persistent SystemsPersistent Systems Brings Institutional Knowledge onto Atlassian
Persistent Systems, an information technology organization in India, uses Jira Service Management from Atlassian to support documentation for specialists and new hires.
Persistent Systems runs documentation on Atlassian so ownership is obvious when work stalls.
“Information Technology work at Persistent Systems spans more than one site, even when headquarters sits in India.”
“Specialists and new hires asked for a shared way to run documentation without freezing local judgment.”
Independent write-up. Figures come from public sources or are illustrative.
Value results
| Category | Value result |
|---|---|
| Productivity | Fewer stalled items because institutional knowledge has a clear owner |
| Productivity | Handoffs in documentation sit in a shared queue instead of a mailbox trail |
| Risk and compliance | Jira Service Management is the governed place specialists and new hires use for documentation |
Story
Information Technology work at Persistent Systems spans more than one site, even when headquarters sits in India. Institutional knowledge was splitting across regional habits. Specialists and new hires asked for a shared way to run documentation without freezing local judgment.
Atlassian (Jira Service Management) is what they standardized on. Atlassian provides work management and DevOps software, including Jira and Confluence, used by software and business teams. Persistent Systems uses it as the system of record for institutional knowledge, with specialists and new hires as the primary operators and other groups coming in through the same queue.
Leaders get a picture they can actually walk. Teams get fewer mystery statuses. The story is about operating change, not an unpublished percentage.
