There is a moment that all organizations eventually experience after a Google Workspace migration, Gemini activation, or Chromebook deployment.
The platform is in place. Access is open. Employees “go on it.” And yet, when we find ourselves in a project committee, the question is no longer “has it been visited?”
The real question, the one that advances an adoption program, is rather:
Are employees really progressing, and what should we do now?
This is exactly the starting point for the redesign of GSkills statistics. 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, the pages are consulted, things are happening.
It's useful. But it doesn't say much about the real level. A visit does not mean understanding. A click does not mean mastery. And what costs an organization the most is not the absence of activity, it is the illusion of adoption.
The new approach starts from another need, very concrete on the side of those responsible for adoption, training, HR, managers, and steering:
- know where users drop out
- identify what is mastered, and what is not
- identify teams that need specific support
- decide which content to integrate, reinforce, or rework
- estimate potential needs for skills development, including through Numericoach training when relevant
In short, we move from a “statement” reading to a “decision” reading.
A page designed to answer the questions that matter
The statistics page has been reorganized so that an administrator can immediately find their way around according to their intention.
If you want to know “where we are,” you naturally go to progress, completion, quiz success, and points of friction.
If you want to understand “why it’s moving forward or why it’s blocked,” you go to engagement and dynamics signals.
If you want to steer “where to act”, you compare the units to identify adoption gaps, and prioritize.
And yes, the traffic is still there. Simply, it is no longer at the center. It comes to complete, not to guide.
The detail that changes everything: we go down from the figure to the action
What often wastes time in an adoption project is not obtaining a percentage. It is answering the following question:
Who is behind this figure, and what do we do now?
The redesign was designed to reduce this gap. Instead of being stuck on a global indicator, you can quickly obtain the useful detail, and retrieve it in a file.
Result: the training, HR, management or management teams can work with concrete data, without requesting a “custom” extraction and without waiting for a technical intervention.
This is where statistics become actionable.
The most visible switch: the AI assistant integrated into the statistics
Three weeks ago, it didn't exist on this page.
Today, it is integrated directly into the statistics, with suggested questions to start, and above all a simple promise: you ask a question in natural language, and you get a structured answer, often in the form of a table, with possible export.
It's a change of posture.
Before, we explored the interface to try to find the information. Now, we ask for what we need.
Some examples of typical questions, on the adoption side:
- "Who started course X but didn't finish it?"
- "Which units are progressing the least in the last 30 days?"
- "On which quizzes do we see the most failures?"
- "Which contents are consulted but remain little mastered?"
And the key point is this: once the answer is obtained, you can extract it into a spreadsheet file to share, work on it, or launch an action.
Comparing is deciding faster
In a large organization, adoption does not advance everywhere at the same pace. That's normal.
What makes the difference is the ability to see it quickly, and to act without getting lost in details.
The comparison between units serves exactly that: to identify the gaps, detect the areas that are dropping off, identify the leading teams that can become relays, and understand where to concentrate the 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 you pilot adoption, you always end up asking yourself a very human question:
Why do some move forward, and others drop out?
The mechanics of progression, points, badges, and more broadly the dynamics of engagement, provide a complementary reading. They make it possible to understand whether the experience encourages regularity, whether the motivation follows, and at what point it decreases.
This is not an aesthetic detail. This is useful information to adapt your internal animation, your communication, or the way you present the courses.
Delegate piloting without opening the entire instance: the OU Administrator role
The second major novelty concerns governance.
GSkills introduces the Organizational Unit Administrator role, to allow finer delegation in large structures.
Specifically, an OU administrator can, within its scope:
- consult all statistics related to its users, including adoption, gamification and use of AI
- access the list of users associated with its units
- consult the accesses linked to the people of its units
The principle is simple: give the right levers to the right relays, without opening access to the global configuration.
Synchronized OUs, and OUs internal to GSkills
The scope may come from:
- units synchronized from the Google Admin console
- units created directly in GSkills, if you need a "project" breakdown that does not 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 skills development?
- What content deserves to be reinforced or added to GSkills?
- Which teams need targeted support?
- What actions should be prioritized to advance appropriation, and measure the effect afterwards?
A simple routine works very well:
- Identify a signal (low progress, low success, dropout).
- Locate where it's happening (comparison between units).
- Get the details thanks to 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, when you connect to 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 as closely as possible to the field.
