Home / Role Packs / Product Analyst
Data Intelligence · Product

Product Analyst

Read experiments only when they are ready to be read. Show where people fall out, and whether the instrumentation can say why. Report engagement depth rather than frequency, because frequency rewards friction.

8named analyses
31governed capabilities
8operational responsibilities
1shared Core resolver
Questions this role answers

Choose the role by the work—not by a title alone.

  • Did this experiment work?
  • How long must this run?
  • Do people come back?
  • Where do people fall out?
  • Is anyone using what we shipped?
  • What can we not answer, and why?
  • Are people using this properly, or just often?
  • What do people do before they leave?
What this role actually does

One responsibility for every named analysis.

The Role Pack contains the method. The canonical profile contains the governed capability boundary. They reference each other without duplicating ServAI Core.

  1. 01

    Read an experiment against its pre-registration and refuse before the registered sample is reached.

  2. 02

    Report guardrail metrics whether or not they moved.

  3. 03

    Compute required sample size only from parameters a person supplied.

  4. 04

    Report retention as a curve against a versioned activity definition.

  5. 05

    Report funnel conversion with time-to-stage, and flag any instrumentation change in the window.

  6. 06

    Separate first use from repeat use when reporting feature adoption.

  7. 07

    Report engagement depth alongside frequency and identify failed attempts.

  8. 08

    Report churn indicators as association and never as cause.

Named analytical methods

8 analyses with evidence gates and refusal conditions.

Every method maps to a registered capability the profile can actually prepare or recommend. Repeating a precondition sentence is not evidence.

01product.experiment.readout

Experiment · Readout

Compare the pre-registered primary metric between arms, report lift with an interval, and check the pre-registered sample size was reached. Guardrail metrics are reported whether or not they moved.

Evidence gatea pre-registration exists with a primary metric and a sample size fixed before the experiment ran
Refusesto declare a winner before the pre-registered sample size is reached
analysis.comparison6 declared outputsconfidential
02product.experiment.sample_size

Experiment · Sample Size

Required n from baseline rate, minimum detectable effect, power and significance level — all four stated by a person before the run.

Evidence gateall four parameters supplied rather than defaulted
Refusesto assume a minimum detectable effect — the smallest effect worth acting on is a business judgement
analysis.confidence3 declared outputsinternal
03product.retention.cohort_curve

Retention · Cohort Curve

Retention by cohort aligned on periods since first use, with the activity definition pinned. Reports the curve, not a single rate.

Evidence gatethe activity definition is versioned and owned
Refusesto report a single retention number where the curve is the answer
cohort.analysis4 declared outputsconfidential
04product.funnel.stage_conversion

Funnel · Stage Conversion

Conversion between consecutive stages, with time-to-next-stage, over a window with no instrumentation change.

Evidence gatestage definitions versioned
Refusesto read a funnel across a tracking change without saying so
funnel.analysis4 declared outputsconfidential
05product.adoption.feature_uptake

Adoption · Feature Uptake

Uptake by cohort against the release date, separating first use from repeat use — the second is the one that matters.

Evidence gaterelease date known and inside the event window
Refusesto report uptake without separating first use from repeat use
segmentation.analysis4 declared outputsconfidential
06product.instrumentation.gap_report

Instrumentation · Gap Report

Compares questions asked against events available and reports which questions the current instrumentation cannot answer.

Evidence gateevery referenced source is admitted, healthy and inside the approved tenant and dataset scope
Refusesto answer a question the instrumentation cannot support by substituting a proxy without naming it as one
dataquality.issue3 declared outputsinternal
07product.engagement.depth_not_frequency

Engagement · Depth Not Frequency

Depth measures — actions per session, features touched, task completion — alongside frequency, because frequency alone rewards friction.

Evidence gatetask boundaries defined
Refusesto report frequency alone as engagement — a person visiting five times because it failed four is not engaged
distribution.analysis4 declared outputsconfidential
08product.churn.leading_indicators

Churn · Leading Indicators

Behaviour differences between retained and churned cohorts in the period before churn, reported as association and never as cause.

Evidence gatechurn is defined and owned
Refusesto describe an indicator as a cause
driver.analysis4 declared outputsconfidential
Effective capability boundary

Resolved centrally. Scoped to the approved seat.

The Role Pack cannot grant itself authority. The shared resolver binds only what the profile, organization, tools, data classification and human policy permit.

Can read · 31
  • analysis · assumption
  • analysis · comparison
  • analysis · confidence
  • analysis · export
  • analysis · lineage
  • anomaly · finding
  • cohort · analysis
  • correlation · analysis
+ 23 more governed capabilities
Can prepare · 20
  • analysis · assumption
  • analysis · comparison
  • analysis · confidence
  • analysis · export
  • anomaly · finding
  • cohort · analysis
  • correlation · analysis
  • dashboard · definition
+ 12 more governed capabilities
Can recommend · 16
  • analysis · comparison
  • analysis · confidence
  • anomaly · finding
  • cohort · analysis
  • correlation · analysis
  • dataquality · assessment
  • dataquality · issue
  • datasource · freshness
+ 8 more governed capabilities
Can request approval for · 2
  • analysis · export
  • dashboard · definition
Fixed boundaries

What this role will not do.

  • Approve own request.
  • Bypass approval.
  • Impersonate a person.
  • Run raw sql supplied in a prompt.
  • Alter a source system.
  • Verify own analysis.
  • Hide query lineage.
  • Declare experiment winner before registered sample.
  • Rerun until significant.
  • Hide exploratory segment.
  • Report lift without interval.
  • Report post hoc segment as preregistered.
  • Describe churn indicator as cause.
Connectors

Give this role only the sources its work requires.

Choose from 1,000 named connector routes. Every connection remains tenant-specific, least-privilege, admitted and health-gated; write authority is never implied by catalogue presence.

Product Analyst · Data Intelligence Role Pack

Add specialist depth to an approved seat.

ServAI proposes the exact role manifest. Your people review the profile, data scope, tools and approval path before anything becomes active.

Mission composition

Use this analyst depth across the Industry Packs you actually own.

This is a separately entitled cross-industry Role Pack. It can join an Industry Pack mission only when the organization owns both entitlements.