There comes a time that all organizations eventually experience after a Google Workspace migration, a Gemini activation, or a Chromebook deployment.
The platform is in place. Access is open. Employees are "using it." And yet, when we meet in a project committee, the question is no longer "has it been visited?".
The real question, the one that drives an adoption program, is rather:
Are employees really progressing, and what needs to be done now?
This is exactly the starting point for the GSkills statistics redesign. The most important change is not a new layout. It's a change in business logic.
When "seeing activity" is no longer enough
For a long time, statistics have been used to verify a simple signal: the application is running, pages are being viewed, things are happening.
That's useful. But it doesn't say much about the actual level. A visit doesn't mean understanding. A click doesn't mean mastery. And what costs an organization the most is not the absence of activity, it's the illusion of adoption.
The new approach starts from another very concrete need for adoption, training, HR, managers, and steering managers:
- know where users are dropping off
- identify what is mastered, and what is not
- identify teams that need specific support
- decide which content to integrate, strengthen, or rework
- estimate potential upskilling needs, including through Numericoach training when relevant
Clearly, we are moving from a "finding" approach to a "decision" approach.
A page designed to answer the questions that matter
The statistics page has been reorganized so that an administrator can immediately find their way according to their intent.
If you want to know "where we are", you naturally look at progression, completion, quiz success, and pain points.
If you want to understand "why it's progressing or why it's blocked", you look at engagement and dynamic signals.
If you want to manage "where to act", you compare units to identify adoption gaps, and prioritize.
And yes, traffic is still there. It's just no longer central. It complements, it doesn't guide.

The detail that changes everything: moving from the number to the action
What often wastes time in an adoption project is not getting a percentage. It's answering the following question:
Who is behind this number, and what do we do now?
The redesign was conceived to bridge this gap. Instead of being stuck on a global indicator, you can quickly get the useful details, and retrieve them in a file.
Result: training, HR, management or executive teams can work with concrete data, without requesting a "custom" extraction and without waiting for technical intervention.
This is where statistics become actionable.
The most visible shift: the AI assistant integrated into statistics
Three weeks ago, it didn't exist on this page.
Today, it is integrated directly into statistics, with suggested questions to get started, and above all, a simple promise: you ask a question in natural language, and you get a structured answer, often in table form, with possible export.
It's a change of stance.
Before, we explored the interface to try to find the information. Now, we ask for what we need.
Some examples of typical adoption questions:
- "Who started journey X but didn't finish it?"
- "Which units are progressing the least over the last 30 days?"
- "On which quizzes are the most failures observed?"
- "Which content is consulted but remains poorly mastered?"
And the key point is this: once you have the answer, you can extract it into a spreadsheet file to share it, work on it, or launch an action.

Comparing means deciding faster
In a large organization, adoption does not progress at the same rate everywhere. This is normal.
What makes the difference is the ability to see it quickly, and to act without getting lost in details.
Comparison between units serves exactly that purpose: to identify discrepancies, detect areas that are falling behind, identify leading teams that can become relays, and understand where to concentrate effort.
It is also an excellent tool to avoid generic action plans. Instead of “we relaunch everyone”, we choose a targeted action where the impact will be real.
Engagement is not a decoration
When driving adoption, one always ends up asking a very human question:
Why do some progress, and others fall behind?
The mechanics of progression, points, badges, and more broadly the engagement dynamic, provide a complementary reading. They help to understand if the experience encourages regularity, if motivation follows, and at what point it decreases.
This is not an aesthetic detail. It is useful information to adapt your internal animation, your communication, or the way you present the journeys.

Delegating management without opening the entire instance: the OU Administrator role
The second major new feature concerns governance.
GSkills introduces the Organizational Unit Administrator role, to allow for finer delegation in large structures.
Concretely, an OU administrator can, within their scope:
- consult all statistics related to their users, including adoption, gamification and AI usage
- access the list of users associated with their units
- consult the access rights related to the people in their units
The principle is simple: give the right levers to the right relays, without opening access to the global configuration.
Synchronized OUs, and internal GSkills OUs
The perimeter can come from:
- units synchronized from the Google Admin console
- units created directly in GSkills, if you need a “project” breakdown that doesn't perfectly match your Google structure
Free assignment by the instance administrator
An important point for the organization: the instance administrator can freely choose who becomes an OU administrator, and assign them one or more units, even if that person does not belong to these units on the Google environment side.
This opens up many use cases: adoption referents, regional managers, training team, HR, relay managers, without artificial constraints.
What you can do tomorrow with these statistics
To summarize, the redesign was designed to help you answer questions that lead to concrete actions:
- Where are the real needs for upskilling?
- Which content deserves to be reinforced or added to GSkills?
- Which teams need targeted support?
- What actions should be prioritized to advance adoption, and then measure the effect?
A simple routine works very well:
- Identify a signal (low progress, low success, disengagement).
- Locate where it happens (comparison between units).
- Get details with the AI assistant, then export.
- Launch a short, targeted, and measurable action (content, animation, support, training if necessary).
Next step
If you are an administrator, by logging into GSkills you will already be guided to these new statistics.
The OU Administrator role is already available. You can now appoint relays and assign them one or more units to manage adoption closer to the field.
Related articles

Chromebook Adoption: measuring usage with GSkills
Deploying Chromebooks is not enough. Discover how GSkills makes adoption visible and measurable: usage tracking, guided discovery of features and progressive daily support for employees.

New Google Admin Console connection in GSkills
GSkills offers a new connection to the Google Admin console for Premium and Platinum customers. The objective is to make visible, within the platform, the main usage indicators for Google Workspace, Gemini, and ChromeOS, to better manage team skill development. This first version will be progressively enhanced to further align activity within GSkills with the actual activity observed in your environment.
