Étude de cas · Solutions pour vos clients
Several weeks saved on an application launch
How Okapya turns its documentation into an adoption lever — without tying up its developers.
- Client Okapya
- Auditoire End users
- Depuis 2020
- Outil Confluence
2020
Partnership start — scope extended step by step
99 h
saved on every launch
99/99
reduction in internal documentation time
« Our partnership with Lios far exceeded our expectations. Pascal and Paige did a top-notch job of adapting to the dynamic and engaging style of documentation that we were looking for. We particularly appreciated the rapport that we built; Pascal and Paige seemed more like colleagues than contractors. We kept in touch day to day on Slack, and the review process that was implemented greatly contributed to the success of the project. We were so confident in them that we expanded their scope to have them review blog posts and marketing materials. I highly recommend Lios and their experts! »
Contexte
With Checklist for Jira, Okapya built one of the most popular apps on Atlassian Marketplace. Ahead of a fully redesigned release, they wanted the documentation to keep pace: friendly online help, the right amount of detail, and use cases that showed everything the app could do.
The non-negotiable: that documentation had to be ready on the day the new version shipped.
Le défi
Okapya’s developers already had their hands full with the new version. Asking them to write the docs in parallel was not realistic.
The paradox: they knew the product too well to explain it. Stepping into a user’s shoes — what to say, and how — had become the hard part. They brought in LIOS.
Approche LIOS
LIOS starts with standards, then writes the help in Confluence with the Okapya team.
-
Step 1
Framing
To match the quality of Checklist, LIOS first looks at what already works for other Marketplace apps. Those examples become a set of best practices — structure, level of detail, types of examples — that guide the rest of the work.
-
Step 2
Production
Help pages are written directly in Confluence, the tool Okapya already uses. A tracking table shows the status of every page. Okapya answers quickly, comments as soon as a section is ready, and reviews from both a technical and a marketing angle — one message, a real back-and-forth.
-
Step 3
Follow-through
While testing procedures, the writing team — first-time users who already know the product — also flags interface issues. LIOS then puts a structure in place so the docs can evolve with Jira hosting (Cloud, Data Center, Server). Okapya can reach the team with a Slack message.
Deliverables
- Online Checklist for Jira documentation, ready on launch day
- Help pages and use cases in Confluence
- Tracking table and a single review process (technical and marketing)
- Update structure for Cloud, Data Center and Server
Impact mesuré
| Delivery | Documentation live the same day as the release |
|---|---|
| Product team | Developers stayed on the new version |
| Collaboration | Day-to-day dialogue in Confluence and Slack |
| Scope | Mandate extended to blog posts and marketing materials |
| Next | Docs that can evolve with Jira hosting |
