How the Adoption Score is calculated, which everyday actions do and don’t move it, a simple weekly routine for individuals, a review sequence for managers, and a worked example moving from At Risk to Champion.
1. The Adoption Score Formula
Adoption looks at recent usage over a 30-day window and rewards regular, meaningful and relevant use of the product.Key distinction
A user can be high in Mastery but low in Adoption if they learned the product earlier and then stopped using it. A user can also be active in the product but have low Mastery if they have not yet generated enough verified mastery evidence.
2. What Actions Help — and What Do Not
3. Dos and Don’ts
4. A Five-Step Routine for Individuals
Use this routine instead of trying to increase a score directly.Start with your assigned work
Progress the work inside Julley PMS
Collaborate where the work exists
Complete genuine work
Repeat across the week and relevant product areas
5. A Manager Review Sequence
Dashboard first
People Analytics next
Position Analytics for structural issues
Leaderboard last
- Create tasks for real, trackable work and give each task a clear owner.
- Keep status current as work moves from Assigned to In Progress, Review/Approval, and Completed.
- Use realistic due dates and act on overdue work instead of letting it age silently.
- Close completed or cancelled work so the system reflects reality.
- Use comments, worklogs, attachments, dependencies, and approvals when they support the actual workflow.
- Review stale, unassigned, overloaded, and approval-heavy areas during regular team reviews.
- Rebalance work when one person or position is carrying too many active or old overdue items.
- Do not create dummy tasks or unnecessary activity to improve points or rank.
- Do not keep tasks In Progress after the work is actually complete.
- Do not use login frequency, points, rank, or completed count as the only measure of employee performance.
- Do not leave ownership unclear or keep tasks assigned to the wrong person.
- Do not ignore old overdue tasks; update, replan, reassign, complete, or cancel them.
- Do not compare teams or roles without considering the nature and volume of their work.
6. Worked Example: At Risk to Champion
The example below uses fictional data to show how regular, meaningful work can improve Adoption while verified task completions also build Mastery. Meera is a project coordinator. At the start, she has used Julley PMS only occasionally — 4 mastery points (Starter), and a low Adoption Score because she has very few active days, meaningful actions, and only one module in use.Starting Point — At Risk
Week 1 — Build a Consistent Working Habit
Meera starts checking and progressing her assigned work on several different working days instead of only when reminded, updates genuine task status and comments only when collaboration is required, uses both Tasks and Projects since both are relevant to her role, and completes 6 additional unique, valid assigned tasks.Week 2 — Reinforce the Habit and Expand Meaningful Usage
Meera continues using the platform across the working week, reaches at least 12 meaningful actions, begins using a third relevant product area as part of her normal workflow, and completes another 10 unique qualifying tasks.What made the difference? Meera did not improve by repeatedly logging in, opening pages or adding random comments. She improved Adoption by returning regularly, taking meaningful actions and using relevant modules; she improved Mastery and her Tier by completing unique qualifying work that generated verified evidence.