For product teams · Planned
Which feature gets used?Event and product data: planned.
Product teams want to know which features get used, where users drop off and whether a release changed anything. That needs event and usage data. Peak Analytics is meant to evaluate it; it is planned and not built, and there is no SDK. Today the preview shows you the state of your backlog and product goals.
Put the goal into words. Add perspectives and timing right below.
Planned, not available. Event, usage and product evaluations are specified and not built; there is no tracking SDK. Examples are fictional.
Read the „export“ event from the product / Week × plan, count of teams / Feature with falling use as a task
Did the release change anything?
- Usage
- „How many teams use the new export each week?“ → Feature with falling use as a task
- Sürümler
- „Does the new onboarding change how many users create their first course?“ → Result in the shared snapshot for the product team
- Today
- „How many backlog tasks have waited weeks for approval?“ → Week with the biggest backlog as „Check“
Your question
Which product question do you want to answer with numbers first?
Answering that takes events from the product: who uses which feature when. Peak Analytics reads no events today; the source is planned. The example runs only in this browser window; the evaluation it describes is planned.
Local working example · nothing is saved or sent. Please don't enter personal data.
Three details. One clear evaluation question.
Draft · not yet put together
- Soru
- Still open
- Data basis
- Still open
- Next step
- Still open
Two fictional situations
Which product question do you want to answer with numbers first?
Two fictional product teams show the planned evaluation; the third example shows what works today.
Planwerk App (fictional)
„How many teams use the new export each week?“
- The action
- Week × plan, count of teams
- The intent
- Feature with falling use as a task
Usage
- Soru
- How many teams use the new export each week?
- Peak Analytics is meant to
- Read the „export“ event from the product
- Why
- Without a defined event, „usage“ would be an estimate; the tracking plan makes it countable.
Two fictional situations make the planned idea tangible. Below is what of it exists today.
To the source and limitIs this for you?
Measure what matters first.
Which feature gets used?
Event and product data: planned.
This is where Peak Analytics helps.
- Without a defined event, „usage“ would be an estimate; the tracking plan makes it countable.
- Before and after only compare when the same event is counted the same way.
- The preview answers this one already: tasks are a source, product events are not yet.
No real data
What doesn't exist yet.
- Planned, not available
- No SDK, no tracking
- What works today
What already exists today
The Peak Analytics preview already exists.
This page describes a planned capability. In the preview today: pivot evaluations over orders, receipts, tasks, goals and files, the largest value with its share, „Check“ as a task, CSV export and sharing a released snapshot. The planned part is meant to build on that. Tasks from Peak Work are one of the five Peak Analytics sources, and „Check“ turns a finding into a task of its own there, with a link back to the evaluation.
Look at Peak WorkPeak Analytics / Your next step
Measure what matters first.
Look at today's five data sources and what they already tell you about your backlog and product goals.
See today's data sources
Measure what matters first.
„How many backlog tasks have waited weeks for approval?“ → Week with the biggest backlog as „Check“
Frequently asked questions
Can I use this in Peak Analytics yet?
No. This capability is planned and not built yet; there is no launch date. Available today is the Peak Analytics preview: pivot evaluations over orders, receipts, tasks, goals and files with CSV export and sharing.
Is there an SDK or API?
No. Peak Analytics collects no events from apps or websites today; API and SDK are planned.
How do I prepare?
With a tracking plan: which events count, what they are called and what they mean. The guide explains the approach.
What can a product team evaluate today?
The product board's tasks by status and week and product goals by status and level.