Working method
Our method
How Content Grovepoint reads app analytics across EdTech learning journeys — from pathway lock to readout.
This page is for teams who want to see the shape of the work before commissioning an audit or workshop. The steps below describe our standard Learning Journey Audit; shorter reviews compress the same logic.
Pathway lock
We agree one learner pathway and what “done” means for that arc. Without this lock, analytics conversations sprawl across every screen in the app.
Evidence pass
Event definitions, sample sessions, curriculum outlines, and support tickets are read together. We note where names, timing, and pedagogy disagree.
Friction ranking
We shortlist three friction points with evidence — not twenty suggestions. Ranking considers learner impact and the effort required from your team.
Shared readout
Product and curriculum attend the same half-day session. The written brief follows, with one revision window so wording matches how your organisation talks.
Materials we usually need
- Current event dictionary or tracking plan
- Access to anonymised session samples or exports
- Outline of the curriculum unit tied to the pathway
- One product owner and one curriculum owner available for working sessions
What we refuse to do
We will not inflate metrics for a pitch deck, reverse-engineer a competitor’s private data, or pretend a two-day visit replaces months of classroom research. If your need is instrumentation engineering, we will say so and step aside.
Natural next actions
